Jump to content

How to suppress "scripting errors" in error log


jjjjp

This topic is 962 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Is there a way to change my coding of scripts so that so-called scripting errors don't show up in server logs when a scheduled script is executed on FM Server? I get dozens of such errors for each daily execution, and Using a Set Error Capture [On] script step doesn't seem to make a difference as to whether the "errors" show up in the server log. The kinds of error codes that do show up (101, 401) don't seem to me to be be the result of scripting errors at all. Rather, they are part of ordinary operations (e.g., testing to see whether to stop looping by checking whether a record exists in a found set).

I raised this question a couple of weeks ago in a much longer email providing a lot of the context that I thought the FM Forum community preferred. I didn't hear back and so have tried to reduce my question here to the bare bones.

Link to comment
Share on other sites

Thanks for that tip, Ocean. Scripting errors aside, is it bad coding practice to, e.g., make an action conditional on the occurrence of an error on opening a record? The term "scripting error" suggests it is.

Link to comment
Share on other sites

This topic is 962 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.