prim29631:Bad public user Name or password. SQL Server Error: [DBNETLIB][ConnectionOpen(Connect()).]SQL Server does not exist or access denied.;

Image may be NSFW.
Clik here to view.

NOTE: The default configuration entries for a standalone installation are localhost\primavera for the server host name and PMDB$primavera for the database name.

FIX 1:
Click back to the Database Configuration and correct the database name.

Image may be NSFW.
Clik here to view.

CAUSE 2:
Connecting to an existing MSDE instance and there were no network protocols enabled for the MDSE instance.

FIX 2:  
Enable the TCP/IP and Named Pipes in SQL Server Network Utility:

1. Click Start, and then click Run.


2. In the Run dialog box, type Svrnetcn in the Open box, and then click OK. 
   
   Image may be NSFW.
   Clik here to view.
   
    Note:  By default, the Svrnetcn.exe file is available in the following folder: 
    Installation Drive/Program Files/Microsoft SQL Server/80/Tools/BINN
    


3. Click OK.


4. In the Server Network Utility dialog box, click the General tab.
   
   Image may be NSFW.
   Clik here to view.
   
    


5. Select your instance of Microsoft SQL Server 2000 Desktop Engine (Windows) or select your instance of MSDE 2000 SP3a or SQL Server 2000 from the Instance(s) on this server list.


6. In the Disabled Protocols list box, select TCP/IP, and then click Enable.


7. Again in the Disabled Protocols list box, select Named Pipes, and then click Enable. 
   
   Image may be NSFW.
   Clik here to view.
    


8. In the Enabled Protocols list box, select TCP/IP, and then click Properties.
   
   Image may be NSFW.
   Clik here to view.
   
    


9. In the <Server Name> – TCP/IP dialog box, type 1433 in the Default Port box (or any unused port) , and then click OK.


10. In the Server Network Utility dialog box, click OK.
    Note:   You may receive a message that states that the changes made will be saved but the changes will take effect only after you restart the SQL Server service. 


11. In the Server Network Utility message box, click OK.


12. Restart the windows service of MSDE or SQL Server 2000 via Control Panels > Administration Tools > Services    (MSSQL$PRIMAVERA) 

FIX 3:
Disable the firewall setting on the XP machine (ensure the machine has other anti-virus/firewall software) which has the MSDE database installed. You will then find the connection will be successful.

FIX 4:
Replace ‘localhost’ with the actual machine name in the db alias connection information

FIX 5:
Enter the server name correctly.  (Example: “localhost\primavera”)

1. GoTo Start, Run and type “cmd” and hit <Enter>


2. At the command prompt, type: “osql -U sa -P prima -S localhost\primavera” and hit <Enter>


3. At the 1> prompt, type: “select name from sysdatabases” and hit <Enter>


4. At the 2> prompt, type: “go” and hit <Enter>


5. This will return a list of all databases on the server.  If databases were created successfully, you should see “pmdb$primavera” and “mmdb$primavera”

FIX 6:
Run ConfigAsst.exe from CD1 to create databases:  (See admin guide pg. 36)

Image may be NSFW.
Clik here to view.

FIX 7:
Start the database windows service for the MSSQL instance

Image may be NSFW.
Clik here to view.

Set the service to Automatic so it will restart after a shutdown of the machine.

If running full SQL 2000, Authentication setting is set to “Windows Only”. 

FIX 8:

Within Enterprise Manager, right click on servername, go to “Properties”.  On Security tab, set Authentication to “SQL Server and Windows”

 Image may be NSFW.
Clik here to view. 

The SQL port was changed on the server and either: 1.) the new port is not dynamcially resolving, or 2.) there is already a static port specified on the client machine.

FIX 9:  (to be done from the machine that can’t connect to the database)

1. Click: Start, Run.


2. Type: cliconfg, Click: OK.


3. In the SQL Server Client Network Utility, click: ‘Alias’ (tab)


4. If an alias is already defined, and its name matches the server name being used while configuring a Primavera Project Management connection, adjust the port number and close.  Otherwise, proceed to the next step:
    


5. Click: ‘Add’ (button), TCP/IP.


6. Type a name in ‘Server alias’.


7. ‘Server name’ must match the database location.
   NOTE: Specify the instance name, if there is one.


8. ‘Dynamically determine port’ should NOT be checked.


9. ‘Port number’ must match the new port of the SQL Service.


10. Click: OK, Apply, OK.

The application was installed using the “Client Applications” whereas the intention was to install the Stand-alone version of the software, which installs a database locally for the client to connect to.

Image may be NSFW.
Clik here to view.

FIX 10:

Uninstall the software and re-install, choosing Stand-alone rather than Client applications

The client machine and database server are on different domains.

FIX 11:

Use the Database Server’s IP address, when prompted for ‘Host Name’.

The SQL Database Server TCP port was changed and the Server was never restarted.

FIX 12:

Restart the SQL Server.