I'll have to test your scenario, but here are some causes and resolutions that were suggested for SL7.
Cause 1
The servername value in the domain table in the Microsoft Dynamics SL system database does not match the name of the
instance of the SQL Server that contains the Microsoft Dynamics SL databases. See Resolution 1.
Cause 2
An alias in the Client Network Utility points to an old server. Make sure that the alias in the Client Network Utility is
correct. See Resolution 2.
Cause 3
The Named Pipes protocol and the TCP/IP protocol are not enabled in the Client Network Utility. See Resolution 3.
Cause 4
Occurs when you try to log on to a new Microsoft Dynamics SL application database, and the name of the database begins
with a number. Because there is a limitation in SQL Server, the database names are required to begin by using an
alphabetical character. See Resolution 4.
Cause 5
You cannot establish a Named Pipes connection to the server because you have insufficient Windows permissions. See
Resolution 5.
Cause 6
TCP/IP is configured incorrectly. See Resolution 6.
Cause 7
The database is set to Single-User mode. See Resolution 7.
Cause 8
The Capicom.dll file on the computer where the error is being received is either corrupted or the version is incorrect. See
Resolution 8.
Cause 9
The Windows Firewall on the SQL Server is blocking the access to the SQL Server/SL databases. See Resolution 9.
Cause 10
You use the Windows Authentication security model in Microsoft Dynamics SL. However, you have not linked the user ID in
Microsoft Dynamics SL to the user ID in Windows. Additionally, you manually created the same user ID in the Microsoft
Dynamics SL system database in SQL Server. See Resolution 10.
Cause 11
The Microsoft Dynamics SL user account is a member of the ADMINISTRATORS group in Microsoft Dynamics SL. However,
the related Windows domain user account is not a member of the sysadmin role in SQL Server. See Resolution 11 and
Resolution 12.
Cause 12
The Windows Firewall in Windows Server 2008 R2 is blocking the access to the SQL Server/SL databases. See Resolution
13.
Cause 13
Occurs in the Find Database (98.000.01) screen when you click to select an application database in the Database
Name box. See Resolution 14.
Cause 14
Occurs in the Find Database (98.000.01) screen when you click OK after having selected the Server Name and
Database Name. See Resolution 15
Resolution 1
Verify the servername value in the domain table to make sure that the value matches the name of the instance of the SQL
Server where the Microsoft Dynamics SL installation is located.
1. In SQL Server Management Studio, run the following statement on the Microsoft Dynamics SL system database.
Select servername, * from domain
2. If the servername value does not match the instance name of SQL Server, run the following statement to update
the servername value:
UPDATE Domain SET ServerName = '<Nameofserver>'
--Replace the <Nameofserver> placeholder with the instance name of SQL Server.
3. Log on to Database Maintenance.
4. On the Update Databases tab, select the Microsoft Dynamics SL system database and all associated application
databases, and then click Update Views.
Resolution 2
Remove the alias that refers to the old server. To do this, follow these steps:
1. Click Start, click Run, type cliconfg, and then press ENTER.
2. On the Alias tab, verify that all aliases listed are accurate and are for current servers. If any of the aliases refer to
old servers, use the pointer to put the focus on the one that you want to remove, and then click Remove.
3. Click OK.
On a 32 bit computer:
Go to start > Run > type cliconfg
On a 64 bit computer:
1. Browse to C:\Windows\SysWOW64
2. Run cliconfg.exe located in that folder
Resolution 3
Verify Named Pipes and TCP/IP are enabled in the Client Network Utility.
1. Click Start, click Run, type cliconfg, and then press ENTER.
2. On the General tab, verify that the Named Pipes protocol and the TCP/IP protocol appear in Enabled protocols
by order. If these protocols are not enabled, use the pointer to put the focus on each one, and then click Enable.
3. If the Named Pipes protocol is not the first protocol in the list, select the Named Pipes protocol and use the arrow
keys to move it.
4. Click OK.
Note: Typically, there is no set recommendation on which protocol should load first. Depending on network
configurations, one protocol may work better than the other.
On a 32 bit computer:
1. Go to start > Run > type cliconfg
2. Make sure both Named Pipes and TCP/IP are enabled.
On a 64 bit computer:
1. Browse to C:\Windows\SysWOW64
2. Run cliconfg.exe located in that folder
3. Make sure both Named Pipes and TCP/IP are enabled.
Resolution 4
Create a backup of the existing Microsoft Dynamics SL application and system databases, and then restore the databases
to the same server by using alpha database names. For more information about how to back up and restore the
databases, click the following article number to view the article in the Microsoft Knowledge Base:
846350 (https://support.microsoft.com/kb/846350/ ) Steps to take to move the Microsoft Dynamics SL databases to
another computer that is running SQL Server 2000, SQL Server 2005, or SQL Server 2008
Note: In step 4, make sure that you restore the database to the same SQL Server.
Resolution 5
Grant user sufficient permissions in Windows.
Note: SQL Server cannot read the Registry Settings to establish a Named Pipe connection because the user has insufficient
permissions in Windows. Contact the Network System Administrator for help.
Resolution 6
Verify that TCP/IP is configured correctly.
1. If you use DHCP to assign IP addresses, make sure that the computer that generates the error is letting the DHCP
server to assign the address, instead of assigning a static IP address.
2. Verify that the workstation can ping the server by <ServerName> or <ServerIPAddress>.
3. If you use static DNS resolution, add the server that is running SQL Server to the DNS Server Search Order list
that is found in Network - TCP/IP Properties - DNS Configuration, or to the Host file on the workstation computer.
Contact the Network System Administrator for help.
Resolution 7
Clear Single User Access in Database Properties.
1. Open SQL Server Management Studio.
2. Expand Databases.
3. Right-click the Microsoft Dynamics SL application database, click Properties.
4. On the Options page, and verify that Single User is not selected as the Restrict Access value.
Resolution 8
Verify the version of the Capicom.dll file and manually register the file.
1. Locate the Capicom.dll file in the following paths:
32-bit Operating System:<SystemDrive> :\Windows\System32
64-bit Operating System:<SystemDrive> :\Windows\SysWOW64
Note<SystemDrive> represents the drive on which Microsoft Windows is installed.
2. Verify that the version of the Capicom.dll file is 2.1.0.1. (For SL2011FP1 it is 2.1.0.2)
To do this, follow these steps:
• Right-click the Capicom.dll file, and then click Properties. The capicom.dll Properties dialog box appears.
• On the Version tab, verify that the File version value is 2.1.0.1.
• Click OK.
3. Right-click the Capicom.dll file, and then click Open With.
4. In the Windows dialog box, click Select the program from a list, and then click OK.
5. In the Open With dialog box, click Browse.
6. Locate and then open the following folder:
32-bit Operating System:<SystemDrive> :\Windows\System32
64-bit Operating System:<SystemDrive> :\Windows\SysWOW64
7. Double-click the Regsvr32.exe file, and then click OK.
8. Click OK when you receive the following message:
RegSvr32 - DllRegisterServer in SystemDrive :\windows\system32\capicom.dll succeeded.
Resolution 9
Open port 1433 on the SQL Server. To do this, follow these steps:
1. In Control Panel, click Windows Firewall.
2. On the Exceptions tab, click Add Port.
3. Specify the following settings:
Name: 1433
Port number: 1433
Select TCP.
4. Click OK two times.
Resolution 10
Delete the user ID that you created in SQL, and then link the Microsoft Dynamics SL user ID to the Windows user ID. To
do this, follow these steps:
1. Delete the user ID that you created in SQL:
• In SQL Server Management Studio, expand Databases, expand the Microsoft Dynamics SL system
database, expand Security, and then expand Users.
• Right-click the user ID that you created, and then click Delete.
• In the Delete Object dialog box, click OK.
2. Link the Microsoft Dynamics SL user ID to the Windows user ID:
• Log on to Microsoft Dynamics SL by using the SYSADMIN user ID.
• In the navigation pane, click Administration.
• In the Administration details pane, under Security, click User Maintenance.
• In the User ID box, type the user ID that cannot log on to Microsoft Dynamics SL.
• On the Details tab, in the Windows User Name box, type <DomainName>\<UserName>.
Note Replace the <DomainName> placeholder with the Windows domain name and replace the
<UserName> placeholder with the Windows user ID.
• Click Save, and then close the User Maintenance (95.260.00) screen.
Resolution 11
Synchronize the ownership and security on the Microsoft Dynamics SL databases. To do this, follow these steps:
1. Open the Database Maintenance (98.290.00) screen.
2. In the Destination SQL Server Name box, type the name of the server.
3. In the Login ID box, type sa.
4. In the Password box, type the password for the SYSADMIN user.
5. Click Connect.
6. On the Update Database tab, iIn the System Database Name box, click the system database.
7. In the Databases column, select your application database.
8. In the Update Scenarios area, select Synchronize All Ownership & Security.
9. Click Update Database.
10. Close the Database Maintenance (98.290.00) screen.
Resolution 12
Remove and re-add all users to the ADMINISTRATORS group in Microsoft Dynamics SL. To do this, follow these steps:
Note This resolution assumes that one or more Microsoft Dynamics SL user accounts with administrative
permissions can log on to Microsoft Dynamics SL, so is probably not applicable...
1. Log on to the domain by using a Windows domain user account that is linked to a Microsoft Dynamics SL user
account that has administrative permissions.
2. Click Administration.
3. In the System Manager pane, click Group Maintenance under Security.
4. In the Group ID box, type ADMINISTRATORS, and then press TAB.
5. Note the user IDs listed in the Detail area.
6. Delete all users from the list except for the user ID you are currently logged on as.
7. Click Save.
8. Add the user IDs, and then click Save.
9. Close the Group Maintenance (95.280.00) screen.
Resolution 13
Open port numbers 1433 and 1434. To do this, follow these steps:
1. On the computer that is running SQL Server, click Start, point to Administrative Tools, and then click Windows
Firewall with Advanced Security.
2. Right-click Inbound Rules, click New Rule, and then click Next.
3. Click All programs, and then click Next.
4. Click Next, click to clear the Public check box, and then click Next.
5. Type SQL SERVER in the Name box, and then click Finish.
6. In the Inbound Rules pane, right-click SQL SERVER, and then click Properties.
7. On the Protocols and Ports tab, click TCP in the Protocol type box.
8. In the Local Port box, click Specific Ports, and then type 1433.
9. Click Apply, and then click OK.
10. Right-click Inbound Rules, click New Rule, and then click Next
11. Click All programs , and then click Next.
12. Click Next, click to clear the Public check box, and then click Next.
13. Type SQL SERVER BROWSER in the Name box, and then click Finish.
14. In the Inbound Rules pane, right-click SQL SERVER BROWSER, and then click Properties.
15. On the Protocols and Ports tab, click UDP in the Protocol type box.
16. In the Local Port box, click Specific Ports, and then type 1434.
17. Click Apply, and then click OK to close the SQL SERVER BROWSER Properties dialog box.
Resolution 14
Click to select the appropiate system database name in the Database Name box, and then click OK.
Resolution 15
Add an Alias back to the SQL server in the SQL Server Client Network Utility:
On a 32 bit machine:
1. Go to start > Run > type cliconfg
2. Make sure both Named Pipes and TCP/IP are enabled.
3. On the Alias tab click Add
4. For Server Alias type your servername exactly as you are typing it in the Find Databases screen
5. Leave everything else default. (should default as a named pipes alias)
6. Click OK.
7. Click Apply.
8. Click OK.
On a 64 bit machine:
1. Navigate to C:\Windows\SysWOW64
2. Run cliconfg.exe located in that folder
3. Make sure both Named Pipes and TCP/IP are enabled.
4 On the Alias tab click Add
5 For Server Alias type your servername exactly as you are typing it in the Find Databases screen
6 Leave everything else default. (should default as a named pipes alias)
7 Click OK.
8. Click Apply.
9 Click OK.
To exclude network issues, create a test ODBC connection on the computer where you receive the error message. To do
this, follow these steps:
1. In Control Panel, click Administrative Tools, and then click Data Sources (ODBC).
2. On the User DSN tab, click Add, scroll to the end of the list, click SQL Server, and then click Finish.
3. Specify the following settings:
Name: TEST
Description: TEST
Server: Type the SQL Server to which you want to connect.
4. Click Next.
5. Select windows authentication or SQL authentication, and type the sa username and password if you have to.
6. Click Next two times, click Finish, and then click Test Data Source.
HTH!
