| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 723.1 |  | LJSRV1::GOODMAN |  | Thu Apr 03 1997 13:32 | 1 | 
|  | Ginny, Do you have a copy of the Listener.ora file?
 | 
| 723.2 | Need more info | DECWET::CAPPELLOF | My other brain is a polymer | Thu Apr 03 1997 13:51 | 6 | 
|  |     In order to diagnose this problem further, we need the detailed
    information from the NT event log entry that says "...does not support
    this type of IRP function".  If you could have the customer send you
    the entire contents of this error packet, including all the data shown
    in Event Viewer, it will tell us which IRP function is causing the
    complaint.
 | 
| 723.3 | The event log information | CSC32::G_OGLESBY | Ginny Oglesby 592-4731 CSC/CS | Thu Apr 03 1997 18:45 | 21 | 
|  | I'm working this problem offline, but I'll post the event log information
in case others following this might find it useful.
System Log
Event Code 40003
Source: CFS
"The Cluster File Ssytem does not support this type of IRP function."
for bytes:
0000:  01 00 00 00 01  00 50 00
0008:  00 00 00 00 43 9c  00 c0
0010:  00 00 00 00 02  00 00 c0
0018:  00 00 00 00 00 00 00 00
0020:  00 00 00 00 00 00 00 00
for words:
0000:  00000001  00500001  00000000  c0009c43
0010:  00000000  c0000002  00000000  00000000
0020:  00000000  00000000
 | 
| 723.4 | CREATE_NAMED_PIPE confuses CFS driver | DECWET::CAPPELLOF | My other brain is a polymer | Tue Apr 08 1997 19:55 | 7 | 
|  |     Hmmm, the first longword in the error packet is 0x00000001, which is
    the major function code for IRP_MJ_CREATE_NAMED_PIPE, which, as the
    error code indicates, a function that's not supported by the CFS driver
    (NT Cluster name client driver).
    
    I wonder what Oracle is doing that causes the CFS driver to see this
    function code?  Normally, it shouldn't get this far.
 |