NetIQ AppManager 7.0.x Agent for Windows
NetIQ AppManager 8.0.x Agent for Windows
Microsoft Windows 2008 Core Server
Microsoft Windows 2012 Core Server
You cannot remove an AppManager 7.0.x or 8.0.x Agent from Maintenance Mode on Windows 2008 Core Server or Windows 2012 Core Server operating systems.
PLEASE NOTE: This solution is provided as a work-around only. Support of the NetIQ AppManager Windows Agent on Microsoft Windows 2008 Core Server and Windows 2012 Core Server is provided as 'Best Effort' at this time.
You should be able to correct this issue by completing the following steps:
- Copy the following files from the SysWOW64 directory of an available Standard or Enterprise versions of Windows 2008 Server or Windows 2012 Server, to the SysWOW64 directory of the affected Windows 2008 Core or Windows 2012 Core server:
- Restart the NetIQ AppManager Client Communication Manager (NetIQccm.exe) & NetIQ AppManager Client Resource Monitor (NetIQmc.exe) services on the affected Windows 2008 Core or Windows 2012 Core server.
In very limited internal testing, this solution worked for both 32-bit and 64-bit versions of the Windows 2008 Core and Windows 2012 Core Server operating systems. Adding these two files should allow the Agent to work with the Jet DB (Local Repository) on Windows 2008 Core and Windows 2012 Core Servers, and as a result, should allow the Agent to exit from Maintenance Mode.
"There is a problem trying to update the Local Repository. Repository Error. [MCRscTable]: repository error
SQLSTATE=22005, NativeErr=-3030, msg=<[Microsoft][ODBC Microsoft Access Driver] Internal OLE Automation error>"
The problem is caused because the Jet database that is used as the Local Repository on the Agent is not supported by Windows 2008 Core or Windows 2012 Core Servers.
The NetIQ AppManager Windows Agent is currently only supported on Microsoftâs Windows 2008 Core Server and Windows 2012 Core Server operating systems on a LIMITED BASIS.
While NetIQ will provide fixes to code issues within our own product, we are also obligated to respect Microsoft limitations and honor Microsoftâs Support Statements relating to those operating systems.