Christophe Fiessinger's Blog Updates on Microsoft's Enterprise Social Networking (ESN) and Project Portfolio Management (PPM) offerings
Common questions and answers on AS 2K5 permissions for EPM 2007 (thank you David & Steven):
Getting Cube to Build
1. Which application account is responsible for building the cube? Is this the SSP account? The SharePoint Timer Service account?
SSP account
2. What are the database permissions needed for this account? DataReader on ReportServer? DataReader and DataWriter on OLAPdb?
DataReader on ReportServer, DataReader and DataWriter on OLAPdb (if using SQL as Analysis repository)
3. What are the system permissions needed for this account on the Project Server machines? On the SQL Server machine? On the Analysis Services machine?
Simple user on PS machine. Have not tested on separate SQL/AS machine, but for AS, it needs to be an AS Admin. In some cases I had to put it as a local admin on the SQL server.
4. Do you have a list of common error messages with their solutions?
http://blogs.msdn.com/brismith/archive/2007/02/14/common-error-messages-when-building-cubes.aspx
Allowing Users to View the Cube
1. What permissions need to be setup for users to view the cube? I think part of this stems from the new Analysis Services 2005 security model.
Normally, the right security is added automatically to a defaut AS role during the cube build.
The user added to this role have the Data analysis Project server right. Typically in the Portfolio group
Application templates are out-of-the-box custom scenarios tailored to address the needs and requirements of specific business processes or sets of tasks in organizations of any size. They can be applied to a task, such as managing a help desk or tracking a marketing campaign, to easily create a dedicated Web-based application for a more efficient and effective way of working.
While application templates can be used to solve particular business needs, they also provide a starting point for partners and developers looking to build deeper SharePoint-based solutions. The templates make use of Windows SharePoint Services 3.0 capabilities and are compatible with Microsoft Office SharePoint Designer 2007 to help make customization easier.
Available here: New Application Templates for Windows SharePoint Services 3.0
By default Project Server 2007 gets deployed on top of WSS V3. I've listed below reasons why one should consider deploying Project Server 2007 with Microsoft Office SharePoint Server.
Ever wondered what would be the advantages?
How about installing SQL x64 on a Windows 2003 x64 server?
Joel Oleson has written an excellent post on this subject: Why WSS 3.0 x64 and MOSS 2007 x64... What's the deal?
Prior to troubleshooting your Analysis Services 2005 configuration to "build" your Project Server Cubes, I'll assume you have read the following KB article: 921116
During the CBS you get the following error: "Error: ActiveX component can't create object"
-> Install the following SQL Server 2005 SP1 components: 1. Microsoft SQL Server Native Client (sqlncli.msi)2. Microsoft SQL Server 2005 Management Objects Collection (sqlserver2005_xmo.msi)3. Microsoft SQL Server 2005 Backward Compatibility Components (SQLServer2005_BC.msi)
DSO section in Analysis Services configuration file is malformed
The msmdsrv.ini is typically located in the following directory: C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Config, once you edit the file use a proper XML editor to ensure that are no carriage return; and no white space are present so that it's a properly formatted XML file.
Ensure the proper sharing permissions have been set on the share DSO9 folder
If you are using NTFS make sur both the user account used fot the CBS has been added to the Permission and the Security sections.
N Tier Deployement
If your EPM 2007 deployment contains multiple servers (front end with PWA and back end with SQL DB for instance) you'll have to use a domain account on the to configure the access the to AS repository. You'll also have to deploy the DSO components listed earlier on each from end server for it to communicate to the back end DB server.
Ensure the account used to connect to the CBS has access to AS
If you change your mind about the load balanced URL, you can modify it afterward in the WSS Central Admin site: OperationsàAlternate Access Mapping link
For more information on Network Load Balancing and Sharepoint please check this excellent post from Joe Oleson: NLB (Network Load Balancing) and SharePoint... Troubleshooting and Configuration tips
13 new languages, 16 total languages are now available for MSDN subscribers. Both the x86 or x64 versions are included in the ISO download package (353MB).
Thanks to a colleague of mine, here is how to do it using STSADM (all the PS 2007 Service Accounts were using the same account):
1. Change the account password
2. Open a command line prompt (Start -> Run -> cmd)
3. Change directory wherever STSADM has been installed, typically:
Ø cd "C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN"
4. Execute the following two command:
Ø stsadm -o updatefarmcredentials -userlogin DOMAIN\user -password NEWPASSWORD
Ø stsadm -o updateaccountpassword -userlogin DOMAIN\USER -password NEWPASSWORD –noadmin
Ø IISRESET
5. Reboot the server
The standard procedure to configure (KB 921116) the Cube Building Services (Analysis Services 2005) for Project Server is to copy the Msmdrep.mdb file on a network share.
¾ Get a backup of a SQL 2000 AS Repository database (you can use the migration wizard within AS 2000 to create one) or download the one below.
¾ Create a database in SQL Server 2005 and call it AS2000_Repository.
¾ Restore the database backup found in the link below to the AS2000_Repository database
¾ Locate the msmdsrv.ini file in C:\Program Files\Microsoft SQL Server\MSSQL.#\OLAP\Config (NOTE: MSSQL.# is the folder in which SQL Analysis Services 2005 files are installed)
¾ Modify the <DSO> section of the msmdsrv.ini to (NOTE: Each XML item should be on a single line):
<DSO><RemoteRepositoryConnectionString>Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Data Source=SERVERNAME;Initial Catalog=AS2000_Repository;</RemoteRepositoryConnectionString><RepositoryConnectionString>Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Data Source=SERVERNAME;Initial Catalog=AS2000_Repository;</RepositoryConnectionString><RemoteLocksDirectory/><LocksDirectory/></DSO>
That's it!