Note: This applies to DocuShare 6.6.1.
Issue
Important: It is very important to LOOK at the Stack Trace Message to determine the issue that caused the problem. If the error displayed in the Stack Trace does not look similar to the error listed below then click the Error Code: 0 Couldn’t get a stream to file: solution link listed at the bottom of the page.
When trying to download a document the following error is displayed on the Web UI:
Note: The keywords to look for in the error have been highlighted in red in the example listed below to make it easier for you to determine if this solution applies.
Example:
System Error
Error Code: 0
Couldn't get a stream to remote file: C:/Xerox/DS_6.5.2/documents/b379\File-891\Version-341\application-pdf\Document-891_Version-341_application-pdf_0; nested exception is: java.rmi.ServerError: Error occurred in server thread; nested exception is: java.lang.StackOverflowError
When trying to upload a file the following error is displayed in the Web UI:
Note: The keywords to look for in the error have been highlighted in red in the example listed below to make it easier for you to determine if this solution applies.
Example:
System Error
Error Code: 700
Unspecified content problem.
OR
System Error
Error Code: 1100
Unspecified DSServer problem.
Stack Trace:
com.xerox.docushare.DSContentElementException: Couldn't get a stream to remote file: C:\Xerox\DS_6.5.2\tmp\Amber5020209194592519062.tmp; nested exception is:
java.rmi.ServerError: Error occurred in server thread; nested exception is: java.lang.StackOverflowError at com.xerox.docushare.FileContentElement.open(FileContentElement.java:209)at com.xerox.docushare.content.impl.ContentStoreImpl.addContent(ContentStoreImpl.java:714) at com.xerox.docushare.impl.server.BackendSessionImpl.saveContentInCS(BackendSessionImpl.java:8555)at com.xerox.docushare.impl.server.BackendSessionImpl.createDocument(BackendSessionImpl.java:5887) at com.xerox.docushare.impl.server.BackendSessionImpl.createDocument(BackendSessionImpl.java:5222)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305) at sun.rmi.transport.Transport$1.run(Transport.java:159)at java.security.AccessController.doPrivileged(Native Method)at sun.rmi.transport.Transport.serviceCall(Transport.java:155) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) 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:619)
-----nested by:
Reason
This has been known to happen when the DocuShare server is unable to communicate with the Document Repository location.
Solution
Reported to Development. (currently investigating)
Workaround
Restart the DocuShare server to re-establish the connection with the Repository.
Solution Published: October 4th, 2011
Solution ID: 938
AR/SPAR: 0026213 0026213