Project 2007 Server Cube Build Fails Connecting To Another SQL 2005 Analysis Server

Have spent days on this. Followed install guides and troubleshooting thouroughly.

Here are the error messages I get when trying to build a cube.

THE PROJECT SERVER ERROR WHEN BUILDING THE CUBE:

===== Initiating cube build process =====
[8/21/2007 12:45 PM] Cube build request message has been added to the Project Server queue
===== Verifying and running pre-build server event handler =====
[8/21/2007 12:45 PM] Verifying and running pre-build server event handler
===== Determining database and cube structure =====
[8/21/2007 12:45 PM] Cube build initialization started
[8/21/2007 12:45 PM] OLAP database and cube structure was determined successfully
===== Building database and cubes =====
[8/21/2007 12:45 PM] Cube build session started
[8/21/2007 12:45 PM] Analysis Services session started
[8/21/2007 12:45 PM] Analysis Services session failed with the following error: Failed to connect to the Analysis Services server dalacctlib. Error: Your permissions on the server computer do not allow you to administer this Analysis server.
Error:
===== Process Completed =====
[8/21/2007 12:45 PM] Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Failed to connect to the Analysis Services server dalacctlib. Error: Your permissions on the server computer do not allow you to administer this Analysis server.
Error:

-

THE EMAILED ERROR:

Your CBSRequest job failed. Its current state is FailedNotBlocking. It was 0% complete.

To get more information about the job failure, please go to Project Web Access. Select Personal Settings from the left menu. Then select My Queued Jobs.

The errors returned from the queue are as follows:
Error ID: 17003
Error ID: 26000

Detailed error below - send it to the administrator for more detailed troubleshooting.

<?xml version="1.0" encoding="utf-16"?>
<errinfo>
<general>
<class name="CBS message processor failed">
<error id="17003" name="CBSASConnectionFailure" uid="159956a3-840b-84af-9b29-dccf8649c22c" QueueMessageBody="Setting UID=00007829-4392-84b3-b533-5a5a4977e3c9 ASServerName=sql2005 ASDBName=ProjectServer_Repository ASExtraNetAddress= RangeChoice=0 PastNum=1 PastUnit=0 NextNum=1 NextUnit=0 FromDate=08/21/2007 12:28:15 ToDate=08/21/2007 12:28:15 HighPriority=True" Error="Analysis Services session failed with the following error: Failed to connect to the Analysis Services server dalacctlib. Error: Your permissions on the server computer do not allow you to administer this Analysis server. &#xD;&#xA; &#xD;&#xA;Error: " />
</class>
<class name="Queue">
<error id="26000" name="GeneralQueueJobFailed" uid="cd4cb275-d48f-4a1e-bf43-0a3ccccd629a" JobUID="b4c3228f-97c1-5c39-9606-d32bbc423198" ComputerName="PROJECT" GroupType="CBSRequest" MessageType="CBSQueueMessage" MessageId="2" Stage="" />
</class>
</general>
</errinfo>

I have the same issue and have also went through the Microsoft configuration, step-by-step “Requirements for using SQL Server 2005 Analysis Services with the Project Server 2007 Cube Building Service”. http://technet2.microsoft.com/Office/en-us/library/86910044-701c-4b02-89d7-e094e9cb7dcd1033.mspx?mfr=true

My error displays as:

===== Process Completed ============================================

[8/21/2007 11:01 AM] Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Failed to connect to the Analysis Services server MYSERVERNAME Error: Your permissions on the server computer do not allow you to administer this Analysis server.

Take a look at the link that I’ve included above. Maybe it will help you.

I’ll post the solution if I find it, please do the same.

|||

thanks, yeah I followed that page completly.

What other possible users aside from the SPPAdmin user could it possibly be trying to use. The project server and the sql server are on the same domain.

|||

This problem was killing us as well, we followed all of the Microsoft documentation and nothing worked till this morning. You have to set the DSO\RemoteLocksDirectory value on the analysis server to \\yourserver\MSOlapRepository$\ and it should go. We spent hours trying every which way going as far as giving everyone permission to everything. Once I set this it went all the way. The document that gave me the hint is the following:

http://msdn2.microsoft.com/en-us/library/ms403370.aspx

|||

The MS whitepaper “Requirements for using SQL Server 2005 Analysis Services with the Project Server 2007 Cube Building Service” shows two methods.

Option 1: Create the repository by using a SQL Server 2000 Microsoft Jet database

Option 2: Create the repository by creating a SQL Server 2005 database

It would appear to me that you’ve selected option one since you are using the share method. I’ve been trying to use option two.

Today I found the cause of the problem we were having. The account we were using for the SSP had limited privileges on the domain. I replaced the SSP account with an elevated account, re-tested the OLAP and the build was successful.

|||

Help! I've given my SSP account every permission under the sun. (domain admin, local domain admin, analysis services repository db_owner, sql server db admin. Can you specify a) how to check to see that it is indeed the SSP account that is failing to access the server and b) what are the elevated permissions to give this user to get the cube to build?

Thanks so much!

|||

I’m not for sure what the specific permission or group membership was that allowed the SSP account to begin working. I can tell you what groups this user is a member of.

The account I’m using for the SSP is a member of our Organizational Unit (OU) administrator group and a member of our domain users group.

One difference I noticed was, when the OLAP build was failing, the account being used for SSP was a “Domain User” level account that I had added to the local administrators group on both the SQL and Applications servers. When I changed the SSP account, I changed it to a “Domain Admin” account. This user was not added to the local admins group on the servers, because the “Domain Admin” group was already a member of the administrators group on both servers since they are members of the domain.

