Quantcast
Channel: Primavera Online Interaction » PMDB
Viewing all articles
Browse latest Browse all 92

prim29157:”Unable to resolve privileged username and password” when using Database Configuration for myPrimavera 5.0

$
0
0
Solution ID: prim29157
"Unable to resolve privileged username and password" when using Database Configuration for myPrimavera 5.0
Status: Reviewed
Version(s): 5.0



Problem: How to Connect MyPrimavera to a named instance of MS SQL Server
Fact: MSDE
Problem: Error during myPrimavera database configuration.
Problem:

Receive error connecting to 5.0 standalone (MSDE) database.


“Unable to resolve privileged username and password” when using Database Configuration for myPrimavera 5.0


 


Error: Unable to resolve privileged username and password


Failed Logon:com.jnetdirect.jsql.u:


TCP/IP connection failed to host:java.net.UnknownHostException: <servername>\primavera


url:jdbc:JSQLConnect://<servername>\primavera:<port>/database=<database name>$primavera



Problem: MyPrimavera Database Configuration fails when connecting to an instance of MSDE
Fix: Database Configuration screen should have the following information:

  1. Username and Password = pubuser

  2. Database Name:  pmdb$primavera  Note: pmdb$primavera is the 5.0 default database name, this may be different.

  3. Database Host Address:  Server Machine name or IP address (or ”localhost” if everything is installed on one machine)   Note: \<SQL instance name> is not needed.

  4. Database Host Port:  To determine the Database Host Port, see instructions below.


To determine the Database Host Port:


Go to Start/Run and type svrnetcn.  Click OK.



Select the \PRIMAVERA instance, highlight TCP/IP and click ‘Properties’.



This is the Default port # for this SQL Instance.


 


 Another alternative to finding the host port is the following:


1.  Log into Project Management.


2.  Go to Help, About Primavera.  Go to the System tab.


3.  Find the port number under the BRE database section:


Fix: This error was also observed in the following scenario:

Customer’s machine name included “\” characters. The JSQLConnect function appears to parse the connect string as “<servername>\<instance>…”.  Any slashes in the servername part cause the connect string to be wrongly interpreted.


The workaround is ensure that the server name does not contain “\” characters.


Viewing all articles
Browse latest Browse all 92

Trending Articles