Cube build fails, security check failure

B

Brian Edwards

Windows Server 2003 SP1
Project Server 2003 SP3
SQL Server 2000 8.00.2039
SQL Server 2000 Analysis Services 8.0.2039.0

It seems our Project Server OLAP cube, scheduled to build every night at
1:00 AM, stopped doing so around 2 months ago. As I did not work for this
company at that time, I have no idea what might have happened to have caused
the problem. Based on the error message showing on the Enterprise Features
page on the Project Server Admin site, it sounds as if there is a problem
with the user account that is in charge of running the cube building process.
As I am not remotely a Project Server expert, I could use some help
diagnosing and solving this problem.

The Project Server 2003 Admin page, Enterprise Features shows the cube
status as:

Current Cube Status
The cube scheduled to be built on 4/11/2010 at 2:25 PM failed.
(14) Cube didn't build because of security check failure

The following 5 error messages display in the Application Log of Event
Viewer after each cube build attempt:

1.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
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>

2.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
Description:
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>

3.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
Description:
Component: PCSViews
File: ViewsDrop.cls
Line: -1
Error Number: 0x80004005
Description: <Description><![CDATA[Failed to generate OLAP Cube for the
following Request :
<BuildCubeRequest><CubeUpdate><CubeStart>20040818</CubeStart><CubeFinish>20190511</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectServer;Data Source=stadler;Connect
Timeout=15</DSOConnection><Server>stadler</Server><CubeDB>NexLearnCube</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>3FF827DE-7221-434E-9B08-AC5C264BFFAE</CubeGUID></CubeUpdate></BuildCubeRequest>]]></Description>

4.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
Description:
Component: PCSViews
File: ViewsDrop.cls
Line: -1
Description: <Description><![CDATA[Error Information:
Additional Information: An error occured calling
CallViewGenerator(ProjectServer, -1, <ProjectData>
<EntProjectName><![CDATA[resglobal] ]></EntProjectName>
<EntResourceIDList>*</EntResourceIDList>
<EntResourceStartDate>2004-08-18T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2019-05-11T00:00:00</EntResourceFinishDate> <BuildCubeRequest><CubeUpdate><CubeStart>20040818</CubeStart><CubeFinish>20190511</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectServer;Data Source=stadler;Connect
Timeout=15</DSOConnection><Server>stadler</Server><CubeDB>NexLearnCube</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>3FF827DE-7221-434E-9B08-AC5C264BFFAE</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>)]]></Description>

5.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
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 :-
<ViewsDropData>
<ProjectData>
<EntProjectName><![CDATA[resglobal] ]></EntProjectName>
<EntResourceIDList>*</EntResourceIDList>
<EntResourceStartDate>2004-08-18T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2019-05-11T00:00:00</EntResourceFinishDate> <BuildCubeRequest><CubeUpdate><CubeStart>20040818</CubeStart><CubeFinish>20190511</CubeFinish><Connection>Provider=SQLOLEDB;
Initial Catalog=ProjectServer;Data
Source=stadler</Connection><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectServer;Data Source=stadler;Connect
Timeout=15</DSOConnection><Server>stadler</Server><CubeDB>NexLearnCube</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>3FF827DE-7221-434E-9B08-AC5C264BFFAE</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>
<OrgGuid>ProjectServer</OrgGuid>
<BasePath>ProjectServer</BasePath>
<TimeStamp>2010-04-11T14:11:43</TimeStamp>
</ViewsDropData>]]></Description>
 
B

Brian Edwards

Really? Nobody has even a suggestion?


Brian Edwards said:
Windows Server 2003 SP1
Project Server 2003 SP3
SQL Server 2000 8.00.2039
SQL Server 2000 Analysis Services 8.0.2039.0

It seems our Project Server OLAP cube, scheduled to build every night at
1:00 AM, stopped doing so around 2 months ago. As I did not work for this
company at that time, I have no idea what might have happened to have caused
the problem. Based on the error message showing on the Enterprise Features
page on the Project Server Admin site, it sounds as if there is a problem
with the user account that is in charge of running the cube building process.
As I am not remotely a Project Server expert, I could use some help
diagnosing and solving this problem.

The Project Server 2003 Admin page, Enterprise Features shows the cube
status as:

Current Cube Status
The cube scheduled to be built on 4/11/2010 at 2:25 PM failed.
(14) Cube didn't build because of security check failure

The following 5 error messages display in the Application Log of Event
Viewer after each cube build attempt:

1.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
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>

2.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
Description:
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>

3.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
Description:
Component: PCSViews
File: ViewsDrop.cls
Line: -1
Error Number: 0x80004005
Description: <Description><![CDATA[Failed to generate OLAP Cube for the
following Request :
<BuildCubeRequest><CubeUpdate><CubeStart>20040818</CubeStart><CubeFinish>20190511</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectServer;Data Source=stadler;Connect
Timeout=15</DSOConnection><Server>stadler</Server><CubeDB>NexLearnCube</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>3FF827DE-7221-434E-9B08-AC5C264BFFAE</CubeGUID></CubeUpdate></BuildCubeRequest>]]></Description>

4.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
Description:
Component: PCSViews
File: ViewsDrop.cls
Line: -1
Description: <Description><![CDATA[Error Information:
Additional Information: An error occured calling
CallViewGenerator(ProjectServer, -1, <ProjectData>
<EntProjectName><![CDATA[resglobal] ]></EntProjectName>
<EntResourceIDList>*</EntResourceIDList>
<EntResourceStartDate>2004-08-18T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2019-05-11T00:00:00</EntResourceFinishDate> <BuildCubeRequest><CubeUpdate><CubeStart>20040818</CubeStart><CubeFinish>20190511</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectServer;Data Source=stadler;Connect
Timeout=15</DSOConnection><Server>stadler</Server><CubeDB>NexLearnCube</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>3FF827DE-7221-434E-9B08-AC5C264BFFAE</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>)]]></Description>

5.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
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 :-
<ViewsDropData>
<ProjectData>
<EntProjectName><![CDATA[resglobal] ]></EntProjectName>
<EntResourceIDList>*</EntResourceIDList>
<EntResourceStartDate>2004-08-18T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2019-05-11T00:00:00</EntResourceFinishDate> <BuildCubeRequest><CubeUpdate><CubeStart>20040818</CubeStart><CubeFinish>20190511</CubeFinish><Connection>Provider=SQLOLEDB;
Initial Catalog=ProjectServer;Data
Source=stadler</Connection><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectServer;Data Source=stadler;Connect
Timeout=15</DSOConnection><Server>stadler</Server><CubeDB>NexLearnCube</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>3FF827DE-7221-434E-9B08-AC5C264BFFAE</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>
<OrgGuid>ProjectServer</OrgGuid>
<BasePath>ProjectServer</BasePath>
<TimeStamp>2010-04-11T14:11:43</TimeStamp>
</ViewsDropData>]]></Description>
Click to expand...
 
