Project Center cannot access the project(s) you are trying to view

[Deano]

Hi all...

After sometime using Project 2007 quite happily via Project Server on
sharepoint, we received this message within Project Center:

"Project Center cannot access the project(s) you are trying to view. It is
most likely that you either don't have permissions to view the project,
another user has deleted this project(s) before you were able to view it or
that another user is in the process of publishing the project."

All Projects are checked in etc.

The only way I've found of removing it is by reinstalling Project Server,
which is obviously not a sustainable method of recovery!

Can anyone help with this, I can't find anything via Google? Many thanks.

 

[Gary L. Chefetz [MVP]]

Deano:

The only thing I can think of that might cause this is database corruption,
that would require some diagnostics to determine the cause.

--

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

 

[Deano]

But why would this keep happening, and why does an install over the top fix
it every time?

Cheers.

 

[Brian Smith \(MSFT\)]

Hi Deano,

Before jumping to the conclusion of corruption (which would not be fixed by
a re-install of the application - as the data in the database would not
change) I would consider this to be related to a SQL timeout - and would
suspect you could see this in either the ULS logs or by profiling SQL
Server. It will unfortunately give the error message making it look like a
permissions thing. Depending on the power of your SQL Server it can happen
if you have several thousand projects in your project view - or several
thousand tasks in the detail view. Sometimes just refreshing will show the
view correctly as the query will have completed and be cached for the next
request. Also re-building the indexes for the Projects and Tasks tables can
help. This isn't adding any new indices - just refreshing the information
SQL Server can use to optimize the query for the current indices We are
looking at this problem and the first potential fix is to allow a longer
timeout so that the queries can complete.

Best regards,

Brian.

 

[Gary L. Chefetz [MVP]]

Brian:

Is this addressed in the service pack?

Deano:

Do you have a SQL DB Maintenance plan running? If not, set one up, if so,
add index optimization to it.

--

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

 

[Bill Mc]

This sounds just like the error that I was receiving about a month ago. And
it was database performance related. You or your DBA might want to try
updating the
index statistics for the Published project database via the sp_updatestats
stored procedure. This fixed the problem for us.

 

[Deano]

Thanks for the tips everyone.

This is the kind of reasoning I've seen else where, but what I would say is
that we only several projects all which only have a dozen or so tasks.

This is what concerns me.

(We're just at the testing phase).

 

[Matt]

I find myself in the same situation. Have you been able to make any progress?

 

[Matt]

I just called Microsoft Support regarding this issue. They said if you have
IIS compression enabled for .ASPX and .ASMX files it can cause this issue. I
disabled compression and everything started to work just fine. It was in an
internal knowledge base article and hasn't been published as a general
knowledge base article.

 

[Assaf]

Hi,
I'm experiencing similar timeout problem when trying to use Build Team from
Enterprise option.
I have ~10500 resources on my project server and when I get to the resources
list it's empty and the event log has a timeout error message.
I tried running sp_updatestats and the IIS compression is disabled on the
server - this sums up the suggested solutions, and the problem still occurs.

Is there any hotfix available for this issue?

Thanks,
Assaf

 

[Buhari]

Hi,

Is there any solution for this issue? I tried both the possiblities like
updating the index statistics using sp_updatestats and disabling IIS
compression.


Thanks,
Buhari

 

[Ashish Gedam]

Dear All,

Simple solution of this issue is, please increase the Application Pool
Performance itdle timeout.

It works with me, i tried out with 7000 activity projects.

Thanks & Regards,

Ashish Gedam

 

[Sara]

What if this error message is only occuring for one individual? This person
is trying to Edit Project Properties when he receives the message. Other
users can access this just fine and he can access it when using someone
else's machine. This is machine specific, but what can determine what it is
his machine?

 

[MisterR]

It's work for me!
Thanks

Dear All,

Simple solution of this issue is, please increase the Application Pool
Performance itdle timeout.

It works with me, i tried out with 7000 activity projects.

Thanks & Regards,

Ashish Gedam