Sign in
 
HomeLibraryLearnDownloadsRepositoryCommunityForumsBlog
Script Center >
> 
> 
Scripts getting aborted abruptly

Answered Scripts getting aborted abruptly

  • Wednesday, January 09, 2013 5:35 PM
     
     
    Sign In to Vote
    0

    Hi,

      I was running and testing a vbscript without any problem. But suddenly all the vbscripts stopped running on my machine. It shows me the msg box or input boxes , but then suddenly the boxes disappear without me even clicking on the box and then nothing works.

    I am new to vbscript. Is there any service that might be running , or some space issue somewhere that might be causing vbscripts to terminate like this.

    Thanks

     

All Replies

  • Wednesday, January 09, 2013 5:41 PM
    Moderator
     
     
    Sign In to Vote
    0

    Hi,

    Your question lacks sufficient detail to provide any input. Please read the following to help you ask a better question:

     
  • Wednesday, January 09, 2013 5:53 PM
     
     Answered
    Sign In to Vote
    1

    Your anti-virus may been killing the wscript/cscript process.

    Turn it off temporarily to test.

    Inspired by Heineken.

     
  • Wednesday, January 09, 2013 6:06 PM
     
     
    Sign In to Vote
    0
    I am sorry if I have not provided enough information. I am not sure what extra details I need to provide. As this is happening with any VBScript I try to run on my machine. I do not get any error message also. I tried to run 3 different scripts. For all the 3 scripts I ran ,the first steps was to display a msg box or the input box. Even before I can click the OK button on MsgBox or enter an input in the InputBox the box disappears. In one of the links I saw that unregistering and reregistering the vbscript dll might help. But it did'nt. I was unable to find any other useful link for this problem. There was nothing new that happened. All these scripts were working properly till today morning and suddenly stopped working. The script I was trying to run opens an excel sheet for input which contains machine names , looks for those names in the network , finds a file from there , reads that file and writes to another excel sheet some of the values in that file. I was just changing the input excel sheet values. No change to the script. And the values changed also are the ones I had tested before this.  Please let me know if you think I should post the script also. 
     
  • Wednesday, January 09, 2013 6:12 PM
     
     
    Sign In to Vote
    0
    Take any 'on error resume next' commands out of your scripts to see any errors that may be occurring.

    Inspired by Heineken.

     
  • Wednesday, January 09, 2013 7:02 PM
     
     
    Sign In to Vote
    0

    Hi RiffyRiot,

      You were right. I was not able to turn off the MCAfee as it is run by administrator , but when I checked the registry entries for VBScript it points to MCafee instead of VB.

    Steps done:

    Open a command prompt in elevated mode (run as administrator).
    - Open regedit and verify that HKLM\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32 is pointing to vbscript.dll
    On a 64-bit machines the key is HKLM\SOFTWARE\Wow6432Node\Classes\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32 

    Now I have to get that pointing back to vbscript .

    Thanks for guiding me in the right direction.

     
  • Wednesday, January 09, 2013 7:15 PM
     
     Answered
    Sign In to Vote
    0
    Just go into McAFEE AND TURN off "ScriptScan".  This will return the setting to normal.  You need to set McAfee to allow local scritps to run from trusted locations.

    Happy New Year ¯\_(ツ)_/¯

     
  • Friday, January 11, 2013 7:00 PM
     
     
    Sign In to Vote
    0

    It took some time for the admin to get back. Unfortunately turning off the scripts did not work. And the admin said that he does not see anything being blocked in the MCafee logs.He disabled the security for some time and ran the scripts but still it did not work. So I am back to the same position.  Any more ideas will be greatly appreciated . 

     
  • Friday, January 11, 2013 7:24 PM
     
     
    Sign In to Vote
    0

    You issue cannot be solved here if the symptoms you are seeing are actually what is happening.  There is nothing in scripting that will terminate a messagebox.  If there are no events in th event log then the issue needs to be resolved via a technician.  I do not see how we can help.

    ¯\_(ツ)_/¯

     
  • Friday, January 11, 2013 7:43 PM
     
     
    Sign In to Vote
    0

    Thanks for your reply. It is just not the message box , but the wscript itself gets killed after a second or two.  I know this is kind of a vague issue. I just wanted to see if anyone ever experienced something similar.

    Thanks for all your help.

     
  • Friday, January 11, 2013 7:48 PM
     
     
    Sign In to Vote
    0

    Thanks for your reply. It is just not the message box , but the wscript itself gets killed after a second or two.  I know this is kind of a vague issue. I just wanted to see if anyone ever experienced something similar.

    Thanks for all your help.

    This is clearly a system problem. You need a technician experienced in troubleshooting system problems.  We can help with scripts and script error but not with system issues.

    You need to see what is happening in your event logs. 

    ¯\_(ツ)_/¯

     
  • Friday, January 11, 2013 8:20 PM
    Moderator
     
     
    Sign In to Vote
    0

    If the scripts are syntactically correct (you already mentioned that the scripts you were using were working before a certain time), then you don't have a scripting problem but rather some other kind of system problem.

    Bill