Microsoft Project 2003 w/Sp1 and Office 2003 w/SP2

[Nelson.G.1]

We are currently running Project Server 2003 with SP1, but one client with MS
Office 2003 SP2, after doing an update process on a project plan, it locked
up project professional on his machine and we haven't been able to open that
project, without locking Project Professional. Also, after this incident, we
haven't been able to build the OLAP cube. It starts initiating and just
hangs, until the Project Server has been rebooted.

 

[Gary L. Chefetz [MVP]]

Nelson:

You shouldn't be using a copy of Project with SP2, especially against a
project server database that hasn't been upgraded. Of course, we now know
that SP2 for Project had a problem and has been temporarily pulled. So, you
need to do the following:

Uninstall Project on that particular client, and reinstall to SP1 and no
higher.
Try to recover the project plan by opening it with a copy of Project
Professional that has been set to manual calculation under options.
If you're unable to retrieve the plan, then you'll need to recover from a
backup
Delete the current version of the plan and import the recovered backup.

Provided that the cube failure is related to corruption in this particular
plan, then that should clear things up. If not, it would be helpful if you'd
have a look at the server application event log and post the related error
messages that you see.




"(e-mail address removed)"

 

[Nelson.G.1]

Thanks Gary,
I've had the back up of the whole database copied on a test server. Can I
only restore the corrupted project plan from that database and not have to
restore the entire database? Also, In the past, when we've deleted a project
plan from project server, we've lost all the actuals that were posted in that
plan. Is there a way I can delete a project and not loose the actuals already
posted?

 

[Gary L. Chefetz [MVP]]

Nelson:

Yes you can restore a single project. Simply create an ODBC connection to
the restored database and open and save the project as an mpp file. When you
restore the backup, you'll be restoring the actual work in stored in the
backup file. Once you import the plan to the server, you'll need to go to
Collaborate Menu and select Publish > Republish and republish all the
assignments in the plan selecting the checkbox to overwrite actual work in
the timesheets in order to push the actual work record into Project Web
Access. If you're using managed time periods, you'll need to turn that
feature off while you do this.




"(e-mail address removed)"

 

[Brian K - Project MVP]

Nelson:

You shouldn't be using a copy of Project with SP2, especially against a
project server database that hasn't been upgraded. Of course, we now know
that SP2 for Project had a problem and has been temporarily pulled. So,
you need to do the following:

It is actually OK to have Project Pro SP2 going against a Server with SP1.
This was from a source within MS that I trust completely on such matters.
That is why you can still download SP2 for Pro but not for Server. They
specifically only pulled the Server SP2.

 

[Gary L. Chefetz [MVP]]

Brian:

I respectfully disagree with you and the trusted source. I've not seen a
preponderance of good things happening when clients and servers are at
different SP levels across all applications, not just Microsoft. I think
it's a bad idea in general, keeping in mind that these same trusted sources
released a dreadfully bad SP to begin with.

 

[Reid McTaggart]

Can we talk specifics, Gary? Do you know of any problem that is demonstrably
caused by using PPro SP2 with PServer SP1?

I've been doing it for a while, and have not yet had any trouble. Of
course, that's no proof; so I'd very much like to know about any problems of
which you are aware.

--
Reid McTaggart
EPM Architect
Microsoft

Brian:

I respectfully disagree with you and the trusted source. I've not seen a
preponderance of good things happening when clients and servers are at
different SP levels across all applications, not just Microsoft. I think
it's a bad idea in general, keeping in mind that these same trusted sources
released a dreadfully bad SP to begin with.

 

[Nelson.G.1]

Gary,
The client with Office SP2 has been taken back to Office SP1 and we were
able to restore the locked project plan. We all thank you for your
assistance. Now to my second problem, in my original note. The cube failure
still exist and we've noticed that it's across all of our server, production
and test. I am attaching the error log from the application events log:

