AppSpecialist
Programmer
I have a VBSCRIPT that I am running via the SQL SERVER Agent. I have it scheduled as a job that runs a operating system command in the way of: wscript "c:\test\test.vbs".
Inside this script I am simply raising a user defined error. This works properly by doubleing clicking the vbs file with windows explorer. A runtime error box appears with the error displayed.
When run through the agent... the job hangs. Is there a simple way to get this error intercepted by SQL Server and be able to see the details in the default job history logs that tell if a job succeeded or failed.
Thanks
Inside this script I am simply raising a user defined error. This works properly by doubleing clicking the vbs file with windows explorer. A runtime error box appears with the error displayed.
When run through the agent... the job hangs. Is there a simple way to get this error intercepted by SQL Server and be able to see the details in the default job history logs that tell if a job succeeded or failed.
Thanks