IMLogicAdminService Uses Old Database Information After IM Manager Configured to Use New Database Information

Article:TECH163571  |  Created: 2011-06-29  |  Updated: 2011-06-29  |  Article URL http://www.symantec.com/docs/TECH163571
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution

Product(s)

Issue



The database information for IM Manager has changed.  IM Manager has been configured to use the new database information using this article: How to Configure IM Manager When Database Server/Account/Password Changes.

However the IM Manager service IMLogicAdminService is still using the old database information.

 

Conditions

  • The value of the registry key for the IMLogicAdminService is still contians the old database information:

32-bit Operating System: HKEY_LOCAL_MACHINE\SOFTWARE\IMLogic\IMLogEnterprise\4.0\AdminService\ConnectionString
64-bit Operating System: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\IMLogic\IMLogEnterprise\4.0\AdminService\ConnectionString

 


Environment



 

  • The only IM Manager components installed on the computer are:

Administration Console/Reviewer/Personal Archives
Administration Service


Cause



The database connection string for the IMLogicAdminService is changed by the IM Manager MMC Snap In.  However the MMC Snap In is not installed in this configuration.  Therefore the database connection string can only be changed directly in the registry.

 

 


Solution



Symantec is aware of this issue.  This article is updated as more information is available.  Subscribe to this article to receive updates.

Workaround

Change the registry key manually:

32-bit Operating System: HKEY_LOCAL_MACHINE\SOFTWARE\IMLogic\IMLogEnterprise\4.0\AdminService\ConnectionString
64-bit Operating System: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\IMLogic\IMLogEnterprise\4.0\AdminService\ConnectionString

The following is an example of the registry key when connecting to a SQL server using trusted authentication:

Driver=SQL Server;Server=10.168.18.116;Database=jvdimm8415;Trusted_Connection=Yes;

The following is an example of the registry key when connecting to a SQL server using SQL authentication:

Driver=SQL Server;Server=10.85.209.4;Database=ben83upgrade;uid=sa;pwd=foobar;

 

 

 


Supplemental Materials

SourceETrack
Value2423186



Article URL http://www.symantec.com/docs/TECH163571


Terms of use for this information are found in Legal Notices