PDXpert PLM Software Installation Guide

Microsoft SQL Server diagnostics

If there's a problem communicating with Microsoft SQL Server, there will usually be error indicators on the PDXpert Application Server console's Information tab.

These instructions have been generalized to address all versions of Microsoft SQL Server (2005, 2008 and 2008R2; 32bit and 64bit; Express and other editions). If you encounter any discrepancy, refer to Microsoft's documentation for your specific configuration.

Is the TCP/IP protocol enabled?

The TCP/IP protocol is typically not enabled by Microsoft SQL installers, although the PDXpert Application Server installer will enable it for you. If you've installed your own copy of SQL Server, then this may be a source of client connection errors.

To enable the TCP/IP protocol:

1. From the Start menu, choose All Programs, point to Microsoft SQL Server, point to Configuration Tools, and then click SQL Server Configuration Manager.

   If you don't see this menu option, you can open the Configuration Manager by right-clicking My Computer (XP) or Computer (Windows 7) in the Start menu and choosing Manage. In the Computer Management window, expand Services and Applications, expand SQL Server Configuration Manager.

2. Expand SQL Server Network Configuration and then select Protocols for PDXPERT

3. In the list of protocols displayed in the central panel, the TCP/IP protocol should be enabled. If you see that the TCP/IP protocol is disabled: click the TCP/IP protocol to select it, and then select Enable from the Action menu or context menu. The status column and icon for the protocol will change to show that the protocol is now enabled. Close the SQL Server Configuration Manager window.

   .

4. Your change will become effective after you (a) restart the "SQL Server (PDXPERT)" service in the Control Panel > Administrative Tools > Services console, or (b) reboot your computer.

Is the firewall allowing communications?

For the Windows firewall, verify that the Windows firewall has an exception. (Refer to the supplier's instructions for all other firewalls.)

To enable the firewall exception in Windows 7:

1. Click Start, and then click Control Panel.

   1. In Category view, open System and Security; on the right panel, click Windows Firewall.

   2. In Icon view, open Windows Firewall.

2. On the left side of the Windows Firewall, click on the Allow a program or feature through Windows Firewall link.

3. In the Allowed programs and features: list, you will probably see that "MS SQL Server" is listed, but it may not be selected. If necessary, mark the check box.

   Alternatively, if "MS SQL Server" is not listed, do the following:

   1. Click the Allow another program button.

   2. Click the Browse... button.

   3. Navigate to (for example):

      drive:\Program Files\Microsoft SQL Server\MSSQL10.PDXPERT\MSSQL\Binn\

   4. Select the file sqlservr.exe and click the Open button to add to the list of exceptions.

To enable the firewall exception in Windows XP or Vista:

1. Click Start, click Control Panel, and then open Security Center.

2. Near the bottom of the window (XP) or along the left side (Vista), click Windows Firewall. In Vista, then click on the Allow a program through Windows Firewall link.

3. On the Exceptions tab, in the Programs and Services list, you will probably see that "MS SQL Server" is listed, but it may not be selected as an exception. Mark the check box to enable the 1433 port for TCP requests.

   Alternatively, if "MS SQL Server" is not listed, do the following:

   1. Click Add Program.

   2. Click Browse.

   3. Navigate to (n is a numbered folder, usually 1, with today's date):

      drive:\Program Files\Microsoft SQL Server\MSSQL.n\MSSQL\BINN

   4. Select the file sqlservr.exe and click the Open button to add to the list of exceptions.

Is your anti-virus software allowing communications?

To determine if your AV software is blocking SQL/PDXpert communications, disable it entirely. Test whether the system is now working and, if so, determine from your AV supplier how to enable communications between SQL Server, and the PDXpert server and client applications.

Is the SQL Server database on a compressed volume?

Microsoft SQL Server does not support databases on a compressed volume. Use an uncompressed volume instead. See http://support.microsoft.com/kb/231347/en-us

If you see any of the following errors, you may have installed a new database, or moved or restored an existing database, onto a compressed disk volume:

• CREATE DATABASE failed. Some file names listed could not be created. Check related errors. (Microsoft SQL Server, Error: 5118)
• The file "[path]\PDXpertDB.mdf" is compressed but does not reside in a read-only database or filegroup. The file must be decompressed.
• Create failed for Database 'PDXpertDB'. (Microsoft.SqlServer.Smo) An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
• Restore failed for Server '<servername>'. (Microsoft.SqlServer.Smo) System.Data.SqlClient.SqlError: The file "[path]\PDXpertDB.mdf" is compressed but does not reside in a read-only database or filegroup. The file must be decompressed. (Microsoft.SqlServer.Smo)
• Database 'PDXpertDB' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details. (Microsoft SQL Server, Error: 945)

If your Windows Explorer shows folder or files names in blue rather than black, then these are compressed.

If you've attempted to install into a compressed location: Uninstall the PDXpert server and SQL Server, uncompress the installation location, and then run the PDXpert installer. When uncompressing the installation location, ensure that all subfolders and files are uncompressed.

Is the SQL Server Browser service exposed?

The SQL Server Browser service lets users connect to instances of the SQL Server database engine that are not listening on port 1433 (which may occur, for example, if another named SQL Server instance has been previously installed). Depending on your Windows configuration, you may need to open UDP port 1434 to expose the SQL Server Browser service.

Using the same general approach as described immediately above:

1. Click Start, click Control Panel, and then open Security Center.

2. Near the bottom of the window (XP) or along the left side (Win7/Vista), click Windows Firewall. In Windows 7, click on the Advanced Settings link. In Vista, then click on the Allow a program through Windows Firewall link.

3. For Windows 7. In the Windows Firewall with Advanced Security window

   1. In the left panel, click on Inbound Rules, and on the right Actions panel, click on the New Rule...

   2. Select Port as the Rule Type. Click Next.

   3. Apply the rule to UDP and specify the local port as 1434. Click Next.

   4. Set the action to Allow the connection. Click Next.

   5. Enable the appropriate profiles. Click Next.

   6. Type SQL Server Browser in the Name text box, and click Finish.

   7. Repeat these steps for the left panel Outbound Rules.

   For Windows XP and Vista. On the Exceptions tab, in the Programs and Services list:

   1. You may see that SQL Server Browser is already listed, but it may not be selected as an exception. Mark the check box to enable the 1434 port for UDP requests.

   2. More likely you will not see any reference to SQL Server Browser. In this case, click Add Port, type SQL Server Browser in the Name text box, type 1434 in the Port Number text box, select UDP, and then click OK.

Is "SQL Server (PDXPERT)" missing from the Services panel?

If "SQL Server (PDXPERT)" is not listed in the Services panel, or you suspect that the installation is not correct, you should reinstall Microsoft SQL Server.

1. Try to remove Microsoft SQL Server by opening to Windows Start menu, selecting the Control Panel, then Add or Remove Programs. If the list shows "Microsoft SQL Server" then click on the Remove button. When you're asked for an instance, select "PDXPERT: Database Engine". Follow any other instructions on the uninstaller program.
2. Run the PDXpertServer.exe installer again, and reboot the computer. Open the PDXpert Application Server console, and check that you can now start the service.

If the PDXpert Application Server service still cannot be started because there are errors in communication with Microsoft SQL Server, send to us the available Microsoft SQL Server log file(s).