This article describes techniques for troubleshooting Word integration. Note that it is possible to save documents into Worldox using Workzone, so if you have an urgent need, do that first, then turn your attention to the troubleshooting.
First - the interim workaround
If you are not able to get the Save As dialog to pop Worldox right away, you can still save files to Worldox using the WorkZone icon in the interim. For more information on using WorkZone, visit: Save a Document - Workzone
Make sure Worldox is running
If Worldox is not launching when selecting File > Save As in Word, the first thing is to of course check that Worldox is running on this workstation. If it is, please fully close it using the "Close Worldox" option in the System Tray icon. Re-open Worldox, and try your save again.
Make sure your version of Microsoft Office is supported
Worldox does not support integration with any 64-bit version of MS Office (64-bit Windows 7 is fine, but only the 32-bit version of Office).
Worldox also does not support 'Click to Run' or 'Starter Edition' installs of Office 2010 (these are typical 'freebie' installations of Office that ship for free with low-end PCs). For details, see A discussion of 32 vs 64 bit versions of Office.
Worldox does support 'Click to Run' installs of Office 2013, but only if installed and ready for "offline" mode.
Worldox does not support Office 365 plans that DO NOT include Desktop versions, cloud-based storage option of 365 (SkyDrive) for Worldox data or the "On Demand" streaming version of MS Office with Worldox.
Check if the Worldox integration macros are disabled
Office 2003 Users:
Right-click in the Word/Excel toolbar area and select Customize
Under the Toolbars tab, select the Worksheet Menu Bar
Select Reset > OK, then Close
Close Word/Excel
Re-open Word and try the save again
If this doesn't do the trick, please try:
Select Help > About > Disabled Items...
If there are any @Wdtemplates in the list, simply click on them and select "Enable"
Close and re-open Office and test the Save As function
Office 2007 Users:
Click the Window button > Word/Excel Options > Add Ins
Select the drop-down arrow and select "Disabled Items"
That will give you the list of items that are disabled
Select the @WD one from the list and choose Enable
Close and re-open Office and test the Save As function
Office 2016 & 2019 "On Demand", "Trusted Application" or "Windows Store App" version Users:
Worldox does not support these configurations. Make sure Word is installed as a desktop application:
Office 2010, 2013, 2016 & 2019 Users:
Select File > Options
Select "Add-Ins" from the left hand menu
Click on the "Manage:" drop-down arrow and select "Disabled Items", then "Go"
That will give you the list of items that are disabled
Select the @WD one from the list and choose Enable
Close and re-open Office and test the Save As function
Check Word's STARTUP-PATH setting
If your site uses a predefined user profile to configure default settings for new users, there is a possibility that the startup-path (where Word loads it's integration macros from) is pointing at the template user's profile instead of the current user's profile. Here's how to check this:
Open RegEdit
For Office 2010 users: Navigate to HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Word\Options
For Office 2013 users: Navigate to HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Word\Options
For Office 2016 users: Navigate to HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Word\Security\Trusted Locations\Location2
Check the STARTUP-PATH value (or just "Path" for Office16), and confirm that it points to a sub-folder inside the correct user's Windows profile
If the STARTUP-PATH is not set properly, change it
If there is no STARTUP-PATH, you'll need to create one. Here's how:
Under the appropriate path (listed above): HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Word\Options, create value of type 'Expandable String Value' (aka REG_EXPAND_SZ). Name it STARTUP-PATH (for Office versions 2010-2013) or Path (for Office 2016). Set the value to: %appdata%\microsoft\word\startup
Close Worldox and Word
Re-open Worldox
Re-open Word, then test the Save As function
Note: If a newer version of Office was installed on the PC and then later downgraded to an older version, the newer Office installation may have installed registry keys. Worldox uses those keys to determine which version of the software to integrate with and it will always pick the newest key available. You may need to remove (or invalidate) the newer version's registry location (typically done at the folder level with the Office version number 15.0 or 16.0) so that Worldox redirects to the proper registry location.
Check integration template Mirror Down
We have seen a small number of workstations where the Word integration template (@wdword?.dot?) doesn't get mirrored down to the workstation properly, unless the file is manually copied once. We have not yet figured out why this happens, and it happens very infrequently, but the following procedure seems to work:
Close Word and Worldox
Go to %appdata%\microsoft\word\startup - confirm that there is no @wdword template in that folder (if there is, don't use this procedure - template mirror down is not the issue)
Manually copy the C:\Worldox\@wdwordd.dotm (make sure you get the 'F' file for Office 2016, 'E' file for Office 2013, 'D' file for Office 2010, C for Office 2007) into that startup folder
Start Word and Worldox and confirmed that the Save As pops worldox
Close Word and Worldox - IMPORTANT: do not stop here - you must confirm that Worldox will now copy the integration template down automatically, otherwise future updates will not get pushed to the workstation
Delete the @wd file from the startup folder
Launch Worldox
Confirm that the @wd file gets copied into the startup folder automatically
If this does not correct the issue, please send an email to support@trumpetinc.com for troubleshooting. Please be sure to include the following information:
The Operating System running on the workstation(s) in question (e.g. Windows 7)
Which version of Office you are running (e.g. Office 2010)
Whether this is happening for all of your users or just some users