|||

Anyone to know how to solve this one:

To refresh the cube, I always get first time the following:

Analysis Services session failed with the following error: Failed to delete the Olap database: EPM2007_2. Error: Your permissions on the server computer do not allow you to administer this Analysis server.

Second time, it works fine (nothing changed in any settings, just re-build again)

Project 2007 Server Cube Build Fails Connecting To Another SQL 2005 Analysis Server

Have spent days on this. Followed install guides and troubleshooting thouroughly.

Here are the error messages I get when trying to build a cube.

THE PROJECT SERVER ERROR WHEN BUILDING THE CUBE:

===== Initiating cube build process =====
[8/21/2007 12:45 PM] Cube build request message has been added to the Project Server queue
===== Verifying and running pre-build server event handler =====
[8/21/2007 12:45 PM] Verifying and running pre-build server event handler
===== Determining database and cube structure =====
[8/21/2007 12:45 PM] Cube build initialization started
[8/21/2007 12:45 PM] OLAP database and cube structure was determined successfully
===== Building database and cubes =====
[8/21/2007 12:45 PM] Cube build session started
[8/21/2007 12:45 PM] Analysis Services session started
[8/21/2007 12:45 PM] Analysis Services session failed with the following error: Failed to connect to the Analysis Services server dalacctlib. Error: Your permissions on the server computer do not allow you to administer this Analysis server.
Error:
===== Process Completed =====
[8/21/2007 12:45 PM] Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Failed to connect to the Analysis Services server dalacctlib. Error: Your permissions on the server computer do not allow you to administer this Analysis server.
Error:

-

THE EMAILED ERROR:

Your CBSRequest job failed. Its current state is FailedNotBlocking. It was 0% complete.

To get more information about the job failure, please go to Project Web Access. Select Personal Settings from the left menu. Then select My Queued Jobs.

The errors returned from the queue are as follows:
Error ID: 17003
Error ID: 26000

Detailed error below - send it to the administrator for more detailed troubleshooting.

<?xml version="1.0" encoding="utf-16"?>
<errinfo>
<general>
<class name="CBS message processor failed">
<error id="17003" name="CBSASConnectionFailure" uid="159956a3-840b-84af-9b29-dccf8649c22c" QueueMessageBody="Setting UID=00007829-4392-84b3-b533-5a5a4977e3c9 ASServerName=sql2005 ASDBName=ProjectServer_Repository ASExtraNetAddress= RangeChoice=0 PastNum=1 PastUnit=0 NextNum=1 NextUnit=0 FromDate=08/21/2007 12:28:15 ToDate=08/21/2007 12:28:15 HighPriority=True" Error="Analysis Services session failed with the following error: Failed to connect to the Analysis Services server dalacctlib. Error: Your permissions on the server computer do not allow you to administer this Analysis server. &#xD;&#xA; &#xD;&#xA;Error: " />
</class>
<class name="Queue">
<error id="26000" name="GeneralQueueJobFailed" uid="cd4cb275-d48f-4a1e-bf43-0a3ccccd629a" JobUID="b4c3228f-97c1-5c39-9606-d32bbc423198" ComputerName="PROJECT" GroupType="CBSRequest" MessageType="CBSQueueMessage" MessageId="2" Stage="" />
</class>
</general>
</errinfo>

I have the same issue and have also went through the Microsoft configuration, step-by-step “Requirements for using SQL Server 2005 Analysis Services with the Project Server 2007 Cube Building Service”. http://technet2.microsoft.com/Office/en-us/library/86910044-701c-4b02-89d7-e094e9cb7dcd1033.mspx?mfr=true

My error displays as:

===== Process Completed ============================================

[8/21/2007 11:01 AM] Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Failed to connect to the Analysis Services server MYSERVERNAME Error: Your permissions on the server computer do not allow you to administer this Analysis server.

Take a look at the link that I’ve included above. Maybe it will help you.

I’ll post the solution if I find it, please do the same.

|||

thanks, yeah I followed that page completly.

What other possible users aside from the SPPAdmin user could it possibly be trying to use. The project server and the sql server are on the same domain.

|||

This problem was killing us as well, we followed all of the Microsoft documentation and nothing worked till this morning. You have to set the DSO\RemoteLocksDirectory value on the analysis server to \\yourserver\MSOlapRepository$\ and it should go. We spent hours trying every which way going as far as giving everyone permission to everything. Once I set this it went all the way. The document that gave me the hint is the following:

http://msdn2.microsoft.com/en-us/library/ms403370.aspx

|||

The MS whitepaper “Requirements for using SQL Server 2005 Analysis Services with the Project Server 2007 Cube Building Service” shows two methods.

Option 1: Create the repository by using a SQL Server 2000 Microsoft Jet database

Option 2: Create the repository by creating a SQL Server 2005 database

It would appear to me that you’ve selected option one since you are using the share method. I’ve been trying to use option two.

Today I found the cause of the problem we were having. The account we were using for the SSP had limited privileges on the domain. I replaced the SSP account with an elevated account, re-tested the OLAP and the build was successful.

|||

Help! I've given my SSP account every permission under the sun. (domain admin, local domain admin, analysis services repository db_owner, sql server db admin. Can you specify a) how to check to see that it is indeed the SSP account that is failing to access the server and b) what are the elevated permissions to give this user to get the cube to build?

Thanks so much!

|||

I’m not for sure what the specific permission or group membership was that allowed the SSP account to begin working. I can tell you what groups this user is a member of.

The account I’m using for the SSP is a member of our Organizational Unit (OU) administrator group and a member of our domain users group.

