My SL is commercial and runs fine on hundreds of machines.
SL uses the WCF service and works as expected, but today I observed behavior on the client machine, where it is not literally called to the server.
After clicking the button that sends the call, some error occurs and Fiddler does not create a WCF call record.
Mistake:
[HttpWebRequest_WebException_RemoteServer] Arguments: NotFound Debugging resource strings are unavailable...
I read about this error that people recommend using Fiddler, but as I said, call does not appear in Fiddler
So, the problem is worse than I originally thought.
He comes and goes. Currently, we have found a working solution that fixes the problem after its appearance, although this does not make any sense to me.
For example, if I get this error in the version of chrome and mozilla and OOB, running the program in IE works, and after that chrome, mozilla and OOB start working too.
The fact is that the same people who solved this problem with this workaround try it again after a few days, like a week, for no apparent reason, and then a combination of launches from different places helps (usually IE helps the most )
Any help is appreciated, I begin generosity as her rather sick mistake, and I need to fix it somehow.
Update
Strange IE fix script:
At some point, the OOB version enters a state where it does not send any WCF request to the server. (the violinist does not see it, the server does not receive it). After launching the web version in IE and pressing the same button that sends the WCF request, we get the desired result in the web version of IE.
Without changing anything else, just restarting the OOB version that was previously in this terrible state, the OOB version works correctly. It has not been reinstalled, not changed - nothing.
This is what I call the "IE curure" of this problem. So the question is, can IE change the potential for the OOB version?