Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Removing RAMS references

...

If you are trying to report a problem with LAMS or RAMS on the LAMS Community, then please take 5 minutes to read these instructions. It looks like a lot to read, but a lot of it is step by step instructions so its not that bad.

...

  • If you get a "horrible" error like the following, please put the first few lines of the error in your message, and then attach the LAMS /RAMS server logs. If you have time to create the DEBUG version of the logs, then that will give us extra details. See "Creating the DEBUG Logs" below for how to create the logs. If you don't have time to create the DEBUG version, or you can't reproduce the problem, please send us the log files that already exist (see "Which Files To Send?") as the complete error is normally written to the logs. Put the logs in a zip file and attach them to the post.

...

When you post a message on the LAMS (or RAMS) Community, there is an option "Attach?" at the bottom of the page. Select  "Yes" and then when you click "Post" it will ask you attach the file.

...

Once you have created the logs and posted them on the LAMS /RAMS Community, or emailed them to whoever is doing your support, then you want to turn off the debugging again as it can slow down your LAMS server. If this is a bug that is difficult to reproduce, you can leave it in DEBUG mode until you have been able to reproduce the problem but on a large production system  you should not run in DEBUG for any longer than you have to.

...