All questions related to installations, configurations and maintenance of Advanced Host Monitor (including additional tools such as RMA for Windows, RMA Manager, Web Servie, RCC).
I have ODBC test with informix driver.
I move HM from server 2003 to server 2008. in 2003 all fine.
On 2008 In Windows ODBC administrator all ODBC DSN work fine when I click TEST.
In options of HM SQL query test I click Test - all OK.
But in main window ODBC test fail with error:
Error: [Informix][Informix ODBC Driver][Informix]Unspecified System Error = -23101[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr faile
I restart HM service and refresh test - nothing.
Are you working with HostMonitor directly or you are using RCC? If you are using RCC, where it is installed? On the same system where HostMonitor is running or different system?
Are you working with Host Monitor directly or you are using RCC?
RCC because HM installed on 2008 server.
Am I right that windows server doesn't have console session so I can use only RCC on windows server 2008?
Early on 2003 I use main window in console session.
In HM action I have "show message" so when my test failed I have WAIKUP window somewhere like console session. Windows write that there is windows
On the same system where Host Monitor is running or different system?
On the same system.
After your post I try to connect by RCC from another PC and get the same result. Refresh not help from remote RCC.
I use HM.v7.78 on windows server 2008 SP2.
I assume test works fine if you start HostMonitor as application?
Probably you are using user data source?
User DSN/System DSN
As you know Windows has system data source names (System DSN) and user data source names (User DSN). System data sources are local to a computer but not user-dedicated; any user with privileges can access a system DSN. User data sources are local to a user and accessible only by the specified user. Using "User DSN/System DSN" option you can choose which data sources list will be used by HostMonitor. Please note if you start HostMonitor as service, it will not be able to use User DSN. Only System DSN will be used . So, if you are planning to start HostMonitor as service and as regular application, use "System DSN" option. In this case HostMonitor will work equally in both modes.
No I use SYSTEM DSN. I export/import DSN from server 2003.
I test it from test option - all ok. How I can test it from test option with positive result and later have error in main HM window.
How I can test it from test option with positive result and later have error in main HM window.
Because you click "Test" button using RCC that is started as application while test items performed by HostMontor that is started as service.
Somehow your ODBC driver returns error in service mode...
I assume test works fine if you start HostMonitor as application?
Do you start RCC using admin account? Could you then specify this account for HostMonitor service using standard Windows Services applet and restart service?
I assume test works fine if you start HostMonitor as application?
I dont check
Do you start RCC using admin account?
LOCAL SYSTEM
So....
I change account (to local admin that I have on server) in main HM window - option (Service), but in Windows service "KS Advanced HM" in options (logon tab) account don't change.
So I write local admin to service option in "Logon" tab.
After that all works fine. But I don't understand why it dont work.
In that case LOCAL SYSTEM account don't have permissions on System DSN?
After that all works fine. But I don't understand why it dont work.
We don't know why this ODBC driver does not work under "local system" account. Actually HostMonitor "impersonates" each test using account specified on Service page in the Options dialog (HostMonitor options dialog), this helps to all built-in test items.
Why it does not work for this specific ODBC driver? We don't know. We are trying to find some manual that will explain this behavior but did not find explanation so far. Have you asked developers of this ODBC driver?
All script test write error Error:Enable to start script after start service as Local admin
From script manager all Ok (run in RCC under local admin session)
In RCC run on local HM server (runas a service as same local admin) I have error Enable to start script