One difference I noticed was, when the OLAP build was failing, the account being used for SSP was a “Domain User” level account that I had added to the local administrators group on both the SQL and Applications servers. When I changed the SSP account, I changed it to a “Domain Admin” account. This user was not added to the local admins group on the servers, because the “Domain Admin” group was already a member of the administrators group on both servers since they are members of the domain.

|||

Anyone to know how to solve this one:

To refresh the cube, I always get first time the following:

Analysis Services session failed with the following error: Failed to delete the Olap database: EPM2007_2. Error: Your permissions on the server computer do not allow you to administer this Analysis server.

Second time, it works fine (nothing changed in any settings, just re-build again)

Project 2007 Server Cube Build Fails Connecting To Another SQL 2005 Analysis Server

Have spent days on this. Followed install guides and troubleshooting thouroughly.

Here are the error messages I get when trying to build a cube.

THE PROJECT SERVER ERROR WHEN BUILDING THE CUBE:

===== Initiating cube build process =====
[8/21/2007 12:45 PM] Cube build request message has been added to the Project Server queue
===== Verifying and running pre-build server event handler =====
[8/21/2007 12:45 PM] Verifying and running pre-build server event handler
===== Determining database and cube structure =====
[8/21/2007 12:45 PM] Cube build initialization started
[8/21/2007 12:45 PM] OLAP database and cube structure was determined successfully
===== Building database and cubes =====
[8/21/2007 12:45 PM] Cube build session started
[8/21/2007 12:45 PM] Analysis Services session started
[8/21/2007 12:45 PM] Analysis Services session failed with the following error: Failed to connect to the Analysis Services server dalacctlib. Error: Your permissions on the server computer do not allow you to administer this Analysis server.
Error:
===== Process Completed =====
[8/21/2007 12:45 PM] Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Failed to connect to the Analysis Services server dalacctlib. Error: Your permissions on the server computer do not allow you to administer this Analysis server.
Error:

-

THE EMAILED ERROR:

Your CBSRequest job failed. Its current state is FailedNotBlocking. It was 0% complete.

To get more information about the job failure, please go to Project Web Access. Select Personal Settings from the left menu. Then select My Queued Jobs.

The errors returned from the queue are as follows:
Error ID: 17003
Error ID: 26000

Detailed error below - send it to the administrator for more detailed troubleshooting.

<?xml version="1.0" encoding="utf-16"?>
<errinfo>
<general>
<class name="CBS message processor failed">
<error id="17003" name="CBSASConnectionFailure" uid="159956a3-840b-84af-9b29-dccf8649c22c" QueueMessageBody="Setting UID=00007829-4392-84b3-b533-5a5a4977e3c9 ASServerName=sql2005 ASDBName=ProjectServer_Repository ASExtraNetAddress= RangeChoice=0 PastNum=1 PastUnit=0 NextNum=1 NextUnit=0 FromDate=08/21/2007 12:28:15 ToDate=08/21/2007 12:28:15 HighPriority=True" Error="Analysis Services session failed with the following error: Failed to connect to the Analysis Services server dalacctlib. Error: Your permissions on the server computer do not allow you to administer this Analysis server. &#xD;&#xA; &#xD;&#xA;Error: " />
</class>
<class name="Queue">
<error id="26000" name="GeneralQueueJobFailed" uid="cd4cb275-d48f-4a1e-bf43-0a3ccccd629a" JobUID="b4c3228f-97c1-5c39-9606-d32bbc423198" ComputerName="PROJECT" GroupType="CBSRequest" MessageType="CBSQueueMessage" MessageId="2" Stage="" />
</class>
</general>
</errinfo>

I have the same issue and have also went through the Microsoft configuration, step-by-step “Requirements for using SQL Server 2005 Analysis Services with the Project Server 2007 Cube Building Service”. http://technet2.microsoft.com/Office/en-us/library/86910044-701c-4b02-89d7-e094e9cb7dcd1033.mspx?mfr=true

My error displays as:

===== Process Completed ============================================

[8/21/2007 11:01 AM] Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Failed to connect to the Analysis Services server MYSERVERNAME Error: Your permissions on the server computer do not allow you to administer this Analysis server.

Take a look at the link that I’ve included above. Maybe it will help you.

I’ll post the solution if I find it, please do the same.

|||

thanks, yeah I followed that page completly.

What other possible users aside from the SPPAdmin user could it possibly be trying to use. The project server and the sql server are on the same domain.

|||

This problem was killing us as well, we followed all of the Microsoft documentation and nothing worked till this morning. You have to set the DSO\RemoteLocksDirectory value on the analysis server to \\yourserver\MSOlapRepository$\ and it should go. We spent hours trying every which way going as far as giving everyone permission to everything. Once I set this it went all the way. The document that gave me the hint is the following:

http://msdn2.microsoft.com/en-us/library/ms403370.aspx

|||

The MS whitepaper “Requirements for using SQL Server 2005 Analysis Services with the Project Server 2007 Cube Building Service” shows two methods.

Option 1: Create the repository by using a SQL Server 2000 Microsoft Jet database

Option 2: Create the repository by creating a SQL Server 2005 database

It would appear to me that you’ve selected option one since you are using the share method. I’ve been trying to use option two.

Today I found the cause of the problem we were having. The account we were using for the SSP had limited privileges on the domain. I replaced the SSP account with an elevated account, re-tested the OLAP and the build was successful.

|||

Help! I've given my SSP account every permission under the sun. (domain admin, local domain admin, analysis services repository db_owner, sql server db admin. Can you specify a) how to check to see that it is indeed the SSP account that is failing to access the server and b) what are the elevated permissions to give this user to get the cube to build?

