Random "write fault" errors or SPOOLSV.EXE or SPOOLSS.EXE service access violations in DPRPCW32.DLL.
(Last modified: 16Sep2003)
This document (10080018) is provided subject to the disclaimer at the end of this document.
fact
Novell Client for Windows NT/2000/XP
Novell Client for Windows 95/98
symptom
Random "write fault" errors or SPOOLSV.EXE or SPOOLSS.EXE service access violations in DPRPCW32.DLL.
Error: "SPOOLSV.EXE has generated errors and will be closed the Windows. You will need to restart the program." on Windows 2000 (and Windows XP, if "Visual Notification" is enabled in DRWTSN32.EXE).
Error: "SPOOLSS.EXE. Exception: access violation (0xc0000005)" on Windows NT 4.0.
Error "SPOOLSV.EXE Application Error. The instruction at "0xnnnnnnnn" referenced memory at "0xnnnnnnnn". The memory could not be "written". Click on OK to terminate the program." when the Microsoft C runtime exception handler catches the error.
Error: "NDPS Print Provider for NetWare Error. A write fault occurred on the network."
NDPPNT.LOG or NDPP95.LOG Error: "writeprinter failed for \\ <treename>\<printername>.<context>, libError = 70000B othererror = 0"
Error NWDP_LE_RPC_CANTDECODEARGS (0x0070000B) reported during NDPS client operations.
cause
The NDPS RPC handler (DPRPCW32.DLL) could potentially cause a write fault error or an access violation when processing RPC messages for transmission that fell within specific sizes.
fix
Fixed in the Novell Client 4.83 SP2 for Windows NT/2000/XP.
This fix is included in the DPRPCW32.DLL v3.0.1 05FEB2003 and later.
note
BACKGROUND:
This issue could occur when the size of an RPC message being sent by the NDPS client happened to be of a size that caused data to fall on specific boundaries. There is not any specific document size or print data size that can be cited, because changing any aspect of the NDPS RPC message being sent can change the overall size such that the issue will occur or not occur.
(For example, even just changing the name of the file being printed during an NDPS print operation could cause or prevent the issue, even though the size of the document itself hadn't changed.)
In this case the "write fault" message was an indirect result of a different issue that had actually occurred. The local workstation incorrectly transmitted an NDPS RPC message, which the NDPS server rejects with an RPC accept status of "can't decode arguments". The workstation then reports this as a "write fault", but the cause was actually the erroneous transmission that the workstation itself made. (i.e. Not because of communication errors or problems external to the workstation.)
Note however that "write fault" messages can also occur due to legitimate communication problems (such as packets dropped or mis-fragmented at routers, etc.). If encountering a persistent "write fault" message, use LAN capture and protocol analysis software to determine whether there is actually a transport-level communication issue occurring, check LAN cabling, network adapters, and other communication-level components.
document
| Document Title: | Random "write fault" errors or SPOOLSV.EXE or SPOOLSS.EXE service access violations in DPRPCW32.DLL. |
| Document ID: | 10080018 |
| Solution ID: | NOVL86856 |
| Creation Date: | 07Feb2003 |
| Modified Date: | 16Sep2003 |
| Novell Product Class: | NetWare |
disclaimer
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.