Last post Aug 08, 2019 06:08 PM by mehmoodahmed...
Jul 27, 2019 01:33 PM|mehmoodahmed...|LINK
Jul 29, 2019 05:45 AM|Yuki Tao|LINK
Application is hosted on windows server 2018.
Windows is automatically taking the updates and installing it.
After very few days, some features stop working and there are no reasons for it. We try to trouble shoot but still same thing happens frequently.
What features have failed?
Do your have any error message?
Could you please post more details so that I can troubleshoot easier.
Aug 04, 2019 10:35 AM|mehmoodahmed...|LINK
I had developed a list of my order
what happened , this list was throwing an error . I have forgotten I think.
When we restarted our server machine , it started to work.
We couldn't reset the app pol at that time due to client usage.
another screen was getting some similar issue and I did nothing just re-run the stored procedure and it started to work.
At that time, if we see the server services, all services were showing an red alerts rather than green.
What that list included :
is a backend query which is bases on tow unions and a cte (includes order by).
and eventually a CTE was being called through rows (start row and end row for getting the paging)
Aug 04, 2019 12:28 PM|PatriceSc|LINK
Still too vague to guess. Error messages are intended to tell you what is wrong without having to guess. By default they are written to the Windows log so the the IT team can monitor them and have a first idea about what happened. You have no trace of that
and need to let it happen again ?
Aug 04, 2019 05:31 PM|mehmoodahmed...|LINK
Aug 05, 2019 08:10 AM|PatriceSc|LINK
How do you handle exceptions for now? Something bad I see being done sometimes is reporting the exception to the user (even worst with full error details) and discarding them entirely on the server side. As a result the IT team in charge of keeping the app
up and running can't know anything about which exceptions happened (andf have nothing else than the IIS log to know exceptions are happening).
If confirmed you should liekly change your exception handling approach so that you can track which exception(s) happened and then wait for this to happen again with hopefully then some more information to share...
Aug 05, 2019 06:52 PM|mehmoodahmed...|LINK
Patrice, you are right.
We didn't implemented exception handling yet.
But we are all in one to check everything even from IIS.
Aug 05, 2019 07:06 PM|PatriceSc|LINK
At the IIS level you could use https://docs.microsoft.com/en-us/iis/troubleshoot/using-failed-request-tracing/troubleshooting-failed-requests-using-tracing-in-iis-85 to
selectively keep a trace of the requests you want such as those producing an http
500 status code...
Still it's likely not a long term replacement for proper exception handling.
Aug 08, 2019 06:08 PM|mehmoodahmed...|LINK
What i can do is to wait until the same issue happens again or through IIS log request.
We can close this issue if you want it meanwhile.
PatricSe thank you