Saturday, February 11, 2012

Unable to connect to admin database with IBM Datacap Taskmaster Capture

Unable to connect to admin database with


IBM Datacap Taskmaster Capture


Abstract


When attempting to login using Taskmaster Web or another Datacap executable,


and error occurs stating that the user is unable to connect to the admin database.


Cause


The application is not correctly configured.


Resolving the problem


To resolve, do the following:




  • Ensure the application name is the same and each character is of the same case in all locations.



    • On the shared drive, usually the Taskmaster Server - \datacap\Datacap.xml, \datacap\appName\appName.app. Use a text editor to view these files.




  • Ensure \datacap\datacap.xml has the retry attribute <k name="tms" ip="127.0.0.1" port="2402" retry="3"/>.




  • On the web server check \datacap\tmweb.net\apps.ini.



    • In the following example, ensure the DateTimeSeparator is set to a pound symbol (#) for SQL or Oracle, and that Oracle=1 for Oracle. It should not include connection strings. Also ensure the application name is correct and each character has the correct case.
      [1040EZ]
      DateTimeSeparator=#
      Delay=20
      Retries=3
      BatchSelectionCustomFields=
      Debug=0
      Oracle=0




  • Ensure the Taskmaster Application Manager’s Service tab points to the shared \datacap.xml unless you are duplicating Datacap.xml and appName.xml locally on the web server.




  • If using Datacap.xml on a shared drive, ensure the user set as the identity of the Application Pool has permission to the share and to read the files.




  • Taskmaster Client and Quattro



    • Ensure the user set as the identity of the Application Pool has permission to the share and to read the files.




  • Taskmaster Server



    • The Windows user specified to run the Datacap Taskmaster Server Service is generally the only user that connects to the admin and engine databases. The clients read the connection strings from appName.app and pass them to Taskmaster Server.




  • If everything looks correct:



    • Create a Taskmaster Server log. Look for the connection string that was used. See if there are errors explaining why the connection failed. Test a thick client application on the Taskmaster Server machine using a local Administrator account.

    • Use the included demo applications e.g. APT, that use Microsoft Access databases to identify the problem as related to connecting to the admin and engine databases.

    • Applications such as APT store additional connection strings and file locations in the following files. These paths and connection strings will not be used for the admin, or engine databases when logging into a client. The best practice is to store connection strings and file locations using the Taskmaster Application Manager.


      • \datacap\appName\dco_appName\paths.ini




      • \datacap\appName\dco_appName\settings.ini







6 comments:

  1. I am seeing a similar error. I recently upgraded from 8.0.1 to 8.1. I converted/upgraded the databases using the procedures described. When I try to open the application using Datacap Studio after the database upgrades, I get the message that Studio was unable to access/connect to the Administration database. I don't see any irregularity in datacap.xml, apps.ini or in Taskmaster Client

    ReplyDelete
  2. I have the same issue but with a brand new installation. I verified all the settings in all the components. DStudio and all the other apps connect correctly. The tmweb still says that cannot connect to the admin database. in the log it says that cannot verify connection parameters but it doesn't show a conn string. Any ideas?

    ReplyDelete
    Replies
    1. @Martin did you manage to solve your problem?

      Delete
  3. This problem because of encription of Database Provides in Application.app file.
    to over come this first run the Following command from Command prompt.

    C:\Datacap\Taskmaster\dcskey.exe e

    Then open Taskmaster Application manager and copy the Admin and Engine DB connections.
    Open your application folder and open application.app file in Notepad.
    in that replace the admin and engine DB connections(which are encrypted) with the Connection strings which are copied from application manager.
    just restart your server and open the application from Datacap studio.

    For each and every application we have to follow the same process(for new applications also)

    hope it works.

    ReplyDelete
  4. @Trinath I've opened my application folder eg.APT.app file in Notepad but I can't find the admin and engine DB connections. Your assistance would be highly appreciated!

    ReplyDelete
  5. I've solve the problem by going to my IIS, Choose tmweb.netAplication Pool, Choose Advanced Settings, Change "Identity" in the Process Model, Change from "ApplicationPoolIdentity" to "LocalSystem"

    ReplyDelete