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

Tech-Archive recommends: Fix windows errors by optimizing your registry



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: Cannot connect a remote sql server
    ... Try disabling the firewall on the client. ... I would also make sure the SQL Browser service is running and that the login credentials you're using have rights to the default database. ... I've also written a long chapter on connecting that has helped a lot of people establish and maintain connections. ... I don't know if this matter but the server I'm trying to connect to is SQL Server 2000. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I moved every table I was able to move to the SQL ... closed connections - but all of these errors are in the version which used ... the SQL Server 2000 and everything worked ... communication between ODBC (OLEDB and Native Client, ...
    (microsoft.public.sqlserver.connect)
  • RE: Website Administration has errors
    ... The application is configured to use SQL Server ... permission issue when the webadmin site page try connecting to the target ... since the web admin site will use the ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • SQL Express Remote Connections
    ... TCP/IP is enabled (because i can get there from the local subnet) and if i go to the properties of the connection and go to IP Addresses they are all active but only the primary host ip is enabled. ... When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. ...
    (microsoft.public.sqlserver.setup)
  • Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... Rebuild the node in the failover cluster. ... Scenario 1" in SQL Server 2000 Books Online. ... This setup process updates to SP4 only the binaries on the new ...
    (microsoft.public.sqlserver.clustering)