Can't find script engine "VBSCRIPT" for "Script-path"

Discussion in 'Scripting' started by Richard, Nov 24, 2003.

  1. Richard

    Richard Guest

    Hi,

    We have a issue where some users can't run a logon-script that we've set in the local GPO on a Windows 2000 Terminal Server (SP3 and SP4) with XPe (SP2/FR2 and SP3/FR3). It doesn' matter which version we ahve of Windows or Citrix service pack. All users are using a mandatory profile and a local vbscript should run at logon to the TS server. If the user logs on to a server where a profile exist for that user becasue it wasn't unloaded at logoff this error is raised at logon in the users session: "Can't find engine "VBSCRIPT" for "script-path".

    Same thing occurs if the user has a session and then just tries to logon with an additional session against the same server ( I know this never happens but just did it for testing with an RDP session). Once the user clicks OK to the error-message he/she gets logged on to the session and then once in there is NO problem at all double-clicking the exact same script and it runs perfectly once the shell is loaded.

    Have chend the HKCR\.vbs, HKCR\VBSFile regsitry keys and they seem to be all ok.. I mean it works for some users but for some it doesn't. So it isn't the server settings that seem wrong.... it seems like the users shell is not wokring properly for some reason. I've enabled verbose logging of the UserEnv.log but can't find anythign there.

    The servers are in a NT4 resource domain but we moved a server into AD but the problem persists. It's not persistent...

    We've reistalled WSH, didn't work.
    Does anyone have any ideas?

    Thanks!

    Richard
     
    Richard, Nov 24, 2003
    #1
    1. Advertisements

  2. Richard

    Guest Guest

    I've not come accross this exact problem but have found
    similar problems with WTS in other software. In my case it
    was down to file permissions, the files in question were
    not read only and so the users were locking the file.
    Could it be the same problem? what about log files for
    VBscript? would the previous session lock the file?

    that we've set in the local GPO on a Windows 2000 Terminal
    Server (SP3 and SP4) with XPe (SP2/FR2 and SP3/FR3). It
    doesn' matter which version we ahve of Windows or Citrix
    service pack. All users are using a mandatory profile and
    a local vbscript should run at logon to the TS server. If
    the user logs on to a server where a profile exist for
    that user becasue it wasn't unloaded at logoff this error
    is raised at logon in the users session: "Can't find
    engine "VBSCRIPT" for "script-path".
    tries to logon with an additional session against the same
    server ( I know this never happens but just did it for
    testing with an RDP session). Once the user clicks OK to
    the error-message he/she gets logged on to the session and
    then once in there is NO problem at all double-clicking
    the exact same script and it runs perfectly once the shell
    is loaded.
    they seem to be all ok.. I mean it works for some users
    but for some it doesn't. So it isn't the server settings
    that seem wrong.... it seems like the users shell is not
    wokring properly for some reason. I've enabled verbose
    logging of the UserEnv.log but can't find anythign there.
    server into AD but the problem persists. It's not
    persistent...
     
    Guest, Nov 24, 2003
    #2
    1. Advertisements

  3. Richard

    Richard Guest

    Hi again,

    No the problem doesn't seem to be permission-realted. I get the same problem even if the script is in a location that only the user I log on with has access to. And even if that user is the only user on the Terminal Server.

    Tricky one...

    Thanx!

    Richard
     
    Richard, Dec 3, 2003
    #3
    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.