Thanks so much!

|||

I’m not for sure what the specific permission or group membership was that allowed the SSP account to begin working. I can tell you what groups this user is a member of.

The account I’m using for the SSP is a member of our Organizational Unit (OU) administrator group and a member of our domain users group.

One difference I noticed was, when the OLAP build was failing, the account being used for SSP was a “Domain User” level account that I had added to the local administrators group on both the SQL and Applications servers. When I changed the SSP account, I changed it to a “Domain Admin” account. This user was not added to the local admins group on the servers, because the “Domain Admin” group was already a member of the administrators group on both servers since they are members of the domain.

|||

Anyone to know how to solve this one:

To refresh the cube, I always get first time the following:

Analysis Services session failed with the following error: Failed to delete the Olap database: EPM2007_2. Error: Your permissions on the server computer do not allow you to administer this Analysis server.

Second time, it works fine (nothing changed in any settings, just re-build again)

Project 2007 Server Cube Build Fails Connecting To Another SQL 2005 Analysis Server

Have spent days on this. Followed install guides and troubleshooting thouroughly.

Here are the error messages I get when trying to build a cube.

THE PROJECT SERVER ERROR WHEN BUILDING THE CUBE:

===== Initiating cube build process =====
[8/21/2007 12:45 PM] Cube build request message has been added to the Project Server queue
===== Verifying and running pre-build server event handler =====
[8/21/2007 12:45 PM] Verifying and running pre-build server event handler
===== Determining database and cube structure =====
[8/21/2007 12:45 PM] Cube build initialization started
[8/21/2007 12:45 PM] OLAP database and cube structure was determined successfully
===== Building database and cubes =====
[8/21/2007 12:45 PM] Cube build session started
[8/21/2007 12:45 PM] Analysis Services session started
[8/21/2007 12:45 PM] Analysis Services session failed with the following error: Failed to connect to the Analysis Services server dalacctlib. Error: Your permissions on the server computer do not allow you to administer this Analysis server.
Error:
===== Process Completed =====
[8/21/2007 12:45 PM] Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Failed to connect to the Analysis Services server dalacctlib. Error: Your permissions on the server computer do not allow you to administer this Analysis server.
Error:

-

THE EMAILED ERROR:

Your CBSRequest job failed. Its current state is FailedNotBlocking. It was 0% complete.

To get more information about the job failure, please go to Project Web Access. Select Personal Settings from the left menu. Then select My Queued Jobs.

The errors returned from the queue are as follows:
Error ID: 17003
Error ID: 26000

Detailed error below - send it to the administrator for more detailed troubleshooting.

<?xml version="1.0" encoding="utf-16"?>
<errinfo>
<general>
<class name="CBS message processor failed">
<error id="17003" name="CBSASConnectionFailure" uid="159956a3-840b-84af-9b29-dccf8649c22c" QueueMessageBody="Setting UID=00007829-4392-84b3-b533-5a5a4977e3c9 ASServerName=sql2005 ASDBName=ProjectServer_Repository ASExtraNetAddress= RangeChoice=0 PastNum=1 PastUnit=0 NextNum=1 NextUnit=0 FromDate=08/21/2007 12:28:15 ToDate=08/21/2007 12:28:15 HighPriority=True" Error="Analysis Services session failed with the following error: Failed to connect to the Analysis Services server dalacctlib. Error: Your permissions on the server computer do not allow you to administer this Analysis server. &#xD;&#xA; &#xD;&#xA;Error: " />
</class>
<class name="Queue">
<error id="26000" name="GeneralQueueJobFailed" uid="cd4cb275-d48f-4a1e-bf43-0a3ccccd629a" JobUID="b4c3228f-97c1-5c39-9606-d32bbc423198" ComputerName="PROJECT" GroupType="CBSRequest" MessageType="CBSQueueMessage" MessageId="2" Stage="" />
</class>
</general>
</errinfo>

I have the same issue and have also went through the Microsoft configuration, step-by-step “Requirements for using SQL Server 2005 Analysis Services with the Project Server 2007 Cube Building Service”. http://technet2.microsoft.com/Office/en-us/library/86910044-701c-4b02-89d7-e094e9cb7dcd1033.mspx?mfr=true

My error displays as:

===== Process Completed ============================================

[8/21/2007 11:01 AM] Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Failed to connect to the Analysis Services server MYSERVERNAME Error: Your permissions on the server computer do not allow you to administer this Analysis server.

Take a look at the link that I’ve included above. Maybe it will help you.

I’ll post the solution if I find it, please do the same.

|||

thanks, yeah I followed that page completly.

What other possible users aside from the SPPAdmin user could it possibly be trying to use. The project server and the sql server are on the same domain.

|||

This problem was killing us as well, we followed all of the Microsoft documentation and nothing worked till this morning. You have to set the DSO\RemoteLocksDirectory value on the analysis server to \\yourserver\MSOlapRepository$\ and it should go. We spent hours trying every which way going as far as giving everyone permission to everything. Once I set this it went all the way. The document that gave me the hint is the following:

http://msdn2.microsoft.com/en-us/library/ms403370.aspx

|||

The MS whitepaper “Requirements for using SQL Server 2005 Analysis Services with the Project Server 2007 Cube Building Service” shows two methods.

Option 1: Create the repository by using a SQL Server 2000 Microsoft Jet database

Option 2: Create the repository by creating a SQL Server 2005 database

It would appear to me that you’ve selected option one since you are using the share method. I’ve been trying to use option two.

