Rasman service init error

Summary

The Remote Access Connection Manager service failed to start due to initialization failure.

Causes

The most common reasons for initialization failure are:

The Remote Access Connection Manager service failed to start the WAN Mini Port (IP) device driver (NDISWAN). The most common reasons for this error are:

• The WAN Mini Port (IP) device driver (NDISWAN) failed to initialize.

• The Remote Access Connection Manager service does not have sufficient permissions to open the driver.

• The Remote Access Connection Manager service failed to create the security object. The most common reason for this error is that not enough memory is available on the server.

The Remote Access Connection Manager service failed to retrieve information for this media device. The most common reasons for this error are:

• Media information for this device could not be retrieved from the registry.

• Rastapi.dll failed to load.

The Remote Access Connection Manager service could not start because it failed to register with the Local Security Authority (LSA). The most common reasons for this error are:

• The Remote Access Connection Manager service does not have required permissions to register with the LSA.

• The LSA does not recognize the authentication package with which the Remote Access Connection Manager service tried to register.

The Remote Access Connection Manager service failed because it encountered an error during RPC initialization. The most common reasons for this error are:

• The service could not load the necessary DLLs.

• The SYSTEM account does not have read/write permissions for the needed registry keys.

• Not enough memory was available on the server.

Sample Events:

• Sample Event #1: Remote Access Connection Manager failed to start because NDISWAN could not be opened.

• Sample Event #2: Remote Access Connection Manager failed to start because it could not initialize the security attributes. Restart the computer. %1

• Sample Event #3: Remote Access Connection Manager failed to start because it could not load one or more communication DLLs. Ensure that your communication hardware is installed and then restart the computer. %1

• Sample Event #4: Remote Access Connection Manager failed to start because it could not locate port information from media DLLs. %1

• Sample Event #5: Remote Access Connection Manager failed to start because it could not register with the local security authority.Restart the computer. %1

• Sample Event #6: Remote Access Connection Manager failed to start because the RAS RPC module failed to initialize. %1

Resolutions

Check whether the System account has read/execute permissions for the file %systemroot%\system32\drivers\ndiswan.sys. To check the permissions:

• Right-click the file name, and then click Properties.

• On the Securities tab, verify that the System account read/execute permissions for the file.

• If the server is low on memory, take appropriate action to increase the available memory. See Help and Support Center for information on low memory.

Verify whether the following registry key exists: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Rasman\Parameters\Medias

If the registry key does not exist, you can create it with the following values:

• Name: Medias; Type: REG_MULTI_SZ;

• Value: rastapi

Verify whether the file rastapi.dll exists in the %systemroot%\system32 folder.

Verify whether the System account has read/execute permissions for rastapi.dll. To check whether the System account has these permissions:

• Right-click rastapi.dll, and click Properties.

• On the Security tab, verify whether the System account has read/execute permissions for rastapi.dll. If it does not, add them.

Verify that the following DLLs exist in the %systemroot%\System32 folder:

• Rasman.dll

• Rasmans.dll

• Rasapi32.dll

If any of these DLLs are not present, you must repair or reinstall the operating system. For more information about repairing and reinstalling the operating system, see Help and Support Center.

Verify whether the SYSTEM account has read/write permissions for the DLLs. To check the permissions:

• Right-click each DLL, and click Permissions.

• Verify whether the SYSTEM account has read/write permissions for the DLL. If it does not, add them.

• If the SYSTEM account has read/write permission for all three DLLs, restart the server. If the problem persists, restart the server.

© 2013 Microsoft Corporation, all rights reserved