Microsoft-Windows-ServicesForNFS-Client

22 events across 2 channels

Event IDTitleChannel
5000Service Control Manager failed a request for Client for NFS to initialize %1.Operational
5001Service Control Manager failed a request to update service status %1.Operational
5002Windows(R) Sockets failed a request to initialize %1.Operational
5003Windows(R) failed a request to initialize the Network File System (NFS) …Operational
5004Windows(R) failed a request to open a communications port to the Network File …Operational
5005Windows(R) failed a request to create a supporting process thread %1.Operational
5006The Windows(R) remote procedure call (RPC) subsystem failed a request to …Operational
5007Windows(R) failed a request to create a security descriptor %1.Operational
5008Windows(R) failed a request to unload the Network File System (NFS) redirector …Operational
5009Client for NFS started successfully.Operational
5010Client for NFS stopped successfully.Operational
5011The Windows(R) remote procedure call (RPC) subsystem failed a request to clean …Operational
5012Windows(R) failed a request to clean up after completing tasks for client %1.Operational
5013Operational
5013Windows(R) Lightweight Directory Access Protocol (LDAP) failed a request to …IdentityMapping
5014Operational
5014The Active Directory Domain Services(R) uidNumber attribute is not set for …IdentityMapping
5015Operational
5015The Active Directory Domain Services(R) gidNumber attribute is not set for …IdentityMapping
5100Windows(R) failed a request to access system resources associated with the …Operational
5101Windows(R) failed a request to communicate with the Network File System (NFS) …Operational
5102Client for NFS cannot communicate with the remote Network File System (NFS) …Operational

Event ID 5000 — Service Control Manager failed a request for Client for NFS to initialize %1.

Provider
Microsoft-Windows-ServicesForNFS-Client
Channel
Operational

Message

Service Control Manager failed a request for Client for NFS to initialize %1.

Client for NFS cannot start.

Windows(R) may be low on system resources.  Try increasing available system resources by closing programs, then start Client for NFS manually.

Fields

NameDescription
ErrorString

Event ID 5001 — Service Control Manager failed a request to update service status %1.

Provider
Microsoft-Windows-ServicesForNFS-Client
Channel
Operational

Message

Service Control Manager failed a request to update service status %1.

Client for NFS cannot properly reflect service status in administrative tools, such as Computer Management.

Windows(R) may be low on system resources.  Try increasing available system resources by closing programs, then start Client for NFS manually.

Fields

NameDescription
ErrorString

Event ID 5002 — Windows(R) Sockets failed a request to initialize %1.

Provider
Microsoft-Windows-ServicesForNFS-Client
Channel
Operational

Message

Windows(R) Sockets failed a request to initialize %1.

Client for NFS cannot start.

Windows may be low on system resources.  Try increasing available system resources by closing programs, then start Client for NFS manually.

Fields

NameDescription
ErrorString

Event ID 5003 — Windows(R) failed a request to initialize the Network File System (NFS) redirector %1.

Provider
Microsoft-Windows-ServicesForNFS-Client
Channel
Operational

Message

Windows(R) failed a request to initialize the Network File System (NFS) redirector %1.

Client for NFS cannot start.

Windows may be low on system resources.  Try increasing available system resources by closing programs, then start Client for NFS manually.

Fields

NameDescription
ErrorString

Event ID 5004 — Windows(R) failed a request to open a communications port to the Network File System (NFS) redirector %1.

Provider
Microsoft-Windows-ServicesForNFS-Client
Channel
Operational

Message

Windows(R) failed a request to open a communications port to the Network File System (NFS) redirector %1.

Client for NFS cannot start.

Windows may be low on system resources.  Try increasing available system resources by closing programs, then start Client for NFS manually.

Fields

NameDescription
ErrorString

Event ID 5005 — Windows(R) failed a request to create a supporting process thread %1.

Provider
Microsoft-Windows-ServicesForNFS-Client
Channel
Operational

Message

Windows(R) failed a request to create a supporting process thread %1.

Client for NFS cannot start.

Windows may be low on system resources.  Try increasing available system resources by closing programs, then start Client for NFS manually.

Fields

NameDescription
ErrorString

Event ID 5006 — The Windows(R) remote procedure call (RPC) subsystem failed a request to register Client for NFS %1.

Provider
Microsoft-Windows-ServicesForNFS-Client
Channel
Operational

Message

The Windows(R) remote procedure call (RPC) subsystem failed a request to register Client for NFS %1.

Client for NFS cannot start.

Windows may be low on system resources.  Try increasing available system resources by closing programs, then start Client for NFS manually.

Fields

NameDescription
ErrorString

Event ID 5007 — Windows(R) failed a request to create a security descriptor %1.

Provider
Microsoft-Windows-ServicesForNFS-Client
Channel
Operational

Message

Windows(R) failed a request to create a security descriptor %1.

Client for NFS cannot start.

Windows may be low on system resources.  Try increasing available system resources by closing programs, then start Client for NFS manually.

Fields

NameDescription
ErrorString

Event ID 5008 — Windows(R) failed a request to unload the Network File System (NFS) redirector while Client for NFS was stopping %1.

Provider
Microsoft-Windows-ServicesForNFS-Client
Channel
Operational

