Database related Errors

Database Connectivity Issues

  • In case of database connectivity issues, perform the following checks.
  • Verify whether the database server is up and if network connectivity is available. 
  • Verify if the required database port is open for proper database communication. 
  • Verify if the connection string is in the proper format.
  • Server name, database, and password must be entered correctly.
  • In case of the Oracle database, DLL versions as listed in AE-Engage-FOSS and Third Party Client Download Software document need to be downloaded on the web server. The download path should be readily available before initiating product installation.
  • Verify if the Database user account is locked. If it is locked, unlock it.
  • Validate the expiry date of the password of the Database user account.
  • In case of Oracle DB, listener service must be running.
  • In case of Oracle DB, check if the entries for config section handler oracle.manageddataaccess.client is already present in the machine.config file on the web server. If the section exists in the machine.config check the Version attribute values. If the Version attribute values in machine.config and web.config of AssistEdge Workflow service do not match, an error message There is a duplicate 'oracle.manageddataaccess.client' section defined. maybe observed at runtime. 
     

To resolve this error, follow the below steps:

  • Update the config section handler entry for oracle.manageddataaccess.client in the web.config of Workflow and Vanguard. Use the version mentioned in the machine.config in both the web.config files and then restart the corresponding services. After performing this action, the workflow gets up and running, however, if it fails to log in to Admin Module, then reverse the action. Use the version mentioned in the workflow.config file in the machine.config and restart the corresponding services.
  • In case the above solution does not work, remove the config section handler entry for oracle.manageddataaccess.client from the machine.config. 
  • However, note that there could be other applications (beyond AssistEdge) on the machine that depended on this entry in the server’s machine.config. In such cases, this config section handler entry will have to be added for all such application's .NET config files present on that server that depend on it.
  • Verify if the Database services are running. If the issue persists, restart the database service and the database server.

 

Errors while searching for a user in the Database Deployment Utility

  • In case of custom authentication, ensure that while “building” the custom authentication DLL in Visual Studio Editor, “any CPU” option is selected.
  • If XML files are used for the database deployment, the file name and path that are mentioned must be the same, as entered in the custom authentication project.
  • In case of LDAP authentication, validate the availability of the domain connection.

SQL Server Error

In case of the errors: Unable to change the default schema of the user to “usch_aese” or tables are not getting created under the schema “usch_aese”, perform the following checks.

  • The user is not mapped to a database with a different schema, other than “usch_aese”.
  • SQL server has permissions to a particular group of users under which the logging-in user is also available.
     

Other Database Errors

If there are multiple instances of SQL servers installed on the database server machine, each instance must have a distinct port assigned to it.