Description

User receives this message each time they launch Worldox:

It is normal for this to happen occasionally (After an update and the user needs to elevate in order to write those changes to the registry) but should not happen each time the user launches Worldox.  But if the above prompt appears every time the user launches Worldox, there may be an issue.  This article describes how to troubleshoot.

Note that repeated WDREGSET dialogs also mean that some of the Worldox integration points (Outlook, Acrobat, Word, Excel) are not being registered properly.

Troubleshooting Steps

Are you changing Internet Explorer protected mode settings?

For Worldox to integrate with Internet Explorer, IE Protected Mode must be disabled.  If you enable protected mode, then launch Worldox, the WDREGSET prompt will appear because Worldox is trying to fix the Protected Mode setting.  This could put you in an endless cycle of Worldox changing the Protected Mode settings, then you re-enabling Protected Mode, etc...

The resolution here is to not adjust the IE Protected Mode setting (strongly recommended), or ask Trumpet to disable Worldox's Internet Explorer Protected Mode adjustment (this will result in integration with Internet Explorer not working).

For reference, the following article describes issues associated with Internet Explorer Protected Mode and Worldox Integration: /index.php?pg=kb.page&id=50

Check UAC

Once of the main causes of this error message is that the workstation's Under Account Control (UAC) settings are not properly configured.

Follow the instructions in User Account Control (UAC) Information to ensure that your have the appropriate settings.

Terminal Server Users

If you are opening Worldox on a Terminal Server, and are experiencing this issue, please refer to our Updating Worldox on a Terminal Sever guide on how to ensure that a Worldox update properly pushes to the terminal server.

Users Who Are Not Permitted to Install Software

If part of the WDREGSET prompt includes typing in an administrative username and password, WDREGSET may fail (silently) in some fairly rare circumstances.

The fix is to perform a Run As operation on the following applications, launching them one time as the Administrator user, then closing the application:

• Adobe Acrobat (or Reader)
• Outlook
• Word
• Excel

Tip: In our experience, the vast majority of the time, the issue is resolved by launching Acrobat or Reader (Outlook, Word and Excel are normally not required).

The next time you launch Worldox, you will receive one more WDREGSET dialog, then after that, the problem should be resolved.

For those of you who are technically inclined, here is a description of what is going on: Differences in the HKEY_CURRENT_USER registry values between the user and the administrator user.  Worldox looks for triggers in the HKEY_CURRENT_USER registry to determine whether it should install addins for Adobe, Word and Excel.  If the user has the 'trigger', but the Administrator user does not have the 'trigger', then WDREGSET will see that it needs to install an integration addin, but after it elevates (running as the administrator user) WDREGSET no longer sees that the change is necessary.