Error "cscript exited with error code 0" when running vbscript from batch
I am trying to create a batch that closes outlook "correctly" on client machines from the server. I know killing outlook would be easy enough, but i don't want outlook scanning files every morning when my users open it up because it was not closed properly.
I found a vbscript that closes outlook, and I am now trying to execute it from a batch. I am currently testing on 2 XP machines, to determine if this is going to work. So far, no luck.
Here is the script that closes outlook:
On Error Resume Next
Set Outlook = GetObject(, "Outlook.Application")
If Err = 0 Then
Outlook.Quit()
End If
When I execute this locally, it works fine.
Here is the test batch that I have created to run remotely:
psexec \\station1812 cscript "c:\test\testscript.vbs"
When I run this from a remote computer I get the following error "cscript exited with error code 0"
Any suggestions? Thanks in advance!
I found a vbscript that closes outlook, and I am now trying to execute it from a batch. I am currently testing on 2 XP machines, to determine if this is going to work. So far, no luck.
Here is the script that closes outlook:
On Error Resume Next
Set Outlook = GetObject(, "Outlook.Application")
If Err = 0 Then
Outlook.Quit()
End If
When I execute this locally, it works fine.
Here is the test batch that I have created to run remotely:
psexec \\station1812 cscript "c:\test\testscript.vbs"
When I run this from a remote computer I get the following error "cscript exited with error code 0"
Any suggestions? Thanks in advance!
Who is Participating?
Error code 0 means that it thinks it completed successfully. I think the problem that your having is with psexec and not the batch file
Maybe try to change your quotes, or no quotes...
psexec \\station1812 "cscript c:\test\testscript.vbs"
psexec \\station1812 cscript c:\test\testscript.vbs
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
Since the outlook session is running under another user's context, you won't be able to get to it using psexec.
Probably a better idea would be to set up a logon script for the user(s) that adds a schedule task (if they have rights to create a task) under their credentials to occur at a specific time of day...