JaySo well have to focus onto MS SQL and Vista. Did you check the Microsoft page for the compatibility list?Under XP I remember that I had to remove all MS SQL entries from the registry before installing P6.1. If not properly done there was one line during SQL installation not marked in green which disappeared after a minute and it was the same result as you had. Only after ALL SQL related items were removed it was possible to install it properly.Next step for you in my opinion: Uninstall P6 and the MS SQL, clean the registry, then try the installation again.Good luck!Dieter. Anime tagalog dubbed. Thanks all.The first time I installed P6 last year it took me 4 hours to Configured but I got it worked out.
But my computer got corrupted so I have no choice but to reformat. I tried to reinstall, unstall and reformat many times to make sure I deleted all the files relating to Primavera and MS SQL but didnt make.
Im trying to install 6.1 and they said it was compatible to Vista and so I reformat again and upgraded into Vista Business, running 32 bit of OS.When I was in the middle of installation, the SQL Server Database Services failed to setup and I guess that was the problem. Ive gone to Registry Editor and deleted all files, unstall all program, even gone to Windows System 32 and had dbexpsda30.dll replaced with dbexpsda.dll but apparently it didnt work out so Id changed it back to original dbexpsda30.dllI checked the PM.exe and it says there that database is null, database is not found, and a lot more database errors.That was the story folks. Appreciate all.V/R,Jay.
Hi Jay,Try this:When P6 Project Management connects to a SQL Server 2000 database, it automatically sets the database transaction isolation level to READ UNCOMMITTED (dirty reads) to reduce concurrency issues. This is no longer necessary for SQL Server 2005 but is still done automatically by the P6 Project Management module.If you are connecting to a SQL Server 2005 database, you should set the AllowDirtyReads key in the Database section of the PM.ini file to False. Setting this key to false causes SQL Server 2005 connections to use the default setting for this database, which is READ COMMITTED SNAPSHOT.STEPS TO RESOLVE THIS ISSUE:Follow these steps to configure any client machines using the P6 Project Management module to connect to a SQL Server 2005 database:1.
Using a text editor, open the PM.ini file located in the PrimaveraProject Management installation directory.2. If the Database section does not exist, add it to the bottom of the file.3. If the AllowDirtyReads key does not exist, add it to the Database section and set it to FALSE. For example:DatabaseAllowDirtyReads=FALSE4. Save the file.
If necessary, restart the P6 Project Management module.HTH. Hi.I think there was no local admin security profile. It keeps showing the same error. I actually reformatted the computer again ang upgraded it into Vista, first thing I installed were Primavera together with MSQL server but failed when it came into databse configuration.I think I followed the procedure, i just dont know whats keeping it failed.Hostname: computernamePrimaveradatabase name: pmdb$PrimaveraUser: pubuser/adminpass: pubuser/adminI also tried to install it with internet connection, nothing happens.Folks I really need some help with this for I am running out of time. If anyone are based here in UAE I would go with my computer if I can.Thanks a lot.
Hi@ Mike, there is and requires a valid license no. And maintenance contract.In Germany it’s included in purchase price for the first 6 months and I have good experience.@ JayIt seems that SQL server wasn’t properly installed. Unfortunately, there are some error, where the message disappears during installation process.You wrote that the PC got a new installation. So it should be ok.The user under which you installed P6, did it have local admin security profile?
Oracle Primavera P6 Installation Guide
The error message shows that the problem is the database server.I don’t know of any conflicts with other software.Did you check DokuTested Configurations for the required version of Windows?RegardsDieter. Hi folks,We reformat the computer twice already without restoring any files.Install, unstall & deleted the files completely and reinstall but still having the same delima.' Bad public user name or password.
Database Server Error: Login failed for user pubuser.;'Bad public user name or password. Database Server Error: Login failed for user admin.;'This was the new message:'Bad public user name or password. Database Server Error: Shared Memory Provider: No process is on the other end of the pipe.;'But then again I turned back with the previous messages.Appreciate any assistance. And awaiting. Hi Hazel,The good news is you have the database system up and running and P6 installed. I suspect you havent created a database, because if you had it should have created the connection information for you.Can you start 'SQL Server Management Studio Express' (or similar).
You should get in with Windows Authentication (Hit 'Connect' button on the login screen). There is a kind of folder structure on the left and if you expand it to list the 'Databases' you should have pmdb$Primavera.If it isnt there or all you have is 'System Databases' then the Primavera Database hasnt been created.Contact me direct if this is a little too much. We could probably sort this out on a phone call.Barrie.
When connect SQL database in Primavera P6 Professional, we usually have problem like:. Error Message: Bad public user Name or password. SQL Server Error: DBNETLIBConnectionOpen(Connect).SQL Server does not exist or access denied. Error message: Bad public user name or password.
SQL Server Error: DBNETLIBConnectionOpen (Invalid Instance). Invalid connection.;”. Error Message: Bad public user name or password. Database Server Error: Login failed for user ‘pubuser’.Below are some Reason and Solution:CAUSE 1:Incorrect hostname, instance or database nameBad public user Name or password. SQL Server Error: DBNETLIB ConnectionOpen(Connect).SQL Server does not exist or access denied. Default port for SQL is 1433. Default Port for Oracle is 1521.
What Is Primavera P6
An exception can be added to the firwewall for pm.exe and dbconfig.exeCAUSE 4:On a machine that does not have a network cable plugged in, ‘localhost’ is not recognized as a valid replacement for the machine name. (This is common in a ‘stand alone’ environment.)FIX 4:Replace ‘localhost’ with the actual machine name in the db alias connection informationCAUSE 5:User made a typo in the server name. Accidentally typed ” / ” (forward slash) instead of the correct ” ” (back slash) or didn’t enter the right name of the Instance.FIX 5:Enter the server name correctly. (Example: “” where is the machine name where SQL Server is installed and is the name of the Instance where the P6 database is located. Example: localhostPrimavera )CAUSE 6:Databases were not created during standalone installation. To verify:Click Start, All Programs, Microsoft SQL Server 2005, SQL Server Management Studio/ SQL Server Management Studio Express.Log in either with Authentication set to Windows Authentication or using Login: sa and Password: Prima123Vera with SQL Server Authentication.Expand the databases folder and see is databases ‘pmdb$primavera’ and ‘mmdb$primavera’ have been created.FIX 6:For P6.0 and P6.1 run the ConfigAsst.exe from CD1 to create databases: ( See admin guide pg. CAUSE 9:The SQL port was changed on the server and either:1.) the new port is not dynamically resolving, or2.) 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).
Click: Start, Run. Type: cliconfg, Click: OK.
In the SQL Server Client Network Utility, click: ‘Alias’ (tab). 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. Microsoft SQL 2005 SP1 is not supported on VistaFIX 15:For Windows XP Upgrade Microsoft SQL Server 2005 to SP2For Windows 2008 use Fix 9 above and supply a period for the hostname field, i.e. Example:USE PMDBEXEC spchangeuserslogin ‘UpdateOne’, ‘pubuser’, ‘pubuser’EXEC spchangeuserslogin ‘UpdateOne’, ‘privuser’, ‘privuser’CAUSE 20:The SQL Server database may be set to auto-close. When trying to log in, the database may not be ready to accept the connection.FIX 20:Change auto-close setting to false:1) Log into SQL Server Management Studio2) Expand Databases3) Right-click on the P6 Database4) Options page5) Under Automatic Section, Set Auto Close to False6) Click OK. Published by Khuong DoMr. Khuong is a competent civil engineer, project planner, forensic delay analyst and IT specialist.
Khuong has prepared numerous delay analysis submissions, some of which were used in international Arbitrations and high-profile projects in Asia and beyond. He's based out of Beijing (China), Dubai (UAE), and Ho Chi Minh (Vietnam).Mr. Khuong has a Bachelor Degree in Engineering and a Bachelor Degree in Management Information System. Winwedge pro. He’s also trained as Primavera Authorised Trainer.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |