Problem:
The DVA does not start.
Possible Cause:
The --home switch is missing.
Action:
Make sure the --home switch provides the correct path to the DVA working directory. This switch is required to start the DVA and must be provided in the DVA startup file.
Possible Cause:
The --home switch points to an unavailable location.
Action:
Make sure the location specified by the ‑‑home switch is currently available to the DVA.
If the working directory is located on a different Windows server from where the DVA will run, you must create the drive mapping to the working directory before starting the MTA.
Possible Cause:
The server where the working directory resides is down.
Action:
Check the status of the server where the working directory resides.
Possible Cause:
The DVA does not have sufficient rights to the working directory.
Action:
Make sure the network rights in the working directory are correct.
Problem:
On Windows, the DVA is configured as a Windows service, and it fails to restart automatically when the Windows server restarts.
Action:
If you configured the DVA service to run as the Local System account on the Windows server, make sure that the --home switch is specified using a mapped drive format to the c: drive, and not a UNC path to the server.
DVA Shuts Down Unexpectedly
Problem:
The DVA has been running smoothly, but stops unexpectedly.
Action:
Make sure that the DVA is completely stopped. Use the system procedure for terminating a program.
Action:
If the DVA shuts down again, exit it again, reboot the server, then start the DVA again.
Action:
Contact Novell Support for assistance. Have a current log file available. If the DVA is running on Linux, look for a core file in the DVA home directory.
Documents Not Being Converted
Problem:
WebAccess users notice that attached documents are not viewable in their Web browsers. Windows client users notice that attached documents are not being indexed.
Action:
Restart the DVA.