Microsoft KB Archive/819513

= FIX: Cluster Service Node Experiences Failover When Services for UNIX is Installed =

Article ID: 819513

Article Last Modified on 10/25/2005

-

APPLIES TO


 * Microsoft Windows Services for Unix 2.3
 * Microsoft Windows Services for UNIX 3.0 Standard Edition

-



SYMPTOMS
When Windows Services for UNIX (SFU) is installed, a node may occasionally experience failover. This symptom may occur when the node is started. You may also not be able to move resources back to the node.



CAUSE
This problem occurs because the port mapper service has too many uncompleted tasks. Eventually, these incomplete tasks can block other system tasks, such as calls to ping. This blockage can cause several symptoms, including node failover.



RESOLUTION
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.   Date         Time   Version            Size    File name --  03-May-2003  00:18  5.3000.2117.9      78,336  Clilocks.dll 03-May-2003 00:08  5.3000.2117.9      31,744  Clusnfs.exe 03-May-2003 00:08  5.3000.2117.9      24,064  Nfsonly.exe 03-May-2003 00:08  5.3000.2117.9      66,048  Nfssh.dll 21-May-2003 20:25  5.3000.2117.9      88,064  Nfsshare.exe 03-May-2003 00:08  5.3000.2117.9     143,360  Nfsshex.dll 03-May-2003 00:08  5.3000.2117.9     113,664  Nfssprop.dll 03-May-2003 00:08  5.3000.2117.9      94,720  Nfssvc.exe 05-Jun-2003 10:19  5.3000.2117.9     324,128  Nfssvr.sys 03-May-2003 00:08  5.3000.2117.9      40,832  Portmap.sys 14-Dec-2001 19:01  5.0.2134.1         35,600  Regini.exe 03-May-2003 00:08  5.3000.2117.9      72,800  Rpcxdr.sys 06-Apr-2002 09:33                     27,102  Supphelp.chm 03-May-2003 00:08  5.3000.2117.9      48,128  Upnfs3.exe The English version of this fix has the file attributes (or later) that are listed in the following table:

   Date         Time   Version            Size    File name --  05-Jun-2003  07:46  7.0.1701.14        23,040  Dsctrs.dll 05-Jun-2003 07:46  7.0.1701.14        25,088  Nfsonly.exe 05-Jun-2003 07:46  7.0.1701.14        67,072  Nfssh.dll 05-Jun-2003 07:45  7.0.1701.14        88,576  Nfsshare.exe 05-Jun-2003 07:46  7.0.1701.14       143,872  Nfsshex.dll 05-Jun-2003 07:46  7.0.1701.14       114,176  Nfssprop.dll 05-Jun-2003 09:36  7.0.1701.14       325,056  Nfssvr.sys 05-Jun-2003 09:36  7.0.1701.14       323,008  Nfssvrn4.sys 03-May-2003 00:43  7.0.1701.14        42,624  Portmap.sys 05-Jun-2003 07:46  7.0.1701.14        73,056  Rpcxdr.sys



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

