Consider the following scenario. You have a Windows Server 2008-based computer. You move the WINS database from the default location (%windir%\system32\wins) to another location. In this scenario, the WINS service may be unable to start. Additionally, the WINS service may return the 0xe0000002 error code. The following events are logged in the system event log:
Log Name: System Source: Service Control Manager Date: date Event ID: 7024 Task Category: None Level: Error Keywords: Classic User: N/A Computer: computer name Description:The WINS service terminated with service-specific error 3758096386 (0xE0000002)
Log Name: System Source: Wins Date: date Event ID: 4224 Task Category: NoneLevel: ErrorKeywords: Classic User: N/A Computer: computer name Description:WINS encountered a database error. This may or may not be a serious error. WINS will try to recover from it. You can check the database error events under 'Application Log' category of the Event Viewer for the Exchange Component, ESENT, source to find out more details about database errors. If you continue to see a large number of these errors consistently over time (a span of few hours), you may want to restore the WINS database from a backup. The error number is in the second DWORD of the data section.
Log Name: System Source: Wins Date: date Event ID: 4318 Task Category: None Level: Error Keywords: Classic User: N/A Computer: computer name Description:WINS could not start due to a missing or corrupt database. Restore the database using WINS Manager (or winscl.exe found in the Windows 2000 Resource Kit) and restart WINS. If WINS still does not start, begin with a fresh copy of the database. To do this: 1) Delete all the files in the %%SystemRoot%%\system32\WINS directory. NOTE: If the WINS database file (typically named wins.mdb) is not in the above directory, check the registry for the full filepath. Delete the .mdb file. NOTE: If jet*.log are not in the above directory, check the registry for the directory path. Delete all log files 2) Restart WINS.
This issue can also occur if you have used jetpack to compress the WINS database and when you try to restart the WINS Service afterwards. Starting the service will fail with the error message "A service specific error occurred: 3758096385.".
In Windows Server 2008, the WINS service is started by the local service account (NT AUTHORITY\LocalService) instead of by the local system account (NT AUTHORITY\System). The local service account has fewer permissions. Therefore, the local service account may not have sufficient permissions to access the WINS database after you move the WINS database to another location.
To resolve this problem, manually grant sufficient access permissions to the WINS service. To do this, grant the Full Control permission to the local service account for the new WINS database location in Windows Explorer. You can also run the following command at a command prompt:
icacls new WINS database location /grant "NT SERVICE\WINS:(OI)(CI)(F)"
Note When you try to back up the WINS database to another target folder, you have to grant sufficient access permissions to the target folder also. Otherwise, you may receive an "access denied" error when you perform the backup.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
The WINS service resolves NetBIOS names to IP addresses on a Windows network. Clients on a WINS-enabled network can dynamically register, update, and remove their names from a WINS-maintained database. As an administrator, you can also assign static entries in a WINS database for computers that are running operating systems other than Windows. Additionally, you can provide redundancy by replicating the WINS database to more than one WINS server on a network. For addresses that are outside the network, you can enable the WINS server to refer to a statically configured LMHosts file.