CANNOT GENERATE OLAP CUBE

A

Angel

Project Server 2003. OLAP Cube was not initially setup to run so I went back
to the installation documentation to try to find all the steps. What am I
missing???

Installed analysis services (same SP as SQL)
Added users to OLAP Administrators group on both DB & Application server
Created Analysis DB in SQL
Gave OLAP Admin group DB_Owner rights
Migrated repository in Analysis Svcs to newly created Analysis DB
Ran PSComPlus
Kicked off cube

Error is below. Oh and yes, we have gone through the Res pool and enterprise
codes to make sure there are no special characters.


Event Type: Error
Event Source: Microsoft Project Server Tracing Eventlog Provider
Event Category: None
Event ID: 2
Date: 6/18/2008
Time: 4:11:22 PM
User: NT AUTHORITY\LOCAL SERVICE
Computer: BRI-PROJECT001
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>2006-08-01T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2011-02-24T00:00:00</EntResourceFinishDate>

<BuildCubeRequest><CubeUpdate><CubeStart>20060801</CubeStart><CubeFinish>20110224</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectSP1;Data
Source=bri-sql001\ssdb01</DSOConnection><Server>bri-project001</Server><CubeDB>OneWebster</CubeDB><CubeDesc>Cube
created for analysis of
OneWebster</CubeDesc><BasePath>projectserver</BasePath><CubeGUID>51F3306B-8014-4199-BBF9-1786A0F32029</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>)]]></Description>
 
A

Angel

OK, same problem but I just thought I'd add that the DB never shows up in
Analysis Services under the Analysis Server name. The XML file generated when
the cube is kicked off is getting processed and it seems like the cube is
failing shortly thereafter (about 20 mins after kickoff).
 
A

Angel

I'm still at a loss and have not received any other recommendations. Any
thougths would be welcomed!!!!

Additional thoughts:
In the Analysis Server, if I click on edit repository connection, I see
this: (please note Initial Catalog = Anallysis _Services, which is the DB we
defined as the Analysis Repository DB)

Provider=SQLOLEDB.1;Integrated Security=SSPI;Initial
Catalog=Analysis_Services;Data Source=bri-sql001\ssdb01;Use Procedure for
Prepare=1;Auto Translate=True;Packet Size=4096;Workstation
ID=BRI-PROJECT001;Use Encryption for Data=False;Tag with column collation
when possible=False

But the error message says the intial catalog is ProjectSP1 (which is the
Project Server DB - not the analysis services DB).

Is this the problem? How do I redefine which DB the analysis server is
pointing to if I've migrated the repository to the analysis services DB
already?



Angel said:
OK, same problem but I just thought I'd add that the DB never shows up in
Analysis Services under the Analysis Server name. The XML file generated when
the cube is kicked off is getting processed and it seems like the cube is
failing shortly thereafter (about 20 mins after kickoff).

Angel said:
Project Server 2003. OLAP Cube was not initially setup to run so I went back
to the installation documentation to try to find all the steps. What am I
missing???

Installed analysis services (same SP as SQL)
Added users to OLAP Administrators group on both DB & Application server
Created Analysis DB in SQL
Gave OLAP Admin group DB_Owner rights
Migrated repository in Analysis Svcs to newly created Analysis DB
Ran PSComPlus
Kicked off cube

Error is below. Oh and yes, we have gone through the Res pool and enterprise
codes to make sure there are no special characters.


Event Type: Error
Event Source: Microsoft Project Server Tracing Eventlog Provider
Event Category: None
Event ID: 2
Date: 6/18/2008
Time: 4:11:22 PM
User: NT AUTHORITY\LOCAL SERVICE
Computer: BRI-PROJECT001
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>2006-08-01T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2011-02-24T00:00:00</EntResourceFinishDate>

<BuildCubeRequest><CubeUpdate><CubeStart>20060801</CubeStart><CubeFinish>20110224</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectSP1;Data
Source=bri-sql001\ssdb01</DSOConnection><Server>bri-project001</Server><CubeDB>OneWebster</CubeDB><CubeDesc>Cube
created for analysis of
OneWebster</CubeDesc><BasePath>projectserver</BasePath><CubeGUID>51F3306B-8014-4199-BBF9-1786A0F32029</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>)]]></Description>
Click to expand...
Click to expand...
 
P

Paul Conroy

What version of SQL are you using?

Have you installed DSO (sql 2000) or Backwared compatability components
(sql2005) on the Project Server ?
--
Did this post help you. Consider passing on the good will by making a
donation this great charity.
http://www.fundraiseonline.co.nz/TheProjectServerGuru/

http://theprojectserverguru.spaces.live.com


Angel said:
I'm still at a loss and have not received any other recommendations. Any
thougths would be welcomed!!!!

Additional thoughts:
In the Analysis Server, if I click on edit repository connection, I see
this: (please note Initial Catalog = Anallysis _Services, which is the DB we
defined as the Analysis Repository DB)

Provider=SQLOLEDB.1;Integrated Security=SSPI;Initial
Catalog=Analysis_Services;Data Source=bri-sql001\ssdb01;Use Procedure for
Prepare=1;Auto Translate=True;Packet Size=4096;Workstation
ID=BRI-PROJECT001;Use Encryption for Data=False;Tag with column collation
when possible=False

But the error message says the intial catalog is ProjectSP1 (which is the
Project Server DB - not the analysis services DB).

Is this the problem? How do I redefine which DB the analysis server is
pointing to if I've migrated the repository to the analysis services DB
already?



Angel said:
OK, same problem but I just thought I'd add that the DB never shows up in
Analysis Services under the Analysis Server name. The XML file generated when
the cube is kicked off is getting processed and it seems like the cube is
failing shortly thereafter (about 20 mins after kickoff).

Angel said:
Project Server 2003. OLAP Cube was not initially setup to run so I went back
to the installation documentation to try to find all the steps. What am I
missing???

Installed analysis services (same SP as SQL)
Added users to OLAP Administrators group on both DB & Application server
Created Analysis DB in SQL
Gave OLAP Admin group DB_Owner rights
Migrated repository in Analysis Svcs to newly created Analysis DB
Ran PSComPlus
Kicked off cube

Error is below. Oh and yes, we have gone through the Res pool and enterprise
codes to make sure there are no special characters.


