Worldox Troubleshooting

Last reviewed: 02/01/2012
Article ID: R10656

The information in this article applies to:

SUMMARY

With the difficulties inherent in third party integration comes the potential for unexpected results and errors. This document may be used to troubleshoot some of the possible problems and error messages that may occur with the PracticeMaster/Worldox integration or with Worldox in general. Software Technology, Inc. cannot guarantee the functionality or stability of any third party system nor does Software Technology, Inc. assume any rights or responsibilities over these systems. Questions or concerns regarding Worldox, not relating to this integration, should be directed to World Software Corporation at 201-444-3290 or on the Internet at www.Worldox.com.

General Troubleshooting

Worldox Issues

PracticeMaster/Worldox Integration Messages

Worldox Messages

General Troubleshooting

Before beginning troubleshooting, verify that Worldox integration is enabled. From the PracticeMaster menu, select Maintenance, point to Integration, and click Worldox Integration. Verify that the check box for Worldox integration is selected. If not, select this option and restart PracticeMaster and Worldox to verify that integration is working.

Worldox Issues

Worldox GX2 issue: New PracticeMaster clients and changes to existing PracticeMaster clients not appearing in Worldox

This issue is generally caused by a change included in an update to Worldox GX2. If you notice this issue, you can resolve it by updating the Tabs3 and PracticeMaster software to version 15.3.2.197 or higher.

Worldox GX issue: New PracticeMaster clients not appearing in Worldox

The most common cause of this issue is that Worldox was not open before PracticeMaster was opened. Check to make sure Worldox is open at your workstation. If it is not open, you will need to close PracticeMaster, then open Worldox on your workstation and re-open PracticeMaster.

This error has also been found to be related to the initial releases of Worldox GX Service Release 1. Check the modified date of the WDAPI32.DLL file. If it is after 09/14/2007 and before 1/10/2008, and you are a Worldox maintenance user, please run WDUPDATE.EXE from your Worldox program directory to update to the most current program files.

Additionally, the Worldox client and/or matter table could become corrupt if too many users are adding or changing client information at the same time. This issue has also been resolved with the 1/10/2008 Worldox update.

If you have some clients coming over but not all clients, check the Worldox Client table for clients with prepended zeros. Worldox has their own setting for forcing fields to be a certain length. So Client 22 in PracticeMaster could be record 0022 in Worldox.

If there are prepended zeros and you do not have the "Prepend zeros to client numbers" option selected in Worldox Integration, in PracticeMaster, you will have to go to the profile group in Worldox (WDADMIN | Profiles | Add | Edit) and make sure the field property of Field Format is blank.

Note: If you have the "Prepend zeros to Client Numbers" option selected and need to change the Maximum Entry Length, you will need to call Worldox and have them help you fix your existing Client Table in Worldox.

Worldox GX issue:  Wrong file opens from Worldox Search

When performing a Worldox Search, opening the documents found may not work correctly. The first time you open a document, it will work. However, subsequent attempts to open a different file from the search results will result in the previous file being mistakenly opened instead. This is a known issue with Worldox GX. If you are a Worldox maintenance user, please run WDUPDATE.EXE from your Worldox program directory to update to the most current program files and resolve this issue. 

Worldox GX issue:  Documents not displaying properly

If you choose to display Worldox documents in the client file, it displays the wrong documents.  For example, if you select a client with a .00 matter number, you will get all the documents for all clients with a matter of .00. This is a known issue with Worldox GX. If you are a Worldox maintenance user, please run WDUPDATE.EXE from your Worldox program directory to update to the most current program files and resolve this issue.

Worldox GX2 issue:  Documents not prompting to save to Worldox

After upgrading to Worldox GX2, documents are no longer prompting to save to Worldox. This is caused by a setting being changed during the installation. If you are a Worldox maintenance user, please run WDADMIN.EXE from your Worldox program directory, locate the Microsoft Word program and select the Save by X option. This will re-enable the Worldox save prompt.

Worldox GX2 issue: No prompt to save in Worldox after Word Document Assembly

When using Word Document Assembly, the prompt for a Worldox save was not happening. Other times when the save would appear to work, the correct client matter information would not be filled out. The cause for these issues was a change in Worldox GX2 and how it requires the information to be sent. To fix these issues, update to the most recent PracticeMaster Version 15.2 or later software (November 2009 or greater release date).

Worldox incorrectly displays when opening a dialog in PracticeMaster or Tabs3.

