Citrix

How to Determine where the IMA Data Store Database is Located

  • CTX105257
  • Created onMar 26, 2014
  • Updated onMay 07, 2014
Article Topic Storage

Objective

This article describes how to identify which server contains the Access or SQL data store.

Instructions

Examine the DSN file, which contains the connection details to the database.
  • 32-bit Servers
    C:\Program Files\Citrix\Independent Management Architecture\MF20.dsn
  • 64-bit Servers
    C:\Program Files (x86)\Citrix\Independent Management Architecture\MF20.dsn
The following is an example of an MF20.dsn file from a server using an Access data store on the local machine:
[ODBC]
DRIVER=Microsoft Access Driver (*.mdb)
PageTimeout=5
MaxBufferSize=2048
FIL=MS Access
DriverId=25
DBQ=C:\Program Files\Citrix\Independent Management Architecture\MF20.mdb

The following is an example of an MF20.dsn file from a server connecting to a remote SQL Server instance:
[ODBC]
DRIVER=SQL Server
UID=useraccount
Address=MySqlServer,1433
Network=DBMSSOCN
DATABASE=myfarmdb
WSID=MyMfServer
APP=Citrix IMA
SERVER=MySqlServer

In some cases, the DATABASE parameter might not be present in the DSN file. The default database of the specified user (UID) is the one being used for the data store. Open Properties of that user account in SQL Management Studio to identify the user’s default database assignment.
If the MF20.dsn file is not present on the server, the server is doing an indirect connection to the data store. The value of PSserver at the following registry key location shows the hostname of the server containing the DSN file:
Caution! Refer to the Disclaimer at the end of this article before using Registry Editor.
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA\
For Access data stores, only one server in the farm (the one hosting the data store) shows imaacces.dll under
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\IMA

Disclaimer

Caution! Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.

Automatic translation

Important: This article was translated by an automatic translation system (also referred to as Machine Translation, or MT) and has not been translated or reviewed by people. Citrix offers a machine translated version of this article to allow for greater access to the support content. However, automatic translation is not always perfect and may contain errors of vocabulary, syntax or grammar. Citrix is not responsible for inconsistencies, errors or damage incurred as a result of the use of MT articles from our customers.Thank you.
Click here to see the English version of this article.
Languages
Was this helpful?
Thank you for your feedback

Share your comments or find out more about this topic

Citrix Forums