Event Type: Error
Event Source: Microsoft Project Server Tracing Eventlog Provider
Event Category: None
Event ID: 2
Date: 6/18/2008
Time: 4:11:22 PM
User: NT AUTHORITY\LOCAL SERVICE
Computer: BRI-PROJECT001
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>2006-08-01T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2011-02-24T00:00:00</EntResourceFinishDate>

<BuildCubeRequest><CubeUpdate><CubeStart>20060801</CubeStart><CubeFinish>20110224</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectSP1;Data
Source=bri-sql001\ssdb01</DSOConnection><Server>bri-project001</Server><CubeDB>OneWebster</CubeDB><CubeDesc>Cube
created for analysis of
OneWebster</CubeDesc><BasePath>projectserver</BasePath><CubeGUID>51F3306B-8014-4199-BBF9-1786A0F32029</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>)]]></Description>
Click to expand...
Click to expand...
Click to expand...
 
A

Angel

It's been a long time since I set up a cube but I thought DSO was installed
when Analysis Services are installed and you only had to install DSO on the
other front-end servers that aren't running Analysis services? In this system
there is a DB server running SQL 2000 and a front-end app server. We
installed Analysis Services on the the front-end server.

The funny thing is that we finally got a cube to run on Friday. It finally
ran after we cleaned up the DB (we kept having crap data creep back into the
DB even after cleaning up the plans. We finally saved a few offline because
everytime we would remove the crap data and save and close the plan, we'd
open the plan again and the data would show up again). I thought that was the
final thing we had to overcome. But then when we tried to generate the cube
again yesterday, it failed with the DSO error. I'm not sure how it would have
ever run in the first place if this is indeed the problem. So perhaps DSO is
NOT installed with Analysis Services??

Thanks for the response.

Paul Conroy said:
What version of SQL are you using?

Have you installed DSO (sql 2000) or Backwared compatability components
(sql2005) on the Project Server ?
--
Did this post help you. Consider passing on the good will by making a
donation this great charity.
http://www.fundraiseonline.co.nz/TheProjectServerGuru/

http://theprojectserverguru.spaces.live.com


Angel said:
I'm still at a loss and have not received any other recommendations. Any
thougths would be welcomed!!!!

Additional thoughts:
In the Analysis Server, if I click on edit repository connection, I see
this: (please note Initial Catalog = Anallysis _Services, which is the DB we
defined as the Analysis Repository DB)

Provider=SQLOLEDB.1;Integrated Security=SSPI;Initial
Catalog=Analysis_Services;Data Source=bri-sql001\ssdb01;Use Procedure for
Prepare=1;Auto Translate=True;Packet Size=4096;Workstation
ID=BRI-PROJECT001;Use Encryption for Data=False;Tag with column collation
when possible=False

But the error message says the intial catalog is ProjectSP1 (which is the
Project Server DB - not the analysis services DB).

Is this the problem? How do I redefine which DB the analysis server is
pointing to if I've migrated the repository to the analysis services DB
already?



Angel said:
OK, same problem but I just thought I'd add that the DB never shows up in
Analysis Services under the Analysis Server name. The XML file generated when
the cube is kicked off is getting processed and it seems like the cube is
failing shortly thereafter (about 20 mins after kickoff).

:

Project Server 2003. OLAP Cube was not initially setup to run so I went back
to the installation documentation to try to find all the steps. What am I
missing???

Installed analysis services (same SP as SQL)
Added users to OLAP Administrators group on both DB & Application server
Created Analysis DB in SQL
Gave OLAP Admin group DB_Owner rights
Migrated repository in Analysis Svcs to newly created Analysis DB
Ran PSComPlus
Kicked off cube

Error is below. Oh and yes, we have gone through the Res pool and enterprise
codes to make sure there are no special characters.


Event Type: Error
Event Source: Microsoft Project Server Tracing Eventlog Provider
Event Category: None
Event ID: 2
Date: 6/18/2008
Time: 4:11:22 PM
User: NT AUTHORITY\LOCAL SERVICE
Computer: BRI-PROJECT001
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>2006-08-01T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2011-02-24T00:00:00</EntResourceFinishDate>

<BuildCubeRequest><CubeUpdate><CubeStart>20060801</CubeStart><CubeFinish>20110224</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectSP1;Data
Source=bri-sql001\ssdb01</DSOConnection><Server>bri-project001</Server><CubeDB>OneWebster</CubeDB><CubeDesc>Cube
created for analysis of
OneWebster</CubeDesc><BasePath>projectserver</BasePath><CubeGUID>51F3306B-8014-4199-BBF9-1786A0F32029</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>)]]></Description>
Click to expand...
Click to expand...
Click to expand...
 
A

Angel

So I'm thinking the error message is just wrong... the cube will complete if
we use the "Update Now" opton. It's when we try to schedule it that we get
the DSO Error. Sounds to me like it's more of an issue with the Scheduling
Process. Any thoughts?

Angel said:
It's been a long time since I set up a cube but I thought DSO was installed
when Analysis Services are installed and you only had to install DSO on the
other front-end servers that aren't running Analysis services? In this system
there is a DB server running SQL 2000 and a front-end app server. We
installed Analysis Services on the the front-end server.

The funny thing is that we finally got a cube to run on Friday. It finally
ran after we cleaned up the DB (we kept having crap data creep back into the
DB even after cleaning up the plans. We finally saved a few offline because
everytime we would remove the crap data and save and close the plan, we'd
open the plan again and the data would show up again). I thought that was the
final thing we had to overcome. But then when we tried to generate the cube
again yesterday, it failed with the DSO error. I'm not sure how it would have
ever run in the first place if this is indeed the problem. So perhaps DSO is
NOT installed with Analysis Services??

Thanks for the response.

Paul Conroy said:
What version of SQL are you using?

Have you installed DSO (sql 2000) or Backwared compatability components
(sql2005) on the Project Server ?
--
Did this post help you. Consider passing on the good will by making a
donation this great charity.
http://www.fundraiseonline.co.nz/TheProjectServerGuru/

http://theprojectserverguru.spaces.live.com


Angel said:
I'm still at a loss and have not received any other recommendations. Any
thougths would be welcomed!!!!

Additional thoughts:
In the Analysis Server, if I click on edit repository connection, I see
this: (please note Initial Catalog = Anallysis _Services, which is the DB we
defined as the Analysis Repository DB)

Provider=SQLOLEDB.1;Integrated Security=SSPI;Initial
Catalog=Analysis_Services;Data Source=bri-sql001\ssdb01;Use Procedure for
Prepare=1;Auto Translate=True;Packet Size=4096;Workstation
ID=BRI-PROJECT001;Use Encryption for Data=False;Tag with column collation
when possible=False

