Sometimes Application features works partially , why?

Question

User-234441352 posted
Hi,
We have developed an application in MVC 5.

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.

Answer 1

User1520731567 posted

Hi mehmoodahmed...,

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.

Best Regards.

Yuki Tao

Answer 2

User-234441352 posted

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)

Answer 3

User753101303 posted

Hi,

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 ?

Answer 4

User-234441352 posted
Hi Patric,
Yes You are right, I am understanding it.
I have tried to check from event viewer and IIS log. But couldn't find anything useful. May be because of suppressing exceptions. Can you guide me from where can I get the exact error? Or it can be possible if it ll happen again.

Answer 5

User753101303 posted

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...

Answer 6

User-234441352 posted

Patrice, you are right.

We didn't implemented exception handling yet.

But we are all in one to check everything even from IIS.

Answer 7

User753101303 posted

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.

Answer 8

User-234441352 posted

Hi PatriceSc,

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