Bad public user name or password.

Written on . By Tracy Mah

When you configure Project Management to connect to  database server and you receive the following errors:

  • Bad public user name or password.
  • Check the public group ID.
  • Bad public user name or password.
  • Unable to Load dbexpsda30.dll.
  • Bad public user name or password.
  • Database Server Error: Login failed for user ‘pubuser’.
  • Bad public user name or password.
  • Database Server Error: Named Pipes Provider: Could not open a connection to SQL Server [53].
  • Bad public user name or password. Access violation at address 019621F8 in module ‘dbexpsda30.dll’.
  • Write of address 0000000A.

The possible causes are:

  1. You give the wrong username/password
  2. You enter the wrong database server host name, i.e. , just enter localhost may not works, and most of times, enter localhost\primavera as database host name works.
  3. You did not enable TCP/IP or Named Pipes in your MS SQL Server for remote connection.
  4. Your database maybe corrupted,  create a new database and try. In particular, if you receive “Bad public user name or password. Check the public group ID.”,  your database is damaged in most cases.
  5. Your firewall blocks port 1433 or related port used for MS SQL Server connections.
  6. The dbexpsda30.dll or dbexpoda.dll  is not compatible with  your  database  server or operating system, ie  if you use  MS SQL Server 2008, you may get this error. If MS Server 2008 is used and P6 Client is running on Windows Server 2008,  the dbexpsda30.dll should be version 4.25.0.8 or higher.
  7. The resources in the server or client have run out. P6 Windows client uses Winsock (wsock32.dll) to connect to the database, and if there are less resources in the server, you may have difficulty to connect to the server. There is a simple method to test if the server have enough TCP/IP resouces, run FTP in the DOS prompt, and try to connect to any FTP server, if you get ftp: bind :No buffer space is supported, then it is clear that your server or client does not have enough resouces. In this case, you should restart some heavy services such MS SQL Server service, even restart the entire machine to release more resources.

Posted in Installation/Admin