But the error message says the intial catalog is ProjectSP1 (which is the
Project Server DB - not the analysis services DB).

Is this the problem? How do I redefine which DB the analysis server is
pointing to if I've migrated the repository to the analysis services DB
already?



:

OK, same problem but I just thought I'd add that the DB never shows up in
Analysis Services under the Analysis Server name. The XML file generated when
the cube is kicked off is getting processed and it seems like the cube is
failing shortly thereafter (about 20 mins after kickoff).

:

Project Server 2003. OLAP Cube was not initially setup to run so I went back
to the installation documentation to try to find all the steps. What am I
missing???

Installed analysis services (same SP as SQL)
Added users to OLAP Administrators group on both DB & Application server
Created Analysis DB in SQL
Gave OLAP Admin group DB_Owner rights
Migrated repository in Analysis Svcs to newly created Analysis DB
Ran PSComPlus
Kicked off cube

Error is below. Oh and yes, we have gone through the Res pool and enterprise
codes to make sure there are no special characters.


Event Type: Error
Event Source: Microsoft Project Server Tracing Eventlog Provider
Event Category: None
Event ID: 2
Date: 6/18/2008
Time: 4:11:22 PM
User: NT AUTHORITY\LOCAL SERVICE
Computer: BRI-PROJECT001
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>2006-08-01T00:00:00</EntResourceStartDate>
<EntResourceFinishDate>2011-02-24T00:00:00</EntResourceFinishDate>

<BuildCubeRequest><CubeUpdate><CubeStart>20060801</CubeStart><CubeFinish>20110224</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectSP1;Data
Source=bri-sql001\ssdb01</DSOConnection><Server>bri-project001</Server><CubeDB>OneWebster</CubeDB><CubeDesc>Cube
created for analysis of
OneWebster</CubeDesc><BasePath>projectserver</BasePath><CubeGUID>51F3306B-8014-4199-BBF9-1786A0F32029</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>)]]></Description>
Click to expand...
Click to expand...
Click to expand...
 
G

Gary L. Chefetz [MVP]

Sounds like a permissions issue for the account you're using for the COM+
identity.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com


Angel said:
So I'm thinking the error message is just wrong... the cube will complete
if
we use the "Update Now" opton. It's when we try to schedule it that we get
the DSO Error. Sounds to me like it's more of an issue with the Scheduling
Process. Any thoughts?

Angel said:
It's been a long time since I set up a cube but I thought DSO was
installed
when Analysis Services are installed and you only had to install DSO on
the
other front-end servers that aren't running Analysis services? In this
system
there is a DB server running SQL 2000 and a front-end app server. We
installed Analysis Services on the the front-end server.

The funny thing is that we finally got a cube to run on Friday. It
finally
ran after we cleaned up the DB (we kept having crap data creep back into
the
DB even after cleaning up the plans. We finally saved a few offline
because
everytime we would remove the crap data and save and close the plan, we'd
open the plan again and the data would show up again). I thought that was
the
final thing we had to overcome. But then when we tried to generate the
cube
again yesterday, it failed with the DSO error. I'm not sure how it would
have
ever run in the first place if this is indeed the problem. So perhaps DSO
is
NOT installed with Analysis Services??

Thanks for the response.

Paul Conroy said:
What version of SQL are you using?

Have you installed DSO (sql 2000) or Backwared compatability components
(sql2005) on the Project Server ?
--
Did this post help you. Consider passing on the good will by making a
donation this great charity.
http://www.fundraiseonline.co.nz/TheProjectServerGuru/

http://theprojectserverguru.spaces.live.com


:

I'm still at a loss and have not received any other recommendations.
Any
thougths would be welcomed!!!!

Additional thoughts:
In the Analysis Server, if I click on edit repository connection, I
see
this: (please note Initial Catalog = Anallysis _Services, which is
the DB we
defined as the Analysis Repository DB)

Provider=SQLOLEDB.1;Integrated Security=SSPI;Initial
Catalog=Analysis_Services;Data Source=bri-sql001\ssdb01;Use Procedure
for
Prepare=1;Auto Translate=True;Packet Size=4096;Workstation
ID=BRI-PROJECT001;Use Encryption for Data=False;Tag with column
collation
when possible=False

But the error message says the intial catalog is ProjectSP1 (which is
the
Project Server DB - not the analysis services DB).

Is this the problem? How do I redefine which DB the analysis server
is
pointing to if I've migrated the repository to the analysis services
DB
already?



:

OK, same problem but I just thought I'd add that the DB never shows
up in
Analysis Services under the Analysis Server name. The XML file
generated when
the cube is kicked off is getting processed and it seems like the
cube is
failing shortly thereafter (about 20 mins after kickoff).

:

Project Server 2003. OLAP Cube was not initially setup to run so
I went back
to the installation documentation to try to find all the steps.
What am I
missing???

Installed analysis services (same SP as SQL)
Added users to OLAP Administrators group on both DB & Application
server
Created Analysis DB in SQL
Gave OLAP Admin group DB_Owner rights
Migrated repository in Analysis Svcs to newly created Analysis DB
Ran PSComPlus
Kicked off cube

Error is below. Oh and yes, we have gone through the Res pool and
enterprise
codes to make sure there are no special characters.


Event Type: Error
Event Source: Microsoft Project Server Tracing Eventlog Provider
Event Category: None
Event ID: 2
Date: 6/18/2008
Time: 4:11:22 PM
User: NT AUTHORITY\LOCAL SERVICE
Computer: BRI-PROJECT001
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>2006-08-01T00:00:00</EntResourceStartDate>

<EntResourceFinishDate>2011-02-24T00:00:00</EntResourceFinishDate>

<BuildCubeRequest><CubeUpdate><CubeStart>20060801</CubeStart><CubeFinish>20110224</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectSP1;Data
Source=bri-sql001\ssdb01</DSOConnection><Server>bri-project001</Server><CubeDB>OneWebster</CubeDB><CubeDesc>Cube
created for analysis of
OneWebster</CubeDesc><BasePath>projectserver</BasePath><CubeGUID>51F3306B-8014-4199-BBF9-1786A0F32029</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>)]]></Description>
Click to expand...
Click to expand...
Click to expand...
 
A

Angel

Any specifics you can direct me to? I've reviewed the install document a
bazillion times and I'm 99.9% sure the account being used has every right
necessary as spelled out in the guide. I guess I just find it odd that we can
build a cube if we manually kick it off but not if we schedule it.

