PerformancePoint Services - Issue with importing the content using DashBoard Designer
If you ever try to import PerformancePoint content using DashBoard designer and if you are not able to see any content imported or if it errored out then, check the SharePoint server's application event log which is running the PerformancePoint Service, if there is a dedicated application server running with that service then check the application event log in the application server.
# Issue1
Log Name: Application
Source:
Microsoft-SharePoint Products-PerformancePoint Service
Date:
9/27/2011 3:05:05 PM
Event ID: 4
Task Category: PerformancePoint Services
Level:
Error
Keywords:
User:
CONTOSO\User1
Computer:
DevComputer1
Description:
An unexpected error occurred. Error 9456.
Exception details:
System.Data.SqlClient.SqlException: Cannot open
database "WSSContent" requested by the login. The login
failed.
Login failed for user
'CONTOSO\User1'.
at
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception,
Boolean breakConnection) at
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
stateObj) at
System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand
cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler,
TdsParserStateObject stateObj) at
System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
at
System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host,
String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject,
SqlConnectionString connectionOptions, Int64 timerStart) at
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection
owningObject, SqlConnectionString connectionOptions, String newPassword,
Boolean redirectedUserInstance)
at
System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity
identity, SqlConnectionString connectionOptions, Object providerInfo, String
newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions
options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection
owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at
System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection
owningObject)
at
System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection
owningObject)
at
System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection
owningObject)
at
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory)
at
System.Data.SqlClient.SqlConnection.Open()
at
Microsoft.SharePoint.Utilities.SqlSession.OpenConnection()
at
Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command,
CommandBehavior behavior, SqlQueryData monitoringData, Boolean
retryForDeadLock)
at
Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command,
Boolean retryForDeadLock)
at
Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command)
at
Microsoft.SharePoint.Upgrade.SPDatabaseSequence.GetVersion(SPDatabase database,
Guid id, Version defaultVersion, SqlSession session, SPDatabaseSequence sequence)
at
Microsoft.SharePoint.Upgrade.SPDatabaseSequence.get_SchemaVersion()
at
Microsoft.SharePoint.Upgrade.SPSequence.get_IsBackwardsCompatible()
at
Microsoft.SharePoint.Upgrade.SPUpgradeSession.IsBackwardsCompatible(Object o,
Boolean bRecurse)
at
Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.get_IsBackwardsCompatible()
at
Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.ValidateBackwardsCompatibility()
at
Microsoft.SharePoint.SPSite.PreinitializeServer(SPRequest request) at
Microsoft.SharePoint.SPWeb.InitializeSPRequest() at
Microsoft.SharePoint.SPWeb.GetList(String strUrl) at
Microsoft.PerformancePoint.Scorecards.Store.SPHelper.GetTargetList(Guid
webSiteID, String listUrl, SPSite& targetSite, SPWeb& targetWeb)
Root Cause:
Once you import the Dashboard designer content to a different SharePoint Server or a different content database the “unattended service” will check for login permission on the target SharePoint Content Database. You can get the “unattended service” account configuration from the PerformancePoint Service application in the target SharePoint Server and add that user account to the content database’s login accounts where you are trying to import.
# Issue2
Log Name: Application
Source:
Microsoft-SharePoint Products-PerformancePoint Service
Date:
9/27/2011 3:32:17 PM
Event ID: 4
Task Category: PerformancePoint Services
Level:
Error
Keywords:
User:
CONTOSO\User1
Computer:
DevComputer1
Description:
An unexpected error occurred. Error 5678.
Exception details:
Microsoft.SharePoint.Upgrade.SPUpgradeCompatibilityException:
There is a compatibility range mismatch between the Web server and database
"WSSContent", and connections to the data have been blocked to
due to this incompatibility. This can happen when a content database has not
been upgraded to be within the compatibility range of the Web server, or if the
database has been upgraded to a higher level than the web server. The Web
server and the database must be upgraded to the same version and build level to
return to compatibility range.
at
Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.ValidateBackwardsCompatibility()
at
Microsoft.SharePoint.SPSite.PreinitializeServer(SPRequest request)
at Microsoft.SharePoint.SPWeb.InitializeSPRequest()
at
Microsoft.SharePoint.SPWeb.GetList(String strUrl)
at
Microsoft.PerformancePoint.Scorecards.Store.SPHelper.GetTargetList(Guid
webSiteID, String listUrl, SPSite& targetSite, SPWeb& targetWeb)
Root Cause: Once you import the Dashboard designer content, SharePoint Server version has to be the same in the target and in the source SharePoint Server. Check the version number in the central administration website, if there is version mismatch apply the same patch in the servers to make it is consistent.
Import PerformancePoint Dashboard 2010 content from a SharePoint Server 2010 server, site, or list