SUPPORT / SAMPLES & SAS NOTES
Problem Note 66471: SAS® Visual Analytics report distributions are not received and the history indicates that they completed with a nonzero exit code
 |  |  |  |  |
SAS Visual Analytics might fail to deliver distributed reports even though there are no errors or warnings when you create the distribution and all other requirements have been met. If you view the history of the distribution, you see the following message:
When this problem occurs, the SAS Visual Analytics Hyperlink log contains the following errors, indicating that the VADistributionJobRunner failed to launch:
LINK ERROR [Thread-149] 2020-08-11 11:15:32,971 [unknown:unknown] com.sas.bicommon.distribution.Launcher - ERROR initializing Launcher
com.sas.bicommon.distribution.VADistributionJobRunnerInitializationException: VADistributionJobRunner launcher error
at com.sas.bicommon.distribution.Launcher.init(Launcher.java:201)
at com.sas.bicommon.distribution.Launcher.access$000(Launcher.java:45)
at com.sas.bicommon.distribution.Launcher$1.run(Launcher.java:85)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NullPointerException
at com.sas.services.user.UserContext.setSessionContext(UserContext.java:782)
at com.sas.services.session.SessionService.newSessionContext(SessionService.java:607)
at com.sas.services.session.SessionServiceProxy.newSessionContext(SessionServiceProxy.java:95)
at com.sas.bicommon.distribution.Launcher.ensureSessionCorrect(Launcher.java:317)
at com.sas.bicommon.distribution.Launcher.locateTrustedUser(Launcher.java:221)
at com.sas.bicommon.distribution.Launcher.init(Launcher.java:101)
... 3 more
com.sas.bicommon.distribution.VADistributionJobRunnerInitializationException: VADistributionJobRunner launcher error
at com.sas.bicommon.distribution.Launcher.init(Launcher.java:201)
at com.sas.bicommon.distribution.Launcher.access$000(Launcher.java:45)
at com.sas.bicommon.distribution.Launcher$1.run(Launcher.java:85)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NullPointerException
at com.sas.services.user.UserContext.setSessionContext(UserContext.java:782)
at com.sas.services.session.SessionService.newSessionContext(SessionService.java:607)
at com.sas.services.session.SessionServiceProxy.newSessionContext(SessionServiceProxy.java:95)
at com.sas.bicommon.distribution.Launcher.ensureSessionCorrect(Launcher.java:317)
at com.sas.bicommon.distribution.Launcher.locateTrustedUser(Launcher.java:221)
at com.sas.bicommon.distribution.Launcher.init(Launcher.java:101)
... 3 more
As a workaround, ensure that the web application server in SASServer12_1 starts up before the web application server in SASServer1_1. SASServer12_1 identifies the web application server on which SAS Visual Analytics is deployed.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Visual Analytics | Microsoft® Windows® for x64 | 7.5 | 9.4 TS1M6 | ||
| Linux for x64 | 7.5 | 9.4 TS1M6 | ||||