Thanks

Gary L. Chefetz said:
Sounds like a permissions issue for the account you're using for the COM+
identity.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com


Angel said:
So I'm thinking the error message is just wrong... the cube will complete
if
we use the "Update Now" opton. It's when we try to schedule it that we get
the DSO Error. Sounds to me like it's more of an issue with the Scheduling
Process. Any thoughts?

Angel said:
It's been a long time since I set up a cube but I thought DSO was
installed
when Analysis Services are installed and you only had to install DSO on
the
other front-end servers that aren't running Analysis services? In this
system
there is a DB server running SQL 2000 and a front-end app server. We
installed Analysis Services on the the front-end server.

The funny thing is that we finally got a cube to run on Friday. It
finally
ran after we cleaned up the DB (we kept having crap data creep back into
the
DB even after cleaning up the plans. We finally saved a few offline
because
everytime we would remove the crap data and save and close the plan, we'd
open the plan again and the data would show up again). I thought that was
the
final thing we had to overcome. But then when we tried to generate the
cube
again yesterday, it failed with the DSO error. I'm not sure how it would
have
ever run in the first place if this is indeed the problem. So perhaps DSO
is
NOT installed with Analysis Services??

Thanks for the response.

:

What version of SQL are you using?

Have you installed DSO (sql 2000) or Backwared compatability components
(sql2005) on the Project Server ?
--
Did this post help you. Consider passing on the good will by making a
donation this great charity.
http://www.fundraiseonline.co.nz/TheProjectServerGuru/

http://theprojectserverguru.spaces.live.com


:

I'm still at a loss and have not received any other recommendations.
Any
thougths would be welcomed!!!!

Additional thoughts:
In the Analysis Server, if I click on edit repository connection, I
see
this: (please note Initial Catalog = Anallysis _Services, which is
the DB we
defined as the Analysis Repository DB)

Provider=SQLOLEDB.1;Integrated Security=SSPI;Initial
Catalog=Analysis_Services;Data Source=bri-sql001\ssdb01;Use Procedure
for
Prepare=1;Auto Translate=True;Packet Size=4096;Workstation
ID=BRI-PROJECT001;Use Encryption for Data=False;Tag with column
collation
when possible=False

But the error message says the intial catalog is ProjectSP1 (which is
the
Project Server DB - not the analysis services DB).

Is this the problem? How do I redefine which DB the analysis server
is
pointing to if I've migrated the repository to the analysis services
DB
already?



:

OK, same problem but I just thought I'd add that the DB never shows
up in
Analysis Services under the Analysis Server name. The XML file
generated when
the cube is kicked off is getting processed and it seems like the
cube is
failing shortly thereafter (about 20 mins after kickoff).

:

Project Server 2003. OLAP Cube was not initially setup to run so
I went back
to the installation documentation to try to find all the steps.
What am I
missing???

Installed analysis services (same SP as SQL)
Added users to OLAP Administrators group on both DB & Application
server
Created Analysis DB in SQL
Gave OLAP Admin group DB_Owner rights
Migrated repository in Analysis Svcs to newly created Analysis DB
Ran PSComPlus
Kicked off cube

Error is below. Oh and yes, we have gone through the Res pool and
enterprise
codes to make sure there are no special characters.


Event Type: Error
Event Source: Microsoft Project Server Tracing Eventlog Provider
Event Category: None
Event ID: 2
Date: 6/18/2008
Time: 4:11:22 PM
User: NT AUTHORITY\LOCAL SERVICE
Computer: BRI-PROJECT001
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>2006-08-01T00:00:00</EntResourceStartDate>

<EntResourceFinishDate>2011-02-24T00:00:00</EntResourceFinishDate>

<BuildCubeRequest><CubeUpdate><CubeStart>20060801</CubeStart><CubeFinish>20110224</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectSP1;Data
Source=bri-sql001\ssdb01</DSOConnection><Server>bri-project001</Server><CubeDB>OneWebster</CubeDB><CubeDesc>Cube
created for analysis of
OneWebster</CubeDesc><BasePath>projectserver</BasePath><CubeGUID>51F3306B-8014-4199-BBF9-1786A0F32029</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>)]]></Description>
Click to expand...
Click to expand...
Click to expand...
 
P

Paul Conroy

look for a file in the project server application files called pscomplus.exe

This app is used to reset the the security identity of the com object used
to build the cube and sync WSS. Simply re-enter the security details of the
user account with OLAP Admin permissions.

--
Did this post help you. Consider passing on the good will by making a
donation this great charity.
http://www.fundraiseonline.co.nz/TheProjectServerGuru/

http://theprojectserverguru.spaces.live.com


Angel said:
Any specifics you can direct me to? I've reviewed the install document a
bazillion times and I'm 99.9% sure the account being used has every right
necessary as spelled out in the guide. I guess I just find it odd that we can
build a cube if we manually kick it off but not if we schedule it.

Thanks

Gary L. Chefetz said:
Sounds like a permissions issue for the account you're using for the COM+
identity.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com


Angel said:
So I'm thinking the error message is just wrong... the cube will complete
if
we use the "Update Now" opton. It's when we try to schedule it that we get
the DSO Error. Sounds to me like it's more of an issue with the Scheduling
Process. Any thoughts?

:

It's been a long time since I set up a cube but I thought DSO was
installed
when Analysis Services are installed and you only had to install DSO on
the
other front-end servers that aren't running Analysis services? In this
system
there is a DB server running SQL 2000 and a front-end app server. We
installed Analysis Services on the the front-end server.

The funny thing is that we finally got a cube to run on Friday. It
finally
ran after we cleaned up the DB (we kept having crap data creep back into
the
DB even after cleaning up the plans. We finally saved a few offline
because
everytime we would remove the crap data and save and close the plan, we'd
open the plan again and the data would show up again). I thought that was
the
final thing we had to overcome. But then when we tried to generate the
cube
again yesterday, it failed with the DSO error. I'm not sure how it would
have
ever run in the first place if this is indeed the problem. So perhaps DSO
is
NOT installed with Analysis Services??

Thanks for the response.

:

What version of SQL are you using?

Have you installed DSO (sql 2000) or Backwared compatability components
(sql2005) on the Project Server ?
--
Did this post help you. Consider passing on the good will by making a
donation this great charity.
http://www.fundraiseonline.co.nz/TheProjectServerGuru/

http://theprojectserverguru.spaces.live.com


