A challenge to Everyone.(me included)

[Tygerwoody]

Our company is all of a sudden receiving the two errors below. We have spent an entire week trying to diagnose the problem, but have come up empty handed. If anyone has ever seen either, or thinks they know how to fix it. I will give them a yellow star. :p

Some helpful info.
It is doing this on 50+ machines.
All machines are fully windows XP updated.
All machines are brand spanking new, freshly formated and redone. The error still comes up even after reformat.
If you have any questions. Just ask.

http://www.nvnews.net/vbulletin/attachment.php?attachmentid=16822&stc=1&d=1142884858

[Monolyth]

Not sure if you read this yet or not, a possible workaround to at least the TODGUB7.dll

Following was copied from http://community.installshield.com forums - Props to Malcolmhum for the workaround.

Source Link (Page 2 of Post): http://community.installshield.com/showthread.php?p=290699

TODGUB7.DLL - Error Work Around
Firstly on the machine you are running installshield on, if the TODGUB7.dll is registered ok then don't take this action:-
To register TODGUB7.dll on the build machine open up the registery and create and entry. Download the reg key from:-http://www.vmsecure.co.uk/support/files/todgub7.dll.zip

Run the reg key to create the entry, and ensure that the file todgub7.dll is in the system32 folder.

In installshield go to the registry tab and then on your machine find HKEY_CLASSES_ROOT\CLSID\{359AA0C1-DDF8-49DB-83FF-6184706A9106}
and then copy that key over into the destination computers registry window. That's it done.

UPDATE: Possibly simpler fix. Try Right Clicking the TODGUB7.dll and selecting "Self-Register". I'm sure you could also probably register through a command window. Shouldn't be a prob to run a regsvr32 script on everyone's machine to register it. *shrugs*

[Tygerwoody]

Not sure if you read this yet or not, a possible workaround to at least the TODGUB7.dll

Following was copied from http://community.installshield.com forums - Props to Malcolmhum for the workaround.

Source Link (Page 2 of Post): http://community.installshield.com/showthread.php?p=290699



UPDATE: Possibly simpler fix. Try Right Clicking the TODGUB7.dll and selecting "Self-Register". I'm sure you could also probably register through a command window. Shouldn't be a prob to run a regsvr32 script on everyone's machine to register it. *shrugs*
Hey Monolyth. Thanks for your input. However, we did try this before and it didn't seem to work. We even tried unregistering and deleting a bunch of dll files and then putting them back in and registering them and it still didnt work. :(


Update however. We were able to "semi" fix the problem. In our VScan 8.0 options, there is an option that we enabled that seems to be causing these errors not to occur. Drawback is the option slows down the computers a good amount, as it basically turns on super antivirus mode(to put it lightly). Its weird that the MORE virus protection you add, the error goes away. Its usually the opposite. Its usually when you have alot of virus protection that blocks stuff you want to work.

[Monolyth]

Off the top of my head, have you tried the most up to date version of the ComponentOne True Ole DbGrid dll? Do you know if you have a ComponentOne package laying around anywhere?

Any Service Pack diff between working and non-working machines?

Have you tried just copying a valid dll off a working machine onto one of the nonworking then re-registering? Tried a completely empty windows install?

Gotta love it.

[Tygerwoody]

Off the top of my head, have you tried the most up to date version of the ComponentOne True Ole DbGrid dll? Do you know if you have a ComponentOne package laying around anywhere?

Any Service Pack diff between working and non-working machines?

Have you tried just copying a valid dll off a working machine onto one of the nonworking then re-registering? Tried a completely empty windows install?

Gotta love it.
Yep... tried all of that :)

We actually called Component One today and they couldnt help us either.

[Monolyth]

Another question:
Are you on the machine as Administrator? Or a limited user account?
Perhaps IE security configuration issues?

Is it just IE that has the problem? Is there anyway to create a quick WindowsForm Application to use the True Ole DBGrid control? And run it to see what happens?