EventLog Errors on Cube Rebuild

E

enomagic

Hello,
I am getting some strange errors from the Project Server Event Log
Provider. The errors are at the bottom of this posting.

The initial ones say that it is a failed security check. I have
verified the credentials that it is using are correct. Also, Project
Web Access states the cube was successfully built at 6.53am - all the
errors occur at 6.18am.

These issues started recently, and there have been no changes to
account details. Change control on the server fails to reveal a
change that co-incides with these messages.

Is PWA lying to me about it being successful? I would like these
errors to cease but would settle if I knew that they were harmless.

In summary, getting these errors in eventlog 18 minutes after
initialisation, but PWA states cube build succesful 52 min after
initialisation. Can I ignore these errors? Anyone else seen this?

Interestingly, it only seems to occur with daily cube builds that are
scheduled - not with manually started rebuilds.

Enomagic



------------------------------------------------------------------------------------------------------------

Component: Views Notification Service
File: C:\Office\dev\project\pcportal\source\viewsnotify\ViewNotify.cpp
Line: 125
Error Number: 0x800a0005
Description: <Description><![CDATA[View scheduler received error while
scheduling views]]></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-01-01T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2009-10-29T00:00:00</EntResourceFinishDate>
<BuildCubeRequest><CubeUpdate><CubeStart>20040101</CubeStart><CubeFinish>20091029</CubeFinish><Connection>Provider=SQLOLEDB;User
ID=MSProjectServerUser; Password=password0;Initial
Catalog=projectserver;Data
Source=dbserver</Connection><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=projectserver;Data
Source=dbserver;Connect
Timeout=15</DSOConnection><Server>projserver</Server><CubeDB>projservolap</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>4FB52051-8ED0-4341-9F7F-0120726A8A60</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>
<OrgGuid>ProjectServer</OrgGuid>
<BasePath>ProjectServer</BasePath>
<TimeStamp>2004-07-12T05:45:54</TimeStamp>
</ViewsDropData>]]></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>

--------------------------------------------------------------------------------------------------------------------
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: PCSViews
File: ViewsDrop.cls
Line: -1
Error Number: 0x80004005
Description: <Description><![CDATA[Failed to generate OLAP Cube for
the following Request :

<BuildCubeRequest><CubeUpdate><CubeStart>20040101</CubeStart><CubeFinish>20091029</CubeFinish><Connection>Provider=SQLOLEDB;User
ID=MSProjectServerUser; Password=password0;Initial
Catalog=projectserver;Data
Source=dbserver</Connection><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=projectserver;Data
Source=dbserver;Connect
Timeout=15</DSOConnection><Server>projserver</Server><CubeDB>projservolap</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>4FB52051-8ED0-4341-9F7F-0120726A8A60</CubeGUID></CubeUpdate></BuildCubeRequest>]]></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-01-01T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2009-10-29T00:00:00</EntResourceFinishDate>
<BuildCubeRequest><CubeUpdate><CubeStart>20040101</CubeStart><CubeFinish>20091029</CubeFinish><Connection>Provider=SQLOLEDB;User
ID=MSProjectServerUser; Password=password0;Initial
Catalog=projectserver;Data
Source=dbserver</Connection><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=projectserver;Data
Source=dbserver;Connect
Timeout=15</DSOConnection><Server>projserver</Server><CubeDB>projservolap</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>4FB52051-8ED0-4341-9F7F-0120726A8A60</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>)]]></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-01-01T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2009-10-29T00:00:00</EntResourceFinishDate>
<BuildCubeRequest><CubeUpdate><CubeStart>20040101</CubeStart><CubeFinish>20091029</CubeFinish><Connection>Provider=SQLOLEDB;User
ID=MSProjectServerUser; Password=password0;Initial
Catalog=projectserver;Data
Source=dbserver</Connection><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=projectserver;Data
Source=dbserver;Connect
Timeout=15</DSOConnection><Server>projserver</Server><CubeDB>projservolap</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>4FB52051-8ED0-4341-9F7F-0120726A8A60</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>
<OrgGuid>ProjectServer</OrgGuid>
<BasePath>ProjectServer</BasePath>
<TimeStamp>2004-07-12T05:45:54</TimeStamp>
</ViewsDropData>]]></Description>



