MonitorWare Knowledge Base

Job Manager seems to be using a trusted connection rather then the sql account set in the dsn. Have tried both system and file DSN's but no luck.

JM Debug log show that JM opens the job definitions correctly but fails to use the same credentials when running the report.

#==============================================================
#JM DebugLog Opened Tuesday, March 21, 2006
#==============================================================
632785304238659260 | dsn=LocalServer;uid=sysloger;pwd=*******
632785304238659260 | Reading values from database
632785304239440520 | Extracting report names
632785304239440520 | extractReportNames: 885
632785304239753024 | Timer Enabled
632785304839760704 | Inside Report Valid
632785304839760704 | Executing reportDefault_Cisco VPN Concentrator Locked Accounts
632785304839916956 | ODBC User = empty, but continue!
632785304839916956 | Inside Report Valid
632785304840073208 | Executing reportDefault_Possible Attacks Report
632785304840073208 | ODBC User = empty, but continue!
632785304840073208 | Inside Report Valid
632785304840073208 | Executing reportnew_Accessed Web Sites Report
632785304840073208 | ODBC User = empty, but continue!
632785304840229460 | Inside Report Valid
632785304840229460 | Executing reportnew_Blocked Ports Activity
632785304840229460 | ODBC User = empty, but continue!

Hi,

for some reason, the ODBC User seems to be empty.
Can you verify that a ODBC User and Passwort is set in the Source Tab in the Job Manager Settings for the Cisco VPN Report.

best regards,
Andre Lorbach

I just got word that this a known bug. You need a fix. This will be provided via the ticket you opened. If anybody else experiences this problem, please email support@adiscon.com.

Thanks,
Rainer Gerhards
Adiscon

Under some circumstance, Job Manager can not read the user name correctly from the Job Manager settings due to a case-sensitive issue. We have verified this issue with version 2.2 of MonitorWare Console. Earlier versions are a not affected.

Solution:
1. Close MonitorWare Console
2. Stop MonitorWare Console's job manager
3. Download the patch at
http://www.adiscon.org/download/mwconsole-2.2-patch.zip
4. Unzip it into your MonitorWare Console folder by overwriting the existing one
5. Unfortunately you have to delete your current job manager settings. To do so, in your SQL Enterprise Manager on MonitorWare database, run the following sql statement:
"truncate table JMSettings" (without the quotes)

Now you can start Console and configure the job manager.

Best regards,
Michael Meckelein
Adiscon

After following the described proceedure I am presented with the following error.

Microsoft.Data.Odbc.OdbcException: ERROR [42S02] [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'CJMSettings'.
at Microsoft.Data.Odbc.OdbcConnection.HandleError(IntPtr hHandle, SQL_HANDLE hType, RETCODE retcode)
at Microsoft.Data.Odbc.OdbcCommand.ExecuteReaderObject(CommandBehavior behavior, String method)
at Microsoft.Data.Odbc.OdbcCommand.ExecuteReader(CommandBehavior behavior)
at Microsoft.Data.Odbc.OdbcCommand.ExecuteReader()
at Adiscon.MonitorWare.Console.CJMSettings.read()

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I then uninstalled (after replacing original exe) and reinstalled. I tried the proceedure again omiting the truncate command but had the same results. I then rolled back to the base package and tried using a lowercase DSN but it failed as well.

What is the exact case-sensitive issue so I can just work around the issue as the fix does not seem to work and breaks the installshield uninst routines?

Thanks, Eric

Unfortunately I have included the wrong file in the zip package. This is fixed now. Could you please re-download the patch and try it again.

Sorry for that hassle

Best regards,
Michael Meckelein
Adiscon

I have verified the new exe works correctly.

Thanks, Eric