Component: Views Notification Service
File: C:\Office\dev\project\pcportal\source\viewsnotify\ViewNotify.cpp
Line: 130
Error Number: 0x800a0005
Description: <Description><![CDATA[The views processor failed to process the
following document:

<ViewsDropData>
<ProjectData>
<EntProjectName><![CDATA[resglobal] ]></EntProjectName>
<EntResourceIDList>*</EntResourceIDList>
<EntResourceStartDate>2004-03-01T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2016-03-14T00:00:00</EntResourceFinishDate>
<BuildCubeRequest><CubeUpdate><CubeStart>20040301</CubeStart><CubeFinish>20160314</CubeFinish><Connection>Provider=SQLOLEDB;
Initial Catalog=Appl_Project;Data
Source=wgpmpd2</Connection><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=Appl_Project;Data
Source=wgpmpd2</DSOConnection><Server>wgpmpd2</Server><CubeDB>ProjectCubeSP</CubeDB><CubeDesc>Project
Server
OLAP</CubeDesc><BasePath>projectserver</BasePath><CubeGUID>DA17961F-B04F-4AA0-A88F-34BD1F62D7B3</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>
<OrgGuid>projectserver</OrgGuid>
<BasePath>projectserver</BasePath>
<TimeStamp>2005-11-23T06:42:50</TimeStamp>
</ViewsDropData>]]></Description>

