Save hangs at 97% for long time

[Quized again.]

Using MSP Server 2007 on a 3 box installation. SQL on its own server and not
shared with other apps (all virtual servers). SQL box had 2 dual cores, 2GB
RAM.

When I import a project into the system, it processes quickly to about 97%
complete and then processes for about an hour. The SQL box is showing about
50-60% utilization on the processors. All counters look fine except the
Processor Queue Legnth with is spiking very high (10-14). THe file size is
relatively small and not overly loaded with resources, etc.

Why would the PQL be spiking so high on a box that is adequate for the job?
SQL guys looked and see nothing odd. No errors being logged. I can save a
very small file while this is hagging on the larger file.


Is there something to look at relating to Active Cache or anything that I
should check?

Thanks.

 

[Gary L. Chefetz [MVP]]

QA:

The most likely cause is corruption in the project plan. The best way to
clear this is to save to XML and then open it again in Project and save to
mpp or import to Server.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com

 

[Quized again]

Thank you for the suggestion. I saved one of the files offline as XML and
reimported it. Still hanging at about 94%. What else might I try? Any idea
what the last 10% of the save action is attempting to do?

Sort of strange, I think.

 

[Paul Conroy]

you could try enabling client side logging, maybe this will uncover the issue

add this regkey onto the client.

[HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\MS Project]
"WinprojLog"=string:"c:\\temp\\"
"DebugCategory"=dword:ffffffff
"DebugLevel"=dword:ffffffff
"DebugLoadSerCategory"=dword:000003ed

