I ran a check disk (chkdsk) to resolve issue. At Stage 4 of 5, Windows replaced bad clusters in the file 9259 of name \windows\system32\wpa.dbl.
Error 0x80040057 - According to ME970988
, this may be recorded in certain conditions when the system has low system resources. As of May 12, 2009, this is still an issue.
This error may also occur if the disk cleanup wizard is run with the "compress old files" option enabled. This can compress the files in the WINDOWS\SYSTEM32 directory, including the WPA.DBL file. Boot into safe mode and check the compression settings on that file. If set to compressed, change to uncompressed and then reboot.
In my case, replacing the OEMBIOS.BIN file from another working system, followed by a restart, solved the problem.
This event can occur when performing an in-place upgrade from non-VLA (Volume License Agreement) media to Windows Server 2003 using VLA media. See ME555488
to find out how to avoid this situation.
- Error code: 0x8007007f - I fixed it only after replacing the dpcdll.dll file from another working system (replaced with version 5.1.2600.2180, old version was 5.1.2600).
- Error code: 0x80070002 - See ME310794
This error might occur if you have overly restrictive permissions set on the WINNT directory. Make sure that Administrators and System have "Full Control" permissions on WINNT, and make sure that the folder is not set to "Read Only". Also check the permissions on the root of "C:", and verify that Administrators and System accounts have "Full Control". This might also occur if the files "WPA.DBL" and/or "WPA.BAK" are marked as "Read Only". If they are, uncheck this setting in the property sheet(s) for the file(s).
As per Microsoft: "If you are running Windows XP SP1/SP2 or Windows Server 2003, the Windows Validation Assistant can scan your product key to help you determine whether your computerís operating system is genuine". See the link to "Windows Validation Assistant" to scan the product key.
From a newsgroup post: "To solve this issue boot the system, start pressing F8, and when the menu appears, choose safe mode. In safe mode do the following: Go to start/run, and type
Another solution is to perform a Repair Installation, inserting the legal Product Key."