Message

Windows(R) failed a request to unload the Network File System (NFS) redirector while Client for NFS was stopping %1.

Client for NFS stopped anyway and may not be able to restart.

Windows may be low on system resources.  Try increasing available system resources by closing programs, then start Client for NFS manually.

Fields

NameDescription
ErrorString

Event ID 5009 — Client for NFS started successfully.

Provider
Microsoft-Windows-ServicesForNFS-Client
Channel
Operational

Message

Client for NFS started successfully.

Event ID 5010 — Client for NFS stopped successfully.

Provider
Microsoft-Windows-ServicesForNFS-Client
Channel
Operational

Message

Client for NFS stopped successfully.

Event ID 5011 — The Windows(R) remote procedure call (RPC) subsystem failed a request to clean up after completing tasks for a client %1.

Provider
Microsoft-Windows-ServicesForNFS-Client
Channel
Operational

Message

The Windows(R) remote procedure call (RPC) subsystem failed a request to clean up after completing tasks for a client %1.

To ensure internal consistency, Client for NFS stopped.

Windows may be low on system resources.  Try increasing available system resources by closing programs, then start Client for NFS manually.

Fields

NameDescription
ErrorString

Event ID 5012 — Windows(R) failed a request to clean up after completing tasks for client %1.

Provider
Microsoft-Windows-ServicesForNFS-Client
Channel
Operational

Message

Windows(R) failed a request to clean up after completing tasks for client %1.

To ensure internal consistency, Client for NFS stopped.

Windows may be low on system resources.  Try increasing available system resources by closing programs, then start Client for NFS manually.

Fields

NameDescription
ErrorString

Event ID 5013 —

Provider
Microsoft-Windows-ServicesForNFS-Client
Channel
Operational

Fields

NameDescription
ErrorString

Event ID 5013 — Windows(R) Lightweight Directory Access Protocol (LDAP) failed a request to connect to Active Directory Domain Services(R) for Windows user %1.

Provider
Microsoft-Windows-ServicesForNFS-Client
Channel
IdentityMapping

Message

Windows(R) Lightweight Directory Access Protocol (LDAP) failed a request to connect to Active Directory Domain Services(R) for Windows user %1.

Without the corresponding UNIX identity of the Windows user, the user cannot access Network File System (NFS) shared resources.

Verify that the Windows user is in Active Directory Domain Services and has access permissions.

Fields

NameDescription
ErrorString

Event ID 5014 —

Provider
Microsoft-Windows-ServicesForNFS-Client
Channel
Operational

Fields

NameDescription
ErrorString

Event ID 5014 — The Active Directory Domain Services(R) uidNumber attribute is not set for Windows(R) user %1.

Provider
Microsoft-Windows-ServicesForNFS-Client
Channel
IdentityMapping

Message

The Active Directory Domain Services(R) uidNumber attribute is not set for Windows(R) user %1.

Without the corresponding UNIX identity of the Windows user, the user cannot access Network File System (NFS) shared resources.

Verify that the Active Directory Domain Services schema includes UNIX identity data, and then set the uidNumber attribute.

Fields

NameDescription
ErrorString

Event ID 5015 —

Provider
Microsoft-Windows-ServicesForNFS-Client
Channel
Operational

Fields

NameDescription
ErrorString

Event ID 5015 — The Active Directory Domain Services(R) gidNumber attribute is not set for Windows(R) user %1.

Provider
Microsoft-Windows-ServicesForNFS-Client
Channel
IdentityMapping

Message

The Active Directory Domain Services(R) gidNumber attribute is not set for Windows(R) user %1.

Without the corresponding UNIX identity of the Windows user, the user cannot access Network File System (NFS) shared resources.

Verify that the Active Directory Domain Services schema includes UNIX identity data, and then set the gidNumber attribute.

Fields

NameDescription
ErrorString

Event ID 5100 — Windows(R) failed a request to access system resources associated with the Network File System (NFS) network provider.

Provider
Microsoft-Windows-ServicesForNFS-Client
Channel
Operational

Message

Windows(R) failed a request to access system resources associated with the Network File System (NFS) network provider.

 If this problem persists, users may not be able to access NFS shared resources.

 Windows may be low on system resources.  Try increasing available system resources by closing programs, then start Client for NFS manually.

Event ID 5101 — Windows(R) failed a request to communicate with the Network File System (NFS) redirector.

Provider
Microsoft-Windows-ServicesForNFS-Client
Channel
Operational

Message

Windows(R) failed a request to communicate with the Network File System (NFS) redirector.

 If this problem persists, users may not be able to access NFS shared resources.

 Windows may be low on system resources.  Try increasing available system resources by closing programs, then start Client for NFS manually.

Event ID 5102 — Client for NFS cannot communicate with the remote Network File System (NFS) server %1.

Provider
Microsoft-Windows-ServicesForNFS-Client
Channel
Operational

Message

Client for NFS cannot communicate with the remote Network File System (NFS) server %1.

 RPC Port Mapper (also known as Portmap and Rpcbind) may not be running on the remote NFS server.

 Try starting RPC Port Mapper on the remote NFS server.

Fields

NameDescription
ServerName