Today I found the cause of the problem we were having. The account we were using for the SSP had limited privileges on the domain. I replaced the SSP account with an elevated account, re-tested the OLAP and the build was successful.

|||

Help! I've given my SSP account every permission under the sun. (domain admin, local domain admin, analysis services repository db_owner, sql server db admin. Can you specify a) how to check to see that it is indeed the SSP account that is failing to access the server and b) what are the elevated permissions to give this user to get the cube to build?

Thanks so much!

|||

I’m not for sure what the specific permission or group membership was that allowed the SSP account to begin working. I can tell you what groups this user is a member of.

The account I’m using for the SSP is a member of our Organizational Unit (OU) administrator group and a member of our domain users group.

One difference I noticed was, when the OLAP build was failing, the account being used for SSP was a “Domain User” level account that I had added to the local administrators group on both the SQL and Applications servers. When I changed the SSP account, I changed it to a “Domain Admin” account. This user was not added to the local admins group on the servers, because the “Domain Admin” group was already a member of the administrators group on both servers since they are members of the domain.

|||

Anyone to know how to solve this one:

To refresh the cube, I always get first time the following:

Analysis Services session failed with the following error: Failed to delete the Olap database: EPM2007_2. Error: Your permissions on the server computer do not allow you to administer this Analysis server.

Second time, it works fine (nothing changed in any settings, just re-build again)

Project 2007 Server Cube Build Fails Connecting To Another SQL 2005 Analysis Server

Have spent days on this. Followed install guides and troubleshooting thouroughly.

Here are the error messages I get when trying to build a cube.

THE PROJECT SERVER ERROR WHEN BUILDING THE CUBE:

===== Initiating cube build process =====
[8/21/2007 12:45 PM] Cube build request message has been added to the Project Server queue
===== Verifying and running pre-build server event handler =====
[8/21/2007 12:45 PM] Verifying and running pre-build server event handler
===== Determining database and cube structure =====
[8/21/2007 12:45 PM] Cube build initialization started
[8/21/2007 12:45 PM] OLAP database and cube structure was determined successfully
===== Building database and cubes =====
[8/21/2007 12:45 PM] Cube build session started
[8/21/2007 12:45 PM] Analysis Services session started
[8/21/2007 12:45 PM] Analysis Services session failed with the following error: Failed to connect to the Analysis Services server dalacctlib. Error: Your permissions on the server computer do not allow you to administer this Analysis server.
Error:
===== Process Completed =====
[8/21/2007 12:45 PM] Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Failed to connect to the Analysis Services server dalacctlib. Error: Your permissions on the server computer do not allow you to administer this Analysis server.
Error:

-

THE EMAILED ERROR:

Your CBSRequest job failed. Its current state is FailedNotBlocking. It was 0% complete.

To get more information about the job failure, please go to Project Web Access. Select Personal Settings from the left menu. Then select My Queued Jobs.

The errors returned from the queue are as follows:
Error ID: 17003
Error ID: 26000

Detailed error below - send it to the administrator for more detailed troubleshooting.

<?xml version="1.0" encoding="utf-16"?>
<errinfo>
<general>
<class name="CBS message processor failed">
<error id="17003" name="CBSASConnectionFailure" uid="159956a3-840b-84af-9b29-dccf8649c22c" QueueMessageBody="Setting UID=00007829-4392-84b3-b533-5a5a4977e3c9 ASServerName=sql2005 ASDBName=ProjectServer_Repository ASExtraNetAddress= RangeChoice=0 PastNum=1 PastUnit=0 NextNum=1 NextUnit=0 FromDate=08/21/2007 12:28:15 ToDate=08/21/2007 12:28:15 HighPriority=True" Error="Analysis Services session failed with the following error: Failed to connect to the Analysis Services server dalacctlib. Error: Your permissions on the server computer do not allow you to administer this Analysis server. &#xD;&#xA; &#xD;&#xA;Error: " />
</class>
<class name="Queue">
<error id="26000" name="GeneralQueueJobFailed" uid="cd4cb275-d48f-4a1e-bf43-0a3ccccd629a" JobUID="b4c3228f-97c1-5c39-9606-d32bbc423198" ComputerName="PROJECT" GroupType="CBSRequest" MessageType="CBSQueueMessage" MessageId="2" Stage="" />
</class>
</general>
</errinfo>

I have the same issue and have also went through the Microsoft configuration, step-by-step “Requirements for using SQL Server 2005 Analysis Services with the Project Server 2007 Cube Building Service”. http://technet2.microsoft.com/Office/en-us/library/86910044-701c-4b02-89d7-e094e9cb7dcd1033.mspx?mfr=true

My error displays as:

===== Process Completed ============================================

[8/21/2007 11:01 AM] Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Failed to connect to the Analysis Services server MYSERVERNAME Error: Your permissions on the server computer do not allow you to administer this Analysis server.

Take a look at the link that I’ve included above. Maybe it will help you.

I’ll post the solution if I find it, please do the same.

|||

thanks, yeah I followed that page completly.

What other possible users aside from the SPPAdmin user could it possibly be trying to use. The project server and the sql server are on the same domain.

|||

This problem was killing us as well, we followed all of the Microsoft documentation and nothing worked till this morning. You have to set the DSO\RemoteLocksDirectory value on the analysis server to \\yourserver\MSOlapRepository$\ and it should go. We spent hours trying every which way going as far as giving everyone permission to everything. Once I set this it went all the way. The document that gave me the hint is the following:

http://msdn2.microsoft.com/en-us/library/ms403370.aspx

|||

The MS whitepaper “Requirements for using SQL Server 2005 Analysis Services with the Project Server 2007 Cube Building Service” shows two methods.

