Note: Applies only to DocuShare 6.6.1 and 6.5.3.
Issue
Even though you may have installed DocuShare on a 64 bit OS, DocuShare may not still be in 32 bit architecture. Or it is also possible that only the components of IDOL server are running in 64 bit mode.
Solution
You can use any one of the following two methods to verify that all DocuShare components are running in 64 bit mode.
Method 1:
1. Open a Command Prompt window on the DocuShare server.
2. Change into the \jdk1.6.0\bin> directory.
Where is replaced with the installation directory for DocuShare. The default installation path is C:\Xerox\Docushare. Depending on your installation environment the path may vary.
3. Type java –version and press Enter.
· On a 64 bit server, you should see 64 bit JVM:
C:\Xerox\Docushare\jdk1.6.0\bin>java -version
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed
mode)
· If your installation is 32 bit, you will see:
C:\Xerox\Docushare661\jdk1.6.0\bin>java -version
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
Java HotSpot(TM) Client VM (build 19.1-b02, mixed mode)
Method 2:
1. Open Task Manager on the DocuShare server.
2. Select the processes tab.
3. Check for the following processes
Note: The DocuShare processes must be running in native 64 bit mode without the WOW 64 emulation like dsarchive.exe*32, dsconvert.exe*32, etc.
For example:
· AutonomyDiSH.exe
· AutonomyFileSystemFetch.exe
· AutonomyIDOLServer.exe
· Content.exe
· dsarchive.exe
· dsconvert.exe
· dssearch.exe
· dsserver.exe
· dssubscript.exe
· dstomcat.exe
· dsworkflow.exe
· java.exe
· rmiregistry.exe
· start_docushare.exe
· dsix.exe (6.5.3 and above)
Solution Published: August 23rd, 2012
Solution ID: 1182