Component: PCSViews
File: ViewsDrop.cls
Line: -1
Error Number: 0x5
Description: <Description><![CDATA[Error Information: Invalid procedure call
or argument
Additional Information: An error occured processing the following view :-
------------------------------------------------------------------------------------------------
Component: PCSViews
File: ViewsDrop.cls
Line: -1
Description: <Description><![CDATA[Error Information:
Additional Information: An error occured calling
CallViewGenerator(projectserver, -1,
Component: PCSViews
File: ViewsDrop.cls
Line: -1
Error Number: 0x80004005
Description: <Description><![CDATA[Failed to generate OLAP Cube for the
following Request :
------------------------------------------------------------------------------------------------
Component: MSP Resource Availablity Refresh and OLAP Cube Creation Component
(ProjOLAP)
File: PROJOLAPProcess
Line: 14
Description: <Description><![CDATA[Error parsing the cube gen XML request.
Security check failure.]]></Description>
------------------------------------------------------------------------------------------------
Component: MSP Resource Availablity Refresh and OLAP Cube Creation Component
(ProjOLAP)
File: PROJOLAPProcess
Line: 14
Description: <Description><![CDATA[Error #: 14 Desc. :Cube didn't build
because of security check failure]]></Description>

End of log.

 

[Gary L. Chefetz [MVP]]

Reid:

No, nothing specific, and yes we've been assured it's not a problem. IMO,
and let's make it real clear that IMO = In My Opinion, this is not a best
practice.

Can we talk specifics, Gary? Do you know of any problem that is
demonstrably
caused by using PPro SP2 with PServer SP1?

I've been doing it for a while, and have not yet had any trouble. Of
course, that's no proof; so I'd very much like to know about any problems
of
which you are aware.

--
Reid McTaggart
EPM Architect
Microsoft

 

[Gary L. Chefetz [MVP]]

Reid:

By the way, I have a client who went ahead and installed SP2 for server and
clients when I wasn't looking. So far no problems. Go figure.

Can we talk specifics, Gary? Do you know of any problem that is
demonstrably
caused by using PPro SP2 with PServer SP1?

I've been doing it for a while, and have not yet had any trouble. Of
course, that's no proof; so I'd very much like to know about any problems
of
which you are aware.

--
Reid McTaggart
EPM Architect
Microsoft

 

[Gary L. Chefetz [MVP]]

Nelson:

Am I understanding that your cube did work at one point? Are you building
this for the first time?

Ostensibly, the errors indicate authentication failure which is most often
caused by permissions for the account used for the WSS Com object. We often
see this problem manifest because of hasty installations where the installer
uses his/her own identity and the password expires some number of days
later. It would help to have some more history with regard to the cube
issue.

Checkout the following article to assist you in troubleshooting:
http://support.microsoft.com/default.aspx?scid=kb;en-us;822220

The 0x5 error in the series can come as a result of the authentication
failures or it can be indicative of corruption. Likewise, the authentication
failures can follow corruption as well, so these get to be a bit ambiguous.
I am surprised to see that you've got projects scheduled to 2016 as most
companies don't plan this far out, although I've certainly seen portfolios
pushing the boundaries of Project's date handling capabilities. Is this the
norm in your environment or an anomaly? If it's the latter, finding the
project that's pushing the cube dates out this far might lead to you to
uncovering the source of corruption.






"(e-mail address removed)"

Gary,
The client with Office SP2 has been taken back to Office SP1 and we were
able to restore the locked project plan. We all thank you for your
assistance. Now to my second problem, in my original note. The cube
failure
still exist and we've noticed that it's across all of our server,
production
and test. I am attaching the error log from the application events log:

Component: Views Notification Service
File: C:\Office\dev\project\pcportal\source\viewsnotify\ViewNotify.cpp
Line: 130
Error Number: 0x800a0005
Description: <Description><![CDATA[The views processor failed to process
the
following document:

<ViewsDropData>
<ProjectData>
<EntProjectName><![CDATA[resglobal] ]></EntProjectName>
<EntResourceIDList>*</EntResourceIDList>
<EntResourceStartDate>2004-03-01T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2016-03-14T00:00:00</EntResourceFinishDate>
<BuildCubeRequest><CubeUpdate><CubeStart>20040301</CubeStart><CubeFinish>20160314</CubeFinish><Connection>Provider=SQLOLEDB;
Initial Catalog=Appl_Project;Data
Source=wgpmpd2</Connection><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=Appl_Project;Data
Source=wgpmpd2</DSOConnection><Server>wgpmpd2</Server><CubeDB>ProjectCubeSP</CubeDB><CubeDesc>Project
Server
OLAP</CubeDesc><BasePath>projectserver</BasePath><CubeGUID>DA17961F-B04F-4AA0-A88F-34BD1F62D7B3</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>
<OrgGuid>projectserver</OrgGuid>
<BasePath>projectserver</BasePath>
<TimeStamp>2005-11-23T06:42:50</TimeStamp>
</ViewsDropData>]]></Description>

Component: PCSViews
File: ViewsDrop.cls
Line: -1
Error Number: 0x5
Description: <Description><![CDATA[Error Information: Invalid procedure
call
or argument
Additional Information: An error occured processing the following view :-
------------------------------------------------------------------------------------------------
Component: PCSViews
File: ViewsDrop.cls
Line: -1
Description: <Description><![CDATA[Error Information:
Additional Information: An error occured calling
CallViewGenerator(projectserver, -1,
Component: PCSViews
File: ViewsDrop.cls
Line: -1
Error Number: 0x80004005
Description: <Description><![CDATA[Failed to generate OLAP Cube for the
following Request :
------------------------------------------------------------------------------------------------
Component: MSP Resource Availablity Refresh and OLAP Cube Creation
Component
(ProjOLAP)
File: PROJOLAPProcess
Line: 14
Description: <Description><![CDATA[Error parsing the cube gen XML request.
Security check failure.]]></Description>
------------------------------------------------------------------------------------------------
Component: MSP Resource Availablity Refresh and OLAP Cube Creation
Component
(ProjOLAP)
File: PROJOLAPProcess
Line: 14
Description: <Description><![CDATA[Error #: 14 Desc. :Cube didn't build
because of security check failure]]></Description>

End of log.

Nelson:

You shouldn't be using a copy of Project with SP2, especially against a
project server database that hasn't been upgraded. Of course, we now know
that SP2 for Project had a problem and has been temporarily pulled. So,
you
need to do the following:

Uninstall Project on that particular client, and reinstall to SP1 and no
higher.
Try to recover the project plan by opening it with a copy of Project
Professional that has been set to manual calculation under options.
If you're unable to retrieve the plan, then you'll need to recover from a
backup
Delete the current version of the plan and import the recovered backup.

Provided that the cube failure is related to corruption in this
particular
plan, then that should clear things up. If not, it would be helpful if
you'd
have a look at the server application event log and post the related
error
messages that you see.




"(e-mail address removed)"

 

[Gary L. Chefetz [MVP]]

Nelson:

In the previous post, please read WSS as OLAP with reference to the COM
object.

Nelson:

Am I understanding that your cube did work at one point? Are you building
this for the first time?

Ostensibly, the errors indicate authentication failure which is most often
caused by permissions for the account used for the WSS Com object. We
often see this problem manifest because of hasty installations where the
installer uses his/her own identity and the password expires some number
of days later. It would help to have some more history with regard to the
cube issue.

Checkout the following article to assist you in troubleshooting:
http://support.microsoft.com/default.aspx?scid=kb;en-us;822220

The 0x5 error in the series can come as a result of the authentication
failures or it can be indicative of corruption. Likewise, the
authentication failures can follow corruption as well, so these get to be
a bit ambiguous. I am surprised to see that you've got projects scheduled
to 2016 as most companies don't plan this far out, although I've certainly
seen portfolios pushing the boundaries of Project's date handling
capabilities. Is this the norm in your environment or an anomaly? If it's
the latter, finding the project that's pushing the cube dates out this far
might lead to you to uncovering the source of corruption.






"(e-mail address removed)"

Gary,
The client with Office SP2 has been taken back to Office SP1 and we were
able to restore the locked project plan. We all thank you for your
assistance. Now to my second problem, in my original note. The cube
failure
still exist and we've noticed that it's across all of our server,
production
and test. I am attaching the error log from the application events log:

Component: Views Notification Service
File: C:\Office\dev\project\pcportal\source\viewsnotify\ViewNotify.cpp
Line: 130
Error Number: 0x800a0005
Description: <Description><![CDATA[The views processor failed to process
the
following document:

<ViewsDropData>
<ProjectData>
<EntProjectName><![CDATA[resglobal] ]></EntProjectName>
<EntResourceIDList>*</EntResourceIDList>
<EntResourceStartDate>2004-03-01T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2016-03-14T00:00:00</EntResourceFinishDate>
<BuildCubeRequest><CubeUpdate><CubeStart>20040301</CubeStart><CubeFinish>20160314</CubeFinish><Connection>Provider=SQLOLEDB;
Initial Catalog=Appl_Project;Data
Source=wgpmpd2</Connection><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=Appl_Project;Data
Source=wgpmpd2</DSOConnection><Server>wgpmpd2</Server><CubeDB>ProjectCubeSP</CubeDB><CubeDesc>Project
Server
OLAP</CubeDesc><BasePath>projectserver</BasePath><CubeGUID>DA17961F-B04F-4AA0-A88F-34BD1F62D7B3</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>
<OrgGuid>projectserver</OrgGuid>
<BasePath>projectserver</BasePath>
<TimeStamp>2005-11-23T06:42:50</TimeStamp>
</ViewsDropData>]]></Description>

Component: PCSViews
File: ViewsDrop.cls
Line: -1
Error Number: 0x5
Description: <Description><![CDATA[Error Information: Invalid procedure
call
or argument
Additional Information: An error occured processing the following view :-
------------------------------------------------------------------------------------------------
Component: PCSViews
File: ViewsDrop.cls
Line: -1
Description: <Description><![CDATA[Error Information:
Additional Information: An error occured calling
CallViewGenerator(projectserver, -1,
Component: PCSViews
File: ViewsDrop.cls
Line: -1
Error Number: 0x80004005
Description: <Description><![CDATA[Failed to generate OLAP Cube for the
following Request :
------------------------------------------------------------------------------------------------
Component: MSP Resource Availablity Refresh and OLAP Cube Creation
Component
(ProjOLAP)
File: PROJOLAPProcess
Line: 14
Description: <Description><![CDATA[Error parsing the cube gen XML
request.
Security check failure.]]></Description>
------------------------------------------------------------------------------------------------
Component: MSP Resource Availablity Refresh and OLAP Cube Creation
Component
(ProjOLAP)
File: PROJOLAPProcess
Line: 14
Description: <Description><![CDATA[Error #: 14 Desc. :Cube didn't build
because of security check failure]]></Description>

End of log.

Nelson:

You shouldn't be using a copy of Project with SP2, especially against a
project server database that hasn't been upgraded. Of course, we now
know
that SP2 for Project had a problem and has been temporarily pulled. So,
you
need to do the following:

Uninstall Project on that particular client, and reinstall to SP1 and no
higher.
Try to recover the project plan by opening it with a copy of Project
Professional that has been set to manual calculation under options.
If you're unable to retrieve the plan, then you'll need to recover from
a
backup
Delete the current version of the plan and import the recovered backup.

Provided that the cube failure is related to corruption in this
particular
plan, then that should clear things up. If not, it would be helpful if
you'd
have a look at the server application event log and post the related
error
messages that you see.




"(e-mail address removed)"
We are currently running Project Server 2003 with SP1, but one client
with
MS
Office 2003 SP2, after doing an update process on a project plan, it
locked
up project professional on his machine and we haven't been able to
open
that
project, without locking Project Professional. Also, after this
incident,
we
haven't been able to build the OLAP cube. It starts initiating and
just
hangs, until the Project Server has been rebooted.