Cannot run Project Server SP1

[Jay]

I know the password for the SQL SA login and use it in the CMD prompt to
apply this update. And have also tried other id's that are in SQL with admin
rights. But I always get the same ol thing "Databse does not exist or access
denied"

 

[Gary L. Chefetz \(MVP\)]

Jay:

Very often it's a silly mistake in typing the command line. So silly that
your eyes won't let you see it. Try posting the command line exactly the way
you're typing it. Don't post the actual password though.

--

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

-

 

[Jay]

Upgdb111.cmd [servername] [projectserver] [sa] [password] is what I use in
the CMD prompt.
I have copied the update to the appropriate directory and ran it from there.
I have had a similar problem when trying to update SQL's Analysis services.
It cannot validate the sa login.

 

[Jay]

OK, I found out some things. I enabled TCP/IP in client network utility for
SQL and that fixed the problem for SQL upgrade and kinda fixed the problem
for Project server upgrade. But now when going thru PS upgrade it tells me it
could not find the specified SQL server. My SQL server is a local SQL with
not name. The name is (local) so I put my swervers name in there but it
doesn't like it. Still tells me that it could not find specified SQL name.
Would it casue a problem that I have 2 databaese called ProjectServer.

 

[Earl Lewis]

Jay,

Did MSSQL actually allow you to create two dbs with the same name?? That is very unexpected.

I don't want to sound condescending, but just so we're clear on terminology and you're not confusing databases with servers - MSSQL runs as a service on a server and is typically referred to as "SQL server". And any single instance of MSSQL "SQL server" can host any number of databases. SQL servers need to have names and databases need to have names.

So given all of that, are you sure there are two databases called ProjectServer? If this was actually allowed to happen I can certainly see that something like connecting to the database may not work. If at all possible I'd look into changing the name of one of those dbs if there really are 2.

Earl
OK, I found out some things. I enabled TCP/IP in client network utility for
SQL and that fixed the problem for SQL upgrade and kinda fixed the problem
for Project server upgrade. But now when going thru PS upgrade it tells me it
could not find the specified SQL server. My SQL server is a local SQL with
not name. The name is (local) so I put my swervers name in there but it
doesn't like it. Still tells me that it could not find specified SQL name.
Would it casue a problem that I have 2 databaese called ProjectServer.

 

[Gary L. Chefetz \(MVP\)]

Jay:

Once again I find myself tossing in a tidbit following sage advice from
Earl, is it possible that you created a named instance of SQL? If so, you
need to specify the SQL named instance in any field or command that calls
it.

--

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

-