Thread: [Solved] Project Server 2003 SP2
View Single Post
 
Old 10-03-2005, 05:19 PM
Microsoft Project
Guest
 
Posts: n/a
Default Re: Project Server 2003 SP2

Thanks to Gary's help in providing me with a database that reproduces the
problem, I have been able to identify the problem and also a workaround.

This issue is definitely new to SP2 and is a result of a performance fix
that was made for better support of a split database deployment.

The basic problem is that the query that populates the Resource Center view
now creates a temp DB but instead of having ALL fields available, it only
includes those that are defined for the view. The query also filters the
results. But, if the field that's in the filter doesn't also exist in the
table, then the failure occurs. The "simple" workaround for now is to add
the particular field(s) to the view. You can add them at the end (right
side) and set their widths = 1 so that users generally won't even notice
they are there.

Sorry for the problem.

Regards,

Adrian Jenkins
Microsoft Project


"Gary L. Chefetz [MVP]" <gary AT chefetz DOT org> wrote in message
news:eV4T42bxFHA.1032@TK2MSFTNGP12.phx.gbl...
Quote:
Guys:

This smacks of an indexing problem in the database. Are you all seeing the
same APP event log errors? Please post a response quickly as we MVPs are
in
Redmond today, and maybe we can get to the bottom of it quickly. Thanks.

--


Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

For Project Server FAQs visit
http://www.projectserverexperts.com

For Project FAQs visit
http://www.mvps.org/project


"Nico Oosthuysen" <demongp@gmail.com> wrote in message
news:1128056371.750110.86680@g49g2000cwa.googlegro ups.com...
Hi Ray,

Was the filter you had based on Resource Type? If so, can you now
create views using a Resource Type Filter? I also managed to remove
the view and create a new one that did not have the Resource Type
filter with no problems. Howerver, when i again try to filter on Type
i get the error again.

Regards,
Nico
Ray wrote:
I just installed SP2 and ran into the same error. I installed in the
correct order, but when I went in and deleted a filter I had on the
View and saved my changes, it worked correctly. Hope this helps.
Cheers, Ray

Nico Oosthuysen wrote:
Hi Rolly, and thanks for replying:

"Have you off-loaded any of the Project Server machine
configurations?

Such as Views Processing, Session Manager and Front-End on separate
machines? Or even a 2-way or 3-way database partition on a separate
SQL
Server?

Plus the Service Pack needs to be installed in the following order:

1. SQL Server --> ProjectServer2003-KB887621-SQLFile-ENU.exe
2. Project Server --> ProjectServer2003SP2-KB887621-FullFile-ENU.exe
3. WSS (templates) --> ProjectServer2003-KB887621-WSSFILE-ENU.exe

Let us know how it turns out "
No, the server is a 2 server installation, with SQL on the one
machine
and Sharepoint and Project Server 2003 on the other one. I performed
the installation as you described above - in that precise order.

Hi Gaurav:

"Did you tried recreating the new view with the same filter.

Let me know. "

Yes, i indeed did try that. I deleted the old view and created a new
on with the Resource Type filter and got precisely the same error.

Thanks for replying so far, folks. I do not think, however, that
this
is something as simple as that, and it may even be strictly related
to
our enviroment only. I would actually like to know as well whether
you
guys have deployed SP2 in all seriousness yet, and have you had any
issues?

Thanks
Nico

Reply With Quote