1/22/2020 8:33 AM | |
Joined: 6/30/2014 Last visit: 8/28/2024 Posts: 463 Rating: (89)
|
Hello, I did not had that before, but usually if COMOS stops working, is due to a endless loop in a script which has been written by an admin or user. Do you know when this did started? Maybe a colleagues of you, which has edited a script will need this information to find where he went wrong :-) So, can you please see if there are any scripts running here which have a wrong expression in it? Solving the script error will solve the issue; you can test this by commenting some parts of the script out or disabling a particular script... Also, you can start COMOS in debug mode, to have more outputs into the log file, to identify the source of the issue. In the documentation I found this: Just in case you are sure or suppose that there is a bad behavior of COMOS itself, which should be investigated by the Siemens developers, you should open a new ticket attaching the log (at best in debug mode), the steps to see the issue and if necessary, a copy of the database which is needed to rebuild the issue. Please confirm the COMOS version which is affected You may do the same steps in the same version of COMOS, but with a standard-DB to see if the same issue happens there: I guess not, as the script which I suppose to be the source of the issue is missing in it... Will you agree? Another idea would be to test this scenario with the latest version of COMOS, 10.3.2, but I think it will not help in case I am right with my assumption about a script error... Just in case you may need some help for the script, they have "customizers" which will surely be glad to help you. I have found for you a couple of good links, I have spread them in this post, for further information feel free to have a look into them. I hope that this helps you a bit, have a nice day, SuperPippo |
Follow us on