After using the SAS^® Migration Utility to migrate from SAS^® 9.1.3 to 9.2 in a four-tier Business Intelligence environment, the following error message appears when you schedule a SAS Web Report Studio report:

Report schedule failed, operation (setSchedulerInfo), 
status (The scheduler login failed for this job.(5)).

The job fails, and in jfd.log, this error message appears to indicate that the wrong credentials are being used for scheduling:

2009 Mar 13 16:45:40 10655 46 8 JFEauthManager::verifyEauth: invoked, user [ctnwadm]
2009 Mar 13 16:45:40 10655 46 7 nb_read_fix: Entering this routine...
2009 Mar 13 16:45:41 10655 46 3 JFEauthManager::verifyEauth: eauth len=6 failed; rc=0.
2009 Mar 13 16:45:41 10655 46 7 JFGenericDaemon::startup:Authentication failed for user [ctnwadm]

Note: To see the error message, you will need to use a debug option. Otherwise, you will see only the verifyEauth: eauth message. See SAS notes 30570 "Turning on the debugging facility for the job-flow daemon in the UNIX environment" and 33147 "Turning on the debugging facility for the job-flow daemon in the Windows environment" for instructions on turning on debugging in the UNIX and in the Windows environments, respectively.

These error messages appear because the SAS Web Report Studio 4.2 environment uses LSF Platform-based scheduling with an incorrect user ID and password to communicate between SAS Web Report Studio and LSF Platform. SAS Web Report Studio is designed to use a single credential for all communication to LSF Platform, sufficient to run commands on the schedule server in the operating system. It is not used to contact metadata. This credential is supposed to be part of the administrator user IDs that are managed centrally with the SAS^® Deployment Manager, but this integration is currently not working as designed.

Workaround

You need to define both of these properties so that SAS Web Report Studio can "read" them:

• wrs.scheduling.LSFSchedulingServerUID
• wrs.scheduling.LSFSchedulingServerPw

These properties are designed as overrides for the properties that instead should be coming from the secure environment properties space that managed by the SAS Deployment Manager.

You have two choices of where to place these properties.

Choice 1:

1. Open SAS^® Management Console.
2. Navigate to the SAS^® Configuration Manager.
3. Select SAS Web Report Studio 4.2, right-click Properties, and select the Advanced tab.
4. Select the Add button and add each property and its value.

   Note: The password can be in clear text or pwencode encoded.

5. Select OK and OK.

• Advantage: Easy.
• Disadvantage: Leaves this user ID and password readable in metadata.

Choice 2

1. Open a text editor.
2. In the customer subdirectory of the SAS Web Report Studio installation directory, locate the LocalProperties.xml.sample file.
3. Make a copy of this file and name it LocalProperties.xml, if necessary.
4. Edit the LocalProperties.xml to add these two properties.

   Note: This file is XML, and has some internal documentation suggesting how to add properties.

• Advantage: Can be securred if machine/folder is secure
• Disadvantage: A more technical change.

IMPORTANT: Restart SAS Web Report Studio so that it "recognizes" the new properties.

Operating System and Release Information