Project Server 2003 SP2

[demongp]

Hi There,

we decided to be one of the early adopters, and as such i upgraded our
EPM
system to SP2 level last-night. the problem is that now we are getting

errors on any views in the Resource Centre that contain a filter based
on the
Resource Type Field. The error states:

"An error ocurred while trying to access the resources stored in the
database. Either there are too many resources, or the Project Server
may not
have the correct DSN configuration. Contact the Server Administrator."

In the eventlog the only errors that seem to be related here is:

Event Type: Error
Event Source: Microsoft Project Server Tracing Eventlog Provider
Event Category: None
Event ID: 2
Date: 2005/09/28
Time: 11:04:56 PM
User: NT AUTHORITY\LOCAL SERVICE
Computer: EPMSERVER
Description:
File: C:\Office\devsp\project\WebClient\source\utility\pjadorsutil2.cpp
Line: 317
Error Number: 0x80040e14
Description: <Description><![CDATA[Assert Detected. The error code was
also
included.]]></Description>
___________________________________

Component: Microsoft OLE DB Provider for SQL Server
Description: <Description><![CDATA[Invalid column name
'ResourceType'.]]></Description>



The error seems to indicate that the column does not exist, but as far
as i
can see (with some investigation using SQL Profiler and Query analyzer)
the
column does indeed show up in the table MSP_VIEW_RES_STD table.

I have tried the upgrade on a different system, with a backup of our DB
and
the same error still occurs.

What may be the problem here?

Thanks!

 

[Renke Holert [MVP]]

Hi,

did you upgrade all: Project Server, the database and WSS Integration?

Regards from Redmond

Renke Holert

Allocatus - Linking MS Project with Outlook and Notes
http://www.allocatus.com

Project - Das Profibuch
http://www.holert.com/project/profibuch

 

[demongp]

Yes i upgraded all 3 components.

 

[Rolly Perreaux]

Yes i upgraded all 3 components.

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

--
Rolly Perreaux, PMP
Project Server Trainer/Consultant

IT Summit Series
Advanced Microsoft Technology Training
http://www.itsummitseries.com

 

[Gaurav Wason]

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

Let me know.

 

[Nico Oosthuysen]

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

 

[Ray]

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]

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,

 

[Gary L. Chefetz [MVP]]

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.

 

[Microsoft Project]

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

 

[Nico Oosthuysen]

Thanks for the feedback Adrian.

I am interested in what your guys' road ahead is with this - are there
any plans for releasing a hotfix for this?

Sorry for being a pain - I am not asking just for myself however, i
look after a couple of big installations

 

[Microsoft Project]

At this point, no decisions have been made on how to address the issue
though a hotfix is a very possible option.

Regards,

Adrian Jenkins
Microsoft Project

 

[Todd Hutchisnon]

I get this right after the login page..

Microsoft JScript runtime error '800a138f'

'null' is null or not an object

/ProjectServer/Shell/Shell.asp, line 529


In the event log I see the same thing you mentioned-

Event Type: Error
Event Source: Microsoft Project Server Tracing Eventlog Provider
Event Category: None
Event ID: 2
Date: 10/25/2005
Time: 12:54:43 AM
User: NT AUTHORITY\LOCAL SERVICE
Computer: PROJECT
Description:
Component: PjQuery
File:
C:\Office\devsp\project\WebClient\source\server\pjquery\PjGenericQuery.cpp
Line: 1073
Error Number: 0x80040e14
Description: <Description><![CDATA[Assert Detected for Virtual Root
'projectserver'. The error code was also included.]]></Description>


This is such a plan Jane install, I'm not using the WSS I've quite suprised
that this wasn't caught in testing. Very suprised. Project is installed on
a virtual machine, so if someone at MS want's me to upload for testing just
ask.

-Todd

 

[Gary L. Chefetz [MVP]]

Todd:

It sounds as though you haven't installed the service pack correctly. See:

http://www.projectserverexperts.com/Shared Documents/Nullisnull.htm

The application event log error indicates that you also have duplicate
records in the database, most likely assignment records. This is a different
issue than the service pack issue.

I get this right after the login page..

Microsoft JScript runtime error '800a138f'

'null' is null or not an object

/ProjectServer/Shell/Shell.asp, line 529


In the event log I see the same thing you mentioned-

Event Type: Error
Event Source: Microsoft Project Server Tracing Eventlog Provider
Event Category: None
Event ID: 2
Date: 10/25/2005
Time: 12:54:43 AM
User: NT AUTHORITY\LOCAL SERVICE
Computer: PROJECT
Description:
Component: PjQuery
File:
C:\Office\devsp\project\WebClient\source\server\pjquery\PjGenericQuery.cpp
Line: 1073
Error Number: 0x80040e14
Description: <Description><![CDATA[Assert Detected for Virtual Root
'projectserver'. The error code was also included.]]></Description>


This is such a plan Jane install, I'm not using the WSS I've quite
suprised
that this wasn't caught in testing. Very suprised. Project is installed
on
a virtual machine, so if someone at MS want's me to upload for testing
just
ask.

-Todd

At this point, no decisions have been made on how to address the issue
though a hotfix is a very possible option.

Regards,

Adrian Jenkins
Microsoft Project

 

[Todd Hutchisnon]

So working before the SP2 install doesn't elimate this?

Also I ran the SQL script from the cmd prompt, ran for like 5 minutes, and
completed without errors. Using the....

Upgdb112.cmd <sql server name> <database name>


-Todd

Todd:

It sounds as though you haven't installed the service pack correctly. See:

http://www.projectserverexperts.com/Shared Documents/Nullisnull.htm

The application event log error indicates that you also have duplicate
records in the database, most likely assignment records. This is a different
issue than the service pack issue.

I get this right after the login page..

Microsoft JScript runtime error '800a138f'

'null' is null or not an object

/ProjectServer/Shell/Shell.asp, line 529


In the event log I see the same thing you mentioned-

Event Type: Error
Event Source: Microsoft Project Server Tracing Eventlog Provider
Event Category: None
Event ID: 2
Date: 10/25/2005
Time: 12:54:43 AM
User: NT AUTHORITY\LOCAL SERVICE
Computer: PROJECT
Description:
Component: PjQuery
File:
C:\Office\devsp\project\WebClient\source\server\pjquery\PjGenericQuery.cpp
Line: 1073
Error Number: 0x80040e14
Description: <Description><![CDATA[Assert Detected for Virtual Root
'projectserver'. The error code was also included.]]></Description>


This is such a plan Jane install, I'm not using the WSS I've quite
suprised
that this wasn't caught in testing. Very suprised. Project is installed
on
a virtual machine, so if someone at MS want's me to upload for testing
just
ask.

-Todd

At this point, no decisions have been made on how to address the issue
though a hotfix is a very possible option.

Regards,

Adrian Jenkins
Microsoft Project

Thanks for the feedback Adrian.

I am interested in what your guys' road ahead is with this - are there
any plans for releasing a hotfix for this?

Sorry for being a pain - I am not asking just for myself however, i
look after a couple of big installations