karinaX

I found a fix for this issue - it started with some update way back in 2002 and has continued to do the same for years...Here is what I found - and the link to the entire forum. There is about 50 people that replied saying this worked for them once they were re-registered....I just sent it onto a Client that is running Vista / IE7 Combination. So I am hoping it will also fix their issue as well. - Good luck! http://www.annoyances.org/exec/forum/winxp/1059879016 >I fixed this issue by clicking on "Start Menu" - "Run", and entering the following >entries on command prompt: > >regsvr32 msscript.ocx [enter] >regsvr32 dispex.dll [enter] >regsvr32 vbscript.dll [enter] > The cause is still unkown - However there is one writer that did a lot of testing and came back with the reason behind the errors: Been dealing with this issue for months, thank you to the poster who let us know the proper .dlls to re-register. The dispex.dll was the one that worked for me. I tested this by unregistering and re-registering the dll several times. If you are missing it you can get it here: http://dll.yaroslavl.ru/index.php3?lng=&in_char=D I'm not sure how current it is though. The Cause: One of two things, either a bogus update from MS (http://windowsupdate.microsoft.com) that breaks the scripting mechanism by unregistering files and not registering them again. Or The Visual Studio .NET installation on IE6 SP1. That's what I've come up with after a little research. If you know of another means, please post! I am just happy to have things back in working order!!!!!! DeAdWhAcKeR