Troubleshooting tips
Occasionally you may encounter a situation when the Universal Capture Component may not function properly. Refer to the information in this chapter to help you resolve the situation before calling Technical Support.
On the AutoStore side, Status Monitor can be used to see logging information.
| Problem | Possible Cause | Solution |
|---|---|---|
| Firewall configuration | When Windows Firewall asks about APD, it enables network communication
for that process on any ports. This leads to a misleading situation where
the external application works when used during configuration but stops
working - as it fails to send documents - since batch.exe
is not permitted to use networks. |
Configure Windows Firewall to explicitly enable network access from and
to the AutoStore and external servers, on the listed ports:
To verify the firewall settings are appropriate, enable the telnet client
role in Windows server, and use that to verify a connection can be made
at the remote port.
Note: When hostnames are used in the configuration,
IPv6 might take priority. Configure Windows Firewall to permit the
appropriate IP addresses.
|
APD config vs batch.exe started |
When AutoStore service batch.exe is running, it is
already using the configured ports, so the component fails when trying to
open a listening socket for that given port. |
Before a configuration change (for example, adding a new document class), stop the AutoStore service. |