Option 1: Create the repository by using a SQL Server 2000 Microsoft Jet database

Option 2: Create the repository by creating a SQL Server 2005 database

It would appear to me that you’ve selected option one since you are using the share method. I’ve been trying to use option two.

Today I found the cause of the problem we were having. The account we were using for the SSP had limited privileges on the domain. I replaced the SSP account with an elevated account, re-tested the OLAP and the build was successful.

|||

Help! I've given my SSP account every permission under the sun. (domain admin, local domain admin, analysis services repository db_owner, sql server db admin. Can you specify a) how to check to see that it is indeed the SSP account that is failing to access the server and b) what are the elevated permissions to give this user to get the cube to build?

Thanks so much!

|||

I’m not for sure what the specific permission or group membership was that allowed the SSP account to begin working. I can tell you what groups this user is a member of.

The account I’m using for the SSP is a member of our Organizational Unit (OU) administrator group and a member of our domain users group.

One difference I noticed was, when the OLAP build was failing, the account being used for SSP was a “Domain User” level account that I had added to the local administrators group on both the SQL and Applications servers. When I changed the SSP account, I changed it to a “Domain Admin” account. This user was not added to the local admins group on the servers, because the “Domain Admin” group was already a member of the administrators group on both servers since they are members of the domain.

|||

Anyone to know how to solve this one:

To refresh the cube, I always get first time the following:

Analysis Services session failed with the following error: Failed to delete the Olap database: EPM2007_2. Error: Your permissions on the server computer do not allow you to administer this Analysis server.

Second time, it works fine (nothing changed in any settings, just re-build again)

programm using ado(sql server 2005) do not run in Windows Vista

Hi!

My C++ programm that use ADO to access SQL Server 2005 Express do not work in Windows Vista. Programm code works in Windows XP, but fails in Vista.

_bstr_t strCnn = L"Provider = 'SQLNCLI'; Data Source='\SERVERSQL';Uid=sa;Pwd=devel; ";
ADODB::_CommandPtr _command;
TESTHR(_command.CreateInstance(__uuidof(ADODB::Command)));
_command->PutActiveConnection(strCnn);

Error:

Unhandled exception in test.exe (secur32.dll) 0xC0000005. Access Violation.

Help Me please.

cmd-connection

C:\>OSQL.exe /S USER123-VISTA\\SERVERSQL /U sa /P devel /i c:\\test\1.sql
error

[SQL Native Client]Client unable to establish connection due to prelogin
failure

I'm not sure why you double the backslashes in the command line, and don't double in the connection string.|||

ok , thanks

in command line run

|||

Help

not work in Vista!

My C++ programm that use ADO to access SQL Server 2005 Express do not work in Windows Vista. Programm code works in Windows XP, but fails in Vista.

_bstr_t strCnn = L"Provider = 'SQLNCLI'; Data Source='\SERVERSQL';Uid=sa;Pwd=devel; ";
ADODB::_CommandPtr _command;
TESTHR(_command.CreateInstance(__uuidof(ADODB::Command)));
_command->PutActiveConnection(strCnn);

Error:

Unhandled exception in test.exe (secur32.dll) 0xC0000005. Access Violation.

Help Me please.

The similar problem

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1517814&SiteID=1

I has not understood the decision

programm using ado(sql server 2005) do not run in Windows Vista

Hi!

My C++ programm that use ADO to access SQL Server 2005 Express do not work in Windows Vista. Programm code works in Windows XP, but fails in Vista.

_bstr_t strCnn = L"Provider = 'SQLNCLI'; Data Source='\SERVERSQL';Uid=sa;Pwd=devel; ";
ADODB::_CommandPtr _command;
TESTHR(_command.CreateInstance(__uuidof(ADODB::Command)));
_command->PutActiveConnection(strCnn);

Error:

Unhandled exception in test.exe (secur32.dll) 0xC0000005. Access Violation.

Help Me please.

cmd-connection

C:\>OSQL.exe /S USER123-VISTA\\SERVERSQL /U sa /P devel /i c:\\test\1.sql
error

[SQL Native Client]Client unable to establish connection due to prelogin
failure

I'm not sure why you double the backslashes in the command line, and don't double in the connection string.|||

ok , thanks

in command line run

|||

Help

not work in Vista!

My C++ programm that use ADO to access SQL Server 2005 Express do not work in Windows Vista. Programm code works in Windows XP, but fails in Vista.

_bstr_t strCnn = L"Provider = 'SQLNCLI'; Data Source='\SERVERSQL';Uid=sa;Pwd=devel; ";
ADODB::_CommandPtr _command;
TESTHR(_command.CreateInstance(__uuidof(ADODB::Command)));
_command->PutActiveConnection(strCnn);

Error:

Unhandled exception in test.exe (secur32.dll) 0xC0000005. Access Violation.

Help Me please.

The similar problem

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1517814&SiteID=1

I has not understood the decision

Programatically created DataFLow task fails

Hi,

I have a package in which i have programatically created dataflow task. It used to work fine but now it fails with series of errors out of which one is below

Error 30002: Type 'MainPipe' is not defined. Line 63 Columns 33-40 Line Text: Dim DataFlowTask As MainPipe = CType(DataFlowTaskHost.InnerObject, MainPipe)

It seems all the function and classes referd from following dlls is not working:

Microsoft.SqlServer.DTSRuntimeWrap.dll

Microsoft.SqlServer.DTSPipelineWrap.dll

I say so because i get the following error also:

