A couple of days ago, after installing PPS2007 SP1, I've created simple application called UserTest and tried to deploy model site. It failed with following error:
"The attempt to deploy, UsersTest, to the model or model site failed. (Error code: PerformancePoint_1050200270)
Failed generate and process of Olap object(s): Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
OLE DB error: OLE DB or ODBC error: Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.; 28000; Cannot open database "UsersTest_App_Db" requested by the login. The login failed.; 42000; Invalid connection string attribute; 01S00.
Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of 'feec5192-c4eb-41c4-8b38-8a9ee2cbedc0', Name of 'AppDB'.
Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Time', Name of 'Time' was being processed.
Errors in the OLAP storage engine: An error occurred while the 'MemberDescription' attribute of the 'Time' dimension from the 'UsersTest_UsersTest' database was being processed."
Hmm, strange..Yesterday everything worked smooth (argh, how many times I'm saying this). So I've made a little investigation and here is the result: Network Service must be granted enough privilegies under SQL Server (both relational and analytical engine!). For example, situation with this account in our database was that it was defined as public role. So I've granted administrator privilegies and everything worked again. Please note, that you have to grant enough privilegies both under relational engine and SSAS!
Tuesday, June 17, 2008
Displaying desired dimension property in Excel Add-in
Let's consider that we have dimension with following properties: Label, Name, Description. We'll call this dimension Department and we'll populate it as follows:
Label Name Description
1001 1001 CEO
1002 1002 VP
etc.
So, what happens when we select this dimension in Excel Add-in? Add-in will select Label as default property and you would get something like this:
As you can see, Labels are displayed instead of some meaningful text. What we can do? Go to PerformancePoint pane in Excel, select dimension and from the drop-down list choose option "Select Properties":
In "Select Dimension Properties" dialog box, select properties you would like to be displayed (e.g. in our case we want to display Description property):
Close the dialog and click Refresh in the PerformancePoint pane. Voila, we get what we wanted :)
Label Name Description
1001 1001 CEO
1002 1002 VP
etc.
So, what happens when we select this dimension in Excel Add-in? Add-in will select Label as default property and you would get something like this:
As you can see, Labels are displayed instead of some meaningful text. What we can do? Go to PerformancePoint pane in Excel, select dimension and from the drop-down list choose option "Select Properties":
In "Select Dimension Properties" dialog box, select properties you would like to be displayed (e.g. in our case we want to display Description property):
Close the dialog and click Refresh in the PerformancePoint pane. Voila, we get what we wanted :)
Submit Draft problem
I had very intriguing situation last week, while developing PoC application using PPS2007. We set up everything (including models, forms, assignments etc.) and tried to enter some data using Excel add-in. Everything went fine, until one of the users selected "Submit Draft" action from the Actions drop-down. When he submitted data, he couldn't get "Submit Final" option anymore!
After searching a while, we have found several solutions:
"An exception occurred while enqueueing a message in the target queue. Error: 15404, State: 19. Could not obtain information about Windows NT group/user 'domain\user_name', error code 0x5."
where domain\user_name is a domain account under which SQL Server is working. Actually, this problem is not an issue of PPS but of SQL Server. We set up SQL Server to run under Network Service account. If any SQL Server entity needs to access Active Directory domain controller (e.g. from stored procedure or via Service Broker like PPS does), SQL Server must be run under domain account! So we changed SQL Server to run under domain account and everything went fine.
This is was very interesting for me, since I've tried to follow all recommendations from Deployment Guide and this topic wasn't mentioned.
After searching a while, we have found several solutions:
- Stop Planning Service and IIS and and do an ALTER application database enabling broker.
- Configure Service Broker.
- Set up Planning Service to use another domain account.
"An exception occurred while enqueueing a message in the target queue. Error: 15404, State: 19. Could not obtain information about Windows NT group/user 'domain\user_name', error code 0x5."
where domain\user_name is a domain account under which SQL Server is working. Actually, this problem is not an issue of PPS but of SQL Server. We set up SQL Server to run under Network Service account. If any SQL Server entity needs to access Active Directory domain controller (e.g. from stored procedure or via Service Broker like PPS does), SQL Server must be run under domain account! So we changed SQL Server to run under domain account and everything went fine.
This is was very interesting for me, since I've tried to follow all recommendations from Deployment Guide and this topic wasn't mentioned.
Welcome to PPS2007 HotSpot!
Hello and welcome to PPS2007 HotSpot! This is the place where you can find interesting tips and trics regarding PPS2007. Hope that you'll enjoy it and please get involved with your comments!
Subscribe to:
Posts (Atom)
Posts
