Troubleshooting client connections

 

After setting up a new PPSEE server you should start PPSEE and successfully log in using the username sa and the password for sa you provided during installation.  Before clicking the continue button print the screen or write down the exact contents of all four boxes on the login screen.  When you successfully enter PPSEE this way, you will know that if the four boxes are identically entered at the client, the problem is in the connection and not the server itself.

 

If you can’t log into PPS from the server, you should check Control Panel – Administrative Tools – Services.  Find either MSSQL$PPSERVER or SQL Server (PPSERVER) in the list and make sure it shows Started in the Status column.  If not, right click it and choose Start.

 

If you then install the PPSEE client or server disk on another computer, enter the exact same information in all four blanks, and do not successfully log in, here are the usual troubleshooting steps.

 

1.       The part of the Server Name preceding the backslash is called the Machine Name.  At the client computer, left click the Start Button on the lower left hand corner of the screen (a circle without words in Vista) and choose Programs or All Programs.  Find Accessories (scroll down if necessary), then choose Command Prompt from the Accessories submenu.  Type the word PING followed by the machinename and hit enter.  If you get the message

 

Ping request could not find host hostname. Please check the name and try again.

 

then your computer does not know that machine by its name, but may know it by its IP address. 

 

 

 

2.       From the server, right click the start button and choose Explore.  Try navigating to the directories in this list until you find one that exists.

 

c:\Program Files\Microsoft SQL Server\MSSQL$PPSERVER\LOG

c:\Program Files (X86)\Microsoft SQL Server\MSSQL$PPSERVER\LOG

c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL \LOG

c:\Program Files (X86)\Microsoft SQL Server\MSSQL$PPSERVER\LOG

 

Open the ERRORLOG file, answering Notepad if asked what to open it with.  Search for the word Listen. Write down the three to five digit number at the end of the line beginning with Server is Listening and containing the word “port”.  This is the Port Number.

 

Left click the Start Button on the lower left hand corner of the screen (a circle without words in Vista) and choose Programs or All Programs.  Find Accessories (scroll down if necessary), then choose Command Prompt from the Accessories submenu.  Type the word IPCONFIG and hit enter.  Look next to IPv4 Address and write down the exact sequence of four numbers separated by periods following the Colon (:).  This is your Server IP Address.

 

Click your Start button.  If you see Control Panel, choose it.  Otherwise choose Settings, then Control Panel from the submenu that pops out.

 

If you see Windows Firewall, choose it, you may need to scroll down to find it.  If not, choose Switch to Classic View from the left side, and try again to find it, scrolling if needed.  Double-click Windows Firewall.  If running Vista, click on Allow a Program Through Windows Firewall on the left side. Now click on the Exceptions tab.  If Windows Firewall is running, you need to have two exceptions to permit other computers to use this computer’s data through SQL Server.  One has a port number of 1434 and a type of UDP.  The other has the Port Number we wrote down earlier and a type of TCP/IP.  Look through the exceptions containing SQL or PPS in the title and right click each, choosing Properties from the menu that pops up.  If you are unable to find either of the needed exceptions, use the Add Port button to create the missing exception(s).

 

3.       Right click the start button and choose Explore or Open Windows Explorer. 

 

If this directory exists:

C:\Program Files\Microsoft SQL Server\80\Tools\Binn

 

navigate to it, find SVRNETCN.EXE or SVRNETCN and double click it.  Make sure Named Pipes and TCP/IP are both in the Enabled column on the right.  If not, highlight each from the list on the left and click the enable button.

 

If you do not find that program try to find Microsoft SQL Server 2005 in Start - Programs (or All Programs).  On the Configuration Tools submenu, select SQL Server Configuration Manager.  Expand SQL Server 2005 Network Configuration.  Make sure Named Pipes and TCP/IP both have a status of Enabled.  If not, right-click each and choose Enable.

 

If not, click the Start Button on the lower left hand corner of the screen (a circle without words in Vista) and choose All Programs.  Find Microsoft SQL Server (scroll down if necessary), then choose Configuration Tools, and finally SQL Server Configuration manager.  If either Named Pipes or TCP/IP has the word disabled next to it, right click each and choose Enable.  Close the Configuration Manager using the red X button in the upper right corner of the small window in the center of the screen.

 

Check Control Panel – Administrative Tools – Services.  If you see SQL Server Browser in the list, make sure it shows Started in the Status column.  If not, right click it and choose Start.

 

Return to the client and try again to enter the exact same information in all four blanks and click continue.  If you still get a login failed message, click Ignore once or twice until it will let you change the Server name.  Remove all of the characters at the beginning before the first backslash.  Type in the exact Server IP Address we wrote down earlier to replace them.  The \PPSERVER should remain at the end.  Click the Continue button again.  If this is successful, then you will use the IP Address instead of the Server Name to log in all clients from now on.  (It may be possible to consult a network administrator to find out why the machine name does not properly resolve to that IP Address, but we now know that this will not be necessary to get PPSEE up and running).

 

If you were unable to log in PPSEE with the Machine Name or the IP Address, choose Start - Programs – Run (for XP) or Start –Run (for Vista).  Type CLICONFG.EXE and click Run.  Make sure Named Pipes and TCP/IP are both in the Enabled column on the right.  If not, highlight each from the list on the left and click the enable button.  Click the Enable Shared Memory Protocol checkbox.  Click OK

 

Return to the client and try again to enter the exact same information in all four blanks and click continue.  If you still get a login failed message, contact Habilitation Software technical support.