[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::winnt-clusters

Title:WinNT-Clusters
Notice:Info directories moved to DECWET::SHARE1$:[NT_CLSTR]
Moderator:DECWET::CAPPELLOF
Created:Thu Oct 19 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:863
Total number of notes:3478

723.0. "System Event error from CFS, and Oracle Listener service stopped." by CSC32::G_OGLESBY (Ginny Oglesby 592-4731 CSC/CS) Mon Mar 31 1997 19:48

Customer is running WNT 3.51 on two 4100 servers.  Oracle Workgroup Server 7.2.
Digital Cluster 1.0sp2.

Earlier today noticed the following in the System Event Log on one of the servers:

Event Code 40003, Source: CFS
"The Cluster File System does not support this type of IRP function."

Users were no longer able to connect to this server, using the server name,
with Oracle.
Turns out the Oracle Listener Service had gone into a stopped state,
possibly the effect of the above error?

No new users were able to connect to this service due to the listener service
being stopped.  Users already connected were OK.  He was simply able to 
re-start the service.

What does this error mean?  What is an IRP function?  What type of scenario
might have caused this?

Thanks in advance for your help.

Ginny
T.RTitleUserPersonal
Name
DateLines
723.1LJSRV1::GOODMANThu Apr 03 1997 14:321
Ginny, Do you have a copy of the Listener.ora file?
723.2Need more infoDECWET::CAPPELLOFMy other brain is a polymerThu Apr 03 1997 14:516
    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.3The event log informationCSC32::G_OGLESBYGinny Oglesby 592-4731 CSC/CSThu Apr 03 1997 19:4521
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.4CREATE_NAMED_PIPE confuses CFS driverDECWET::CAPPELLOFMy other brain is a polymerTue Apr 08 1997 20:557
    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.