Enterprise features /SQL database connection stop working

K

keith

Hi,

Our recently set up project server enterprise edition
stopped being able to perform enterprise features after 1)
my employer and the main user of Project changed the
Administrator's log on password 2) We started service with
a new ISP, which required changing the IP addresses of all
our machines. We changed the password back to the
original, but the problem remains.

We now get the "failed log in or server can't be found"
message (the alert isn't clear on which of these is
occurring), followed by the dialog box asking for
MSProjectUser's password, which though filled in, fails.
The correct SQL server does show up in the top drop down
server list.

The SQLserver and Project server are on the same machine
(small office installation), and using Enterprise Manager,
I have no problem logging into the SQLServer as
MSProjectUser.

Thus I suspect that it's a problem of no longer being able
to fing the SQL server. Is there a place to set up this
connection. Looking through the knowledgebase I saw that
there are some registry keys that provide a connection
string to the sql server, but the password part here is
encryped - of course - and I'm very reluctant to solve
this using hack methodology. And It may be the change in
log in that's the cause, though how changing the Project
Administrator's log in effects the MSProject users ability
to access the DB is a mystery to me.

The consultant who help with the install also had us
change the hosts file in system32/drivers/etc to add the
project server, so I did make sure these were updated
after the ISP change.

Any suggestions gratefully appreciated.

Keith
 
G

Gary L. Chefetz

Kieth:

Changing the IP address alone wouldn't cause this unless you used the IP
address instead of the server name when you installed. That scenario would
have the same affect as changing the server name, which would require that
you hand edit the references to it in the reistry. There's an article that
covers the important registry settings for Project Server on TechNet.
Changing the name of the server or the IP address ir used as a substitute
for server name will also require that you change your connection accounts
within Project Pro as well.

Take a look at the following to help get you past the admin password issue:

http://www.projectserverexperts.com/Project Server FAQs/forgotadminpassword.htm

--

Gary Chefetz [MVP]
http://www.msprojectexperts.com
"We wrote the book on Project Server"

*** Remember to look for line breaks in links posted to the news group, use
cut and paste for these.
 
K

keith

I seem to have made it signifigantly worse. I went and
reset the MSProjectUser and MSProjectServer user to what
the documentation indicated them to be. Now the database
cannot be found at all.

Is there a way to resync these values into project server?

Keith
 
G

Gary L. Chefetz

Keith:

To reset the passwords to the value that appears in the registry. First
harvest the passwords from the registry, then remove the accounts from the
ProjectServer database. Next change the passwords under SQL Logins to the
value harvested from the registry, then add the logins back to the Project
Server database assigning the proper roles.

--

Gary Chefetz [MVP]
http://www.msprojectexperts.com
"We wrote the book on Project Server"

*** Remember to look for line breaks in links posted to the news group, use
cut and paste for these.
 
K

keith

Thanks for your help.

looking at the connection string pointed to in this
technet article in the Proj Username and
MicrosoftProjectServerUser keys:
http://www.microsoft.com/technet/treeview/default.asp?
url=/technet/prodtechnol/project/project2002/reskit/ps02/ps
instl/psgblset.asp
it looks like the passwords here are are encrypted.

Is there another place to harvest the passwords?

Thanks again.

Keith
 
G

Gary L. Chefetz

Keith:

The passwords are not encrypted (much to the dismay of many administrators).
They are very strong passwords, so treat them as literals.

--

Gary Chefetz [MVP]
http://www.msprojectexperts.com
"We wrote the book on Project Server"

*** Remember to look for line breaks in links posted to the news group, use
cut and paste for these.
 
K

Kevin Flanagan

THere are approx. 140 pages with hard-coded information
on them from the installation process that include,
domain name, IP/URL addresses, user accounts (including
domain names) and passwords. This may be the cause of
your issues you are experiencing. We found this out from
just attempting to migrate to a new domain.

Kevin
 
Top