In the past 2 weeks, our nightly IISReset has not come back up successfully and caused us an outage.
We have a Windows Task that runs every night that executes an IISReset, and I'm wondering if this is even necessary anymore?
Should I be looking into the functionality in the app pool to restart itself instead?
I've just spent the past 10 hours trying to figure out why my http request was failing when I did a
request.Content.ReadAsMultipartAsync().Result.Contents
It kept returning the error:
Unexpected end of MIME multipart stream. MIME multipart message is not complete.
After many hours of research, I finally discovered that the request did not have an ending CRLF, which apparently .Net needs to determine the end of the request. When I added my own CRLF, everything worked great.
In WireShark, I looked at one of the requests, I saw that the chunked request did have an ending CRLF, but the De-Chunked request did not.
So that leaves me with 2 questions.
My Windows Server is running on 3gb of memory right now, and I would like to upgrade to 16gb.
However, I don't know what type of memory to buy. I know that the notches in the physical RAM are different depending on the memory type.
Is there a way in Windows Server 2012 to detect the type of memory so I get the correct one?