Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

DoOpenPipeStream in ScrRun.dll not found

60 views
Skip to first unread message

Mark Hurd

unread,
Oct 15, 2001, 12:14:17 PM10/15/01
to
I've looked at the history of this problem in Google and I see that it
occurred when WSH 5.6 beta was installed incorrectly, but I'm getting it now
:-(

On a clean install (OEM) of Win2k, I applied SP2, Office through to SP2, the
Office Updates, the Windows Updates, and IE6.

I then installed scripten.exe for WSH 5.5 for W2k! (Because it was part of a
larger set of things to installed, like MSDE)

After this I get the "Procedure entry point DoOpenPipeStream in ScrRun.dll not
found" error when executing a .VBS followed by the script completing without a
VBScript error, but registry access has failed and returned default values.

Until I saw the newsgroup references I guessed this related to stopping the
script virii.

It looks like the WSH 5.6 from IE6 includes a 'new' version of a file with a
version that is 'older' than what is installed by the scripten.exe for 5.5?

I don't have the PC in front of me to play with, so I've downloaded the 5.6
scripten.exe and I'll report back to this newsgroup the results.

Can anyone else confirm that the WSH 5.5 scripten.exe 'kills' the scripting
support provided by IE6?


Torgeir Bakken

unread,
Oct 15, 2001, 12:51:26 PM10/15/01
to
Hi

File           v. 5.5      v. 5.6 (IE6)

cscript.exe   5.1.0.5907   5.6.0.6626
dispex.dll    5.1.0.4615   5.6.0.6626
jscript.dll   5.5.0.6330   5.6.0.6626
scrobj.dll    1.1.0.5628   5.6.0.6626
scrrun.dll    5.1.0.5010   5.6.0.6626
vbscript.dll  5.5.0.6330   5.6.0.6626
wscript.exe   5.1.0.5907   5.6.0.6626
wshext.dll    5.1.0.5907   5.6.0.6626
wshom.ocx     5.1.0.5907   5.6.0.6626

Nothing here indicates that a dll-downgrade should occur!

Regards,
Torgeir

Mark Hurd

unread,
Oct 16, 2001, 2:46:56 AM10/16/01
to
Installing the latest scripten.exe (5.6 with the vbscript.dll 6914 build)
fixed the problem.

So I don't know how, but it does look like one of the 'standard' installation
steps (Windows SP2, Windows Update, Office Update or IE6) failed to update
something. We did get Windows File Protection warnings when we reapplied the
old scripten. The WFP dialogue box stayed behind other windows so I may have
not noticed it the first time we installed scripten.

Regards,
Mark Hurd, B.Sc.(Ma.) (Hons.)
CTO
MGMWireless Pty. Ltd.
______________________________________________________________
MGMWireless Pty. Ltd. does not guarantee that this message is virus or
error free and is not responsible for any non-MGMWireless changes made to
this message and any attachments. It is your responsibility to virus scan
this message. The content and opinions in this message are not necessarily
those of MGMWireless Pty. Ltd.
For more information visit www.mgmwireless.com


Luke Zhang

unread,
Oct 16, 2001, 3:27:50 AM10/16/01
to
Hi Mark,

They should be compatible. The problem sounds like a setup issue.

0 new messages