G

Gary L. Chefetz

Brian:

2010 is coming out in less than a month, so don't be surprised if many folks
have moved on from 2003. I don't like answering 2003 questions any more as
it hurts my brain to try to hold onto that knowledge. In all likelihood, the
account that is running the OLAP build had its password expire or it became
locked. The other outside possibility is bad data. What happens when you
logon as an administrator in Project Server and try the Build Now feature?
Does that also fail?

We've still got some of our books available for 2003. You might consider
investing in those if this is your new role.

--
Gary L. Chefetz, MVP, MCT, MCTIP
Business: http://www.msprojectexperts.com
FAQs: http://www.projectserverexperts.com
BLOG: http://www.projectserverhelp.com

Really? Nobody has even a suggestion?


Brian Edwards said:
Windows Server 2003 SP1
Project Server 2003 SP3
SQL Server 2000 8.00.2039
SQL Server 2000 Analysis Services 8.0.2039.0

It seems our Project Server OLAP cube, scheduled to build every night at
1:00 AM, stopped doing so around 2 months ago. As I did not work for
this
company at that time, I have no idea what might have happened to have
caused
the problem. Based on the error message showing on the Enterprise
Features
page on the Project Server Admin site, it sounds as if there is a problem
with the user account that is in charge of running the cube building
process.
As I am not remotely a Project Server expert, I could use some help
diagnosing and solving this problem.

The Project Server 2003 Admin page, Enterprise Features shows the cube
status as:

Current Cube Status
The cube scheduled to be built on 4/11/2010 at 2:25 PM failed.
(14) Cube didn't build because of security check failure

The following 5 error messages display in the Application Log of Event
Viewer after each cube build attempt:

1.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
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>

2.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
Description:
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>

3.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
Description:
Component: PCSViews
File: ViewsDrop.cls
Line: -1
Error Number: 0x80004005
Description: <Description><![CDATA[Failed to generate OLAP Cube for the
following Request :
<BuildCubeRequest><CubeUpdate><CubeStart>20040818</CubeStart><CubeFinish>20190511</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectServer;Data
Source=stadler;Connect
Timeout=15</DSOConnection><Server>stadler</Server><CubeDB>NexLearnCube</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>3FF827DE-7221-434E-9B08-AC5C264BFFAE</CubeGUID></CubeUpdate></BuildCubeRequest>]]></Description>

4.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
Description:
Component: PCSViews
File: ViewsDrop.cls
Line: -1
Description: <Description><![CDATA[Error Information:
Additional Information: An error occured calling
CallViewGenerator(ProjectServer, -1, <ProjectData>
<EntProjectName><![CDATA[resglobal] ]></EntProjectName>
<EntResourceIDList>*</EntResourceIDList>
<EntResourceStartDate>2004-08-18T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2019-05-11T00:00:00</EntResourceFinishDate>
<BuildCubeRequest><CubeUpdate><CubeStart>20040818</CubeStart><CubeFinish>20190511</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectServer;Data
Source=stadler;Connect
Timeout=15</DSOConnection><Server>stadler</Server><CubeDB>NexLearnCube</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>3FF827DE-7221-434E-9B08-AC5C264BFFAE</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>)]]></Description>

5.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
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 :-
<ViewsDropData>
<ProjectData>
<EntProjectName><![CDATA[resglobal] ]></EntProjectName>
<EntResourceIDList>*</EntResourceIDList>
<EntResourceStartDate>2004-08-18T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2019-05-11T00:00:00</EntResourceFinishDate>
<BuildCubeRequest><CubeUpdate><CubeStart>20040818</CubeStart><CubeFinish>20190511</CubeFinish><Connection>Provider=SQLOLEDB;
Initial Catalog=ProjectServer;Data
Source=stadler</Connection><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectServer;Data
Source=stadler;Connect
Timeout=15</DSOConnection><Server>stadler</Server><CubeDB>NexLearnCube</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>3FF827DE-7221-434E-9B08-AC5C264BFFAE</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>
<OrgGuid>ProjectServer</OrgGuid>
<BasePath>ProjectServer</BasePath>
<TimeStamp>2010-04-11T14:11:43</TimeStamp>
</ViewsDropData>]]></Description>
Click to expand...
Click to expand...
 
B

Brian Edwards

Thanks Gary, unfortunately upgrading right now is out of the question. I'm
certain it has to be bad data, though I have no idea how to locate that data.
I've tried the Update Now utiltiy, tried EditSite, tried PSComPlus, etc.
How do I find out what account is responsible for running the OLAP build?
I've also verified (I think) that the VWNotify.exe memory leak is not the
issue. I'm at a total loss. I've tried everything I can find on the
internet. A call to MS is the next step if I can't get this working this
week.

I've also noticed that in the last few days hundreds of errors every morning
when the cube build is scheduled to fire up:

Component: PjSvrNPE
File: C:\Office\devsp\project\WebClient\source\server\pjnpe\ReminderCache.h
Line: 53
Error Number: 0x80004005
Description: <Description><![CDATA[Assert Detected. The error code was also
included.]]></Description>

I'm sure this is probably related to some setting I have changed recently,
perhaps the account I used with PSComPlus. Unfortunately at this company
nobody who works here has any information regarding what accounts were used
to setup Project Server and the Cube processes, and the guy who set this all
up did so many years ago and can't remember himself. What a mess!

Thanks,
Brian


Gary L. Chefetz said:
Brian:

2010 is coming out in less than a month, so don't be surprised if many folks
have moved on from 2003. I don't like answering 2003 questions any more as
it hurts my brain to try to hold onto that knowledge. In all likelihood, the
account that is running the OLAP build had its password expire or it became
locked. The other outside possibility is bad data. What happens when you
logon as an administrator in Project Server and try the Build Now feature?
Does that also fail?

We've still got some of our books available for 2003. You might consider
investing in those if this is your new role.

--
Gary L. Chefetz, MVP, MCT, MCTIP
Business: http://www.msprojectexperts.com
FAQs: http://www.projectserverexperts.com
BLOG: http://www.projectserverhelp.com

Really? Nobody has even a suggestion?


Brian Edwards said:
Windows Server 2003 SP1
Project Server 2003 SP3
SQL Server 2000 8.00.2039
SQL Server 2000 Analysis Services 8.0.2039.0

It seems our Project Server OLAP cube, scheduled to build every night at
1:00 AM, stopped doing so around 2 months ago. As I did not work for
this
company at that time, I have no idea what might have happened to have
caused
the problem. Based on the error message showing on the Enterprise
Features
page on the Project Server Admin site, it sounds as if there is a problem
with the user account that is in charge of running the cube building
process.
As I am not remotely a Project Server expert, I could use some help
diagnosing and solving this problem.

