HELP: error code 9415, can't connect to Project Server

J

Jørgen Strand

All,

our configuration is Project server 2003, Project Pro
2003, Sql Server Enterprise edition with Analysis Services
and Windows 2000 Adv. Server (2 boxes, one running SQL
server).

Everything worked fine until today when an administrative
project was checked back in after some changes. After that
no one can connect from Project Pro to Project Server.

The error message is "An exception occured in Project
Server. Project Server encountered a problem with this
error code: 9415...."

The event viewer spits this one out:
Component: PDS
Line: 0
Error Number: 0x24c7
Description: said:
</Description>
Click to expand...

From what I can read from the SDK error code 9415 is:
9300 - 9499 are reserved for DataAccess exception errors,
and are not enumerated.

We have done no changes in our environment (we are testing
it and we are two users) and have certainly not tampered
any settings. The system has been working fine for a
period of time now...

Our pilot starts on monday, so any input would be
appreciated.

-Lost MSP Soul
 
D

David Gage

You would probably need to get Microsoft involved to get this answered.
Would probably require you sending your database to them.

Do you happen to have a backup that you could revert to?

You could also try going into Project Web Access --> Admin --> Cleanup
Project Server Database. See if the offending admin project is in the list
and delete the project.

David
 
J

Jørgen

Thank you for your quick reply David,

Since this is the test environment, I tried to clean the
database after the principle of last-in, first-out.
The environment is now completely scrubbed and there are
no projects left, and still no resolution to our problem.

When it comes to backup, it really doesn't matter at this
stage since the environment can be rebuilt.

What concerns me here, is the stability of the product and
potentially jeopardizing the production start. I really do
not feel confident in rolling this out when these kind of
issues arise.

Any thoughts about this? Any known issues with MS Project
2003 that I should be aware of?

Cheers,

Jørgen
 
D

David Gage

Project Server 2003 is a 2.0 product version so I believe it should be
better than 2002. While 2002 definitely had some problems and bugs, overall
it was very good. Once it was setup, Project Server 2002 was pretty stable.

As far as 2003, it is a fairly new product but I like it so far. However,
there is no telling if you have found a bug and whether that is 1 of a few
bugs or 1 of many.

Ultimately, I think you need to feel confident before you roll the system
out. However, realize that Project Server 2002 has been successfully used
in a large number of companies with overall positive success.

David
--
David Gage
Microsoft Project MVP
QuantumPM

Thank you for your quick reply David,

Since this is the test environment, I tried to clean the
database after the principle of last-in, first-out.
The environment is now completely scrubbed and there are
no projects left, and still no resolution to our problem.

When it comes to backup, it really doesn't matter at this
stage since the environment can be rebuilt.

What concerns me here, is the stability of the product and
potentially jeopardizing the production start. I really do
not feel confident in rolling this out when these kind of
issues arise.

Any thoughts about this? Any known issues with MS Project
2003 that I should be aware of?

Cheers,

Jørgen
 
Top