:

I'm still at a loss and have not received any other recommendations.
Any
thougths would be welcomed!!!!

Additional thoughts:
In the Analysis Server, if I click on edit repository connection, I
see
this: (please note Initial Catalog = Anallysis _Services, which is
the DB we
defined as the Analysis Repository DB)

Provider=SQLOLEDB.1;Integrated Security=SSPI;Initial
Catalog=Analysis_Services;Data Source=bri-sql001\ssdb01;Use Procedure
for
Prepare=1;Auto Translate=True;Packet Size=4096;Workstation
ID=BRI-PROJECT001;Use Encryption for Data=False;Tag with column
collation
when possible=False

But the error message says the intial catalog is ProjectSP1 (which is
the
Project Server DB - not the analysis services DB).

Is this the problem? How do I redefine which DB the analysis server
is
pointing to if I've migrated the repository to the analysis services
DB
already?



:

OK, same problem but I just thought I'd add that the DB never shows
up in
Analysis Services under the Analysis Server name. The XML file
generated when
the cube is kicked off is getting processed and it seems like the
cube is
failing shortly thereafter (about 20 mins after kickoff).

:

Project Server 2003. OLAP Cube was not initially setup to run so
I went back
to the installation documentation to try to find all the steps.
What am I
missing???

Installed analysis services (same SP as SQL)
Added users to OLAP Administrators group on both DB & Application
server
Created Analysis DB in SQL
Gave OLAP Admin group DB_Owner rights
Migrated repository in Analysis Svcs to newly created Analysis DB
Ran PSComPlus
Kicked off cube

Error is below. Oh and yes, we have gone through the Res pool and
enterprise
codes to make sure there are no special characters.


Event Type: Error
Event Source: Microsoft Project Server Tracing Eventlog Provider
Event Category: None
Event ID: 2
Date: 6/18/2008
Time: 4:11:22 PM
User: NT AUTHORITY\LOCAL SERVICE
Computer: BRI-PROJECT001
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>2006-08-01T00:00:00</EntResourceStartDate>

<EntResourceFinishDate>2011-02-24T00:00:00</EntResourceFinishDate>

<BuildCubeRequest><CubeUpdate><CubeStart>20060801</CubeStart><CubeFinish>20110224</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectSP1;Data
Source=bri-sql001\ssdb01</DSOConnection><Server>bri-project001</Server><CubeDB>OneWebster</CubeDB><CubeDesc>Cube
created for analysis of
OneWebster</CubeDesc><BasePath>projectserver</BasePath><CubeGUID>51F3306B-8014-4199-BBF9-1786A0F32029</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>)]]></Description>
Click to expand...
Click to expand...
Click to expand...
 
A

Angel

I've done that several times actually. I think Gary was trying to say that
perhaps that login didn't have some right it needs to have. I'm just not sure
what other right to give it since I've given it every right necessary
according to the installation guide. It is a domain-level account, it is part
of the OLAP Admin group on both servers, it has DB_Owner rights to the
DB/repository in SQL, etc.

I still don't understand why this account would be the issue if I can run
the cube manually. Doesn't it run under the same credentials whether I click
"Update Now" or schedule it? Of course I don't particularly understand why I
got the error message about DSO not being installed either even though it is.

Paul Conroy said:
look for a file in the project server application files called pscomplus.exe

This app is used to reset the the security identity of the com object used
to build the cube and sync WSS. Simply re-enter the security details of the
user account with OLAP Admin permissions.

--
Did this post help you. Consider passing on the good will by making a
donation this great charity.
http://www.fundraiseonline.co.nz/TheProjectServerGuru/

http://theprojectserverguru.spaces.live.com


Angel said:
Any specifics you can direct me to? I've reviewed the install document a
bazillion times and I'm 99.9% sure the account being used has every right
necessary as spelled out in the guide. I guess I just find it odd that we can
build a cube if we manually kick it off but not if we schedule it.

Thanks

Gary L. Chefetz said:
Sounds like a permissions issue for the account you're using for the COM+
identity.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com


So I'm thinking the error message is just wrong... the cube will complete
if
we use the "Update Now" opton. It's when we try to schedule it that we get
the DSO Error. Sounds to me like it's more of an issue with the Scheduling
Process. Any thoughts?

:

It's been a long time since I set up a cube but I thought DSO was
installed
when Analysis Services are installed and you only had to install DSO on
the
other front-end servers that aren't running Analysis services? In this
system
there is a DB server running SQL 2000 and a front-end app server. We
installed Analysis Services on the the front-end server.

The funny thing is that we finally got a cube to run on Friday. It
finally
ran after we cleaned up the DB (we kept having crap data creep back into
the
DB even after cleaning up the plans. We finally saved a few offline
because
everytime we would remove the crap data and save and close the plan, we'd
open the plan again and the data would show up again). I thought that was
the
final thing we had to overcome. But then when we tried to generate the
cube
again yesterday, it failed with the DSO error. I'm not sure how it would
have
ever run in the first place if this is indeed the problem. So perhaps DSO
is
NOT installed with Analysis Services??

Thanks for the response.

:

What version of SQL are you using?

Have you installed DSO (sql 2000) or Backwared compatability components
(sql2005) on the Project Server ?
--
Did this post help you. Consider passing on the good will by making a
donation this great charity.
http://www.fundraiseonline.co.nz/TheProjectServerGuru/

http://theprojectserverguru.spaces.live.com


:

I'm still at a loss and have not received any other recommendations.
Any
thougths would be welcomed!!!!

Additional thoughts:
In the Analysis Server, if I click on edit repository connection, I
see
this: (please note Initial Catalog = Anallysis _Services, which is
the DB we
defined as the Analysis Repository DB)

Provider=SQLOLEDB.1;Integrated Security=SSPI;Initial
Catalog=Analysis_Services;Data Source=bri-sql001\ssdb01;Use Procedure
for
Prepare=1;Auto Translate=True;Packet Size=4096;Workstation
ID=BRI-PROJECT001;Use Encryption for Data=False;Tag with column
collation
when possible=False

But the error message says the intial catalog is ProjectSP1 (which is
the
Project Server DB - not the analysis services DB).

Is this the problem? How do I redefine which DB the analysis server
is
pointing to if I've migrated the repository to the analysis services
DB
already?



:

OK, same problem but I just thought I'd add that the DB never shows
up in
Analysis Services under the Analysis Server name. The XML file
generated when
the cube is kicked off is getting processed and it seems like the
cube is
failing shortly thereafter (about 20 mins after kickoff).