The Project Server 2003 Admin page, Enterprise Features shows the cube
status as:

Current Cube Status
The cube scheduled to be built on 4/11/2010 at 2:25 PM failed.
(14) Cube didn't build because of security check failure

The following 5 error messages display in the Application Log of Event
Viewer after each cube build attempt:

1.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
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>

2.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
Description:
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>

3.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
Description:
Component: PCSViews
File: ViewsDrop.cls
Line: -1
Error Number: 0x80004005
Description: <Description><![CDATA[Failed to generate OLAP Cube for the
following Request :
<BuildCubeRequest><CubeUpdate><CubeStart>20040818</CubeStart><CubeFinish>20190511</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectServer;Data
Source=stadler;Connect
Timeout=15</DSOConnection><Server>stadler</Server><CubeDB>NexLearnCube</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>3FF827DE-7221-434E-9B08-AC5C264BFFAE</CubeGUID></CubeUpdate></BuildCubeRequest>]]></Description>

4.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
Description:
Component: PCSViews
File: ViewsDrop.cls
Line: -1
Description: <Description><![CDATA[Error Information:
Additional Information: An error occured calling
CallViewGenerator(ProjectServer, -1, <ProjectData>
<EntProjectName><![CDATA[resglobal] ]></EntProjectName>
<EntResourceIDList>*</EntResourceIDList>
<EntResourceStartDate>2004-08-18T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2019-05-11T00:00:00</EntResourceFinishDate>
<BuildCubeRequest><CubeUpdate><CubeStart>20040818</CubeStart><CubeFinish>20190511</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectServer;Data
Source=stadler;Connect
Timeout=15</DSOConnection><Server>stadler</Server><CubeDB>NexLearnCube</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>3FF827DE-7221-434E-9B08-AC5C264BFFAE</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>)]]></Description>

5.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
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 :-
<ViewsDropData>
<ProjectData>
<EntProjectName><![CDATA[resglobal] ]></EntProjectName>
<EntResourceIDList>*</EntResourceIDList>
<EntResourceStartDate>2004-08-18T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2019-05-11T00:00:00</EntResourceFinishDate>
<BuildCubeRequest><CubeUpdate><CubeStart>20040818</CubeStart><CubeFinish>20190511</CubeFinish><Connection>Provider=SQLOLEDB;
Initial Catalog=ProjectServer;Data
Source=stadler</Connection><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectServer;Data
Source=stadler;Connect
Timeout=15</DSOConnection><Server>stadler</Server><CubeDB>NexLearnCube</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>3FF827DE-7221-434E-9B08-AC5C264BFFAE</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>
<OrgGuid>ProjectServer</OrgGuid>
<BasePath>ProjectServer</BasePath>
<TimeStamp>2010-04-11T14:11:43</TimeStamp>
</ViewsDropData>]]></Description>
Click to expand...
Click to expand...
Click to expand...
 
B

Brian Edwards

OK, I don't know exactly what I did to fix the problem, but the cube status
now says the cube is being built. I restarted the VWNOTIFY.exe service
again, maybe that was the fix. Anyway, in the VIEWDROP folder there were a
couple hundred XML files. Before hitting the Update Now button in PWA to
manually build the cube, I moved those XML files to a temp folder. Two quick
questions:

- will I need to re-process all of those XML files, moving them back into
VIEWDROP one at a time or something, or can I safely ignore/delete them?
- assuming one or more of those XML files contains bad data, re-processing
them could point out what project that bad data exists in, correct?

Thanks,
Brian


Gary L. Chefetz said:
Brian:

2010 is coming out in less than a month, so don't be surprised if many folks
have moved on from 2003. I don't like answering 2003 questions any more as
it hurts my brain to try to hold onto that knowledge. In all likelihood, the
account that is running the OLAP build had its password expire or it became
locked. The other outside possibility is bad data. What happens when you
logon as an administrator in Project Server and try the Build Now feature?
Does that also fail?

We've still got some of our books available for 2003. You might consider
investing in those if this is your new role.

--
Gary L. Chefetz, MVP, MCT, MCTIP
Business: http://www.msprojectexperts.com
FAQs: http://www.projectserverexperts.com
BLOG: http://www.projectserverhelp.com

Really? Nobody has even a suggestion?


Brian Edwards said:
Windows Server 2003 SP1
Project Server 2003 SP3
SQL Server 2000 8.00.2039
SQL Server 2000 Analysis Services 8.0.2039.0

It seems our Project Server OLAP cube, scheduled to build every night at
1:00 AM, stopped doing so around 2 months ago. As I did not work for
this
company at that time, I have no idea what might have happened to have
caused
the problem. Based on the error message showing on the Enterprise
Features
page on the Project Server Admin site, it sounds as if there is a problem
with the user account that is in charge of running the cube building
process.
As I am not remotely a Project Server expert, I could use some help
diagnosing and solving this problem.

The Project Server 2003 Admin page, Enterprise Features shows the cube
status as:

Current Cube Status
The cube scheduled to be built on 4/11/2010 at 2:25 PM failed.
(14) Cube didn't build because of security check failure

The following 5 error messages display in the Application Log of Event
Viewer after each cube build attempt:

1.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
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>

2.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
Description:
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>

3.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
Description:
Component: PCSViews
File: ViewsDrop.cls
Line: -1
Error Number: 0x80004005
Description: <Description><![CDATA[Failed to generate OLAP Cube for the
following Request :
<BuildCubeRequest><CubeUpdate><CubeStart>20040818</CubeStart><CubeFinish>20190511</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectServer;Data
Source=stadler;Connect
Timeout=15</DSOConnection><Server>stadler</Server><CubeDB>NexLearnCube</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>3FF827DE-7221-434E-9B08-AC5C264BFFAE</CubeGUID></CubeUpdate></BuildCubeRequest>]]></Description>

4.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
Description:
Component: PCSViews
File: ViewsDrop.cls
Line: -1
Description: <Description><![CDATA[Error Information:
Additional Information: An error occured calling
CallViewGenerator(ProjectServer, -1, <ProjectData>
<EntProjectName><![CDATA[resglobal] ]></EntProjectName>
<EntResourceIDList>*</EntResourceIDList>
<EntResourceStartDate>2004-08-18T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2019-05-11T00:00:00</EntResourceFinishDate>
<BuildCubeRequest><CubeUpdate><CubeStart>20040818</CubeStart><CubeFinish>20190511</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectServer;Data
Source=stadler;Connect
Timeout=15</DSOConnection><Server>stadler</Server><CubeDB>NexLearnCube</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>3FF827DE-7221-434E-9B08-AC5C264BFFAE</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>)]]></Description>

