Re: Error Message: Could Not Create "WScript.Shell"

Discussion in 'Windows XP General' started by Doug Knox MS-MVP, Aug 15, 2003.

  1. Something is trying to execute the file mentioned in the error message.
    The error may have a variety of causes. Locate the VBS file referenced,
    right click it and select Edit. Post the contents back here.
     
    Doug Knox MS-MVP, Aug 15, 2003
    #1
    1. Advertisements

  2. Sounds like his WSH executable is deleted or blocked. I wonder if McAfee
    tagged that Server.VBS file as a virus...?

    Randall Arnold
     
    Randall Arnold, Aug 15, 2003
    #2
    1. Advertisements

  3. Doug, here are contents of "server.vbs" as you asked.
    Thanks for your help.
    **********************************************************
    ' VBScript Source File -- Created with Support.com
    ScriptCenter(TM)
    '
    ' NAME: server.vbs
    '
    ' AUTHOR: Chip Blais, Content Developer, Tiger Team, Sony
    Electronics
    ' DATE : 10/11/2000
    '
    ' COMMENT: Support Action to set active servers
    ' checks for registry key about
    notification, True = notify, False = turn off notification.
    ' Sets server paths.
    '
    '==========================================================
    ================

    Option Explicit

    Dim global, shellobj, wshEnv, strRegKey, strSysFolder,
    strUser, strNotify

    Const forcesyncpath = "C:\Progra~1
    \Support.com\client\bin\forcesync.exe"
    const tgfixpath = "C:\Progra~1
    \Support.com\client\bin\tgfix.exe "
    const lserver = "C:\Program
    files\Support.com\client\lserver"
    const tgcmdpath = "c:\progra~1
    \Support.com\client\bin\tgcmd.exe "
    set shellobj = WScript.createobject("WScript.shell")
    Set wshEnv = shellObj.Environment("Process")

    On Error Resume Next

    shellobj.run tgcmdpath & "/server",1, false


    '==========================================================
    ===========================================================
    ===============================

    strSysFolder = wshEnv("WINDIR")

    If strSysFolder = "C:\WINNT" then

    strRegKey
    = "HKLM\Software\Microsoft\WindowsNT\CurrentVersion\WinLogo
    n\Defaultusername"

    Else If strSysFolder = "C:\WINDOWS" then

    strRegKey = "HKLM\Network\Logon\username"

    End If
    End If

    err.Clear

    strUser = shellobj.RegRead (strRegKey)

    strRegKey = "HKLM\Software\support.com\users\" & strUser
    & "\DnaServerList\74D49528\"

    '==========================================================
    ===========================================================
    ===============================

    On Error Resume Next

    strNotify = shellobj.RegRead
    ("HKEY_LOCAL_MACHINE\Software\tioga\Notification")

    IF strNotify = "False" then

    global = ""

    shellobj.run tgfixpath & "/fds " &
    global ,1, TRUE

    shellobj.RegDelete strRegKey

    Else

    global
    = "http://sdcglobal4.sel.sony.com/global"

    shellobj.run tgfixpath & "/fds " &
    global ,1, TRUE


    End If

    err.Clear

    shellobj.run tgfixpath & "/fds " & chr(34) & lserver & chr
    (34) ,1, TRUE
    shellobj.run forcesyncpath, 1, true


    wscript.Quit
     
    Dave Luehrman, Aug 15, 2003
    #3
  4. Doug/Randall: Observing your correspondence regarding my
    server.vbs file, I add this item of info: when initially
    installing the McAfee VirusScan, it did indeed hit on this
    file as "file attempting to execute" and seemed to treat
    it as a virus. My choice was "Yes, allow to
    continue", "No, do not allow" and "Quarantine this file".
    At one time or another I must have tried all three options
    to get it to continue. However, even now as I have de-
    installed all the McAfee items it continues to appear. I
    am going to pursue the idea that McAfee treats it as a
    virus in a McAfee forum, but am posting the contents of
    the server.vbs file in next message here. THANKS for
    quick response :)
     
    Dave Luehrman, Aug 15, 2003
    #4
  5. As Doug noted, VBS files tend to be regarded suspiciously by default. Some
    protection tools want to block them all outright, while others are more
    discerning (again as Doug noted).

    I have a file called Server.VBS on my PC that I downloaded from a WSH
    development site, specifically for testing purposes. However, anyone can
    name a script file as they please and it *may* be possible that yours is
    malicious. Many you-know-whats out there use VBS files to wreak havoc on
    the PCs of innocent users. As a VB developer, this irritates me to no end.

    Just ignore the rant; post the contents as Doug recommended and someone here
    can figure it out. DO NOT execute the file!!! Right-click and select edit.

    Randall Arnold
     
    Randall Arnold, Aug 15, 2003
    #5
  6. Doug Knox MS-MVP

    Guest Guest

    Hi, Doug

    I have almost the same problem from the same VB file posted by David
    Here is wat I got

    ############################################
    Windows Script Hos
    C:\ProgramFiles\Support.com\Client\Server\Server.vb
    Line: 2
    Char:
    Error: Could not create object named "WScript.shell
    Code: 800401
    Source: WScript.Createobjec
    ##########################################

    I have XP home edition from SONY VIAO come with McAfee installe
    Here is what happend
    After I insatlled anther Anti-virus program from Norton it had conflicts with McAfee, which made my VIAO ra
    extremly slow. I had to uninstallthe Norton and then updated the McAfee virus definition (because it just showed up for updating). Well after that I got this problem

    I followed your suggestions to run
    REGSVR32 wshext.dll and REGSVR32 vbscript.dl
    Both were updated succesfully but the error message still shows up every time when users logo
    Any suggestions

    Thank

    Yua
     
    Guest, Nov 14, 2003
    #6
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.