There weren't as many error codes in this range as I had initially thought. Please let us know if you find others.
Microsoft VBScript runtime (0x800a0030)
Error in loading DLL |
See Article #2357 for more information.
Microsoft VBScript runtime error '800a0033'
Internal error |
This usually happens in global.asa, and indicates that the scripting engines have become corrupt. See Article #2151 for information on ensuring that your server is up to date.
Microsoft VBScript runtime (0x800A0034)
Bad file name or number
or
Server object error 'ASP 0177 : 800a0034'
Server.CreateObject Failed
/<file>.asp, line <line>
The operation completed successfully. |
See Article #2379 for more information about these errors.
Microsoft VBScript runtime (0x800A0035)
File not found
or
Server object error 'ASP 0177 : 800a0035'
Server.CreateObject Failed
/<file>.asp, line <line>
The operation completed successfully. |
See KB #276011. If you are trying to access a file on a network drive, see Article #2168.
Microsoft VBScript runtime (0x800A0036)
Bad file mode
or
Server object error 'ASP 0177 : 800a0036'
Server.CreateObject Failed
/<file>.asp, line <line>
The operation completed successfully. |
This usually means you tried opening or creating a file with a named constant, like ForAppending, when you should have used a constant. The following chart shows the possible values:
| ForReading | 1 |
| ForWriting | 2 |
| ForAppending | 8 |
Microsoft VBScript runtime (0x800A003a)
File already exists
or
Server object error 'ASP 0177 : 800a003a'
Server.CreateObject Failed
/<file>.asp, line <line>
The operation completed successfully. |
Sounds like you used Scripting.FileSystemObject to move or copy a file to a location, however there is already a file with the same name at that location.
[ Comment, Edit or Article Submission ]