5.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
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 :-
<ViewsDropData>
<ProjectData>
<EntProjectName><![CDATA[resglobal] ]></EntProjectName>
<EntResourceIDList>*</EntResourceIDList>
<EntResourceStartDate>2004-08-18T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2019-05-11T00:00:00</EntResourceFinishDate>
<BuildCubeRequest><CubeUpdate><CubeStart>20040818</CubeStart><CubeFinish>20190511</CubeFinish><Connection>Provider=SQLOLEDB;
Initial Catalog=ProjectServer;Data
Source=stadler</Connection><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectServer;Data
Source=stadler;Connect
Timeout=15</DSOConnection><Server>stadler</Server><CubeDB>NexLearnCube</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>3FF827DE-7221-434E-9B08-AC5C264BFFAE</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>
<OrgGuid>ProjectServer</OrgGuid>
<BasePath>ProjectServer</BasePath>
<TimeStamp>2010-04-11T14:11:43</TimeStamp>
</ViewsDropData>]]></Description>
Click to expand...
Click to expand...
Click to expand...
 
B

Brian Edwards

New status:

"The cube was built on 4/15/2010 at 11:31 AM with errors. The errors
will not prevent use of the cube."

From Event Viewer:

"Component: MSP Resource Availablity Refresh and OLAP Cube Creation
Component (ProjOLAP)
File: PROJOLAPProcess
Line: 0
Description: <Description><![CDATA[Some errors were encountered - but
the process has successfully created an OLAP cube]]></Description>"

"Component: MSP Resource Availablity Refresh and OLAP Cube Creation
Component (ProjOLAP)
File: PROJOLAPProcess
Line: 0
Description: <Description><![CDATA[Process Completed - though 1 or
more non-fatal errors were detected and handled]]></Description>"

I have no idea what the errors were/are.

:-/



Brian Edwards said:
OK, I don't know exactly what I did to fix the problem, but the cube status
now says the cube is being built. I restarted the VWNOTIFY.exe service
again, maybe that was the fix. Anyway, in the VIEWDROP folder there were a
couple hundred XML files. Before hitting the Update Now button in PWA to
manually build the cube, I moved those XML files to a temp folder. Two quick
questions:

- will I need to re-process all of those XML files, moving them back into
VIEWDROP one at a time or something, or can I safely ignore/delete them?
- assuming one or more of those XML files contains bad data, re-processing
them could point out what project that bad data exists in, correct?

Thanks,
Brian


Gary L. Chefetz said:
Brian:

2010 is coming out in less than a month, so don't be surprised if many folks
have moved on from 2003. I don't like answering 2003 questions any more as
it hurts my brain to try to hold onto that knowledge. In all likelihood, the
account that is running the OLAP build had its password expire or it became
locked. The other outside possibility is bad data. What happens when you
logon as an administrator in Project Server and try the Build Now feature?
Does that also fail?

We've still got some of our books available for 2003. You might consider
investing in those if this is your new role.

--
Gary L. Chefetz, MVP, MCT, MCTIP
Business: http://www.msprojectexperts.com
FAQs: http://www.projectserverexperts.com
BLOG: http://www.projectserverhelp.com

Really? Nobody has even a suggestion?


:

Windows Server 2003 SP1
Project Server 2003 SP3
SQL Server 2000 8.00.2039
SQL Server 2000 Analysis Services 8.0.2039.0

It seems our Project Server OLAP cube, scheduled to build every night at
1:00 AM, stopped doing so around 2 months ago. As I did not work for
this
company at that time, I have no idea what might have happened to have
caused
the problem. Based on the error message showing on the Enterprise
Features
page on the Project Server Admin site, it sounds as if there is a problem
with the user account that is in charge of running the cube building
process.
As I am not remotely a Project Server expert, I could use some help
diagnosing and solving this problem.

The Project Server 2003 Admin page, Enterprise Features shows the cube
status as:

Current Cube Status
The cube scheduled to be built on 4/11/2010 at 2:25 PM failed.
(14) Cube didn't build because of security check failure

The following 5 error messages display in the Application Log of Event
Viewer after each cube build attempt:

1.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
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>

2.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
Description:
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>

3.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
Description:
Component: PCSViews
File: ViewsDrop.cls
Line: -1
Error Number: 0x80004005
Description: <Description><![CDATA[Failed to generate OLAP Cube for the
following Request :
<BuildCubeRequest><CubeUpdate><CubeStart>20040818</CubeStart><CubeFinish>20190511</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectServer;Data
Source=stadler;Connect
Timeout=15</DSOConnection><Server>stadler</Server><CubeDB>NexLearnCube</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>3FF827DE-7221-434E-9B08-AC5C264BFFAE</CubeGUID></CubeUpdate></BuildCubeRequest>]]></Description>

4.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
Description:
Component: PCSViews
File: ViewsDrop.cls
Line: -1
Description: <Description><![CDATA[Error Information:
Additional Information: An error occured calling
CallViewGenerator(ProjectServer, -1, <ProjectData>
<EntProjectName><![CDATA[resglobal] ]></EntProjectName>
<EntResourceIDList>*</EntResourceIDList>
<EntResourceStartDate>2004-08-18T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2019-05-11T00:00:00</EntResourceFinishDate>
<BuildCubeRequest><CubeUpdate><CubeStart>20040818</CubeStart><CubeFinish>20190511</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectServer;Data
Source=stadler;Connect
Timeout=15</DSOConnection><Server>stadler</Server><CubeDB>NexLearnCube</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>3FF827DE-7221-434E-9B08-AC5C264BFFAE</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>)]]></Description>

5.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
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 :-
<ViewsDropData>
<ProjectData>
<EntProjectName><![CDATA[resglobal] ]></EntProjectName>
<EntResourceIDList>*</EntResourceIDList>
<EntResourceStartDate>2004-08-18T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2019-05-11T00:00:00</EntResourceFinishDate>
<BuildCubeRequest><CubeUpdate><CubeStart>20040818</CubeStart><CubeFinish>20190511</CubeFinish><Connection>Provider=SQLOLEDB;
Initial Catalog=ProjectServer;Data
Source=stadler</Connection><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectServer;Data
Source=stadler;Connect
Timeout=15</DSOConnection><Server>stadler</Server><CubeDB>NexLearnCube</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>3FF827DE-7221-434E-9B08-AC5C264BFFAE</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>
<OrgGuid>ProjectServer</OrgGuid>
<BasePath>ProjectServer</BasePath>
<TimeStamp>2010-04-11T14:11:43</TimeStamp>
</ViewsDropData>]]></Description>
Click to expand...
Click to expand...
Click to expand...
 
G

Gary L. Chefetz

Brian:

If I remember correctly you use the ComPlus+ utility to set the identity for
cube build. It sounds like you had a clog in the view drop folder. This can
happen if one job gets stuck. You drop the jobs back into the folder in
small batches and see what happens.

