B
BW
Hey Microsoft, this is a real bug which should be reported
to those owning Application Center Test (ACT) and
VBScript's scrrun.dll version 5.6.
VBScript/Windows Script Host uses /system32/scrrun.dll to
perform file manipulations by using the FileSystemObject
(FSO).
VBScripts using FSO work fine on their own, however when
evoked from within ACT they sometimes cause the ACT script
to hang (run endlessly). This can be temporarily fixed by
unregistering scrrun.dll and re-registering it OR re-
running scrrun version 5.6 script win2k/xp install.
Details:
Using .Net 2003 ACT.
Using Windows XP Pro with all service packs/updates.
Gave ACT user id full admin access rights.
scrrun.dll version is 5.6 for Win2K/XP.
Would someone from Microsoft please verify this and file a
bug so that the ACT/scrrun.dll corruption relationship is
fixed.
This bug really sucks since our company is trying to
embrace the ACT tool combined with file manipulation
scripts in automating our tests of web sites.
I am only 3 minutes from the Redmond campus and would
gladly bring my XP/.Net 2003 laptop to reproduce the bug.
to those owning Application Center Test (ACT) and
VBScript's scrrun.dll version 5.6.
VBScript/Windows Script Host uses /system32/scrrun.dll to
perform file manipulations by using the FileSystemObject
(FSO).
VBScripts using FSO work fine on their own, however when
evoked from within ACT they sometimes cause the ACT script
to hang (run endlessly). This can be temporarily fixed by
unregistering scrrun.dll and re-registering it OR re-
running scrrun version 5.6 script win2k/xp install.
Details:
Using .Net 2003 ACT.
Using Windows XP Pro with all service packs/updates.
Gave ACT user id full admin access rights.
scrrun.dll version is 5.6 for Win2K/XP.
Would someone from Microsoft please verify this and file a
bug so that the ACT/scrrun.dll corruption relationship is
fixed.
This bug really sucks since our company is trying to
embrace the ACT tool combined with file manipulation
scripts in automating our tests of web sites.
I am only 3 minutes from the Redmond campus and would
gladly bring my XP/.Net 2003 laptop to reproduce the bug.