This situation was known to occur when opening the "Select Files" dialog from both PracticeMaster and Tabs3 Reindex programs. On some systems, Worldox would display a Word Perfect 9 File Compare dialog when attempting to select files in PM or Tabs3. This issue is a direct result of the way Worldox determines if it should display its own windows. If a dialog opens that contains the same title bar text and the same properties as a dialog it is designed to search for, Worldox may incorrectly intervene because it cannot differentiate between the two dialogs. This issue has been corrected for the "Select Files" dialog.

Worldox's DropZone hangs or crashes when dragging an item or an e-mail attachment from the DropBox to the DropZone.

This issue only applies to PracticeMaster Version 12 and is a known issue with the Worldox software. Updating to Worldox GX will correct this.

No Worldox results are displayed when including Worldox in PracticeMaster's Conflict of Interest Search.

Keep in mind that the Worldox Indexing Service must be run before Worldox results can be included in PracticeMaster's Conflict of Interest Search. For more information, please see the Help provided with PracticeMaster.

Worldox Document List is Not Displayed

If PracticeMaster's Display Worldox Documents is displaying documents for some client and not others, and you know there are documents saved under the clients not displaying documents, the following could explain this. When using the Display Worldox Documents button, we send a search string to Worldox based on how your PracticeMaster and Worldox integration is set up. If you do not have the "Prepend Zero's to client numbers" option selected, PracticeMaster sends over the Client ID exactly as it is displayed in PracticeMaster (e.g., Client 22.00 would be sent over as Client = 22 Matter = 00). However, if the "Prepend zeros to Client Numbers" option is selected, PracticeMaster sends over the number of characters your current Key Type is set to (e.g., If you have Decimal Places of 2 in PracticeMaster, search string of Client = 000000022 Matter = 00 would be sent).

If you Worldox Client Table structure does not match either of these, you will want to check Profile properties and make sure the Field Format is blank.

Note: If you have the "Prepend zeros to Client Numbers" option selected and need to change the Maximum Entry Length, you will need to call Worldox and have them help you fix your existing Client Table in Worldox.

PracticeMaster/Worldox Integration Messages

You must first install Worldox before you can enable integration.

This message may occur from the Worldox Integration dialog if you do not have Worldox installed but attempt to enable the integration check box.

The value of this key defines where the Worldox program and API may be found. If this key or value is not found, the program is either not installed or problems occurred during the installation before this key could be created. A corrupt registry may also cause problems.

Worldox must be running to initialize settings. Integration is temporarily disabled.

This message will occur from the Worldox Integration dialog if Worldox is not running while the dialog is open and the integration check box is enabled. The Worldox API is only functional when Worldox is running, therefore PracticeMaster is unable to extract any information or settings. Start Worldox then re-enable the integration check box.

PracticeMaster found no Worldox Profile Groups.

Verify that a Profile Group is defined in Worldox that contains "Client" and "Matter" as fields or "Case" as a field. It makes no difference which fields in the Profile Group are used for these fields. However, the field descriptions for these Profile fields must actually be labeled as "Client" and "Matter" or "Case".

You must also have the correct permissions for this Profile Group.

When the integration switch is enabled, PracticeMaster queries the Worldox databases for Profile Groups that it is able to integrate with and fills in the selection box with these choices. PracticeMaster considers a Profile Group to be valid if one or both of the following is true: 1) there is a field called "client" and a field called "matter"; or 2) there is a field called "case". The client, matter and case field names are all case insensitive. There is also the possibility that one of these profile groups does in fact exist, but it cannot be used by the current Worldox user because of incorrect permissions. If there are no valid Profile Groups available to the current Worldox user, integration cannot occur. Profile Groups and permissions are defined within the Worldox program.

GX Note:  This error has been found to be related to the initial releases of Service Release 1 of GX. Check the modified date of the WDAPI32.DLL file. If it is after 09/14/2007 and before 1/10/2008, and you are a Worldox maintenance user, please run WDUPDATE.EXE from your Worldox program directory to update to the most current program files.

GX2 Note: This error has been found to occur when integrating PracticeMaster with Worldox GX2 and using WDMIRROR.EXE, the workstation executable. This is an issue with the API on the Worldox side and Worldox does have an unpublished patch available for this issue. To receive this patch, clients need to contact Support at Worldox, 201-444-3290.

PracticeMaster found no Worldox Profile Groups.
     ...or...
You must first logon to PracticeMaster.

These errors have been found to occur when Worldox GX2 is installed in a path that contains a space character (e.g., C:\Program Files\Worldox). Worldox has confirmed that at this time, Worldox does not allow space characters in the folder name. To resolve this issue, you must move the Worldox folder to a location that does not include a space character, or remove the space from the folder name.