--
Gary L. Chefetz, MVP, MCT, MCTIP
Business: http://www.msprojectexperts.com
FAQs: http://www.projectserverexperts.com
BLOG: http://www.projectserverhelp.com

Thanks Gary, unfortunately upgrading right now is out of the question.
I'm
certain it has to be bad data, though I have no idea how to locate that
data.
I've tried the Update Now utiltiy, tried EditSite, tried PSComPlus, etc.
How do I find out what account is responsible for running the OLAP build?
I've also verified (I think) that the VWNotify.exe memory leak is not the
issue. I'm at a total loss. I've tried everything I can find on the
internet. A call to MS is the next step if I can't get this working this
week.

I've also noticed that in the last few days hundreds of errors every
morning
when the cube build is scheduled to fire up:

Component: PjSvrNPE
File:
C:\Office\devsp\project\WebClient\source\server\pjnpe\ReminderCache.h
Line: 53
Error Number: 0x80004005
Description: <Description><![CDATA[Assert Detected. The error code was
also
included.]]></Description>

I'm sure this is probably related to some setting I have changed recently,
perhaps the account I used with PSComPlus. Unfortunately at this company
nobody who works here has any information regarding what accounts were
used
to setup Project Server and the Cube processes, and the guy who set this
all
up did so many years ago and can't remember himself. What a mess!

Thanks,
Brian


Gary L. Chefetz said:
Brian:

2010 is coming out in less than a month, so don't be surprised if many
folks
have moved on from 2003. I don't like answering 2003 questions any more
as
it hurts my brain to try to hold onto that knowledge. In all likelihood,
the
account that is running the OLAP build had its password expire or it
became
locked. The other outside possibility is bad data. What happens when you
logon as an administrator in Project Server and try the Build Now
feature?
Does that also fail?

We've still got some of our books available for 2003. You might consider
investing in those if this is your new role.

--
Gary L. Chefetz, MVP, MCT, MCTIP
Business: http://www.msprojectexperts.com
FAQs: http://www.projectserverexperts.com
BLOG: http://www.projectserverhelp.com

Really? Nobody has even a suggestion?


:

Windows Server 2003 SP1
Project Server 2003 SP3
SQL Server 2000 8.00.2039
SQL Server 2000 Analysis Services 8.0.2039.0

It seems our Project Server OLAP cube, scheduled to build every night
at
1:00 AM, stopped doing so around 2 months ago. As I did not work for
this
company at that time, I have no idea what might have happened to have
caused
the problem. Based on the error message showing on the Enterprise
Features
page on the Project Server Admin site, it sounds as if there is a
problem
with the user account that is in charge of running the cube building
process.
As I am not remotely a Project Server expert, I could use some help
diagnosing and solving this problem.

The Project Server 2003 Admin page, Enterprise Features shows the cube
status as:

Current Cube Status
The cube scheduled to be built on 4/11/2010 at 2:25 PM failed.
(14) Cube didn't build because of security check failure

The following 5 error messages display in the Application Log of Event
Viewer after each cube build attempt:

1.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
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>

2.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
Description:
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>

3.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
Description:
Component: PCSViews
File: ViewsDrop.cls
Line: -1
Error Number: 0x80004005
Description: <Description><![CDATA[Failed to generate OLAP Cube for
the
following Request :
<BuildCubeRequest><CubeUpdate><CubeStart>20040818</CubeStart><CubeFinish>20190511</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectServer;Data
Source=stadler;Connect
Timeout=15</DSOConnection><Server>stadler</Server><CubeDB>NexLearnCube</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>3FF827DE-7221-434E-9B08-AC5C264BFFAE</CubeGUID></CubeUpdate></BuildCubeRequest>]]></Description>

4.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
Description:
Component: PCSViews
File: ViewsDrop.cls
Line: -1
Description: <Description><![CDATA[Error Information:
Additional Information: An error occured calling
CallViewGenerator(ProjectServer, -1, <ProjectData>
<EntProjectName><![CDATA[resglobal] ]></EntProjectName>
<EntResourceIDList>*</EntResourceIDList>
<EntResourceStartDate>2004-08-18T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2019-05-11T00:00:00</EntResourceFinishDate>
<BuildCubeRequest><CubeUpdate><CubeStart>20040818</CubeStart><CubeFinish>20190511</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectServer;Data
Source=stadler;Connect
Timeout=15</DSOConnection><Server>stadler</Server><CubeDB>NexLearnCube</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>3FF827DE-7221-434E-9B08-AC5C264BFFAE</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>)]]></Description>

5.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
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
:-
<ViewsDropData>
<ProjectData>
<EntProjectName><![CDATA[resglobal] ]></EntProjectName>
<EntResourceIDList>*</EntResourceIDList>
<EntResourceStartDate>2004-08-18T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2019-05-11T00:00:00</EntResourceFinishDate>
<BuildCubeRequest><CubeUpdate><CubeStart>20040818</CubeStart><CubeFinish>20190511</CubeFinish><Connection>Provider=SQLOLEDB;
Initial Catalog=ProjectServer;Data
Source=stadler</Connection><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectServer;Data
Source=stadler;Connect
Timeout=15</DSOConnection><Server>stadler</Server><CubeDB>NexLearnCube</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>3FF827DE-7221-434E-9B08-AC5C264BFFAE</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>
<OrgGuid>ProjectServer</OrgGuid>
<BasePath>ProjectServer</BasePath>
<TimeStamp>2010-04-11T14:11:43</TimeStamp>
</ViewsDropData>]]></Description>
Click to expand...
Click to expand...
Click to expand...
 
B

Brian Edwards

numen said:
i have this same issue ... do you have some answers?
Click to expand...


Restarting the Views Notification process combined with emptying the
VIEWDROP folder fixed our issue temporarily. Now we're going back and
re-introducing the XML files to VIEWDROP one at a time to see if they will
process. We know there is some bad data in one of the projects causing these
failures, and we're 99% sure we know which project, we just don't know what
the bad data is. It sounds like you're in the same boat. Find the bad
project then locate and fix the bad data, republish, rebuild the cube. Cross
fingers.
 
B

Brian Edwards

The nightly cube build has continued succeeding with errors, nothing is
getting stuck in VIEWDROP anymore and we re-processed all of the stuck XML
files successfully. However, now the hours being reported for each resource
in current projects are way overboard, but not all by the same factor. Some
resources may be showing hours doubled, some are showing tens of thousands of
hours when they should show < 100 hours. This is in the 'WORK' column in MS
Project Pro 2003.

Could re-processing those XML files have caused this problem?

Is there a solution to this problem other than tearing down Rome and
rebuilding it from scratch? I've come across a ton of people all over the
internet who have experienced this problem at one time or another in the last
5-7 years, but cannot find any information related to wonky hours being
displayed.

