MVP Systems Software  
email us now

Disabling JAMS Server to Agent Authentication

Expand / Collapse
 

Disabling JAMS Server to Agent Authentication


You may encounter a situation in JAMS where submitting a Job that runs on a JAMS Agent results in that Job's log file showing an error like the one below:

Exception while authenticating Agent Socket:
The server has rejected the client credentials.
The logon attempt failed

When JAMS runs a Job on an Agent, the Agent asks that JAMS authenticate itself.  JAMS first tries using the account that the JAMS Executor service is running under (usually Local System), and if that doesn't work we try using the account that the Job is going to run under (list on Submit Options tab of Job properties).

This error can occur in rare environments where both of these fail, perhaps due to a possible configuration issue in Windows, or when the Job is attempting to run on an Agent machine that is in its own Workgroup.

The first step when you see this error is to verify that the account that the Job should run under on that Agent machine is correct.

If you are still seeing the error after confirming that the Job is running under the proper credentials, the authentication between JAMS and the Agent can be disabled so that the Job will be allowed to start.  To do so, edit the User.config file located on the JAMS Agent machine or the Common.config file located on the JAMS Scheduler machine:
 
JAMS Agent User.config - Edit this file if you would like to disable authentication between the Server and Agent for only that one specific JAMS Agent.  This file is located on the JAMS Agent machine in the Program Files/MVPSI/JAMS/Agent directory.

JAMS Scheduler Common.config -
Edit this file if you would like to disable authentication between the Server and Agents for all Agents.  The file is located on the JAMS Scheduler machine in the Program Files/MVPSI/JAMS/Scheduler directory. 
 
When editing the file, change the DisableAuthentication key value from 0 to 1 to disable it.  If the DisableAuthentication key does not exist (for example, if editing the Common.config on the Scheduler machine), you can add it to the existing Common.config file using the following syntax:
 
<add key="DisableAuthentication" value="1"/>



Rate this Article:

Add Your Comments


Name: *
Email Address:
Web Address:
   
  
 
 
   
Verification Code:
*
 

Details
Last Modified:Wednesday, November 30, 2011

Last Modified By: ChrisW

Type: HOWTO

Rated 4 stars based on 2 votes.

Article has been viewed 176 times.

Options