This article describes Terminal Server error messages 200 to 999.
The code segment cannot be greater than or equal to 64KB.
The system could not find the environment option that was entered.
No process in the command subtree has a signal handler.
The filename or extension is too long.
The ring 2 stack is in use.
The global filename characters, * or ?, are entered incorrectly or too many global filename characters are specified.
The signal being posted is not correct.
The signal handler cannot be set.
The segment is locked and cannot be reallocated.
Too many dynamic link modules are attached to this program or dynamic link module.
Can't nest calls to LoadModule.
The pipe state is invalid.
All pipe instances are busy.
The pipe is being closed.
No process is on the other end of the pipe.
More data is available.
The session was cancelled.
The specified extended attribute name was invalid.
The extended attributes are inconsistent.
No more data is available.
The Copy API cannot be used.
The directory name is invalid.
The extended attributes did not fit in the buffer.
The extended attribute file on the mounted file system is corrupt.
The extended attribute table file is full.
The specified extended attribute handle is invalid.
The mounted file system does not support extended attributes.
Attempt to release mutex not owned by caller.
Too many posts were made to a semaphore.
Only part of a Read/WriteProcessMemory request was completed.
Attempt to access invalid address.
Arithmetic result exceeded 32 bits.
There is a process on other end of the pipe.
Waiting for a process to open the other end of the pipe.
Access to the extended attribute was denied.
The I/O operation has been aborted because of either a thread exit or an application request.
Overlapped I/O event is not in a signalled state.
Overlapped I/O operation is in progress.
Invalid access to memory location.
Error performing inpage operation.
Id. de artículo: 186549 - Última revisión: 31 oct. 2006 - Revisión: 1