------------------------------------------------------------

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-01-01T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2009-10-29T00:00:00</EntResourceFinishDate>
<BuildCubeRequest><CubeUpdate><CubeStart>20040101</CubeStart><CubeFinish>20091029</CubeFinish><Connection>Provider=SQLOLEDB;User
ID=MSProjectServerUser; Password=password0;Initial
Catalog=projectserver;Data
Source=dbserver</Connection><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=projectserver;Data
Source=dbserver;Connect
Timeout=15</DSOConnection><Server>projserver</Server><CubeDB>projservolap</CubeDB><CubeDesc></CubeDesc><BasePath>ProjectServer</BasePath><CubeGUID>4FB52051-8ED0-4341-9F7F-0120726A8A60</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>
<OrgGuid>ProjectServer</OrgGuid>
<BasePath>ProjectServer</BasePath>
<TimeStamp>2004-07-12T05:45:54</TimeStamp>
</ViewsDropData>]]></Description>
 
G

Gary L. Chefetz \(MVP\)

Maybe you can, maybe you can't. Without seeing the errors, who could say?

--

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

-
enomagic said:
Hello,
I am getting some strange errors from the Project Server Event Log
Provider. The errors are at the bottom of this posting.

The initial ones say that it is a failed security check. I have
verified the credentials that it is using are correct. Also, Project
Web Access states the cube was successfully built at 6.53am - all the
errors occur at 6.18am.

These issues started recently, and there have been no changes to
account details. Change control on the server fails to reveal a
change that co-incides with these messages.

Is PWA lying to me about it being successful? I would like these
errors to cease but would settle if I knew that they were harmless.

In summary, getting these errors in eventlog 18 minutes after
initialisation, but PWA states cube build succesful 52 min after
initialisation. Can I ignore these errors? Anyone else seen this?

Interestingly, it only seems to occur with daily cube builds that are
scheduled - not with manually started rebuilds.

Enomagic



-------------------------------------------------------------------------- ----------------------------------

Component: Views Notification Service
File: C:\Office\dev\project\pcportal\source\viewsnotify\ViewNotify.cpp
Line: 125
Error Number: 0x800a0005
Description: <Description><![CDATA[View scheduler received error while
scheduling views]]></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-01-01T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2009-10-29T00:00:00</EntResourceFinishDate>
ID=MSProjectServerUser; Password=password0;Initial
Catalog=projectserver;Data
Source=dbserver said:
Security Info=False;Initial Catalog=projectserver;Data
Source=dbserver;Connect
Timeout=15</DSOConnection><Server>projserver</Server><CubeDB>projservolap</C
ubeDB> said:
</ProjectData>
<OrgGuid>ProjectServer</OrgGuid>
<BasePath>ProjectServer</BasePath>
<TimeStamp>2004-07-12T05:45:54</TimeStamp>
</ViewsDropData>]]></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>

-------------------------------------------------------------------------- ------------------------------------------
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: PCSViews
File: ViewsDrop.cls
Line: -1
Error Number: 0x80004005
Description: <Description><![CDATA[Failed to generate OLAP Cube for
the following Request :
ID=MSProjectServerUser; Password=password0;Initial
Catalog=projectserver;Data
Source=dbserver said:
Security Info=False;Initial Catalog=projectserver;Data
Source=dbserver;Connect
Timeout=15</DSOConnection><Server>projserver</Server><CubeDB>projservolap</C
ubeDB> said:
</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-01-01T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2009-10-29T00:00:00</EntResourceFinishDate>
ID=MSProjectServerUser; Password=password0;Initial
Catalog=projectserver;Data
Source=dbserver said:
Security Info=False;Initial Catalog=projectserver;Data
Source=dbserver;Connect
Timeout=15</DSOConnection><Server>projserver</Server><CubeDB>projservolap</C
ubeDB> said:
</ProjectData>)]]></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-01-01T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2009-10-29T00:00:00</EntResourceFinishDate>
ID=MSProjectServerUser; Password=password0;Initial
Catalog=projectserver;Data
Source=dbserver said:
Security Info=False;Initial Catalog=projectserver;Data
Source=dbserver;Connect
Timeout=15</DSOConnection><Server>projserver</Server><CubeDB>projservolap</C
ubeDB> said:
</ProjectData>
<OrgGuid>ProjectServer</OrgGuid>
<BasePath>ProjectServer</BasePath>
<TimeStamp>2004-07-12T05:45:54</TimeStamp>
</ViewsDropData>]]></Description>