-Brian


Gary L. Chefetz said:
Brian:

If I remember correctly you use the ComPlus+ utility to set the identity for
cube build. It sounds like you had a clog in the view drop folder. This can
happen if one job gets stuck. You drop the jobs back into the folder in
small batches and see what happens.

--
Gary L. Chefetz, MVP, MCT, MCTIP
Business: http://www.msprojectexperts.com
FAQs: http://www.projectserverexperts.com
BLOG: http://www.projectserverhelp.com

Thanks Gary, unfortunately upgrading right now is out of the question.
I'm
certain it has to be bad data, though I have no idea how to locate that
data.
I've tried the Update Now utiltiy, tried EditSite, tried PSComPlus, etc.
How do I find out what account is responsible for running the OLAP build?
I've also verified (I think) that the VWNotify.exe memory leak is not the
issue. I'm at a total loss. I've tried everything I can find on the
internet. A call to MS is the next step if I can't get this working this
week.

I've also noticed that in the last few days hundreds of errors every
morning
when the cube build is scheduled to fire up:

Component: PjSvrNPE
File:
C:\Office\devsp\project\WebClient\source\server\pjnpe\ReminderCache.h
Line: 53
Error Number: 0x80004005
Description: <Description><![CDATA[Assert Detected. The error code was
also
included.]]></Description>

I'm sure this is probably related to some setting I have changed recently,
perhaps the account I used with PSComPlus. Unfortunately at this company
nobody who works here has any information regarding what accounts were
used
to setup Project Server and the Cube processes, and the guy who set this
all
up did so many years ago and can't remember himself. What a mess!

Thanks,
Brian


Gary L. Chefetz said:
Brian:

2010 is coming out in less than a month, so don't be surprised if many
folks
have moved on from 2003. I don't like answering 2003 questions any more
as
it hurts my brain to try to hold onto that knowledge. In all likelihood,
the
account that is running the OLAP build had its password expire or it
became
locked. The other outside possibility is bad data. What happens when you
logon as an administrator in Project Server and try the Build Now
feature?
Does that also fail?

We've still got some of our books available for 2003. You might consider
investing in those if this is your new role.

--
Gary L. Chefetz, MVP, MCT, MCTIP
Business: http://www.msprojectexperts.com
FAQs: http://www.projectserverexperts.com
BLOG: http://www.projectserverhelp.com

Really? Nobody has even a suggestion?


:

Windows Server 2003 SP1
Project Server 2003 SP3
SQL Server 2000 8.00.2039
SQL Server 2000 Analysis Services 8.0.2039.0

It seems our Project Server OLAP cube, scheduled to build every night
at
1:00 AM, stopped doing so around 2 months ago. As I did not work for
this
company at that time, I have no idea what might have happened to have
caused
the problem. Based on the error message showing on the Enterprise
Features
page on the Project Server Admin site, it sounds as if there is a
problem
with the user account that is in charge of running the cube building
process.
As I am not remotely a Project Server expert, I could use some help
diagnosing and solving this problem.

The Project Server 2003 Admin page, Enterprise Features shows the cube
status as:

Current Cube Status
The cube scheduled to be built on 4/11/2010 at 2:25 PM failed.
(14) Cube didn't build because of security check failure

The following 5 error messages display in the Application Log of Event
Viewer after each cube build attempt:

1.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
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>

2.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
Description:
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>

3.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
Description:
Component: PCSViews
File: ViewsDrop.cls
Line: -1
Error Number: 0x80004005
Description: <Description><![CDATA[Failed to generate OLAP Cube for
the
following Request :
<BuildCubeRequest><CubeUpdate><CubeStart>20040818</CubeStart><CubeFinish>20190511</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectServer;Data
Source=stadler;Connect
Timeout=15</DSOConnection><Server>stadler</Server><CubeDB>NexLearnCube</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>3FF827DE-7221-434E-9B08-AC5C264BFFAE</CubeGUID></CubeUpdate></BuildCubeRequest>]]></Description>

4.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
Description:
Component: PCSViews
File: ViewsDrop.cls
Line: -1
Description: <Description><![CDATA[Error Information:
Additional Information: An error occured calling
CallViewGenerator(ProjectServer, -1, <ProjectData>
<EntProjectName><![CDATA[resglobal] ]></EntProjectName>
<EntResourceIDList>*</EntResourceIDList>
<EntResourceStartDate>2004-08-18T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2019-05-11T00:00:00</EntResourceFinishDate>
<BuildCubeRequest><CubeUpdate><CubeStart>20040818</CubeStart><CubeFinish>20190511</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectServer;Data
Source=stadler;Connect
Timeout=15</DSOConnection><Server>stadler</Server><CubeDB>NexLearnCube</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>3FF827DE-7221-434E-9B08-AC5C264BFFAE</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>)]]></Description>

5.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
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
:-
<ViewsDropData>
<ProjectData>
<EntProjectName><![CDATA[resglobal] ]></EntProjectName>
<EntResourceIDList>*</EntResourceIDList>
<EntResourceStartDate>2004-08-18T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2019-05-11T00:00:00</EntResourceFinishDate>
<BuildCubeRequest><CubeUpdate><CubeStart>20040818</CubeStart><CubeFinish>20190511</CubeFinish><Connection>Provider=SQLOLEDB;
Initial Catalog=ProjectServer;Data
Source=stadler</Connection><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectServer;Data
Source=stadler;Connect
Timeout=15</DSOConnection><Server>stadler</Server><CubeDB>NexLearnCube</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>3FF827DE-7221-434E-9B08-AC5C264BFFAE</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>
<OrgGuid>ProjectServer</OrgGuid>
<BasePath>ProjectServer</BasePath>
<TimeStamp>2010-04-11T14:11:43</TimeStamp>
</ViewsDropData>]]></Description>
Click to expand...
Click to expand...
Click to expand...
 
G

Gary L. Chefetz

Brian:

Any chance that you've got resources assigned to summary tasks? That would
explain the overstatement of hours.

--
Gary L. Chefetz, MVP, MCT, MCTIP
Business: http://www.msprojectexperts.com
FAQs: http://www.projectserverexperts.com
BLOG: http://www.projectserverhelp.com

The nightly cube build has continued succeeding with errors, nothing is
getting stuck in VIEWDROP anymore and we re-processed all of the stuck XML
files successfully. However, now the hours being reported for each
resource
in current projects are way overboard, but not all by the same factor.
Some
resources may be showing hours doubled, some are showing tens of thousands
of
hours when they should show < 100 hours. This is in the 'WORK' column in
MS
Project Pro 2003.

Could re-processing those XML files have caused this problem?

