Upon invocation, SAS Warranty Analysis might have a problem when it reads logical server definitions from the SAS Metadata Server. The problem is that the information-service queries do not restrict the search to just the metadata server. If you have access to the SAS^® Content Server, then the information service also searches that server, and the queueing start-up code might fail. The queueing start-up code failure is indicated by a Java stack trace in a log file.

For release 4.2, the stack trace is in the Analytics Platform log.

For release 4.3, the stack trace is in the application server's log file.

As a workaround, remove access to the content server.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for SAS Warranty Analysis 4.2_M1 is available at: