Jump to: navigation, search

Connection to a Database Fails

If your application or Composer is not able to connect to your database, you can:

  • Check connection parameters in the Connection editor UI and verify they are correct.
  • Verify that the database is up and running and accepting new connections.
  • Check the error message that is stored in the Composer logs. It will contain the database-specific error message returned by the JDBC driver.
  • For SQLServer, you can create a new ODBC connection to verify whether the information is correct. Access it from Control Panel > Administrative Tools > Data Source (ODBC). Provide the same information that you provided in the connection and test the connection.
  • For Oracle, run SQLPlus and try connecting to your database with the same information you provided in the Connection Profiles editor.

Oracle and .NET Composer Projects

While working with .NET Composer Projects and Oracle, you may get this error at runtime: Oracle client and networking components were not found. These components are supplied by Oracle Corporation and are part of the Oracle Version 7.3.3 or later client software installation. Provider is unable to function until these components are installed. If so, try the following steps:

  1. Log on to Windows as a user with Administrator privileges.
  2. Launch Windows Explorer from the Start Menu and navigate to the  ORACLE_HOME folder. To find this value, look up this variable in your machine environment variables through My Computer > Properties > Advanced > Environment Variables > System Variables.
  3. Right-click the ORACLE_HOME folder in Windows Explorer and select the Properties option from the drop down list.  A Properties window appears.
  4. Click the Security tab of the Properties window. Click the Authenticated Users item in the Name list (on Windows XP the Name list is called Group or user names).
  5. Uncheck the Read and Execute box in the Permissions list under the Allow column (on Windows XP the Permissions list is called Permissions for Authenticated Users).
  6. Recheck the Read and Execute box under the Allow column (this is the box you just unchecked).
  7. Click the Advanced button and in the Permission Entries list make sure you see the Authenticated Users listed there with:

Permission = Read & Execute Apply To = This folder, subfolders and files If this is not the case, edit that line and make sure the Apply onto dropdown box is set to This folder, subfolders and files.  This should already be set properly, but it is important to verify it.

  1. Click the OK button until you close out all of the security properties windows. This may take a few seconds as permissions are applied.
  2. Restart your computer to assure that these changes have taken effect.
  3. Retest your application.

Additional Troubleshooting Steps

If dbrequest.aspx returns a 500 error (with ASP debugging enabled) and if the event viewer shows the following exception message: Failed to access IIS metabase try granting access using the following at the command line (sample version number): Start > Run > C:\WINDOWS\Microsoft.NET\Framework\v2.0xyz\aspnet_regiis -i

Comment on this article:

blog comments powered by Disqus
This page was last modified on 9 March 2015, at 09:48.