Is there a solution to this problem other than tearing down Rome and
rebuilding it from scratch? I've come across a ton of people all over the
internet who have experienced this problem at one time or another in the
last
5-7 years, but cannot find any information related to wonky hours being
displayed.

-Brian


Gary L. Chefetz said:
Brian:

If I remember correctly you use the ComPlus+ utility to set the identity
for
cube build. It sounds like you had a clog in the view drop folder. This
can
happen if one job gets stuck. You drop the jobs back into the folder in
small batches and see what happens.

--
Gary L. Chefetz, MVP, MCT, MCTIP
Business: http://www.msprojectexperts.com
FAQs: http://www.projectserverexperts.com
BLOG: http://www.projectserverhelp.com

Thanks Gary, unfortunately upgrading right now is out of the question.
I'm
certain it has to be bad data, though I have no idea how to locate that
data.
I've tried the Update Now utiltiy, tried EditSite, tried PSComPlus,
etc.
How do I find out what account is responsible for running the OLAP
build?
I've also verified (I think) that the VWNotify.exe memory leak is not
the
issue. I'm at a total loss. I've tried everything I can find on the
internet. A call to MS is the next step if I can't get this working
this
week.

I've also noticed that in the last few days hundreds of errors every
morning
when the cube build is scheduled to fire up:

Component: PjSvrNPE
File:
C:\Office\devsp\project\WebClient\source\server\pjnpe\ReminderCache.h
Line: 53
Error Number: 0x80004005
Description: <Description><![CDATA[Assert Detected. The error code was
also
included.]]></Description>

I'm sure this is probably related to some setting I have changed
recently,
perhaps the account I used with PSComPlus. Unfortunately at this
company
nobody who works here has any information regarding what accounts were
used
to setup Project Server and the Cube processes, and the guy who set
this
all
up did so many years ago and can't remember himself. What a mess!

Thanks,
Brian


:

Brian:

2010 is coming out in less than a month, so don't be surprised if many
folks
have moved on from 2003. I don't like answering 2003 questions any
more
as
it hurts my brain to try to hold onto that knowledge. In all
likelihood,
the
account that is running the OLAP build had its password expire or it
became
locked. The other outside possibility is bad data. What happens when
you
logon as an administrator in Project Server and try the Build Now
feature?
Does that also fail?

We've still got some of our books available for 2003. You might
consider
investing in those if this is your new role.

--
Gary L. Chefetz, MVP, MCT, MCTIP
Business: http://www.msprojectexperts.com
FAQs: http://www.projectserverexperts.com
BLOG: http://www.projectserverhelp.com

message
Really? Nobody has even a suggestion?


:

Windows Server 2003 SP1
Project Server 2003 SP3
SQL Server 2000 8.00.2039
SQL Server 2000 Analysis Services 8.0.2039.0

It seems our Project Server OLAP cube, scheduled to build every
night
at
1:00 AM, stopped doing so around 2 months ago. As I did not work
for
this
company at that time, I have no idea what might have happened to
have
caused
the problem. Based on the error message showing on the Enterprise
Features
page on the Project Server Admin site, it sounds as if there is a
problem
with the user account that is in charge of running the cube
building
process.
As I am not remotely a Project Server expert, I could use some
help
diagnosing and solving this problem.

The Project Server 2003 Admin page, Enterprise Features shows the
cube
status as:

Current Cube Status
The cube scheduled to be built on 4/11/2010 at 2:25 PM failed.
(14) Cube didn't build because of security check failure

The following 5 error messages display in the Application Log of
Event
Viewer after each cube build attempt:

1.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
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>

2.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
Description:
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>

3.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
Description:
Component: PCSViews
File: ViewsDrop.cls
Line: -1
Error Number: 0x80004005
Description: <Description><![CDATA[Failed to generate OLAP Cube for
the
following Request :
<BuildCubeRequest><CubeUpdate><CubeStart>20040818</CubeStart><CubeFinish>20190511</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectServer;Data
Source=stadler;Connect
Timeout=15</DSOConnection><Server>stadler</Server><CubeDB>NexLearnCube</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>3FF827DE-7221-434E-9B08-AC5C264BFFAE</CubeGUID></CubeUpdate></BuildCubeRequest>]]></Description>

4.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
Description:
Component: PCSViews
File: ViewsDrop.cls
Line: -1
Description: <Description><![CDATA[Error Information:
Additional Information: An error occured calling
CallViewGenerator(ProjectServer, -1, <ProjectData>
<EntProjectName><![CDATA[resglobal] ]></EntProjectName>
<EntResourceIDList>*</EntResourceIDList>
<EntResourceStartDate>2004-08-18T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2019-05-11T00:00:00</EntResourceFinishDate>
<BuildCubeRequest><CubeUpdate><CubeStart>20040818</CubeStart><CubeFinish>20190511</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectServer;Data
Source=stadler;Connect
Timeout=15</DSOConnection><Server>stadler</Server><CubeDB>NexLearnCube</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>3FF827DE-7221-434E-9B08-AC5C264BFFAE</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>)]]></Description>

5.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
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
:-
<ViewsDropData>
<ProjectData>
<EntProjectName><![CDATA[resglobal] ]></EntProjectName>
<EntResourceIDList>*</EntResourceIDList>
<EntResourceStartDate>2004-08-18T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2019-05-11T00:00:00</EntResourceFinishDate>
<BuildCubeRequest><CubeUpdate><CubeStart>20040818</CubeStart><CubeFinish>20190511</CubeFinish><Connection>Provider=SQLOLEDB;
Initial Catalog=ProjectServer;Data
Source=stadler</Connection><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectServer;Data
Source=stadler;Connect
Timeout=15</DSOConnection><Server>stadler</Server><CubeDB>NexLearnCube</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>3FF827DE-7221-434E-9B08-AC5C264BFFAE</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>
<OrgGuid>ProjectServer</OrgGuid>
<BasePath>ProjectServer</BasePath>
<TimeStamp>2010-04-11T14:11:43</TimeStamp>
</ViewsDropData>]]></Description>
Click to expand...
Click to expand...
Click to expand...
 
B

Brian Edwards

I think that may be it, Gary. The person who reported the failure is fairly
novice with Project so I think she's maybe confused about what she's looking
at. Other people have checked it for me and they don't report the same
problems.

Thanks,
Brian

Gary L. Chefetz said:
Brian:

Any chance that you've got resources assigned to summary tasks? That would
explain the overstatement of hours.

--
Gary L. Chefetz, MVP, MCT, MCTIP
Business: http://www.msprojectexperts.com
FAQs: http://www.projectserverexperts.com
BLOG: http://www.projectserverhelp.com

The nightly cube build has continued succeeding with errors, nothing is
getting stuck in VIEWDROP anymore and we re-processed all of the stuck XML
files successfully. However, now the hours being reported for each
resource
in current projects are way overboard, but not all by the same factor.
Some
resources may be showing hours doubled, some are showing tens of thousands
of
hours when they should show < 100 hours. This is in the 'WORK' column in
MS
Project Pro 2003.

