Job Manager Service not running
Created 2003-07-02 by Wajih-ur-Rehman
When the Job Manager Service is started, it logs an
error about ODBC in the Windows Event Log and no report is generated.
The Job Manager Service runs under Local System
account. When creating the DSN for the underlying database, make sure that you
don't use Windows Integrated Security, rather you give the login and password (you
can use "sa" without the quotes as the login with no password). If you use Windows Integrated security then you might see the following error logged by the Job Manager in the Application log:
Microsoft.Data.Odbc.OdbcException: ERROR [28000] [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
ERROR [28000] [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
at Microsoft.Data.Odbc.OdbcConnection.Open()
at Adiscon.MonitorWare.JobManager.JMSettings.read()
If you see this kind of error, it means that you are using DSN with Windows Integrated Security and the Job Manager is not able to access the database since it is running under local system. To solve this problem, either create a new DSN without windows integrated security or update your existing DSN such that you give username and password in it as shown in the following figure:
One you have done this, you should enter all of the three parameters in the Job Manager form. i.e. DSN name, user name and password.
Similarly when you start MonitorWare Console, and you click on the "Edit Database Connection"
link on the right side, make sure that you enter all the three things i.e. DSN
name, user name and password.
|
