Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals > Office PerformancePoint Server Forums > Planning > Error creating a Data Source from the Planning Administration Console

Answered Error creating a Data Source from the Planning Administration Console

    •  
      Monday, March 16, 2009 1:10 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Hi guys,

      Help please! I am stuck!

      I am trying to create a data source from the Planning Admin Console, and I keep getting the following error message:

      You do not have the required permissions to connect to the specified database (Error code: PerformancePoint_225000183) Connection to database AdventureWorksDW on server local failed.

      Also, I get the following warning in the event viewer:

      Error occurred in MetadataManager::Request.

      App Domain: /LM/W3SVC/923608964/Root-1-128816785392973600
      Culture: en-US
      Host: esensesoftware.local\2k3base32
      Identity: 2K3BASE32\Administrator
      Message Id: PerformancePoint_100013072
      Process: 2468
      Severity: Warning
      Source: PerformancePoint Server
      Thread: 1732
      Time: 2009-03-16T15:06:20.42+02:00
      UI Culture: en-US
      Data:  Exception: Exception:
      Type: Microsoft.PerformancePoint.Planning.Common.Exceptions.BizServerException
      Message: Could not obtain all tables or views from data source AdventureWorksDW.
      ErrorCode: -2146232832
      StackTrace:
        at Microsoft.PerformancePoint.Planning.Mal.DataIntegration.QueryDataSourceOperation.GetAllTables()
        at Microsoft.PerformancePoint.Planning.Mal.PerformancePointMalRequestVisitor.Visit(QueryDataSourceRequest Request)
        at Microsoft.PerformancePoint.Planning.Bmo.Interfaces.QueryDataSourceRequest.AcceptVisitor(PerformancePointRequestVisitor visitor)
        at Microsoft.PerformancePoint.Planning.Server.Interfaces.MetadataManager.ExecuteRequest(PerformancePointRequest PerformancePointRequest)
        at Microsoft.PerformancePoint.Planning.Server.Interfaces.MetadataManager.Request(PerformancePointRequest PerformancePointRequest)
        at Microsoft.PerformancePoint.Planning.Server.WebServices.MetadataManagerWebService.<>c__DisplayClassd.<Request>b__a()
      InnerException:
        Type: System.Data.SqlClient.SqlException
        StackTrace:
          at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
          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.SqlDataReader.ConsumeMetaData()
          at System.Data.SqlClient.SqlDataReader.get_MetaData()
          at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
          at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
          at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
          at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
          at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
          at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior)
          at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
          at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
          at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
          at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet)
          at Microsoft.PerformancePoint.Planning.Mal.DataIntegration.QueryDataSourceOperation.GetAllTables()
        InnerException: (null)

      I have Win 2K SP2, with SQL 2K5 SP2 and cumulative update 3186, and of course, PPS 2K7 SP2.

      HELP PLEASE!


       

    Answers

    • Monday, March 16, 2009 3:06 PM
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote
      Hi,


      The issue may be due to SQL Server Collation of AdventureWorks may be different from default Collation.  Please take a look into the documentation regarding PPS SQL Server Collation http://technet.microsoft.com/en-us/library/bb838707.aspx
       and from the link

      Selecting collation settings

      Collation settings affect searches, look-ups, and ORDER BY commands. The character data is also affected by ASCII and Unicode character sets. We recommend that you use the default collation settings for SQL Server 2005.

      If you install SQL Server 2005 and Analysis Services on the same computer and with English-language Windows collation, the default SQL Server collation will be set automatically to SQL_Latin1_General_CP1_CI_AS, which is case-insensitive.

      Thank you,
      Sundar - MSFT

      This posting is provided "AS IS" with no warranties, and confers no rights.
      • Marked As Answer by YousefO Wednesday, March 18, 2009 7:16 AM
      •  
       

    All Replies

    • Monday, March 16, 2009 3:06 PM
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote
      Hi,


      The issue may be due to SQL Server Collation of AdventureWorks may be different from default Collation.  Please take a look into the documentation regarding PPS SQL Server Collation http://technet.microsoft.com/en-us/library/bb838707.aspx
       and from the link

      Selecting collation settings

      Collation settings affect searches, look-ups, and ORDER BY commands. The character data is also affected by ASCII and Unicode character sets. We recommend that you use the default collation settings for SQL Server 2005.

      If you install SQL Server 2005 and Analysis Services on the same computer and with English-language Windows collation, the default SQL Server collation will be set automatically to SQL_Latin1_General_CP1_CI_AS, which is case-insensitive.

      Thank you,
      Sundar - MSFT

      This posting is provided "AS IS" with no warranties, and confers no rights.
      • Marked As Answer by YousefO Wednesday, March 18, 2009 7:16 AM
      •  
       
    • Wednesday, March 18, 2009 7:15 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Perfect!

      Changed the collation of database AdventureWorksDW to SQL_Latin1_General_CP1_CI_AS. Everything works perfectly now.

      Yousef