PS2003-SP2a upgrade.

[Mark Byington]

Tried an SP2a upgrade in our test environment. Install successful. BUT in PWA
now when navigating to the 'Resource Center' (A custom view) I get the follow
message box:

"Either there are too many resources, or the Project Server may not have the
correct DSN configuration. Contact the server administrator" (..which is me!)

The only option is an 'OK' button.

Anyone familiar with this?

Sure hope so, scratching my head here.

Thanks,

 

[NZ Projects]

It's possibel that there was a filter applied to this particular view that
wasn't working


Check and change the view

Login into PWA as administrator
Admin
Manage Views
Resource Center: Resource Summary (or the view you receive this error on)
Modify View
Remove Filter


Save Changes

 

[Mark Byington]

Looked fine to me. I'll re-check.

 

[Brian Tkatch]

Tried an SP2a upgrade in our test environment. Install successful. BUT in PWA
now when navigating to the 'Resource Center' (A custom view) I get the follow
message box:

"Either there are too many resources, or the Project Server may not have the
correct DSN configuration. Contact the server administrator" (..which is me!)

The only option is an 'OK' button.

Anyone familiar with this?

Sure hope so, scratching my head here.

Thanks,

Very familiar!

Microsoft KB article 832588
<URL:http://support.microsoft.com/kb/832588/en-us> deals with this.

The problem is the file "Msadcs.dll" not being anonymously accessible.
There are a number of reasons this can happen. The installation of the
SP deleted your PWA virtual directory and re-created it. That
sometimes resets rights.

In our case, for example, we had installed SiteMinder. SiteMinder has
a wonderful quirk in that it only protects virtual directories created
*after* its installation. Previously existing virtual directories seem
to get off with the grandfather clause. When we installed SP2a, it
re-created the directory, throwing it under protection (thus
disallowing anonymous access), and so we needed to unprotect the file
manually.

Check the KB article, see if it helps, if not, try to figure out what
is protecting that file.

B.