Hi,

I am running a scheduled script on server 9v3. It worked fine for a little while and now I am getting a "ScriptMaker script aborted" message. I checked all steps and they are all web compatible. There is not conflict with other schedules and I have changed the time and frequency of it and still the same. I run the script manually and it works fine. Is there at least some way to find out why? It doesn't tell me why just that it aborted. What could be causing this?

Thanks

Mike

Have the server email you the results.. It will tell you the error message.... Do you have a loop in you script?... if so see my other post in this category.

I was afraid you were going to tell me that. The server machine is not set up for email. I have a loop in the script, but it aborts before it gets to that point.

Mike

Run you script with the script debugger on with pause at error... Step through you script on line at a time.... If you have subscript use the second button from left to step through it... this button will step through all subscripts to... If you see an error message you need to fix it or in my experience the script will abort and possibly hang up your machine.

Does the Account under which the script is running have the permissions needed to do what the script calls it to do?

Steven

If I run the script from a user machine manually it runs fine with no errors. The permissions are set at full access to run it from the server.

I am not sure I know how to run the debugger when triggering it from a server schedule.

What does the script exactly ?

Strange! Well, Allow User Abort[] is IWP compatible and TechInfo says 'This script functions differently on the web than in the desktop application.' Then continues, "Allow User Abort- Determines how unsupported script steps are handled. Enable to stop scripts from continuing, and disable to skip over unsupported steps."

Could someone be aborting it? Or might it hit a non-IWP compatible step? I know you checked them. Like Ugo says, maybe we can spot it for you. Also remember that, if it isn't the main script but rather a sub-script, we need to see the main script as well. And if this is main script and has any sub-scripts, then we'll need to see them. Are there an Halt Script steps anywhere?

Edited May 6, 200817 yr by Guest
Added paragraph :o)

Thanks for all your help everyone. Apparantly it happened when it tried to open a file referenced by the script. The file was set to open as a guest but the guest account was not active. All is well now.

Mike