NetIQmc and NetIQccm services fail to start with local repository error (NETIQKB44106)

  • 7744106
  • 02-Feb-2007
  • 02-Jun-2011

Environment

NetIQ AppManager 6.x
NetIQ AppManager 7.0.x

Situation

The NetIQ AppManager Client Resource Monitor (NetIQmc) service fails to start. The following error is generated in the Application Event log and mctrace.log:

Error: 'The following is the message from NetIQmc: [1424] Failed to establish ODBC connection to local repository <'SQLSTATE=S1000, NativeErr=-1022, msg> [Microsoft][ODBC Microsoft Access Driver] Disk or network error'

The NetIQ AppManager Client Communications Manager (NetiQccm) service fails with a similar error.

Error: 'EventID 257 is logged to the NT event log'

Resolution

First, verify that the local repository file Local-repository.mdb exists in the location that is specified in the following registry value:

   HKEY_LOCAL_MACHINE\SOFTWARE\NetIQ\AppManager\4.0\NetIQmc\local repository

By default, the location is C:\Program Files\NetIQ\AppManager\db 

If a ".lck" file also exists in the folder, then the file is being held open by some process other than the AppManager agent processes.  It may be necessary to reboot the server to clear the lock.

Verify that the file and directory permissions allow FULL access by the agent service account.

Make sure that both agent services are configured to use the SAME account, or are BOTH set to run as 'Local system'.

For certain conditions, Microsoft has provided a fix for the issue: Disk or Network Error" or "Unspecified Error" Returned when Using Jet (previously published under Q251254).

Cause

This problem occurs when the AppManager Agent services (NetIQmc, NetIQccm) are unable to access the agent's local repository file.  This can occur for any of the following reasons:

  • The two agent services are each running under different account credentials.
  • A third-party application, such as a backup utility or virus scanner has the file open exclusively
  • A file permission restriction is preventing access
  • The file has been deleted or become corrupt

Additional Information

Formerly known as NETIQKB44106

Feedback service temporarily unavailable. For content questions or problems, please contact Support.