MSDE Installation, Network and Connection problems

MSDE Installation, Network and Connection problems

All Orders 4.X

Installation Problems

Connection and Network Problems

MSDE Install error: The wizard was interrupted before MSDE could be successfully installed.

Check to see if the Windows service Server and Computer Browser are running.  If it isn't, you need to start it.

To check, right click on My Computer, select Manage, click Services and Applications, then click Services.  Scroll down until you see the service Server and Computer Browser.  To start it, right click and select Start.

If you don't see Server and Browser  in your list of services, then you need to enable on File and Print sharing:

  • Open up Control Panel, select Network Connections, Local Area Connection and right click for Properties

  • In the window that is labeled “This connection uses the following items:” you won't see File and Printer Sharing for Microsoft Networks.

  • Click Install, then Service, then Add, then click on this service.

  • It should now be listed as one of the connection items. Click OK.


MSDE Install error: You are running with Microsoft Terminal Server (or Citrix) and the installation starts, runs for a while, and then uninstalls itself.

This error is due to installing MSDE under Microsoft Terminal Server, and there is a conflict in environmental variables for TEMP.  See Microsoft aritcle: 830629.  You can verify this problem by installing the Microsoft MSDE, and specify the /*Lv switch on  the MSDE setup command line.

To work around this problem and complete the MSDE 2000 installation, use one of the following workarounds:

  • Run the MSDE 2000 Setup program from a Terminal server and not from a Terminal Services client session.

  • On the remote server, change from Application Server mode to Remote Administration mode.

  • Make sure that the Local Temp/TMP environment variables and the system environment variables point to the same location.

The following tended to work for other sites:

  • Reboot; then install right from console.

  • Verify the temp variables as stated above

  • Try to temporarily disable Terminal Services (if possible), reboot (without terminal services starting), install MSDE, and the re-enable Terminal Services, and reboot again.


MSDE Install error: The wizard was interrupted before MSDE could be successfully installed.

This error can be due to a prior bad installation of MSDE.

Try to uninstall MSDE.  If you cannot uninstall MSDE, you can try (albeit dangerous) to modify the registry.  You can rename the following keys (the keyname has a "0" in front - allowing you to rename it back if you mess things up).  The keys are in HKEY_LOCAL_MACHINE:



SOFTWARE\Microsoft\Microsoft SQL Server

SOFTWARE\Microsoft\0Microsoft SQL Server



Once you have renamed the keys, try to re-install either MSDE_SETUP or run Microsoft MSDE setup program (described elsewhere).


MSDE Install error: Setup failed to configure the server. Refer to the server error logs and setup error logs for more information.

If you server name has a lowercase letters (such as "MyComputer" or "mycomputer"), MSDE setup may fail with the error "".  See Microsoft article: Installation fails when windows computer name is mixed or lowercase.  Change your server name to all uppercase.

This issue may also occur due to missing entries in the computers registry, generally related to installing SQL Server on machines running Windows XP Home/MediaCenter operating systems.

Please do the following:

1.    Open Windows Registry (go to the start menu and click Run. Type regedit into the box and click OK).

2.    Expand the following entried: HKEY_LOCAL_MACHINE -> SOFTWARE -> ODBC -> ODBCINST.INI -> SQLServer. If any of these keys are missing add them to the registry by right clicking on the parent you wish to add the key to and clicking New Key.

3.    Once you are in the HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\SQL Server key, check for the following values.

                              Driver value=<Path to SQLSRV32.dll>

                              Setup value =<Path to SQLSRV32.dll>

      Note - The Path to SQLSRV32.dll should be C:\Windows\System\SQLSRV32.dll

4.   If either of the values are missing or incorrect add/modify them. A value can be edited by double clicking on it and a new one can be added by right clicking an empty space on the right window pane and clicking New -> String Value.

5.   After fixing these values try to install the All Orders 4 Server Setup again. If the same error occurs download this registry file. Just unzip and double click the registry file to import it directly into your regsitry.


MSDE Install error: Setup failed to configure the server. Refer to the server error logs and setup error logs for more information.

If the Microsoft SQL Server directory exists and is not empty, you may get the error  "Setup failed to configure the server. Refer to the server error logs and setup error logs for more information".   Delete the following directory (and all subdirectories within it):

C:\Program Files\Microsoft SQL Server


The setup hangs after ten minutes, but hasn't completed.

You may have to stop all of the following services (as described in the following Microsoft article: 183692 - SQL Server Setup appears to stop responding):

  • All Microsoft Internet Information Server (IIS) services. This includes all of the following:

    • Certificate Authority

    • Content Index

    • FTP Publishing Service

    • Gopher

    • IIS Admin Service

    • World Wide Web (WWW) Publishing

    • Microsoft NNTP Service

    • Microsoft SMTP Service

    • Microsoft Message Queue Service (MMSQ)

    • MSDTC

  • Microsoft Exchange Server

  • DBWeb

  • ARCserve backup

  • InocuLAN virus protection

  • McAfee antivirus services

  • UniCenter system monitoring

Once you have stopped all of those services, the MSDE installation should proceed.  If you cancelled the installation , try to install MSDE again.  


Windows XP - MSDE Install hangs at the message: Please wait while Windows configures Microsoft SQL Server Desktop Engine.  Time remaining: 6 seconds

If you use fast user switching to log on with administrative privileges, the installation of SQL Server 2000 Desktop Engine (MSDE 2.0) will fail with the above error.  

When you press Cancel, Setup does NOT cancel and the folder created is NOT deleted.  To workaround this behavior, do a normal log on with an account that is a member of the local Administrators group and re-install MSDE.


MSDE Install failure when SQL Client Tools (but not SQL Server or MSDE) were installed on the server.

You will need to de-install SQL Client Tools, then install MSDE, then re-install SQL Client Tools.


MSDE appears to install but doesn't show up in the list of installed applications (in the Add/Remove programs), when running under Terminal Server.

Install MSDE only when logged in on the terminal server and not from a client.


Connection and Network Problems

Cannot Connect to Server - Unknown error or long pause of inactivity

Upon trying to Open a NC Version 4 Company, an error occurs saying 'cannot connect to server or there is a long pause of inactivity or an unknown error happens

This happens because SQL SERVER Network Protocols are not enabled

1. Navigate to sub-folder C:\Program Files\Microsoft SQLServer\80\Tools\Binn

2. Double click SVRNETCN.exe.

You will see a screen thatlooks like this:

SQL Server Network Utility

3. Make sure that in addition to Named Pipes, all protocols are Enabled, select them all on the left and click "Enable".


IF UPON CLICKING ON SVRNETCN.EXE YOU ENCOUNTER A 126 - MODULE NOT FOUND ERROR, even when the file is visible in the directory, do as follows:


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\80\Tools\ClientSetup

SQLPath=C:\\Program Files\\Microsoft SQL Server\\80\\Tool BY CHANGING 'Tool' TO 'tools'




This machine does not have the SQL engine...

You are installing on a Workstation and not on the Sever

1. Make sure that you are pointing to the machine that has the SQL Engine,YOUR SERVER, thru File -> Maint -> Advanced -> "change server settings"

2. Make sure that on your SERVER, NC Version 4 has been installed.

3. Make sure that on your SERVER, The SQL SERVER NETWORK PROTOCOLS have been enabled as described on FAQ# 158


Access denied

This error may occur when attempting to create an All Orders company file from a client machine.

Your network user settings do not allow the user to create a company file.

Create the All Orders company file from the data server.   You can install QuickBooks on the server then uninstall it after the All Orders data file has been created.


Device Activation error. The physical filename may be incorrect.

When attempting to re-attach an file onto a different server you may get the following error:

Device Activation error. The physical filename
"c:\xxxx.MDF" may be incorrect.

Issue is related to the permission level of the folder.


  1. Create a new folder

  2. Move the mdf file to the new folder

  3. Attempt to re-attach the file.


SQL Server does not exist or access denied or [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

This error may be generated when attempting to create a new company or open a company previously created on a different machine.

The workstation generating this error is unable to talk to the database server across the network. You may still be able to access files and other resources on the server as this is not related to the configuration of the database server. Due to this being a network issue there are many different network configuration that may cause this issue to appear. Below is a list of some the the possible causes and resolutions that have worked on different networks.

Cause # 1 - MDAC (Microsoft Data Access Components) is in need of repair on the workstation (If only select workstations do not work this may be the issue).

Resolution - To confirm that this is the issue go to and download the MDAC Component Checker. After running the component checker see if any of the files are mismatched. If there are mismatches download the latest version of MDAC from the above link and install. If you are running Windows XP SP 2 you will not be allowed to reinstall MDAC and will have to follow this guide. Once MDAC is reinstalled verify that the mismatched files have been fixed.

Cause # 2 - You are on a domain and SQL Server is attempting to use protocols that are not configured on the network (If none of the workstations work this may be the issue).

Resolution - Under the Microsoft SQL Server Program Files folder on the server you will find the 80->Tools->Binn folder (default path is C:\Program Files\Microsoft SQL Server\80\Tools\Binn). In the Binn folder is the SVRNETCN.exe utitlity with which protocols may be enable/disabled. Disable all protocols besides Named Pipes and then click OK. Open the SQL Server Service Manager that is located by the clock in the system tray. Select the server with the same name as the server name with an \ALLORDERS at the end of the name and then stop and start the server.

Cause # 3 - You are on a workgroup and network configurations prevent other workstations from seeing SQL Server on the server.

Resolution - Make sure that all users that will be accessing the SQL Server have the same local user created on the machine that will be hosting the SQL Server and they they have the proper permissions to be able to access the SQL Server across the network.

Cause # 3 - You are on a workgroup and firewalls are up that may be blocking the port the SQL Server is using.

Resolution - Under the Microsoft SQL Server Program Files folder on the server you will find the 80->Tools->Binn folder (default path is C:\Program Files\Microsoft SQL Server\80\Tools\Binn). In the Binn folder is the SVRNETCN.exe. Open the utility and make sure that TCP/IP is enable. Select TCP/IP and click the properties button. Make a note of the port that is currently being used (the default is 1433).

In your firewall make an exception and open that port for communications. For example, in Windows Firewall make sure that Don't Allow Exceptions is not checked. Then under the exceptions tab click Add Port. Name the new port SQLPort and enter the port number that SQL is using and leave TCP checked. On most machines the client should now be able to connect to SQL Server.

To test this out on the client machine go to Control Panel -> Administrative Tools -> Data Sources (ODBC) . Under the User DSN tab click Add and then in the new dialog box that appears select SQL Server and click Finish. This will bring up the Create New Data Source... dialog. Enter any relevant name into the Name box. Description can be left blank. In the server box enter the server name and then \ALLORDERS. So if my server is named MyServer I would enter MYSERVER\ALLORDERS (If the drop down already contains the name of the server then you should already be able to connect without a problem). Click next and check the box to use SQL Server authentication. Check the "Connect to SQL Server to obtain default settings for the additional configuration options and enter the username sa and the password sysadmin. Click Next until you get to Finish and then click Finish. Click Test Data Source to make sure you were able to connect.

If you were not able to connect it may be due to the client not automatically accessing the proper port so we must direct it manually. Follow the steps to create an ODBC connection again but this time at the screen where you enter the username/password click on Client Configuration. The Server Alias and Server Name should both be the name of the server and the dynamically determine port checkbox should be unchecked so that port that has been opened can be entered. Finish creating and testing the connection.

If none of these solution work please refer to Microsoft's article on this error message.



Call Cruncher
More questions?

Call to speak with a NumberCruncher Solutions Consultant at:

call us