:

Project Server 2003. OLAP Cube was not initially setup to run so
I went back
to the installation documentation to try to find all the steps.
What am I
missing???

Installed analysis services (same SP as SQL)
Added users to OLAP Administrators group on both DB & Application
server
Created Analysis DB in SQL
Gave OLAP Admin group DB_Owner rights
Migrated repository in Analysis Svcs to newly created Analysis DB
Ran PSComPlus
Kicked off cube

Error is below. Oh and yes, we have gone through the Res pool and
enterprise
codes to make sure there are no special characters.


Event Type: Error
Event Source: Microsoft Project Server Tracing Eventlog Provider
Event Category: None
Event ID: 2
Date: 6/18/2008
Time: 4:11:22 PM
User: NT AUTHORITY\LOCAL SERVICE
Computer: BRI-PROJECT001
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>2006-08-01T00:00:00</EntResourceStartDate>

<EntResourceFinishDate>2011-02-24T00:00:00</EntResourceFinishDate>

<BuildCubeRequest><CubeUpdate><CubeStart>20060801</CubeStart><CubeFinish>20110224</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectSP1;Data
Source=bri-sql001\ssdb01</DSOConnection><Server>bri-project001</Server><CubeDB>OneWebster</CubeDB><CubeDesc>Cube
created for analysis of
OneWebster</CubeDesc><BasePath>projectserver</BasePath><CubeGUID>51F3306B-8014-4199-BBF9-1786A0F32029</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>)]]></Description>
Click to expand...
Click to expand...
Click to expand...
 
P

Paul Conroy

Is the SP for DSO at the same level as OLAP/SQL ?

--
Did this post help you. Consider passing on the good will by making a
donation this great charity.
http://www.fundraiseonline.co.nz/TheProjectServerGuru/

http://theprojectserverguru.spaces.live.com


Angel said:
I've done that several times actually. I think Gary was trying to say that
perhaps that login didn't have some right it needs to have. I'm just not sure
what other right to give it since I've given it every right necessary
according to the installation guide. It is a domain-level account, it is part
of the OLAP Admin group on both servers, it has DB_Owner rights to the
DB/repository in SQL, etc.

I still don't understand why this account would be the issue if I can run
the cube manually. Doesn't it run under the same credentials whether I click
"Update Now" or schedule it? Of course I don't particularly understand why I
got the error message about DSO not being installed either even though it is.

Paul Conroy said:
look for a file in the project server application files called pscomplus.exe

This app is used to reset the the security identity of the com object used
to build the cube and sync WSS. Simply re-enter the security details of the
user account with OLAP Admin permissions.

--
Did this post help you. Consider passing on the good will by making a
donation this great charity.
http://www.fundraiseonline.co.nz/TheProjectServerGuru/

http://theprojectserverguru.spaces.live.com


Angel said:
Any specifics you can direct me to? I've reviewed the install document a
bazillion times and I'm 99.9% sure the account being used has every right
necessary as spelled out in the guide. I guess I just find it odd that we can
build a cube if we manually kick it off but not if we schedule it.

Thanks

:

Sounds like a permissions issue for the account you're using for the COM+
identity.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com


So I'm thinking the error message is just wrong... the cube will complete
if
we use the "Update Now" opton. It's when we try to schedule it that we get
the DSO Error. Sounds to me like it's more of an issue with the Scheduling
Process. Any thoughts?

:

It's been a long time since I set up a cube but I thought DSO was
installed
when Analysis Services are installed and you only had to install DSO on
the
other front-end servers that aren't running Analysis services? In this
system
there is a DB server running SQL 2000 and a front-end app server. We
installed Analysis Services on the the front-end server.

The funny thing is that we finally got a cube to run on Friday. It
finally
ran after we cleaned up the DB (we kept having crap data creep back into
the
DB even after cleaning up the plans. We finally saved a few offline
because
everytime we would remove the crap data and save and close the plan, we'd
open the plan again and the data would show up again). I thought that was
the
final thing we had to overcome. But then when we tried to generate the
cube
again yesterday, it failed with the DSO error. I'm not sure how it would
have
ever run in the first place if this is indeed the problem. So perhaps DSO
is
NOT installed with Analysis Services??

Thanks for the response.

:

What version of SQL are you using?

Have you installed DSO (sql 2000) or Backwared compatability components
(sql2005) on the Project Server ?
--
Did this post help you. Consider passing on the good will by making a
donation this great charity.
http://www.fundraiseonline.co.nz/TheProjectServerGuru/

http://theprojectserverguru.spaces.live.com


:

I'm still at a loss and have not received any other recommendations.
Any
thougths would be welcomed!!!!

Additional thoughts:
In the Analysis Server, if I click on edit repository connection, I
see
this: (please note Initial Catalog = Anallysis _Services, which is
the DB we
defined as the Analysis Repository DB)

Provider=SQLOLEDB.1;Integrated Security=SSPI;Initial
Catalog=Analysis_Services;Data Source=bri-sql001\ssdb01;Use Procedure
for
Prepare=1;Auto Translate=True;Packet Size=4096;Workstation
ID=BRI-PROJECT001;Use Encryption for Data=False;Tag with column
collation
when possible=False

But the error message says the intial catalog is ProjectSP1 (which is
the
Project Server DB - not the analysis services DB).

Is this the problem? How do I redefine which DB the analysis server
is
pointing to if I've migrated the repository to the analysis services
DB
already?



:

OK, same problem but I just thought I'd add that the DB never shows
up in
Analysis Services under the Analysis Server name. The XML file
generated when
the cube is kicked off is getting processed and it seems like the
cube is
failing shortly thereafter (about 20 mins after kickoff).

:

Project Server 2003. OLAP Cube was not initially setup to run so
I went back
to the installation documentation to try to find all the steps.
What am I
missing???

Installed analysis services (same SP as SQL)
Added users to OLAP Administrators group on both DB & Application
server
Created Analysis DB in SQL
Gave OLAP Admin group DB_Owner rights
Migrated repository in Analysis Svcs to newly created Analysis DB
Ran PSComPlus
Kicked off cube

Error is below. Oh and yes, we have gone through the Res pool and
enterprise
codes to make sure there are no special characters.


Event Type: Error
Event Source: Microsoft Project Server Tracing Eventlog Provider
Event Category: None
Event ID: 2
Date: 6/18/2008
Time: 4:11:22 PM
User: NT AUTHORITY\LOCAL SERVICE
Computer: BRI-PROJECT001
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>2006-08-01T00:00:00</EntResourceStartDate>

