Administrator Password on Install Issue - Error 5006 message.

[Dominic Moss]

First Off, I have installed Office Project Server 2003 plenty of times
without a problem. I am trying to install a new instance of Office Project
Server 2003 on a laptop for demonstration purposes - the laptop is of a good
enough spec to cope with Windows 2003 Server, SQL etc.

I have experienced a fairly common problem with the Adminstrator Password on
a fresh install of Office Project Server 2003. The "Validated" password
provided for the Adminstrator during the install process does not work.

I say "Validated" as I assume that the install process would not proceed if
there were any discrepancies in the password as it is entered twice during
the install process. In all instances I have ensure all items in the
Prepeare the Servers preparatory steps and have done all the Post Install
actions including run proxycfg.exe and PSComplus.exe as well as checking the
URL in the pds.wsdl file and checking IIS for Anonymous Access (I go to IIS,
select the Default Web Site Node, right click, properties, Directory
Security, Enable anonymous access, Edit and ensure the tickbox is turned
OFF).

Entering the Adminstrator Password results in the 5006 Error Message. All
attempts and combinations fail.

I have uninstalled Project Server and then created the SQL Database from the
...\Support\Database command prompt. I then install Project Server and
specify connection to an existing Database - the install process proceeds to
completion. I do all the post install actions as described above. Entering
the Adminstrator Password again results in the 5006 Error Message.

Trying again I try running the SETUPDB.CMD command from the installation CD
and again run all the post install actions - guess what? Entering the
Adminstrator Password results in the 5006 Error Message yet again. One point
here is that in the DOS Prompt window when running the SETUPDB.CMD command
towards the end, after all the numbers flash up on the screen, there are a
whole series of single entry rows displaying the following text - "1 row
affected" - is this of any significance?

I have succesfully "repaired" instances of Office Project Server 2003 in the
past using this last fix, both on my own test servers and also at a client
site where they had installed Office Project Server 2003 themselves.

Does anyone have any idea what might be the cause of my problem in this
instance? I think I have all bases covered and have been through the install
process by the book.

--
Dominic Moss

www.projectability.co.uk

Helping people achieve more with Microsoft Project

Tel +44 8707 303 400
Fax +44 8707 303 500

 

[Gary L. Chefetz \(MVP\)]

Dominic:

When you use the setupdb.cmd approach, no password is assigned to the
built-in administrator account. See the following link that will help you
troubleshoot, or at least eliminate the password as your problem.

http://www.projectserverexperts.com/Shared Documents/forgotadminpassword.htm

--

Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

For Project Server FAQs visit
http://www.projectserverexperts.com

For Project FAQs visit
http://www.mvps.org/project

-

 

[Dominic Moss]

Dear Gary,

I tried the fix referenced on your Website which was a useful new one -
sadly result was the same.

I then started anew with the whole process and this time hit a stumbling
block a lot earlier in the Windows SharePoint Services install - the only
thing that was different this time was that I had installed SQL using
Windows Authentication. When installing the SP3 I got a message saying my sa
account had no password, please provide one - this again was something I had
not seen before and assume is a direct result of installing SQL with only
Windows Authentication.

After creating the application pool the next step after running iisrest and
clicking the OK button "Set Configuration Database" was where I hit
problems - no matter what combination of Server Name, SQL Name and login I
kept getting an error message. I had seen this before and guess it is all
down to not setting Mixed mode Authentication when installing SQL - I tried
to fix this retrospectively but it did not seem to work. I am resigned to
starting again from scratch.

I am totally mystified as to what is happening as I have previously
installed Office Project Server on another Laptop for demo purposes and have
followed my own documented step by step install notes to the letter.

Thanks for all your advice and support on this and many numerous previous
issues.

Dominic