Information: Forum is in read-only mode
For details and other support options see https://www.adiscon.com/news/support-forum-set-to-read-only-mode/

Job Manager error - Login failed for user '(null)'.

Support, Questions and Discussions on MonitorWare Console

Moderator: alorbach

Google Ads


Job Manager error - Login failed for user '(null)'.

Postby esaabye » Tue Mar 21, 2006 4:35 pm

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.
esaabye
New
 
Posts: 4
Joined: Tue Mar 21, 2006 4:31 pm

More info

Postby esaabye » Tue Mar 21, 2006 4:47 pm

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!
esaabye
New
 
Posts: 4
Joined: Tue Mar 21, 2006 4:31 pm

Postby alorbach » Wed Mar 22, 2006 9:48 am

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
alorbach
Site Admin
 
Posts: 1627
Joined: Thu Feb 13, 2003 11:55 am

Postby rgerhards » Wed Mar 22, 2006 9:56 am

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
rgerhards
Site Admin
 
Posts: 3807
Joined: Thu Feb 13, 2003 11:57 am

Postby mmeckelein » Wed Mar 22, 2006 10:20 am

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
mmeckelein
Adiscon Support
 
Posts: 176
Joined: Wed Mar 12, 2003 12:07 pm

Fix did not work

Postby esaabye » Wed Mar 22, 2006 3:06 pm

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
esaabye
New
 
Posts: 4
Joined: Tue Mar 21, 2006 4:31 pm

Postby mmeckelein » Wed Mar 22, 2006 5:41 pm

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 :oops:

Best regards,
Michael Meckelein
Adiscon
mmeckelein
Adiscon Support
 
Posts: 176
Joined: Wed Mar 12, 2003 12:07 pm

Problem Resolved

Postby esaabye » Wed Mar 22, 2006 7:24 pm

I have verified the new exe works correctly.

Thanks, Eric
esaabye
New
 
Posts: 4
Joined: Tue Mar 21, 2006 4:31 pm

Google Ads



Return to MonitorWare Console

Who is online

Users browsing this forum: No registered users and 0 guests

cron