Error 30652: Reference required to assembly 'Microsoft.SqlServer.DTSRuntimeWrap, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' containing the type 'Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSConnectionManager90'. Add one to your project. Line 86 Columns 33-64 Line Text: DtsConvert.ToConnectionManager90(ChildPackage.Connections(""Source""))

These dlls are in GAC and in C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies with same version but still it gives above error.

Thanks

Mohit

Mohit,

If it used to work and now it doesn't (as you suggest) then if it were me I would try and track down what got changed in the interim.

-Jamie

|||

Hi Jamie,

There is no change in code because it was deployed in production. Is there possibility of this error being caused by any SQL server service pack or hotfix on the server.

Thanks

Mohit

|||

MohitGupta wrote:

Hi Jamie,

There is no change in code because it was deployed in production. Is there possibility of this error being caused by any SQL server service pack or hotfix on the server.

Thanks

Mohit

yes, its certainly a possibility. That's what I meant by identify what has changed. Code changes? Service pack changes? Windows Update changes? They're all changes that could *potentially* cause problems.

-Jamie

|||

Jamie Thomson wrote:

MohitGupta wrote:

Hi Jamie,

There is no change in code because it was deployed in production. Is there possibility of this error being caused by any SQL server service pack or hotfix on the server.

Thanks

Mohit

yes, its certainly a possibility. That's what I meant by identify what has changed. Code changes? Service pack changes? Windows Update changes? They're all changes that could *potentially* cause problems.

-Jamie

Any pointers to the article resolving this specific error will be very helpful.

Mohit

|||

MohitGupta wrote:

Jamie Thomson wrote:

MohitGupta wrote:

Hi Jamie,

There is no change in code because it was deployed in production. Is there possibility of this error being caused by any SQL server service pack or hotfix on the server.

Thanks

Mohit

yes, its certainly a possibility. That's what I meant by identify what has changed. Code changes? Service pack changes? Windows Update changes? They're all changes that could *potentially* cause problems.

-Jamie

Any pointers to the article resolving this specific error will be very helpful.

Mohit

Have you added the reference that it talks about?

-Jamie

|||

Jamie Thomson wrote:

MohitGupta wrote:

Jamie Thomson wrote:

MohitGupta wrote:

Hi Jamie,

There is no change in code because it was deployed in production. Is there possibility of this error being caused by any SQL server service pack or hotfix on the server.

Thanks

Mohit

yes, its certainly a possibility. That's what I meant by identify what has changed. Code changes? Service pack changes? Windows Update changes? They're all changes that could *potentially* cause problems.

-Jamie

Any pointers to the article resolving this specific error will be very helpful.

Mohit

Have you added the reference that it talks about?

-Jamie

Yes the dlls are refered from the following location: C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies

|||

MohitGupta wrote:

Yes the dlls are refered from the following location: C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies

That's wrong. Reference them from the GAC.

-Jamie

|||

Jamie Thomson wrote:

MohitGupta wrote:

Yes the dlls are refered from the following location: C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies

That's wrong. Reference them from the GAC.

-Jamie

When the dll reference is added there is no option to browse and add assembly. It shows .NET assemblies which are from GAC out of which both the dll have this path: C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies in the property box. This is on my development machine. But in dtsx file, it does not have any reference of this path. Below is the code generated used in production server:

<Reference

Name = "Microsoft.SqlServer.DTSPipelineWrap"

AssemblyName = "Microsoft.SqlServer.DTSPipelineWrap"

/>

<Reference

Name = "Microsoft.SQLServer.DTSRuntimeWrap"

AssemblyName = "Microsoft.SqlServer.DTSRuntimeWrap"

/>

I assume it is coming from GAC.

-Mohit

|||

MohitGupta wrote:

Jamie Thomson wrote:

When the dll reference is added there is no option to browse and add assembly. It shows .NET assemblies which are from GAC out of which both the dll have this path: C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies in the property box. This is on my development machine. But in dtsx file, it does not have any reference of this path. Below is the code generated used in production server:

<Reference

Name = "Microsoft.SqlServer.DTSPipelineWrap"

AssemblyName = "Microsoft.SqlServer.DTSPipelineWrap"

/>

<Reference

Name = "Microsoft.SQLServer.DTSRuntimeWrap"

AssemblyName = "Microsoft.SqlServer.DTSRuntimeWrap"

/>

I assume it is coming from GAC.

-Mohit

This "property box" that you speak of. What object does that contain the properties of? On my machine I check properties of Microsoft.SqlServer.DTSPipelineWrap in c:\windows\assembly and there is no mention of a path anywhere. I'm confused.

The .dtsx file will not contain paths to DLLs, that's the whole point of GACing them.

-Jamie

|||

Finally I got resolution to this issue

Cause:

Security Update for Microsoft .Net Framework 2.0 (KB928365) is installed on the server which causes SSIS packages to fail (Specifically custom data flow tasks using GACed dll)

Resolution:

Install this KB: SQLServer2005-KB932557-x86-ENU.exe on the server.

Link: http://support.microsoft.com/kb/932557/

This KB while installing gives option to Install the patch only for SQL Server Integration Services 2005 and SQL Server Tools and Workstation Components 2005. This KB is not required to be installed for SQL Server Instances. (Restart not required)

Known Issue:

After installing this KB, few warnings may be displayed which are known issues with SSIS.

Thanks

Mohit

Programatically created DataFLow task fails

Hi,

I have a package in which i have programatically created dataflow task. It used to work fine but now it fails with series of errors out of which one is below

Error 30002: Type 'MainPipe' is not defined. Line 63 Columns 33-40 Line Text: Dim DataFlowTask As MainPipe = CType(DataFlowTaskHost.InnerObject, MainPipe)

