Unable to Load Modules

[hanham123]

Hi,

I have installed wingate on a windows 7 64 but when going into the console I have 17 modules in red which are not loading, the message is "Not Loaded (Untrusted)

Any ideas ?

Thanks

Scott

[adrien]

Hi

that normally means the signature in the manifest files don't match the DLLs

Did anything get altered, e.g. DLL files, or even CHM files?

Has there been a previous version of WinGate 7 on this computer?

Does the engine start? Which modules are showing unloaded?

Adrien

[hanham123]

Hi,

I dont think I have installed before and have not changed anything, the modules not loading are:

loggui
timelinegui
permissionsgui
eventsgui
wintNTUDBGUI
DNSClientgui
httpcachegui
emailgui
updategui
datagui
perfcountgui
schedulegui
notifygui
udbui
adudbgui
policygui
udbgui
categoriesUI

They are all listed as version 7.0.8.3364

Thanks

Scott

[adrien]

Hi

is there any chance of looking at that computer remotely, e.g. with remote desktop or teamviewer?

If so, send details to support@wingate.com

Regards

Adrien

[lasserasch]

Hi there. I know this post is old, so this reply is for future readers :

I had the exact same problem. I installed Wingate 8, opened up the administration interface and logged in with default username : administrator/(blank password).

I played around for a few minutes and then without closing the administration interface i tried to restart the wingate engine. That made the administrator interface crash. The engine started successfully again and i reopened the admin interface. Now a LOT of UI modules failed to load with the samme error message as described ealier in this post.

To fix it i just reinstalled Wingate. That made all the modules load again...

Best Regards
Lasse Rasch

[adrien]

HI

thanks for reporting.

One of the things the installer does is install a certificate into the trusted store on the computer. This is so that the computer doesn't moan about trusting our driver in the driver installer, and so we can evaluate trust on signed modules and catalog files when loading modules.

If that part of the install failed the first time, I guess that could explain this sort of problem.

We install the GlobalSign root cert (which is actually normally already there), and intermediate cert. I't not certain, but it's also possible we install the Qbik cert issued by GlobalSign. Easy enough to check in certificates MMC.

Regards

Adrien