Re: Problem upgrading Microsoft Office Accounting Professional from 2008 to 2009 using SQL Express 2008

Thanks for the suggestions. I just temporarily disabled my firewall completely and I still get the same error message.

As far as I know, I'm not doing anything to cause the connection to use named pipes. The connect is handled by the software when I "Open up a Company." The file that is attached to the "Open a Company" command is a text document that appears to just contain the connection string for the selected company. Is there a way I could manually edit this to force a connection using TCP/IP?

"Rick Byham, (MSFT)" <rickbyh@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:60390734-8727-4B4F-9E71-79C684533A4C@xxxxxxxxxxxxxxxx
I don't know anything about MOA. However, if you can connect to your SQL Server Express Edition locally, but cannot connect remotely, and if the SQL Server Express Edition is listening on Named Pipes, then I suspect a firewall issue on the computer that is running SQL Server Express Edition. In particular, make sure that UDP port 1434 is open so that the SQL Server Browser Service on the SQL Server Express computer can provide the named pipe name to the client component.
Is there any particular reason you are connecting by using named pipes? Perhaps you should try TCP/IP?
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Gerald Barber" <gerald_barber_100@xxxxxxx> wrote in message news:90F7AE41-E094-424E-A534-C9ABF43A41DF@xxxxxxxxxxxxxxxx
I tried posting this in the Microsoft Small Business Accounting Forum and have written to John Thuneby directly and have not received a response. Since the problem appears to involve some sort of interaction between Microsoft Office Accounting Professional(MOA) and SQL Express 2008 hopefully someone in this forum will understand the error message I'm receiving and can suggest some possible solutions for me to try.

I'm trying to upgrade my MOA installation from the 2008 to the 2009 release. The accounting data itself is contained in a SQL Express 2008 database. While this is not the standard configuration for MOA 2009 (the standard configuration uses the 2005 version of SQL Express), using the 2008 version of SQL Express should be a viable configuration. Specifically, John Thuneby at Microsoft has written "Whilst we didn't have time to switch SQL Express 2005 out with SQL Express 2008 when it finally became ready (we shipped Office Accounting 2009 months ago), we do support the newer and faster SQL in Office Accounting Professional. You can basically
install SQL Server 2008 first, and then choose to install the client only of Office Accounting and point to SQL 2008."

However, when I try this I receive the following error message: "A network-related or instance-specific error occurred while
establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error 30 - Could not open a connection to SQL Server)"

I verified that the server is configured to allow remote connections and the 2008 version of the MOA software, which is still installed on my computer, has no problem connecting to it.

Does anyone have any idea what I should do or try next? Thanks.

Jerry

.

Relevant Pages

  • Re: SQL Resets
    ... If it were SQL that was falling short, ... The default backlog for SQL Server is 5. ... System.InvalidOperationException: Internal connection fatal error. ... From time to time, under heavy loads, we are getting resets at ...
    (microsoft.public.sqlserver.connect)
  • Re: provider: Named Pipes Provider, error: 40 - Could not open a c
    ... I have tried connecting to Sql Management Studio and it worked pretty much ... An error has occurred while establishing a connection to the server. ... under the default settings SQL Server does not allow remote connections. ... I have a sql server install / database on the web server. ...
    (microsoft.public.sqlserver.connect)
  • RE: Logging in in background
    ... wold take all kinds of modifictions as I'd need to be checking that each SQL ... my database and all have connection strings associated with them. ... I suspect that there is also an issue on the SQL Server side as I keep ...
    (microsoft.public.access.modulesdaovba)
  • Re: SQL Adaptor - Timeout
    ... Anyway there is not many methods to throttling: ... SQL send port trying to repeat the SP several times then suspend the ... Server stored procedures using SQL Server Adaptor. ... The adapter "SQL" raised an error message. ...
    (microsoft.public.biztalk.general)
  • .Net framework error
    ... Unfortunately the information is very limited and usually the report just ... The application is a front end for a SQL Server 2005 Express database, ... connection string in the app config file. ...
    (microsoft.public.dotnet.languages.vb)
Loading