3 weeks ago
We have a server which just got the newest API: 1.0.449.0.
Now we have the problem that at the beginning of the day it just doesn't work.
We get a 502 response back.
Recycling or manually restarting the application pool doesn't help: you then get a 401 Unauthorized when authorizing.
We have to also reset the Act apppool OR reset IIS entirely to get it up and running again.
What to do about this?
Can anyone please pay attention to this topic? Because more and more problems arise because of this.
Clients their connections through the API don't work at a regular basis and we have to reset the act.web.api apppool all the time...