If a database client is not installed or configured correctly, an administrator may encounter problems when using Contributor Administration.

Problems Creating an Application in an SQL Environment
When using Contributor Administration to create an application in an SQL Environment, the following error message appears:

Unable to connect to computer name using SQL
Server Data Manipulation Objects (SQLDMO). Unable to create the object with ProgID ’SQLDMO.SQLServer’To avoid this problem, install Microsoft SQL Server on the computer where the planning server is installed.

Problems Creating an Application in a DB2 Environment
When using Contributor Administration to create an application using a DB2 datastore, the following error message appears:

Unable to execute the statement.~~~~The SQL was:~~CREATE
TABLE The row length of the table exceeded a limit of "4005"
bytes.  To fix this problem, configure the DB2 tablespace size to be 8k instead of 4k.

Problems Importing Data in an SQL Environment
When using Contributor Administration to import data, the following error messages appear:

There was a problem during the load.The error details have been recorded in the error log.Unable to Bulk Load the data.To avoid this problem, install Microsoft SQL Server on the computer where the planning server is installed.

Problems Running Go to Production in an SQL Environment
When using Contributor Administration to run the Go to Production process, the process fails and following error message appears in the log file:

Unable to execute the statement.Could not find database
ID 22. Database may not be activated yet or may be in transition.To avoid this problem, install Microsoft SQL Server on the computer where the planning server is installed.

www.cogknowhow.com