Enterprise Global corrupted and Project deletion issue

C

Carlos Dietrich

Hello everyone,

first I would like to ask you for forgiveness because english is not my
primary language, so I'll try my best to explain what is happening.

This is what we have in place:

Virtual Machine running on Virtual Server
1GB of memory
Windows Server 2003 R2 + SP2
SQL Server 2005 + SP2
Project Server 2003 + SP2a - Portuguese Brazilian (Not MUI) + Hotfixes
KB921115 and KB923802


We are experiencing two different issues... we are not sure if they are
related but the fact is that we are experiencing both together.

1- When we try to read the ProjectCodeValues from any project, the CPU goes
to 100%. The worker process from the PWA Pool is the process that consumes
all the CPU.
This happens when we use PDS or click "Edit" on Project Central.

This is the XML we send to PDS:

<Request>
<ProjectCodeValues>
<ProjectID></ProjectID>
</ProjectCodeValues>
</Request>

On this matter we did A LOT of research and we found that the problem is
related to Enterprise Global. To "solve" it we just have to open the
Enterprise Global on Project Professional and save it, without changes.

2- After deleting the LAST (bigger PROJ_ID) project using PSCleaner we are
not able to create new projects. We are using PDS to create projects.
This is the xml used to create projects:

<Request>
<ProjectCreate>
<AutoPublish>1</AutoPublish>
<Project>
<ProjectName></ProjectName>
<StartDate></StartDate>
<TemplateID></TemplateID>
</Project>
</ProjectCreate>
</Request>

We also did A LOT of research and found that when Project Server tries to
create the new project it fails on this procedure:
"MSP_PDS_SP_ProjectCreateFromTemplate"

The message is:
"Msg 2601, Level 14, State 1, Procedure
MSP_PDS_SP_ProjectCreateFromTemplate, Line 43
Cannot insert duplicate key row in object 'dbo.MSP_RESOURCES' with unique
index 'I_MSP_RESOURCES'.
The statement has been terminated."

Based on that information we used PSCleaner again and discover that
MSP_RESOURCES is not been cleaned properly even after we used SQL Profiler
during a project exclusion and the statement:

"DELETE FROM MSP_RESOURCES WHERE PROJ_ID = XXXXX"

is executed without problem.

In a desperate attempt we created a empty database on a SQL Server 2000 and
migrated all data from SQL Server 2005.

On this downgraded database, the 100% CPU problem still happens, but saving
the Enterprise Global still "solves" it. The deletion problem apparently is
resolved, but we just can't downgrade everything back to SQL Server 2000.

We also tried to update Project Server 2003 and the SQL Server 2005 database
using Project Server SP3, but both errors are still happening.

I hope you guys can understand and help me.

Thanks,

Carlos
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top