Project is locked...

R

Ran @Comverse

Hi,

After resources update thier work on the PWA (MSP 2007) , i try to open the
project and I get this message:

"Project XXX cannot be opened at this time becasue it is locked on the
server to apply status updates from team members.

Please try to open the project after some time when the updates may have
been applied."

In the queue I see a job "status updates" which is waiting for optimization.
And it stuck for ever. when I cancell it the project cannot be opened until
I clean my cache, close and reopen MSP.

Please advise...

Thanks,
Ran.
 
P

Paul Conroy

Have you applied Service Pack 1 ? If not, then I'd strongly recommend doing
to see if it resolves your problem.

P
 
R

Ran @Comverse

Yes, both Server and Pro.

Paul Conroy said:
Have you applied Service Pack 1 ? If not, then I'd strongly recommend doing
to see if it resolves your problem.

P
 
P

Paul Conroy

Have you checked the ULS logs for any additional information as to why this
job is failing ?
 
R

Ran @Comverse

Thanks for the help but what is exactly ULS?

Paul Conroy said:
Have you checked the ULS logs for any additional information as to why this
job is failing ?
 
P

Paul Conroy

The ULS logs are the core application logs for WSS/Project Server.

To find the location of the logs, open the diagnostic logging section under
the operations tab in WSS Central Admin.

These logs can get very large which makes finding the information difficult
to find. Can I suggest opening the logs in MS Excel ? This makes
filtering\viewing columns and finding the data you need significantly easier.
Given that there will possibly be a large number of logs, go through the
process of cleaning down the cache etc to get it into a working state then
repro your issue. This will ensure that any issue will be captured at the
top of the logs and therefore easier to find.

You may need to raise the logging level of the Project Queue to verbose
(same page as detailed above) in order to capture a increased amount of
logging. Revert back from verbose as soon as you've finished troubleshooting
so as not to needlessly generate large log files.

You can also try enabling client side logging to try an capture any issues
which are occuring in Proj Pro (see reg key below for enabling client logging)

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

HTH

Paul
 
R

Ran @Comverse

Paul, again thanks... I learned a new thing!!!

I saw this line in the ULS:
[QUEUE] ProjectQ: Group skipped: a5974fc1-4aa1-4540-86b4-74a619000284 type
= StatusApproval

But what does it say???
Why did Project skipped this???

Paul Conroy said:
The ULS logs are the core application logs for WSS/Project Server.

To find the location of the logs, open the diagnostic logging section under
the operations tab in WSS Central Admin.

These logs can get very large which makes finding the information difficult
to find. Can I suggest opening the logs in MS Excel ? This makes
filtering\viewing columns and finding the data you need significantly easier.
Given that there will possibly be a large number of logs, go through the
process of cleaning down the cache etc to get it into a working state then
repro your issue. This will ensure that any issue will be captured at the
top of the logs and therefore easier to find.

You may need to raise the logging level of the Project Queue to verbose
(same page as detailed above) in order to capture a increased amount of
logging. Revert back from verbose as soon as you've finished troubleshooting
so as not to needlessly generate large log files.

You can also try enabling client side logging to try an capture any issues
which are occuring in Proj Pro (see reg key below for enabling client logging)

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

HTH

Paul

Ran @Comverse said:
Thanks for the help but what is exactly ULS?
 
P

Paul Conroy

Is the project checked out ?
Are they any other jobs blocking this from completing (check Queue) ?
Has the assignment been updated in Proj Pro since the updates where
submitted ?

Ran @Comverse said:
Paul, again thanks... I learned a new thing!!!

I saw this line in the ULS:
[QUEUE] ProjectQ: Group skipped: a5974fc1-4aa1-4540-86b4-74a619000284 type
= StatusApproval

But what does it say???
Why did Project skipped this???

Paul Conroy said:
The ULS logs are the core application logs for WSS/Project Server.

To find the location of the logs, open the diagnostic logging section under
the operations tab in WSS Central Admin.

These logs can get very large which makes finding the information difficult
to find. Can I suggest opening the logs in MS Excel ? This makes
filtering\viewing columns and finding the data you need significantly easier.
Given that there will possibly be a large number of logs, go through the
process of cleaning down the cache etc to get it into a working state then
repro your issue. This will ensure that any issue will be captured at the
top of the logs and therefore easier to find.

You may need to raise the logging level of the Project Queue to verbose
(same page as detailed above) in order to capture a increased amount of
logging. Revert back from verbose as soon as you've finished troubleshooting
so as not to needlessly generate large log files.

You can also try enabling client side logging to try an capture any issues
which are occuring in Proj Pro (see reg key below for enabling client logging)

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

HTH

Paul

Ran @Comverse said:
Thanks for the help but what is exactly ULS?

:

Have you checked the ULS logs for any additional information as to why this
job is failing ?

:

Yes, both Server and Pro.

:

Have you applied Service Pack 1 ? If not, then I'd strongly recommend doing
to see if it resolves your problem.

P

:

Hi,

After resources update thier work on the PWA (MSP 2007) , i try to open the
project and I get this message:

"Project XXX cannot be opened at this time becasue it is locked on the
server to apply status updates from team members.

Please try to open the project after some time when the updates may have
been applied."

In the queue I see a job "status updates" which is waiting for optimization.
And it stuck for ever. when I cancell it the project cannot be opened until
I clean my cache, close and reopen MSP.

Please advise...

Thanks,
Ran.
 

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