It seems all the function and classes referd from following dlls is not working:

Microsoft.SqlServer.DTSRuntimeWrap.dll

Microsoft.SqlServer.DTSPipelineWrap.dll

I say so because i get the following error also:

Error 30652: Reference required to assembly 'Microsoft.SqlServer.DTSRuntimeWrap, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' containing the type 'Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSConnectionManager90'. Add one to your project. Line 86 Columns 33-64 Line Text: DtsConvert.ToConnectionManager90(ChildPackage.Connections(""Source""))

These dlls are in GAC and in C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies with same version but still it gives above error.

Thanks

Mohit

Mohit,

If it used to work and now it doesn't (as you suggest) then if it were me I would try and track down what got changed in the interim.

-Jamie

|||

Hi Jamie,

There is no change in code because it was deployed in production. Is there possibility of this error being caused by any SQL server service pack or hotfix on the server.

Thanks

Mohit

|||

MohitGupta wrote:

Hi Jamie,

There is no change in code because it was deployed in production. Is there possibility of this error being caused by any SQL server service pack or hotfix on the server.

Thanks

Mohit

yes, its certainly a possibility. That's what I meant by identify what has changed. Code changes? Service pack changes? Windows Update changes? They're all changes that could *potentially* cause problems.

-Jamie

|||

Jamie Thomson wrote:

MohitGupta wrote:

Hi Jamie,

There is no change in code because it was deployed in production. Is there possibility of this error being caused by any SQL server service pack or hotfix on the server.

Thanks

Mohit

yes, its certainly a possibility. That's what I meant by identify what has changed. Code changes? Service pack changes? Windows Update changes? They're all changes that could *potentially* cause problems.

-Jamie

Any pointers to the article resolving this specific error will be very helpful.

Mohit

|||

MohitGupta wrote:

Jamie Thomson wrote:

MohitGupta wrote:

Hi Jamie,

There is no change in code because it was deployed in production. Is there possibility of this error being caused by any SQL server service pack or hotfix on the server.

Thanks

Mohit

yes, its certainly a possibility. That's what I meant by identify what has changed. Code changes? Service pack changes? Windows Update changes? They're all changes that could *potentially* cause problems.

-Jamie

Any pointers to the article resolving this specific error will be very helpful.

Mohit

Have you added the reference that it talks about?

-Jamie

|||

Jamie Thomson wrote:

MohitGupta wrote:

Jamie Thomson wrote:

MohitGupta wrote:

Hi Jamie,

There is no change in code because it was deployed in production. Is there possibility of this error being caused by any SQL server service pack or hotfix on the server.

Thanks

Mohit

yes, its certainly a possibility. That's what I meant by identify what has changed. Code changes? Service pack changes? Windows Update changes? They're all changes that could *potentially* cause problems.

-Jamie

Any pointers to the article resolving this specific error will be very helpful.

Mohit

Have you added the reference that it talks about?

-Jamie

Yes the dlls are refered from the following location: C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies

|||

MohitGupta wrote:

Yes the dlls are refered from the following location: C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies

That's wrong. Reference them from the GAC.

-Jamie

|||

Jamie Thomson wrote:

MohitGupta wrote:

Yes the dlls are refered from the following location: C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies

That's wrong. Reference them from the GAC.

-Jamie

When the dll reference is added there is no option to browse and add assembly. It shows .NET assemblies which are from GAC out of which both the dll have this path: C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies in the property box. This is on my development machine. But in dtsx file, it does not have any reference of this path. Below is the code generated used in production server:

<Reference

Name = "Microsoft.SqlServer.DTSPipelineWrap"

AssemblyName = "Microsoft.SqlServer.DTSPipelineWrap"

/>

<Reference

Name = "Microsoft.SQLServer.DTSRuntimeWrap"

AssemblyName = "Microsoft.SqlServer.DTSRuntimeWrap"

/>

I assume it is coming from GAC.

-Mohit

|||

MohitGupta wrote:

Jamie Thomson wrote:

When the dll reference is added there is no option to browse and add assembly. It shows .NET assemblies which are from GAC out of which both the dll have this path: C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies in the property box. This is on my development machine. But in dtsx file, it does not have any reference of this path. Below is the code generated used in production server:

<Reference

Name = "Microsoft.SqlServer.DTSPipelineWrap"

AssemblyName = "Microsoft.SqlServer.DTSPipelineWrap"

/>

<Reference

Name = "Microsoft.SQLServer.DTSRuntimeWrap"

AssemblyName = "Microsoft.SqlServer.DTSRuntimeWrap"

/>

I assume it is coming from GAC.

-Mohit

This "property box" that you speak of. What object does that contain the properties of? On my machine I check properties of Microsoft.SqlServer.DTSPipelineWrap in c:\windows\assembly and there is no mention of a path anywhere. I'm confused.

The .dtsx file will not contain paths to DLLs, that's the whole point of GACing them.

-Jamie

|||

Finally I got resolution to this issue

Cause:

Security Update for Microsoft .Net Framework 2.0 (KB928365) is installed on the server which causes SSIS packages to fail (Specifically custom data flow tasks using GACed dll)

Resolution:

Install this KB: SQLServer2005-KB932557-x86-ENU.exe on the server.

Link: http://support.microsoft.com/kb/932557/

This KB while installing gives option to Install the patch only for SQL Server Integration Services 2005 and SQL Server Tools and Workstation Components 2005. This KB is not required to be installed for SQL Server Instances. (Restart not required)

Known Issue:

After installing this KB, few warnings may be displayed which are known issues with SSIS.

Thanks

Mohit