HOWTO: Troubleshoot a Zetadocs for NAV Installation
This Zetadocs technical note applies to:
- Zetadocs for Microsoft Dynamics NAV
This technote describes how to troubleshoot a Zetadocs for Microsoft Dynamics NAV system.
This technote provides help with resolving common problems with the system. To assist in trouble shooting problem with the Zetadocs system there are a number of log files which can help diagnose a problem or assist in getting the configuration of the system correct.
Ensure that Logging Enabled is ticked ON in the Zetadocs System Settings Form. The Logging Level determines the amount of information written to the log file. For general configuration and trouble shooting, WARNING or ERROR should suffice. The NAV log is saved to the users temp folder location. This can be found by either pressing Start > Run, then type %Temp% and press OK; or manually browse to C:\Users\< username> \AppData\Local\Temp(Vista) or C:\Documents and Settings\< username> \Local\Temp(XP) directory.
There are two logs produced by the Zetadocs for NAV Addin.
- ZdExternalUtilitiesDll.log - logging of document queue actions and external calls to Zetadocs API. Only valid for troubleshooting issues with Equisys.
- ZetadocsNAV.log - standard logging of activity that occurs in the Zetadocs for NAV objects.
Please refer to the Zetadocs Client help for information on client logging.
The Zetadocs API runtime, which is used as part of the Zetadocs for NAV addin logs information to the users Zetadocs folder. Its contents are usually of value when troubleshooting issues with Equisys.
It can be found at:
- C:\Users\< username> \AppData\Local\Equisys/Zetadocs PDF/ZdApi.log(Vista)
- C:\Documents and Settings\< username> \Local\ApplicationData\Equisys\Zetadocs PDF\ZdApi.log (XP).
Object ID collisions when importing the Zetadocs objects .fob file
Unless you are re-importing the objects or performing an upgrade it is unlikely that you will come across an ID collision. If you do, please continue and view the recommendations of the import collision wizard in NAV. It is not recommended to undertake collision resolution unless you are an experienced NAV consultant.
Some objects fail to compile during import of the Zetadocs objects .fob file
Most likely this is due to not having installed the Zetadocs for NAV Client on the machine you are using to import the Zetadocs objects from. Many of the codeunits in Zetadocs for NAV use automation components which must be installed prior to importing to ensure that all objects compile successfully.
Things to check for (in order):
- You have installed the Zetadocs for NAV Client on the machine you are using to import the Zetadocs objects
- You are logged in as the user who installed the Zetadocs for NAV Client
- If the above are true but you are still having problems try uninstalling and re-installing the Zetadocs for NAV Client
When you run the Customer/Vendor Card no information is displayed in the Zetadocs tab
Copy and pasting the Zetadocs subform control on to the Zetadocs tab should copy all required subform links. If you are experiencing problems check the following property values on the subform control on the Zetadocs tab:
- SubFormID: Zetadocs Customer Rule Subform
- SubFormLink: Customer No.=FIELD(No.),Zd Rule ID No.=CONST(0)
OR For Vendors
- SubFormID: Zetadocs Vendor Rule Subform
- SubFormLink: Vendor No.=FIELD(No.),Zd Rule ID No.=CONST(0)
The logs for Zetadocs activity on your SharePoint site can be found in the following locations:
SharePoint 2007 Systems
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS\Zetadocs
SharePoint 2010 Systems
C:\inetpub\wwwroot\wss\VirtualDirectories\80\%CommonProgramFiles%\Microsoft Shared\Web Server Extensions\14\LOGS\Zetadocs
Last updated 19th August 2013 (MW/)