If the OnBase Client or Configuration modules do not seem to use DCS verify that the communication is working and that OnBase has network access to the DCSserver. If communication is not successful, the following may be the source of the problem:
-
The network address is incorrect. The DCS console shows the network addresses that can be used to access it. The network address can have one of these forms:
-
TCP/IP (1.2.3.4): use this form to diagnose network problems if the other forms listed will not work.
-
Domain (workstation.domain.com)
-
Windows (workstation)
-
-
The port number is incorrect. If the port is correct, then the network routers and/or gateways may be blocking the port number.
-
DCS is not running on the workstation at the network address.
-
UDP traffic may be blocked between the OnBase Client or application server and the DCS server. DCS requires unrestricted bidirectional network access for User Datagram Protocol (UDP) and Transmission Control Protocol (TCP) on the specified port.
-
If the network is having difficulty maintaining a persistent connection, you can select Use non-persistent TCP connections (old method), located in the Storage Integration for EMC Centera® dialogue box, to reconnect to the DCS server with each file request instead of maintaining a persistent connection. This will result in slower transfer times for files retrieved, and is not recommended for long-term usage.
Centera SDK versions prior to 3.0 cannot write files larger than 10 megabytes to Centera Disk Groups when the uncommitted copy (Copy 1) is accessed via Storage Integration for EMC Centera® (DCS), FTP, or any other non-UNC method. If a user attempts to commit files 10 megabytes or greater, an error is encountered and the file is moved to the Incomplete Commit Queue under Platter Management. To resolve this error, the Centera SDK must be upgraded to version 3.0 or greater. Contact your first line of support for assistance.