& Quot; the key set does not exist & quot; error caused by the encoding format of the Asp.net page

Google's "key set does not exist" error solution cannot solve my problem. This error is an unprocessed exception. However, the user code cannot catch this exception and can only be observed through the event viewer. If this error occurs, the webserver w3wp.exe will be shut down unexpectedly and restarted. The result is that the Session will expire soon, the process will end, and the Session variable will no longer exist.

 

 

 

 

The ID1334, 5000, and 4096 events occur in a regular order.

 

The customer had to switch back to the previous backup when the call was made. As a result, this error disappears. The problem must have been caused by recent program modifications. However, I did not find any problems by carefully comparing the program code.

 

I accidentally thought of the encoding format, because many inexplicable problems are caused by the file encoding format. Open a recently modified file in notepad. aspx, "File Save as", found to be ANSI format, but other files are Utf-8 format, suddenly remembered in the modify. the aspx file copies a piece of code from the Utf-8 file to. in aspx. Will this cause an IIS exception?

 

So save the file as UTF-8 encoding format, and then copy the Code, after the release the problem is resolved, the error does not appear again. However, this kind of error usually rarely appear, are UTF-8 format, appear may do not care, but simply comes down to the RP problem. I hope it will help my friends who have encountered the same problem.

 

Warning: there is no difference between a piece of text, but it is in the encoding format.

Author Slmk