Odd (and infrequent) render error on 64bit ASP.NET app ...

Question

User-1249438147 posted
Folks,

We recently cut over to 64bit hardware (unrelated saga here) and things are much, much better. We really didnt have any snafu's of note, just a small batch of little things. We have however noticed two new kinds of errors that dont make a lot of sense.

The first error appears to be a render error (as best I can tell) where very infrequently (1 error per 10,000 requests) will cause a script tag added via the script manager to get munged.

For example, the legimate script tag we add looks like this:

    <script src="/foresee/foresee-trigger.js" type="text/javascript"></script>

Yet we get 404 errors for a GET that looks like this:

    http://www.trailblazerhealth.com/FileNotFound.aspx?404;http://www.trailblazerhealth.com:80/foresee/foresee-trigge%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3Ca%20id 

To avoid ya'll having to translate that in your head, this is what the decoded URL looks like:

    http://www.trailblazerhealth.com/FileNotFound.aspx?404;http://www.trailblazerhealth.com:80/foresee/foresee-trigge                        <a id=

The legitimate link was apparently cut off by what appears to be generic HTML from somewhere.

Has anyone seen/heard anything like this? I am going to add the script tag via an ASP:Literal in the head (script manager writes to the ) and see what happens, but this might be a problem for others even if I am able to work around.

The second error we have seen is equally as odd. The error only seems to come from one page, but again its not clearly reproducable. This is one of our most heavily trafficed "look up" pages, so again the error rate has to be pretty low (1 in 1,000). This is an example of what we see:

    '???_6it*?I J?E)?`a???4I?,??k‑? ?sp' is not a valid virtual path.

The hex equivalent (via a cut and paste from an error email) is as follows:

    27 3f 20 3f 3f 5f 20 36 20 69 74 2a 3f 49 20 4a 3f 45 20 29 3f 60 61 3f 3f 3f 34 49 3f 2c 3f 20 3f 6b 20 3f 20 20 3f 73 70 27

No other pages seem to have this problem and the page in question doesn't do any crazy dynamic stuff. The requests that generate these errors seem legitimate from what we log and its not clear why the request results in an invalid virtual path.

Just wanted to post on the off chance someone else is seeing or knows about either of these two issues.

Regards,

Stuart