------------------------------------------------------------

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-01-01T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2009-10-29T00:00:00</EntResourceFinishDate>
ID=MSProjectServerUser; Password=password0;Initial
Catalog=projectserver;Data
Source=dbserver said:
Security Info=False;Initial Catalog=projectserver;Data
Source=dbserver;Connect
Timeout=15</DSOConnection><Server>projserver</Server><CubeDB>projservolap</C
ubeDB> said:
</ProjectData>
<OrgGuid>ProjectServer</OrgGuid>
<BasePath>ProjectServer</BasePath>
<TimeStamp>2004-07-12T05:45:54</TimeStamp>
</ViewsDropData>]]></Description>
 
E

enomagic

OK. Not sure what I did to deserve that short sharp meaningless reply.

So apart from the eventlog errors **which I included**, what else do
you expect me to provide? Some direction would certainly help.

Can anyone else possibly direct me as to what I should be looking for,
and could provide in a posting to explain the issue I am having??
Eventlog errors were included with original post.

Thanks
Enomagic.
 
G

Gary L. Chefetz \(MVP\)

Sorry, somehow missed them. I suspect you've got illegal characters in your
resource names or Outline Code names. On the Update resource tables and OLAP
cube page, there are a number of characters listed as not being allowed in
the cube name. These same characters should not appear in any of your
Project or Resource outline codes and they should not be used as part of a
resource name. This is the most common issue when the cube build succeeds
with errors. The next most likely problem is database corruption which
typically results in a failed cube build.

--

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

-
 
E

enomagic

Do you mean corrupt PS2k3 database, or corrput Anaysis Service Repository database?

I don't believe any of the names used use bad characters.

enomagic
 
E

enomagic

OK - so would the following be a potential cause??

Cube name is projservolap - that should be OK.
But,
(e-mail address removed) from the WRES_EMAIL column in
MSP_WEB_RESOURCES table?

Is the hyphon in the email possibly going to give the project server
grief with respect to cube creation?

The illegal chars from manage ent feat. page are
/";:<>|[],.'?~`!$%^&*()-+={}\

Or is it only the RES_NAME that matters?
 
G

Gary L. Chefetz \(MVP\)

They can cause cube problems if they appear in resource names or in
Enterprise outline code names and values

--

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

-
enomagic said:
OK - so would the following be a potential cause??

Cube name is projservolap - that should be OK.
But,
(e-mail address removed) from the WRES_EMAIL column in
MSP_WEB_RESOURCES table?

Is the hyphon in the email possibly going to give the project server
grief with respect to cube creation?

The illegal chars from manage ent feat. page are
/";:<>|[],.'?~`!$%^&*()-+={}\

Or is it only the RES_NAME that matters?


"Gary L. Chefetz \(MVP\)" <gary.nospam at chefetz.org> wrote in message
Sorry, somehow missed them. I suspect you've got illegal characters in your
resource names or Outline Code names. On the Update resource tables and OLAP
cube page, there are a number of characters listed as not being allowed in
the cube name. These same characters should not appear in any of your
Project or Resource outline codes and they should not be used as part of a
resource name. This is the most common issue when the cube build succeeds
with errors. The next most likely problem is database corruption which
typically results in a failed cube build.
 
E

enomagic

OK - considering that the resource names could have chars in them
quite innocently like 'Jo-anne' (as is the case for us) doesn't this
limit how easily PS can be implemented in a enterprise environment??

Would this be worth pointing out to MS product manager for PS?

Enomagic
 
E

enomagic

Not meaning to draw this out, but my point is that whilst not using
those chars in the cube name *is* pointed out as you indicate, from
what you have told me the use of those chars for AD account names
which then feeds into res_name in msp_web_resources from an AD sync
also potentially causes issues - and I do not believe I have seen this
any on the doco (not saying it isn't there) but I have read through
most of the doco (admin, config, install guides etc) and did not see
any mention of AD names having a potential flow through effect to cube
generation. Happy to be corrected if I am mistaken, but I suspect it
would have stuck out if I saw it.

Since hyphons are legit in people's names - this seems to me fairly
difficult to work with unless we put some rule in prohibiting illegit
chars in peoples names for their accounts, and retronaming the several
thousand (or tens of thousands for enterprises) users already
existing.

It just seems odd that the end result is that you can use OLAP unless
one of your resources has a hyphon in their name.

Cheers,
Enomagic.
 
M

Michael Patrick

In my experience the illegal characters can cause
problems pretty much anywhere. If you use the renaming
tool you also need to make sure all of your updates are
processed first or you will generate errors when they try
to update based upon any old names.

All in all a very frustrating problem.
 

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

Top