Thankyou for proving that File System Object works inside=20
of the ACT UI. It inspired the following solution:
My series of events which others may run into:
When I first ran a test VBScript on its own, I got an=20
error that FSO had not been a registered activex=20
component. To solve this, I opened a cmd window and did=20
the usual registration of a dll by doing,
regsvr32 c:\%system%\scrrun.dll
Was then able to run any VBScript, however FSO could not=20
be evoked from an ACT project (ACT UI or ACT Visual ide).
I then uninstalled ACT from .Net and reinstalled ACT=20
for .Net 2003. Still could not evoke and use the FSO from=20
within ACT, however I could run FSO from stand alone=20
VBScripts. I even gave the ACT user full admin rights.
Today, I unregistered the dll which contains FSO by,
regsvr32 /u scrrun.dll=20
and then reregisterd the same dll by,
regsvr32 scrrun.dll
I then opened up ACT and ran SUCCESSFULLY a script which=20
evoked FSO. Everything works fine and I leave it to=20
Microsoft to determine the mystery why one has to=20
unregister the scrrun.dll and then re-register it, OR does=20
one need to install ACT for .Net 2003 and then re-register=20
scrrun.dll???
- BW (Microsoft contract STE/SDET) MCSE.
[quoted text, click to view] >
>I ran the same code you posted, on Visual Studio 2003=20
from the IDE and did=20
>not get an endless loop. Are you sure you are actually=20
getting an endless=20
>loop?
>
>Also, I did not have to change any permissions for the=20
ACT agent, nor run=20
>anything against scrun.dll... I am not sure why you did=20
that.
>
>Bottom line, the exact same code ran only once. Make=20
sure in the test=20
>properties you set it up for only 1 iteration, just to=20
make sure there is=20
>no endless loop. If the test is set to run more than 1=20
time or for a=20
>period of time, then you will repeat the same code=20
execution over and over.
>
>
>Hope this helps.
>
>-Andr=E9s
>
>.
Here is the final solution to this freaking puzzle:
Each time I registered scrrun.dll, everything worked until=20
I rebooted the computer where for some reason scrrun.dll=20
had to be re-registerd again.
To get to the bottom of this mystery, I took a snap shot=20
(using VeriTest-Rational Install Analyzer) of the WinXP=20
system where scrrun.dll had been re-registered, rebooted=20
the system and then took another snap shot of the now=20
messed up scrrun.dll, ran a comparison and low and behold=20
after reading through the registry changes determined that=20
Norton Anti-virus takes the GUID for sccrun.dll and re-
points it towards their script blocking dll.
To properly solve this problem, I went into the Norton=20
AntiVirus options and turned off script blocking, rebooted=20
and now all is fine. Sheeeeeeeeesh!!
Bottom line is that ACT does not know that scrrun.dll has=20
been hi-jacked by Norton script blocking dll and just runs=20
the test script forever until it times out.
[quoted text, click to view] >-----Original Message-----
>Thankyou for proving that File System Object works inside=20
>of the ACT UI. It inspired the following solution:
>
>My series of events which others may run into:
>
>When I first ran a test VBScript on its own, I got an=20
>error that FSO had not been a registered activex=20
>component. To solve this, I opened a cmd window and did=20
>the usual registration of a dll by doing,
>
>regsvr32 c:\%system%\scrrun.dll
>
>Was then able to run any VBScript, however FSO could not=20
>be evoked from an ACT project (ACT UI or ACT Visual ide).
>
>I then uninstalled ACT from .Net and reinstalled ACT=20
>for .Net 2003. Still could not evoke and use the FSO=20
from=20
>within ACT, however I could run FSO from stand alone=20
>VBScripts. I even gave the ACT user full admin rights.
>
>Today, I unregistered the dll which contains FSO by,
>
>regsvr32 /u scrrun.dll=20
>
>and then reregisterd the same dll by,
>
>regsvr32 scrrun.dll
>
>I then opened up ACT and ran SUCCESSFULLY a script which=20
>evoked FSO. Everything works fine and I leave it to=20
>Microsoft to determine the mystery why one has to=20
>unregister the scrrun.dll and then re-register it, OR=20
does=20
>one need to install ACT for .Net 2003 and then re-
register=20
>scrrun.dll???
>
>- BW (Microsoft contract STE/SDET) MCSE.
>
>>
>>I ran the same code you posted, on Visual Studio 2003=20
>from the IDE and did=20
>>not get an endless loop. Are you sure you are actually=20
>getting an endless=20
>>loop?
>>
>>Also, I did not have to change any permissions for the=20
>ACT agent, nor run=20
>>anything against scrun.dll... I am not sure why you did=20
>that.
>>
>>Bottom line, the exact same code ran only once. Make=20
>sure in the test=20
>>properties you set it up for only 1 iteration, just to=20
>make sure there is=20
>>no endless loop. If the test is set to run more than 1=20
>time or for a=20
>>period of time, then you will repeat the same code=20
>execution over and over.
>>
>>
>>Hope this helps.
>>
>>-Andr=E9s
>>
>>.
>>
>.
Unbelievable!
Great catch BW! I did not know Norton AV would re-map your script engine
in this manner! I hope nobody sees this problem again, but if they do I
will make sure to note it for future reference. I am curious why the
problem did not occur from a simple VBScript though, and only occurred from
inside ACT.
Odd.
Anyway, thanks for the update and good luck.
-Andrés
Don't see what you're looking for? Try a search.
