Diagnosing Problems

On a 64-bit Windows system, the DSN has been set up, and the connection has been saved. The connection is accessible in Data Management Studio, but not in Data Management Server.

The 64-bit credentials must be saved explicitly for 64-bit systems. The connection must be replicated in a 64-bit ODBC connection, either by using the ODBC Administrative Tool in the Control Panel or by using the odbcad32.exe executable in %systemdrive%\Windows\System32.

A bulk load using a database utility (for example, sqlldr or bcp) does not work.

Check the log files for the run in <SAS MDM Install Directory>\data. Look at the timestamps to determine which logs might be relevant.

Logging on to SAS MDM generates a message about the wrong number of types or arguments in a call to a stored procedure.

Ensure that your ODBC settings are configured correctly. The Procedure Return Results setting might not have been set properly. If you are running a 64-bit system, ensure that both the 32-bit driver used by Data Management Studio, and the 64-bit driver used by Data Management Server have the same settings.

Logging on to SAS MDM generates a message about not being able to load the model.

Check your application server and ensure that the data source has been configured correctly. For tcServer, check the configuration in the context.xml file and the availability of the JDBC drivers in the application server classpath. The application server uses context.xml to configure the resources required by the web application. The resource is a data source that provides connection information to the database for the workflow engine, which uses a JDBC connection pool instead of an ODBC DSN.

Not all areas of the SAS Data Management Console web application are visible.

The suggested minimum browser screen size for SAS MDM web components is 1024 x 768, but larger sizes are preferred. Smaller sizes might obscure parts of the application.

You cannot log on and the error log states that context initialization failed or that it is unable to find [jdbc].

If the source directory used to specify the JDBC driver classpath during the SAS MDM installation contained any additional JAR files, you might have introduced extra JAR files into your web server environment. To correct the problem, remove the incorrect JAR files from the web application server lib directory (for example, ..\SAS\mdmadv_1machine\Lev1\Web\WebAppServer\SASServer13_1\lib) and restart the web server. When setting the JDBC driver classpath, the only file in the source directory should be the JDBC driver JAR file that matches your SAS MDM target database system.