Could re-processing those XML files have caused this problem?

Is there a solution to this problem other than tearing down Rome and
rebuilding it from scratch? I've come across a ton of people all over the
internet who have experienced this problem at one time or another in the
last
5-7 years, but cannot find any information related to wonky hours being
displayed.

-Brian


Gary L. Chefetz said:
Brian:

If I remember correctly you use the ComPlus+ utility to set the identity
for
cube build. It sounds like you had a clog in the view drop folder. This
can
happen if one job gets stuck. You drop the jobs back into the folder in
small batches and see what happens.

--
Gary L. Chefetz, MVP, MCT, MCTIP
Business: http://www.msprojectexperts.com
FAQs: http://www.projectserverexperts.com
BLOG: http://www.projectserverhelp.com

Thanks Gary, unfortunately upgrading right now is out of the question.
I'm
certain it has to be bad data, though I have no idea how to locate that
data.
I've tried the Update Now utiltiy, tried EditSite, tried PSComPlus,
etc.
How do I find out what account is responsible for running the OLAP
build?
I've also verified (I think) that the VWNotify.exe memory leak is not
the
issue. I'm at a total loss. I've tried everything I can find on the
internet. A call to MS is the next step if I can't get this working
this
week.

I've also noticed that in the last few days hundreds of errors every
morning
when the cube build is scheduled to fire up:

Component: PjSvrNPE
File:
C:\Office\devsp\project\WebClient\source\server\pjnpe\ReminderCache.h
Line: 53
Error Number: 0x80004005
Description: <Description><![CDATA[Assert Detected. The error code was
also
included.]]></Description>

I'm sure this is probably related to some setting I have changed
recently,
perhaps the account I used with PSComPlus. Unfortunately at this
company
nobody who works here has any information regarding what accounts were
used
to setup Project Server and the Cube processes, and the guy who set
this
all
up did so many years ago and can't remember himself. What a mess!

Thanks,
Brian


:

Brian:

2010 is coming out in less than a month, so don't be surprised if many
folks
have moved on from 2003. I don't like answering 2003 questions any
more
as
it hurts my brain to try to hold onto that knowledge. In all
likelihood,
the
account that is running the OLAP build had its password expire or it
became
locked. The other outside possibility is bad data. What happens when
you
logon as an administrator in Project Server and try the Build Now
feature?
Does that also fail?

We've still got some of our books available for 2003. You might
consider
investing in those if this is your new role.

--
Gary L. Chefetz, MVP, MCT, MCTIP
Business: http://www.msprojectexperts.com
FAQs: http://www.projectserverexperts.com
BLOG: http://www.projectserverhelp.com

message
Really? Nobody has even a suggestion?


:

Windows Server 2003 SP1
Project Server 2003 SP3
SQL Server 2000 8.00.2039
SQL Server 2000 Analysis Services 8.0.2039.0

It seems our Project Server OLAP cube, scheduled to build every
night
at
1:00 AM, stopped doing so around 2 months ago. As I did not work
for
this
company at that time, I have no idea what might have happened to
have
caused
the problem. Based on the error message showing on the Enterprise
Features
page on the Project Server Admin site, it sounds as if there is a
problem
with the user account that is in charge of running the cube
building
process.
As I am not remotely a Project Server expert, I could use some
help
diagnosing and solving this problem.

The Project Server 2003 Admin page, Enterprise Features shows the
cube
status as:

Current Cube Status
The cube scheduled to be built on 4/11/2010 at 2:25 PM failed.
(14) Cube didn't build because of security check failure

The following 5 error messages display in the Application Log of
Event
Viewer after each cube build attempt:

1.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
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>

2.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
Description:
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>

3.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
Description:
Component: PCSViews
File: ViewsDrop.cls
Line: -1
Error Number: 0x80004005
Description: <Description><![CDATA[Failed to generate OLAP Cube for
the
following Request :
<BuildCubeRequest><CubeUpdate><CubeStart>20040818</CubeStart><CubeFinish>20190511</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectServer;Data
Source=stadler;Connect
Timeout=15</DSOConnection><Server>stadler</Server><CubeDB>NexLearnCube</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>3FF827DE-7221-434E-9B08-AC5C264BFFAE</CubeGUID></CubeUpdate></BuildCubeRequest>]]></Description>

4.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
Description:
Component: PCSViews
File: ViewsDrop.cls
Line: -1
Description: <Description><![CDATA[Error Information:
Additional Information: An error occured calling
CallViewGenerator(ProjectServer, -1, <ProjectData>
<EntProjectName><![CDATA[resglobal] ]></EntProjectName>
<EntResourceIDList>*</EntResourceIDList>
<EntResourceStartDate>2004-08-18T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2019-05-11T00:00:00</EntResourceFinishDate>
<BuildCubeRequest><CubeUpdate><CubeStart>20040818</CubeStart><CubeFinish>20190511</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectServer;Data
Source=stadler;Connect
Timeout=15</DSOConnection><Server>stadler</Server><CubeDB>NexLearnCube</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>3FF827DE-7221-434E-9B08-AC5C264BFFAE</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>)]]></Description>

5.
Source: Microsoft Project Server Tracing Eventlog Provider
Event ID: 2
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
:-
<ViewsDropData>
<ProjectData>
<EntProjectName><![CDATA[resglobal] ]></EntProjectName>
<EntResourceIDList>*</EntResourceIDList>
<EntResourceStartDate>2004-08-18T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2019-05-11T00:00:00</EntResourceFinishDate>
<BuildCubeRequest><CubeUpdate><CubeStart>20040818</CubeStart><CubeFinish>20190511</CubeFinish><Connection>Provider=SQLOLEDB;
Initial Catalog=ProjectServer;Data
Source=stadler</Connection><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectServer;Data
Source=stadler;Connect
Timeout=15</DSOConnection><Server>stadler</Server><CubeDB>NexLearnCube</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>3FF827DE-7221-434E-9B08-AC5C264BFFAE</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>
<OrgGuid>ProjectServer</OrgGuid>
<BasePath>ProjectServer</BasePath>
<TimeStamp>2010-04-11T14:11:43</TimeStamp>
</ViewsDropData>]]></Description>
Click to expand...
Click to expand...
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Cube building problem!! 11
Cube failed - (-2147221492) Unable to save object. 1
OLAP CUBE ERROR in Project Server 2003 environment..Need help!!!!! 1
Having trouble building OLAP cube 2
OLAP Cube creation errors 4
The cube scheduled to be built on xxx at xxx failed. (-2147221411) 0
OLAP cube generation doesn't work anymore 0
Cube building doesn't update PS database? HELP! 2

Top