SUPPORT

Select Your Region

Visit the Cary, NC, US corporate headquarters site

Americas

Europe

Middle East & Africa

Asia Pacific

View our worldwide contacts list for help finding your region

Americas

Europe

Middle East & Africa

Asia Pacific

Sign In

Get access to My SAS, trials, communities and more.

Sign Out

Get access to My SAS, trials, communities and more.

SAS Sites

sas.com
Support
Blogs
Communities
Developer
Curiosity
Videos

Documentation

Learn
Brand
PartnerNet
Merchandise
SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 49559: No SAS® log is produced when you run a SAS® task from within SAS® Model Manager

DetailsHotfixAboutRate It

No SAS log is produced when you run a SAS task (such as the scoring task or any reports) within SAS Model Manager. The lack of a SAS log results in empty task log files (for example, taskCode.log, PerformanceMonitor.log, or ModelRetrain.log).

In addition, the following Java stack-trace error appears in the SASWIPServices9.x.log file that resides in SAS_configuration_directory\Lev1\Web\Logs\:

ERROR [unknown] org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/SASWIPServices].[remote] - Servlet.service() for servlet [remote] in context with path [/SASWIPServices] threw exception
java.io.StreamCorruptedException: invalid stream header: 6C6F676F
	at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:782)
	at java.io.ObjectInputStream.(ObjectInputStream.java:279)
	at org.springframework.core.ConfigurableObjectInputStream.(ConfigurableObjectInputStream.java:64)
	at org.springframework.remoting.rmi.CodebaseAwareObjectInputStream.(CodebaseAwareObjectInputStream.java:97)
	at org.springframework.remoting.rmi.RemoteInvocationSerializingExporter.createObjectInputStream(RemoteInvocationSerializingExporter.java:122)
	at org.springframework.remoting.httpinvoker.HttpInvokerServiceExporter.readRemoteInvocation(HttpInvokerServiceExporter.java:114)
	at org.springframework.remoting.httpinvoker.HttpInvokerServiceExporter.readRemoteInvocation(HttpInvokerServiceExporter.java:95)
	at org.springframework.remoting.httpinvoker.HttpInvokerServiceExporter.handleRequest(HttpInvokerServiceExporter.java:72)
	at org.springframework.web.servlet.mvc.HttpRequestHandlerAdapter.handle(HttpRequestHandlerAdapter.java:49)
	at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:900)
	at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:827)
	at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:882)
	at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:789)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
	at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:929)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
	at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1002)
	at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:585)
	at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)

No workaround is available for this problem.

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



Operating System and Release Information

Product FamilyProductSystemSAS Release
ReportedFixed*
SAS SystemSAS Model ManagerMicrosoft Windows Server 2003 Enterprise Edition9.3 TS1M29.3 TS1M2
Microsoft Windows Server 2003 Datacenter Edition9.3 TS1M29.3 TS1M2
Microsoft® Windows® for x649.3 TS1M29.3 TS1M2
Microsoft Windows Server 2003 Standard Edition9.3 TS1M29.3 TS1M2
Microsoft Windows Server 2003 for x649.3 TS1M29.3 TS1M2
Microsoft Windows Server 20089.3 TS1M29.3 TS1M2
Microsoft Windows Server 2008 for x649.3 TS1M29.3 TS1M2
Microsoft Windows XP Professional9.3 TS1M29.3 TS1M2
Windows 7 Enterprise 32 bit9.3 TS1M29.3 TS1M2
Windows 7 Enterprise x649.3 TS1M29.3 TS1M2
Windows 7 Home Premium 32 bit9.3 TS1M29.3 TS1M2
Windows 7 Home Premium x649.3 TS1M29.3 TS1M2
Windows 7 Professional 32 bit9.3 TS1M29.3 TS1M2
Windows 7 Professional x649.3 TS1M29.3 TS1M2
Windows 7 Ultimate 32 bit9.3 TS1M29.3 TS1M2
Windows 7 Ultimate x649.3 TS1M29.3 TS1M2
Windows Vista9.3 TS1M29.3 TS1M2
Windows Vista for x649.3 TS1M29.3 TS1M2
64-bit Enabled AIX9.3 TS1M29.3 TS1M2
64-bit Enabled Solaris9.3 TS1M29.3 TS1M2
HP-UX IPF9.3 TS1M29.3 TS1M2
Linux for x649.3 TS1M29.3 TS1M2
Solaris for x649.3 TS1M29.3 TS1M2
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.