<EntResourceFinishDate>2011-02-24T00:00:00</EntResourceFinishDate>

<BuildCubeRequest><CubeUpdate><CubeStart>20060801</CubeStart><CubeFinish>20110224</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectSP1;Data
Source=bri-sql001\ssdb01</DSOConnection><Server>bri-project001</Server><CubeDB>OneWebster</CubeDB><CubeDesc>Cube
created for analysis of
OneWebster</CubeDesc><BasePath>projectserver</BasePath><CubeGUID>51F3306B-8014-4199-BBF9-1786A0F32029</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>)]]></Description>
Click to expand...
Click to expand...
Click to expand...
 
A

Angel

Yes, SP3.

Paul Conroy said:
Is the SP for DSO at the same level as OLAP/SQL ?

--
Did this post help you. Consider passing on the good will by making a
donation this great charity.
http://www.fundraiseonline.co.nz/TheProjectServerGuru/

http://theprojectserverguru.spaces.live.com


Angel said:
I've done that several times actually. I think Gary was trying to say that
perhaps that login didn't have some right it needs to have. I'm just not sure
what other right to give it since I've given it every right necessary
according to the installation guide. It is a domain-level account, it is part
of the OLAP Admin group on both servers, it has DB_Owner rights to the
DB/repository in SQL, etc.

I still don't understand why this account would be the issue if I can run
the cube manually. Doesn't it run under the same credentials whether I click
"Update Now" or schedule it? Of course I don't particularly understand why I
got the error message about DSO not being installed either even though it is.

Paul Conroy said:
look for a file in the project server application files called pscomplus.exe

This app is used to reset the the security identity of the com object used
to build the cube and sync WSS. Simply re-enter the security details of the
user account with OLAP Admin permissions.

--
Did this post help you. Consider passing on the good will by making a
donation this great charity.
http://www.fundraiseonline.co.nz/TheProjectServerGuru/

http://theprojectserverguru.spaces.live.com


:

Any specifics you can direct me to? I've reviewed the install document a
bazillion times and I'm 99.9% sure the account being used has every right
necessary as spelled out in the guide. I guess I just find it odd that we can
build a cube if we manually kick it off but not if we schedule it.

Thanks

:

Sounds like a permissions issue for the account you're using for the COM+
identity.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com


So I'm thinking the error message is just wrong... the cube will complete
if
we use the "Update Now" opton. It's when we try to schedule it that we get
the DSO Error. Sounds to me like it's more of an issue with the Scheduling
Process. Any thoughts?

:

It's been a long time since I set up a cube but I thought DSO was
installed
when Analysis Services are installed and you only had to install DSO on
the
other front-end servers that aren't running Analysis services? In this
system
there is a DB server running SQL 2000 and a front-end app server. We
installed Analysis Services on the the front-end server.

The funny thing is that we finally got a cube to run on Friday. It
finally
ran after we cleaned up the DB (we kept having crap data creep back into
the
DB even after cleaning up the plans. We finally saved a few offline
because
everytime we would remove the crap data and save and close the plan, we'd
open the plan again and the data would show up again). I thought that was
the
final thing we had to overcome. But then when we tried to generate the
cube
again yesterday, it failed with the DSO error. I'm not sure how it would
have
ever run in the first place if this is indeed the problem. So perhaps DSO
is
NOT installed with Analysis Services??

Thanks for the response.

:

What version of SQL are you using?

Have you installed DSO (sql 2000) or Backwared compatability components
(sql2005) on the Project Server ?
--
Did this post help you. Consider passing on the good will by making a
donation this great charity.
http://www.fundraiseonline.co.nz/TheProjectServerGuru/

http://theprojectserverguru.spaces.live.com


:

I'm still at a loss and have not received any other recommendations.
Any
thougths would be welcomed!!!!

Additional thoughts:
In the Analysis Server, if I click on edit repository connection, I
see
this: (please note Initial Catalog = Anallysis _Services, which is
the DB we
defined as the Analysis Repository DB)

Provider=SQLOLEDB.1;Integrated Security=SSPI;Initial
Catalog=Analysis_Services;Data Source=bri-sql001\ssdb01;Use Procedure
for
Prepare=1;Auto Translate=True;Packet Size=4096;Workstation
ID=BRI-PROJECT001;Use Encryption for Data=False;Tag with column
collation
when possible=False

But the error message says the intial catalog is ProjectSP1 (which is
the
Project Server DB - not the analysis services DB).

Is this the problem? How do I redefine which DB the analysis server
is
pointing to if I've migrated the repository to the analysis services
DB
already?



:

OK, same problem but I just thought I'd add that the DB never shows
up in
Analysis Services under the Analysis Server name. The XML file
generated when
the cube is kicked off is getting processed and it seems like the
cube is
failing shortly thereafter (about 20 mins after kickoff).

:

Project Server 2003. OLAP Cube was not initially setup to run so
I went back
to the installation documentation to try to find all the steps.
What am I
missing???

Installed analysis services (same SP as SQL)
Added users to OLAP Administrators group on both DB & Application
server
Created Analysis DB in SQL
Gave OLAP Admin group DB_Owner rights
Migrated repository in Analysis Svcs to newly created Analysis DB
Ran PSComPlus
Kicked off cube

Error is below. Oh and yes, we have gone through the Res pool and
enterprise
codes to make sure there are no special characters.


Event Type: Error
Event Source: Microsoft Project Server Tracing Eventlog Provider
Event Category: None
Event ID: 2
Date: 6/18/2008
Time: 4:11:22 PM
User: NT AUTHORITY\LOCAL SERVICE
Computer: BRI-PROJECT001
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>2006-08-01T00:00:00</EntResourceStartDate>

<EntResourceFinishDate>2011-02-24T00:00:00</EntResourceFinishDate>

<BuildCubeRequest><CubeUpdate><CubeStart>20060801</CubeStart><CubeFinish>20110224</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectSP1;Data
Source=bri-sql001\ssdb01</DSOConnection><Server>bri-project001</Server><CubeDB>OneWebster</CubeDB><CubeDesc>Cube
created for analysis of
OneWebster</CubeDesc><BasePath>projectserver</BasePath><CubeGUID>51F3306B-8014-4199-BBF9-1786A0F32029</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>)]]></Description>
Click to expand...
Click to expand...
Click to expand...
 
G

Gary L. Chefetz [MVP]

Angel:

Whe you hit build now, the system uses the credentials you are logged on
with, when you schedule the build, it uses the credentials used for COM+
which leads me to believe that it's a permissions issue for the COM+
identity. Try making it a local admin on the SQL server box for a moment and
see if it solves the problem. If it does, then we know it's a permissions
problem and can work backward from there. Keep in mind that I'm getting a
bit rusty on 2003 so I can't pull this from my head like I used to!

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com


Angel said:
I've done that several times actually. I think Gary was trying to say that
perhaps that login didn't have some right it needs to have. I'm just not
sure
what other right to give it since I've given it every right necessary
according to the installation guide. It is a domain-level account, it is
part
of the OLAP Admin group on both servers, it has DB_Owner rights to the
DB/repository in SQL, etc.

I still don't understand why this account would be the issue if I can run
the cube manually. Doesn't it run under the same credentials whether I
click
"Update Now" or schedule it? Of course I don't particularly understand why
I
got the error message about DSO not being installed either even though it
is.

Paul Conroy said:
look for a file in the project server application files called
pscomplus.exe

This app is used to reset the the security identity of the com object
used
to build the cube and sync WSS. Simply re-enter the security details of
the
user account with OLAP Admin permissions.

--
Did this post help you. Consider passing on the good will by making a
donation this great charity.
http://www.fundraiseonline.co.nz/TheProjectServerGuru/

http://theprojectserverguru.spaces.live.com


Angel said:
Any specifics you can direct me to? I've reviewed the install document
a
bazillion times and I'm 99.9% sure the account being used has every
right
necessary as spelled out in the guide. I guess I just find it odd that
we can
build a cube if we manually kick it off but not if we schedule it.

Thanks

:

Sounds like a permissions issue for the account you're using for the
COM+
identity.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com


So I'm thinking the error message is just wrong... the cube will
complete
if
we use the "Update Now" opton. It's when we try to schedule it that
we get
the DSO Error. Sounds to me like it's more of an issue with the
Scheduling
Process. Any thoughts?

:

It's been a long time since I set up a cube but I thought DSO was
installed
when Analysis Services are installed and you only had to install
DSO on
the
other front-end servers that aren't running Analysis services? In
this
system
there is a DB server running SQL 2000 and a front-end app server.
We
installed Analysis Services on the the front-end server.

The funny thing is that we finally got a cube to run on Friday. It
finally
ran after we cleaned up the DB (we kept having crap data creep
back into
the
DB even after cleaning up the plans. We finally saved a few
offline
because
everytime we would remove the crap data and save and close the
plan, we'd
open the plan again and the data would show up again). I thought
that was
the
final thing we had to overcome. But then when we tried to generate
the
cube
again yesterday, it failed with the DSO error. I'm not sure how it
would
have
ever run in the first place if this is indeed the problem. So
perhaps DSO
is
NOT installed with Analysis Services??

Thanks for the response.

:

What version of SQL are you using?

Have you installed DSO (sql 2000) or Backwared compatability
components
(sql2005) on the Project Server ?
--
Did this post help you. Consider passing on the good will by
making a
donation this great charity.
http://www.fundraiseonline.co.nz/TheProjectServerGuru/

http://theprojectserverguru.spaces.live.com


:

I'm still at a loss and have not received any other
recommendations.
Any
thougths would be welcomed!!!!

Additional thoughts:
In the Analysis Server, if I click on edit repository
connection, I
see
this: (please note Initial Catalog = Anallysis _Services,
which is
the DB we
defined as the Analysis Repository DB)

Provider=SQLOLEDB.1;Integrated Security=SSPI;Initial
Catalog=Analysis_Services;Data Source=bri-sql001\ssdb01;Use
Procedure
for
Prepare=1;Auto Translate=True;Packet Size=4096;Workstation
ID=BRI-PROJECT001;Use Encryption for Data=False;Tag with
column
collation
when possible=False

But the error message says the intial catalog is ProjectSP1
(which is
the
Project Server DB - not the analysis services DB).

Is this the problem? How do I redefine which DB the analysis
server
is
pointing to if I've migrated the repository to the analysis
services
DB
already?



:

OK, same problem but I just thought I'd add that the DB
never shows
up in
Analysis Services under the Analysis Server name. The XML
file
generated when
the cube is kicked off is getting processed and it seems
like the
cube is
failing shortly thereafter (about 20 mins after kickoff).

:

Project Server 2003. OLAP Cube was not initially setup to
run so
I went back
to the installation documentation to try to find all the
steps.
What am I
missing???

Installed analysis services (same SP as SQL)
Added users to OLAP Administrators group on both DB &
Application
server
Created Analysis DB in SQL
Gave OLAP Admin group DB_Owner rights
Migrated repository in Analysis Svcs to newly created
Analysis DB
Ran PSComPlus
Kicked off cube

Error is below. Oh and yes, we have gone through the Res
pool and
enterprise
codes to make sure there are no special characters.


Event Type: Error
Event Source: Microsoft Project Server Tracing Eventlog
Provider
Event Category: None
Event ID: 2
Date: 6/18/2008
Time: 4:11:22 PM
User: NT AUTHORITY\LOCAL SERVICE
Computer: BRI-PROJECT001
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>2006-08-01T00:00:00</EntResourceStartDate>

<EntResourceFinishDate>2011-02-24T00:00:00</EntResourceFinishDate>

<BuildCubeRequest><CubeUpdate><CubeStart>20060801</CubeStart><CubeFinish>20110224</CubeFinish><DBType>0</DBType><DSOConnection>Provider=SQLOLEDB.1;Persist
Security Info=False;Initial Catalog=ProjectSP1;Data
Source=bri-sql001\ssdb01</DSOConnection><Server>bri-project001</Server><CubeDB>OneWebster</CubeDB><CubeDesc>Cube
created for analysis of
OneWebster</CubeDesc><BasePath>projectserver</BasePath><CubeGUID>51F3306B-8014-4199-BBF9-1786A0F32029</CubeGUID></CubeUpdate></BuildCubeRequest>
</ProjectData>)]]></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 build fails, security check failure 11
OLAP CUBE ERROR in Project Server 2003 environment..Need help!!!!! 1
Cube failed - (-2147221492) Unable to save object. 1
Having trouble building OLAP cube 2
OLAP Cube creation errors 4
OLAP Cube Creation Error 3
Cube building doesn't update PS database? HELP! 2

Top