Then,
check to determine whether any logs were created by the Output Generation
Tool. For a default Windows installation, the logs are located in
the following path:
C:\Program Files\SAS9.2\SASBIReportServices\4.2\logs
For a
default UNIX installation, the path is as follows:
SAS-config-dir/lev
x/Applications/SASBIReportServices42/logs
If no
logs are present in this path, check to make sure that you have completed
these tasks:
-
-
-
accurately entered the command
in the
Command Line field when you defined
the SAS Java Batch Server in SAS Management Console.
See Step 2: Verify That a SAS Java Batch Server Has Been Defined .
Make sure that quotation
marks appear around the arguments, as shown in the example. If you
copied and pasted the command, make sure that a space appears after
outputgen.exe
.
On Windows systems,
you can verify the command by pasting it into a DOS command window.
The command should execute with no errors.
If logs are present in the path, then check for the
following error messages:
An error occurred: Unable to login user. Cause:
Access denied.
or
Caused by: com.sas.iom.SASIOMDefs.GenericError:
Error authenticating user SAS Trusted User in function LogonUser
.
Make sure that the
user ID and password for the SAS Trusted User (sastrust) are specified
correctly in the OutputManagementConfigTemplate.xml
file. You might need to remove the domain, or make sure that the
domain is followed by a forward slash (/) rather than a backward slash
(\).
An error occurred: Exception while rendering
report in batch. Cause: cxp.002.ex.msg: The connection factory requires
an identity for the authentication domain "DefaultAuth", but the user
context provided for user "SAS Demo User" does not have any identities
for that domain. Therefore, the user cannot be authorized to use the
connection factory.
For additional troubleshooting information, see Resolving Issues Related to Scheduling with Platform Suite for SAS .