Dear Kevin Williams,
Did you ever heard, in movies and TV, the girl says to the guy that
"Its not you, it's me"? This time it is certainly not you, it's them.
Microsoft VBScript [Visual Basic] runtime wrror '800a000d' is a well
known (or should I say: notorious) problem in Active Server Pages
(.asp) that depend on this script. Basically, it happens when there
are incompatible VBS types.
Mike from Microsoft support forum says "Basically it is a line of,
presumably, server side code that is trying to process a string
variable that is either missing, empty, null value or otherwise
incorrect." (Source:
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&threadm=4f3101c26276%2454bbec20%2437ef2ecf%40TKMSFTNGXA13&rnum=16&prev=/groups%3Fq%3D%27800a000d%27%26start%3D10%26hl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26selm%3D4f3101c26276%252454bbec20%252437ef2ecf%2540TKMSFTNGXA13%26rnum%3D16)
And Michael Corning also writes, that "this often occurs when passing
parameters to object methods". (Source: 15 Seconds.com
http://www.15seconds.com/faq/Errors/475.htm).
Sometimes, if you use another browser, it would work (depending on the
problem). I hope that answered your question. Please let me know if
you need any further clarifications before you rate the answer. I'd be
pleased to clarify my answer before you rate it. |