You are configured to integrate with Worldox, but Worldox is not currently running. You must restart this program with Worldox running or re-enable integration with Worldox in order for integration to be successful.

This message may occur during PracticeMaster startup if integration is enabled but Worldox is not currently running. The Worldox API is only functional when the program is running. You will need to start Worldox and then either restart the Tabs3 or PracticeMaster program or go to the Worldox Integration dialog and re-enable the integration check box.

Could not find Worldox in the registry, integration aborted.

This message may occur when starting PracticeMaster if PracticeMaster has been configured to integrate with Worldox. Though Worldox may already be running, PracticeMaster could not get the installation path defined in the registry key:  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\WORLDOX.EXE. Since no path could be found, PracticeMaster is unable to load the appropriate DLLs for the integration. Please consult Worldox for possible causes or solutions.

Could Not access \\<ComputerName>\Worldox\wduser.ini.

This message appears because the Windows User does not have access rights to the directory. If running Version 15, make sure your programs are dated after 9/9/09.

One work-around to avoid receiving this message is to launch PracticeMaster using the "Run as" or "Run as administrator" option and enter administrative credentials.  Running PracticeMaster with administrative rights will bypass all elevation prompts in the software.

Could not access "\\<path to the Worldox INI file>"\wduser.ini.

Note: The <path to the Worldox INI file> may contain non-standard characters.

This message may occur on PracticeMaster workstations configured to integrate with Worldox GX2. The issue affects Worldox GX2 workstations installed after Jan. 22, 2010 and can be resolved by installing an update to Worldox GX2. If you are experiencing this issue, running WDUPDATE.EXE will download the update needed. If you have any trouble downloading or installing this update, please contact Worldox technical support for further assistance.

For integration, you must have at least Worldox 8 - Service Pack 3. Please consult Worldox to obtain this latest release.

PracticeMaster has determined that the v2 API included with Worldox does not contain the necessary functionality. To determine if you have an appropriate version of the API, select Help | About in Worldox; the date displayed must be 07/04/00 or later. Updates of Worldox SP3 and all versions of Worldox 2000 should contain the necessary functionality. Though Software Technology, Inc. has determined this to be a minimum API requirement and has tested several releases of this API, Software Technology, Inc. does not imply nor guarantee the functionality of any third party API. Please consult Worldox for newer versions of the API.

Error % loading WDAPI32.DLL (Worldox v2 API), Worldox integration aborted.

This message may occur when loading the Worldox version 2 API from the directory specified by the registry key. If the DLL is not found or cannot be loaded, % will be replaced by the error code returned by the operating system. This DLL must load correctly for integration to occur.

Error % loading WDWRDM32.DLL (Worldox v1.2 API), integration aborted.

This message may occur when loading the Worldox version 1.2 API from the directory specified by the registry key. If the DLL is not found or cannot be loaded, % will be replaced by the error code returned by the operating system. Though PracticeMaster requires the v2 API, some of the functionality comes from the old API. At the time of this writing, the old API was not yet included in the v2 API so PracticeMaster must also load the old API. Until this API is included with v2, this DLL must also load correctly for integration to occur.

Could not initialize Worldox integration. Integration has been disabled.

While the previous three error messages may occur as a result of PracticeMaster's attempt to ensure that the correct APIs are present, this message may occur as a result of the correct APIs lacking the needed functionality. It is during this time that verification of every possible feature and function call used by PracticeMaster is made. This error may have resulted from an early release of the v2 API or an incomplete API and is the last check PracticeMaster makes before determining if it can or cannot successfully integrate with Worldox.

Worldox Messages

The ordinal 30 could not be located in the dynamic link library MAPI32.dll.

This message may occur when starting Worldox 2002 when a MAPI e-mail program other than Microsoft Outlook (e.g., GroupWise) has been installed and that MAPI e-mail program modified the MAPI32.dll file. To resolve this error, contact World Software Corporation at 201-444-3290 or on the Internet at www.Worldox.com.


© 1999-2012 Software Technology, Inc.   All rights reserved. Terms of Use
The maker of Tabs3 and PracticeMaster
Tabs3, PracticeMaster, and the “pinwheel” symbol (The "Pinwheel" symbol is a Registered Trademark of Software Technology, Inc.) are registered trademarks of Software Technology, Inc.
e-Mail Suggestions for the Knowledge Base to: kb@Tabs3.com
Technical Support via e-mail is not available.
Knowledge Base:   http://support.Tabs3.com
Web Site:   http://www.Tabs3.com