have you deleted the cache on the PC? If not, try doing so (delete the
folder in windows explorer, rather than clearing it down in project pro.

--
Please rate this post if it has helped

http://theprojectserverguru.spaces.live.com

 

[Gary L. Chefetz [MVP]]

QA:

Did you delete the plan from the server before importing it back to the
server? Have you looked at the server application log and the ULS logs?

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com

 

[Quized again]

Thanks Paul.
I added the regkey but nothing is logging or I do not know where to look.
I did delete the cache as you suggested.
No change.
More ideas?

you could try enabling client side logging, maybe this will uncover the issue

add this regkey onto the client.

[HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\MS Project]
"WinprojLog"=string:"c:\\temp\\"
"DebugCategory"=dword:ffffffff
"DebugLevel"=dword:ffffffff
"DebugLoadSerCategory"=dword:000003ed

have you deleted the cache on the PC? If not, try doing so (delete the
folder in windows explorer, rather than clearing it down in project pro.

--
Please rate this post if it has helped

http://theprojectserverguru.spaces.live.com

Thank you for the suggestion. I saved one of the files offline as XML and
reimported it. Still hanging at about 94%. What else might I try? Any idea
what the last 10% of the save action is attempting to do?

Sort of strange, I think.

 

[Quized again]

I renamed it then imported it. I also deleted all codes and resources that
existed from its MSP2003 state. No external links.

THe logs all show normal operations. It is just slow but not thowing errors.
I have noticed that the SQL server logs are showing timestamps that are
different than the app logs. Is there some form of time synch that should
happen? Just taking wild shots 'cause I don't know.

Thanks for your help. Any more suggestions?

 

[Paul Conroy]

check SQL and Projects servers have the same time !

--
Please rate this post if it has helped

http://theprojectserverguru.spaces.live.com

 

[Gary L. Chefetz [MVP]]

QA:

This still smacks of corruption. Run the following query to determine if
this suspicion is correct:

USE [ProjectServer_Published]
SELECT MSP_PROJECTS.PROJ_NAME,
MSP_ASSIGNMENTS_SAVED.TASK_NAME,
MSP_RESOURCES.RES_NAME,
MSP_ASSIGNMENTS_SAVED.ASSN_UID,
MSP_ASSIGNMENTS_SAVED.PROJ_UID,
MSP_ASSIGNMENTS_SAVED.TASK_UID,
MSP_ASSIGNMENTS_SAVED.RES_UID
FROM MSP_ASSIGNMENTS_SAVED INNER JOIN
MSP_PROJECTS ON MSP_ASSIGNMENTS_SAVED.PROJ_UID =
MSP_PROJECTS.PROJ_UID INNER JOIN
MSP_RESOURCES ON MSP_ASSIGNMENTS_SAVED.RES_UID =
MSP_RESOURCES.RES_UID
WHERE (NOT EXISTS
(SELECT TASK_UID
FROM MSP_TASKS_SAVED
WHERE (TASK_UID = MSP_ASSIGNMENTS_SAVED.TASK_UID)))


--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com

 

[Quized again]

Ok so perhaps we are clsoing in. Thanks!
I ran the script against both draft and published DBs on two different
instances under one SSP and all of them returned no results (both instances
contain the same files for testing). However the reporting database on both
instances returned:

Msg 208, Level 16, State 1, Line 2
Invalid object name 'MSP_ASSIGNMENTS_SAVED'.

Do you know what this means?


A google search on everything but the table name shows a fix for SQL server
2000 if you get the error running DBCC CHECKCONSTRAINTS. But the fix was
incorporated in SQLSvr2000 SP4 and it does not seem like it applies here
anyway.

I hope this means we are closer!

QA:

This still smacks of corruption. Run the following query to determine if
this suspicion is correct:

USE [ProjectServer_Published]
SELECT MSP_PROJECTS.PROJ_NAME,
MSP_ASSIGNMENTS_SAVED.TASK_NAME,
MSP_RESOURCES.RES_NAME,
MSP_ASSIGNMENTS_SAVED.ASSN_UID,
MSP_ASSIGNMENTS_SAVED.PROJ_UID,
MSP_ASSIGNMENTS_SAVED.TASK_UID,
MSP_ASSIGNMENTS_SAVED.RES_UID
FROM MSP_ASSIGNMENTS_SAVED INNER JOIN
MSP_PROJECTS ON MSP_ASSIGNMENTS_SAVED.PROJ_UID =
MSP_PROJECTS.PROJ_UID INNER JOIN
MSP_RESOURCES ON MSP_ASSIGNMENTS_SAVED.RES_UID =
MSP_RESOURCES.RES_UID
WHERE (NOT EXISTS
(SELECT TASK_UID
FROM MSP_TASKS_SAVED
WHERE (TASK_UID = MSP_ASSIGNMENTS_SAVED.TASK_UID)))


--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com

I renamed it then imported it. I also deleted all codes and resources that
existed from its MSP2003 state. No external links.

THe logs all show normal operations. It is just slow but not thowing
errors.
I have noticed that the SQL server logs are showing timestamps that are
different than the app logs. Is there some form of time synch that should
happen? Just taking wild shots 'cause I don't know.

Thanks for your help. Any more suggestions?

 

[Quized again]

Ok, I was wrong about the servers being off-clock. THey were only by seconds
and I changed that.

Thanks for your time Paul. Got any other suggestions?

 

[Gary L. Chefetz [MVP]]

QA:

The reporting database does not contain the same project table structure
that the Published and Draft databases contain, so this isn't very
surprising. I'm scratching my head at this point. Does this only happen when
you import projects or does it happen to projects that already exist on the
system? Has the project ever been published before? Did you set the ULS
logging to verbose? Does this only happen to projects that originated in
2003? Does it happen to other projects only one.

If you've got the 2003 server environment running, you might also try to
force a binary rebuild following these directions before trying the import
again. the 2003 format had more potential for binary corruption than 2007
has.

http://www.projectserverexperts.com/ProjectServerFAQKnowledgeBase/BinaryRebuild.aspx


--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com

Ok so perhaps we are clsoing in. Thanks!
I ran the script against both draft and published DBs on two different
instances under one SSP and all of them returned no results (both
instances
contain the same files for testing). However the reporting database on
both
instances returned:

Msg 208, Level 16, State 1, Line 2
Invalid object name 'MSP_ASSIGNMENTS_SAVED'.

Do you know what this means?


A google search on everything but the table name shows a fix for SQL
server
2000 if you get the error running DBCC CHECKCONSTRAINTS. But the fix was
incorporated in SQLSvr2000 SP4 and it does not seem like it applies here
anyway.

I hope this means we are closer!

QA:

This still smacks of corruption. Run the following query to determine if
this suspicion is correct:

USE [ProjectServer_Published]
SELECT MSP_PROJECTS.PROJ_NAME,
MSP_ASSIGNMENTS_SAVED.TASK_NAME,
MSP_RESOURCES.RES_NAME,
MSP_ASSIGNMENTS_SAVED.ASSN_UID,
MSP_ASSIGNMENTS_SAVED.PROJ_UID,
MSP_ASSIGNMENTS_SAVED.TASK_UID,
MSP_ASSIGNMENTS_SAVED.RES_UID
FROM MSP_ASSIGNMENTS_SAVED INNER JOIN
MSP_PROJECTS ON MSP_ASSIGNMENTS_SAVED.PROJ_UID =
MSP_PROJECTS.PROJ_UID INNER JOIN
MSP_RESOURCES ON MSP_ASSIGNMENTS_SAVED.RES_UID =
MSP_RESOURCES.RES_UID
WHERE (NOT EXISTS
(SELECT TASK_UID
FROM MSP_TASKS_SAVED
WHERE (TASK_UID = MSP_ASSIGNMENTS_SAVED.TASK_UID)))


--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com

I renamed it then imported it. I also deleted all codes and resources
that
existed from its MSP2003 state. No external links.

THe logs all show normal operations. It is just slow but not thowing
errors.
I have noticed that the SQL server logs are showing timestamps that are
different than the app logs. Is there some form of time synch that
should
happen? Just taking wild shots 'cause I don't know.

Thanks for your help. Any more suggestions?

:

QA:

Did you delete the plan from the server before importing it back to
the
server? Have you looked at the server application log and the ULS
logs?

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com


message
Thank you for the suggestion. I saved one of the files offline as
XML
and
reimported it. Still hanging at about 94%. What else might I try?
Any
idea
what the last 10% of the save action is attempting to do?

Sort of strange, I think.

:

QA:

The most likely cause is corruption in the project plan. The best
way
to
clear this is to save to XML and then open it again in Project and
save
to
mpp or import to Server.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com


message
Using MSP Server 2007 on a 3 box installation. SQL on its own
server
and
not
shared with other apps (all virtual servers). SQL box had 2 dual
cores,
2GB
RAM.

When I import a project into the system, it processes quickly to
about
97%
complete and then processes for about an hour. The SQL box is
showing
about
50-60% utilization on the processors. All counters look fine
except
the
Processor Queue Legnth with is spiking very high (10-14). THe
file
size
is
relatively small and not overly loaded with resources, etc.

Why would the PQL be spiking so high on a box that is adequate
for
the
job?
SQL guys looked and see nothing odd. No errors being logged. I
can
save
a
very small file while this is hagging on the larger file.


Is there something to look at relating to Active Cache or
anything
that
I
should check?

Thanks.

 

[Quized again]

Gary thanks for all of your time.
It happens on the files from MSP2003 (no server). Those are what I had to
start with. I just created a 1000 line plan with resources and complicated
logic and it saves to the server in less than a minute. Cube built in 3
minutes (one resource per task).

Even the files from 2003 that I opened on server 2007 and saved back to
server 2007 with a new name took 40 minutes to save. Made few changes to
durations and resave, another 40 minutes. So I think you are correct that
there is corruption. To me the good news is that the corruption seems to be
in the files I used. I will obtain a different set of plans from a different
program and retry. If it gets wacky I will repost.

Again to you I am greatfull for your help.

Will be Quized Again soon, I am sure.

QA:

The reporting database does not contain the same project table structure
that the Published and Draft databases contain, so this isn't very
surprising. I'm scratching my head at this point. Does this only happen when
you import projects or does it happen to projects that already exist on the
system? Has the project ever been published before? Did you set the ULS
logging to verbose? Does this only happen to projects that originated in
2003? Does it happen to other projects only one.

If you've got the 2003 server environment running, you might also try to
force a binary rebuild following these directions before trying the import
again. the 2003 format had more potential for binary corruption than 2007
has.

http://www.projectserverexperts.com/ProjectServerFAQKnowledgeBase/BinaryRebuild.aspx


--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com

Ok so perhaps we are clsoing in. Thanks!
I ran the script against both draft and published DBs on two different
instances under one SSP and all of them returned no results (both
instances
contain the same files for testing). However the reporting database on
both
instances returned:

Msg 208, Level 16, State 1, Line 2
Invalid object name 'MSP_ASSIGNMENTS_SAVED'.

Do you know what this means?


A google search on everything but the table name shows a fix for SQL
server
2000 if you get the error running DBCC CHECKCONSTRAINTS. But the fix was
incorporated in SQLSvr2000 SP4 and it does not seem like it applies here
anyway.

I hope this means we are closer!

QA:

This still smacks of corruption. Run the following query to determine if
this suspicion is correct:

USE [ProjectServer_Published]
SELECT MSP_PROJECTS.PROJ_NAME,
MSP_ASSIGNMENTS_SAVED.TASK_NAME,
MSP_RESOURCES.RES_NAME,
MSP_ASSIGNMENTS_SAVED.ASSN_UID,
MSP_ASSIGNMENTS_SAVED.PROJ_UID,
MSP_ASSIGNMENTS_SAVED.TASK_UID,
MSP_ASSIGNMENTS_SAVED.RES_UID
FROM MSP_ASSIGNMENTS_SAVED INNER JOIN
MSP_PROJECTS ON MSP_ASSIGNMENTS_SAVED.PROJ_UID =
MSP_PROJECTS.PROJ_UID INNER JOIN
MSP_RESOURCES ON MSP_ASSIGNMENTS_SAVED.RES_UID =
MSP_RESOURCES.RES_UID
WHERE (NOT EXISTS
(SELECT TASK_UID
FROM MSP_TASKS_SAVED
WHERE (TASK_UID = MSP_ASSIGNMENTS_SAVED.TASK_UID)))


--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com


I renamed it then imported it. I also deleted all codes and resources
that
existed from its MSP2003 state. No external links.

THe logs all show normal operations. It is just slow but not thowing
errors.
I have noticed that the SQL server logs are showing timestamps that are
different than the app logs. Is there some form of time synch that
should
happen? Just taking wild shots 'cause I don't know.

Thanks for your help. Any more suggestions?

:

QA:

Did you delete the plan from the server before importing it back to
the
server? Have you looked at the server application log and the ULS
logs?

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com


message
Thank you for the suggestion. I saved one of the files offline as
XML
and
reimported it. Still hanging at about 94%. What else might I try?
Any
idea
what the last 10% of the save action is attempting to do?

Sort of strange, I think.

:

QA:

The most likely cause is corruption in the project plan. The best
way
to
clear this is to save to XML and then open it again in Project and
save
to
mpp or import to Server.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com


message
Using MSP Server 2007 on a 3 box installation. SQL on its own
server
and
not
shared with other apps (all virtual servers). SQL box had 2 dual
cores,
2GB
RAM.

When I import a project into the system, it processes quickly to
about
97%
complete and then processes for about an hour. The SQL box is
showing
about
50-60% utilization on the processors. All counters look fine
except
the
Processor Queue Legnth with is spiking very high (10-14). THe
file
size
is
relatively small and not overly loaded with resources, etc.

Why would the PQL be spiking so high on a box that is adequate
for
the
job?
SQL guys looked and see nothing odd. No errors being logged. I
can
save
a
very small file while this is hagging on the larger file.


Is there something to look at relating to Active Cache or
anything
that
I
should check?

Thanks.

 

[Quized again]

Hello Gary. The problem turned out to be the Infrastructure Update. I
uninstalled it and the files saved in about 10 minutes rather than 3 hours.
As it turns out, I missed the warning that this was a known side affect of
the infrastructure update. The August Cumulative Update is supposed to fix
this issue. I hope so because I want the fixes in the Infrastructure Update!

Thanks for your help.

QA:

The reporting database does not contain the same project table structure
that the Published and Draft databases contain, so this isn't very
surprising. I'm scratching my head at this point. Does this only happen when
you import projects or does it happen to projects that already exist on the
system? Has the project ever been published before? Did you set the ULS
logging to verbose? Does this only happen to projects that originated in
2003? Does it happen to other projects only one.

If you've got the 2003 server environment running, you might also try to
force a binary rebuild following these directions before trying the import
again. the 2003 format had more potential for binary corruption than 2007
has.

http://www.projectserverexperts.com/ProjectServerFAQKnowledgeBase/BinaryRebuild.aspx


--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com

Ok so perhaps we are clsoing in. Thanks!
I ran the script against both draft and published DBs on two different
instances under one SSP and all of them returned no results (both
instances
contain the same files for testing). However the reporting database on
both
instances returned:

Msg 208, Level 16, State 1, Line 2
Invalid object name 'MSP_ASSIGNMENTS_SAVED'.

Do you know what this means?


A google search on everything but the table name shows a fix for SQL
server
2000 if you get the error running DBCC CHECKCONSTRAINTS. But the fix was
incorporated in SQLSvr2000 SP4 and it does not seem like it applies here
anyway.

I hope this means we are closer!

QA:

This still smacks of corruption. Run the following query to determine if
this suspicion is correct:

USE [ProjectServer_Published]
SELECT MSP_PROJECTS.PROJ_NAME,
MSP_ASSIGNMENTS_SAVED.TASK_NAME,
MSP_RESOURCES.RES_NAME,
MSP_ASSIGNMENTS_SAVED.ASSN_UID,
MSP_ASSIGNMENTS_SAVED.PROJ_UID,
MSP_ASSIGNMENTS_SAVED.TASK_UID,
MSP_ASSIGNMENTS_SAVED.RES_UID
FROM MSP_ASSIGNMENTS_SAVED INNER JOIN
MSP_PROJECTS ON MSP_ASSIGNMENTS_SAVED.PROJ_UID =
MSP_PROJECTS.PROJ_UID INNER JOIN
MSP_RESOURCES ON MSP_ASSIGNMENTS_SAVED.RES_UID =
MSP_RESOURCES.RES_UID
WHERE (NOT EXISTS
(SELECT TASK_UID
FROM MSP_TASKS_SAVED
WHERE (TASK_UID = MSP_ASSIGNMENTS_SAVED.TASK_UID)))


--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com


I renamed it then imported it. I also deleted all codes and resources
that
existed from its MSP2003 state. No external links.

THe logs all show normal operations. It is just slow but not thowing
errors.
I have noticed that the SQL server logs are showing timestamps that are
different than the app logs. Is there some form of time synch that
should
happen? Just taking wild shots 'cause I don't know.

Thanks for your help. Any more suggestions?

:

QA:

Did you delete the plan from the server before importing it back to
the
server? Have you looked at the server application log and the ULS
logs?

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com


message
Thank you for the suggestion. I saved one of the files offline as
XML
and
reimported it. Still hanging at about 94%. What else might I try?
Any
idea
what the last 10% of the save action is attempting to do?

Sort of strange, I think.

:

QA:

The most likely cause is corruption in the project plan. The best
way
to
clear this is to save to XML and then open it again in Project and
save
to
mpp or import to Server.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com


message
Using MSP Server 2007 on a 3 box installation. SQL on its own
server
and
not
shared with other apps (all virtual servers). SQL box had 2 dual
cores,
2GB
RAM.

When I import a project into the system, it processes quickly to
about
97%
complete and then processes for about an hour. The SQL box is
showing
about
50-60% utilization on the processors. All counters look fine
except
the
Processor Queue Legnth with is spiking very high (10-14). THe
file
size
is
relatively small and not overly loaded with resources, etc.

Why would the PQL be spiking so high on a box that is adequate
for
the
job?
SQL guys looked and see nothing odd. No errors being logged. I
can
save
a
very small file while this is hagging on the larger file.


Is there something to look at relating to Active Cache or
anything
that
I
should check?

Thanks.

 

[Quized again]

Hello Paul. The problem turned out to be the Infrastructure Update. I
uninstalled it and the files saved in about 10 minutes rather than 3 hours.
As it turns out, I missed the warning that this was a known side affect of
the infrastructure update. The August Cumulative Update is supposed to fix
this issue.
Thanks for your help.

you could try enabling client side logging, maybe this will uncover the issue

add this regkey onto the client.

[HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\MS Project]
"WinprojLog"=string:"c:\\temp\\"
"DebugCategory"=dword:ffffffff
"DebugLevel"=dword:ffffffff
"DebugLoadSerCategory"=dword:000003ed

have you deleted the cache on the PC? If not, try doing so (delete the
folder in windows explorer, rather than clearing it down in project pro.

--
Please rate this post if it has helped

http://theprojectserverguru.spaces.live.com

Thank you for the suggestion. I saved one of the files offline as XML and
reimported it. Still hanging at about 94%. What else might I try? Any idea
what the last 10% of the save action is attempting to do?

Sort of strange, I think.