Something went wrong. An error message is logged - But where?

Sometimes there's an error and CS says:

Something went wrong. An error message is logged with current time: 2016-12-15 12:09:10

Very good! But where is the error message logged?

RE: Something went wrong. An error message is logged - But where?

It is logged to files which are located in the CS install directory.

For example my local installation has the log files here:

E:\SuperOffice\Customer Service\log

Av: Stian Andre Olsen 15. des 2016

RE: Something went wrong. An error message is logged - But where?

.. or if it's not online you can read it in your browser by using the dumpWarningLog action.

fcgi:
rms.fcgi?action=dumpWarningLog&date=<date>
dateformat = YYYY-MM-DD

exe:
rms.exe?action=dumpWarningLog&date=<date>
dateformat = YYYY-MM-DD

Av: Hans Wilhelmsen 15. des 2016

RE: Something went wrong. An error message is logged - But where?

When using the dumpWarningLog I can see the errors. But when looking in the file earlier I did not. Are errors written all the time or only at certain times?

Av: Peter Borg 15. des 2016

RE: Something went wrong. An error message is logged - But where?

The data is written to the logfile immediately. Infact &action=dumpWarningLog reads the values from that file. You can see this if you rename the logfile on disk, and try to refresh the &action=dumpWarnignLog. Then you'll get an error saying it can't open the logfile.

But the big question is; how can we get the same information in the Online environment? Since &action=dumpWarningLog has been disabled we're totally in the dark when these errors happen.

Av: Frode Lillerud 15. des 2016

RE: Something went wrong. An error message is logged - But where?

Currently, only the operation team has access to this log through OC. I guess customers will never get access to it (due to security reasons), but it could be discussed if partners should be able to view the log.

Av: Stian Andre Olsen 16. des 2016

RE: Something went wrong. An error message is logged - But where?

It is very much needed. I'm currently writing a long script in Online, and have to test it every time I make the slightest of changes. If I make too many changes at once, and it starts failing there is really no way to find the error easily.

Av: Frode Lillerud 16. des 2016

RE: Something went wrong. An error message is logged - But where?

Or perhaps it would be easier if we just send the error by mail to the address we define in the system settings.

No more security settings necessary :)

/Niels

Av: Niels van Broekhoven 16. des 2016

RE: Something went wrong. An error message is logged - But where?

I've submitted this as a wish. We REALLY need to get access to the logfiles in Online. 

A suggestion would be to make some sort of portal that partners can log into where we can download logfiles for our customers.

Av: Frode Lillerud 17. feb 2017

RE: Something went wrong. An error message is logged - But where?

Is there any news regarding this issue?

I'm still having problems debugging screens Online :)

Av: Kasper Rosenlund 17. okt 2019

RE: Something went wrong. An error message is logged - But where?

Isn't enabling the 'print exceptions to screen' debug option a solution for this?

Av: David Hollegien 17. okt 2019

RE: Something went wrong. An error message is logged - But where?

Well, I can't find it if its available for screens 

Av: Kasper Rosenlund 17. okt 2019

RE: Something went wrong. An error message is logged - But where?

Hi Kasper,

If you go to .../ticket.fcgi?action=debug, and enable "Print exceptions to screen", then most exceptions will print to the screen. Some exceptions, specifically query exceptions, will still not be printed due to security concerns.

Sverre

Av: Sverre Hjelm 18. okt 2019