"Unexpected error" when scheduling or distributing if the SAS® Java Batch Server and the pooled workspace server do not use the same machine


If your environment has multiple server contexts (for example, SASApp, SASApp2), you must ensure that the Java Batch Server and the pooled workspace server defined in the same server context are associated with the same machine. For example, if SAS Web Report Studio is using the SASApp - Pooled Workspace Server, and this server is associated with sasapp.mymachine, then the SASApp - BRM Java Batch Server must also be associated with sasapp.machine. Otherwise, you see an "Unexpected error" message when you attempt to schedule or distribute. In addition, the SAS Web Report Studio log contains the following error:

2012-02-15 16:34:43,729 [http-443-18] ERROR [48c2fd22977cc35e:-2e10b99:1357ef5ea83:-68f7SAS Demo User] com.sas.apps.citation.controller.action.report.ScheduleWizardAction - Root Cause:   java.lang.NullPointerException
    at com.sas.scheduler.api.oma.MetaUtilities.getBatchServer(MetaUtilities.java:971)
    at com.sas.scheduler.api.oma.DeployedJob.getInfo(DeployedJob.java:864)
    at com.sas.scheduler.api.oma.DeployedJob.getInfo(DeployedJob.java:827)
    at com.sas.scheduler.api.oma.DeployedFlow.setJobInfo(DeployedFlow.java:3663)
    at com.sas.scheduler.api.oma.DeployedFlow.getInfo(DeployedFlow.java:3523)
    at com.sas.scheduler.api.oma.BatchJob.scheduleNowHelper(BatchJob.java:3492)
    at com.sas.scheduler.api.oma.BatchJob.runNow(BatchJob.java:2101)
    at com.sas.apps.citation.model.scheduler.ScheduleManager.scheduleCommit(ScheduleManager.java:1613)
    at com.sas.apps.citation.model.scheduler.ScheduleManager.scheduleBurstDefinition(ScheduleManager.java:1566)
    at com.sas.apps.citation.controller.action.report.ScheduleWizardAction.scheduleReport(ScheduleWizardAction.java:982)
    at com.sas.apps.citation.controller.action.report.ScheduleWizardAction.doPerform(ScheduleWizardAction.java:195)
    at com.sas.apps.citation.controller.action.CitationAction._execute(CitationAction.java:191)
    at com.sas.apps.citation.controller.action.CitationAction.execute(CitationAction.java:166)
    at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:425)
    [ 57 lines suppressed ]
Which Caused: com.sas.apps.citation.model.scheduler.WRSSchedulerException: Unexpected exception. [ java.lang.NullPointerException ] 
    at com.sas.apps.citation.model.scheduler.ScheduleManager.scheduleBurstDefinition(ScheduleManager.java:1574)
    at com.sas.apps.citation.controller.action.report.ScheduleWizardAction.scheduleReport(ScheduleWizardAction.java:982)
    at com.sas.apps.citation.controller.action.report.ScheduleWizardAction.doPerform(ScheduleWizardAction.java:195)
    at com.sas.apps.citation.controller.action.CitationAction._execute(CitationAction.java:191)
    at com.sas.apps.citation.controller.action.CitationAction.execute(CitationAction.java:166)
    at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:425)
    [ 57 lines suppressed ]

Note: The same requirements apply if your deployment uses the standard workspace server instead of the pooled workspace server.