Workstation problem log with solutions
From Jonsdocswiki
Contents |
Boot issues
Restore image
Symptoms
When attempting to boot, before even receiving an XP splash screen you receive:
The system could not be restarted from its previous location because the restoration image is corrupt. Delete restoration data and proceed to system boot menu.
Fix
This shows that the computer was in hibernation and for some reason the information it saved has become irretrievably damaged. The cure is to highlight delete restoration data and proceed to system boot menu and press enter - the unit will then boot to Windows fine.
BSOD with A3AB.sys
Symptoms
A blue screen of death appears with a DRIVER_IRQL_NOT_LESS_OR_EQUAL error and also mentions A3AB.sys when the user logs on to Windows.
Information
The file A3AB.sys is part of the DLink wireless driver. Logging into Windows without the DLINK card in gives the Novell Netware logon prompt but this may not happen on every occasion.
Fix
Removing and reinstalling the driver may not work. A known fix was to swap the card out with a netgear wireless instead.
See Also
Authentication issues
compromise security error
Symptoms
When attempting to access their home area, one user received the above message. Their workstation had been on overnight and had authenticated against a DC that had failed.
Fix
Reboot the workstation to force re-authentication against a valid (working) DC.
Time Skewed
Symptoms
If a workstation's clock is too far out for domain policy, you will get this error.
Resolution
Login locally and adjust the time and date to match the server time. You may be able to do this using net time
Computer account issue
Symptoms
When attempting to logon to the domain a user receives the message: Windows cannot connect to the domain, either because the domain controller is down or otherwise unavailable, or because your computer account was not found. Please try again later. If this message continues to appear, contact your system administrator for assistance.
This may be accompanied by the following error in the system event log of the domain controller.
Event Type: Error Event Source: NETLOGON Event Category: None Event ID: 5722 Date: 01/07/2008 Time: 15:46:00 User: N/A Computer: BACKUPDC Description: The session setup from the computer RM3030 failed to authenticate. The name(s) of the account(s) referenced in the security database is RM3030$. The following error occurred: Access is denied.
Fix
Rejoining the computer to the domain will resolve this. It is best practise to reset the computer account in Active Directory Users and Computers first (see MSKB 216393).
See also
Windows needs your current credentials
These errors appear when server Active Directory synchronisation is incomplete, behind or generally not working.
Symptoms
Fix
Get the user to attempt to act as instructed. If that fails, get them to change their password. If that also fails, change their password on the domain controller.
Windows is unable to obtain a domain name
Symptoms
Event ID: 1054
Source: Userenv Type: Error Description: Windows cannot obtain the domain controller name for the computer network. (The specified domain either does not exist or exist or could not be contacted). Group Policy processing aborted. Data: (unavailable)
This is an issue with network drivers and NDIS. The solution is the addition of a registry key.
Please see Microsoft KB article 840669
See also
File Synchronisation Issues
File problems
Problems redirecting My Documents
Symptoms
When attempting to redirect My Documents there are no options available - the target box is read only and there are no buttons beneath it (pictured left).
Fix
This is likely due to the presence of a registry key designed to prevent this change, you will need to edit the registry to fix this:
- Open regedit (Start > Run > regedit > OK)
- Expand HKEY_CURRENT_USER
- Continue expanding along this path: \Software\Microsoft\Windows\CurrentVersion\Policies\Explorer
- Look for the key called DisablePersonalDirChange and delete it (you may wish to back it up / export it first)
- Close the registry editor
- Continue redirecting My Documents (changes to the registry are instant)
See Also
Installation Problems
MSI error 1325
Symptoms
When trying to run an application for the first time / install an application the user is told:
Error 1325: <FILE> is not a valid short file name
Fix
Using the MSI Clean up utility, remove the application. You will then need to reinstall the application from disk or from network. If this doesn't resolve the issue, see if there is an update to the application available.
See also
- MS KB328162
- How to remove Office 2007 without Add/Remove programs (can't use the same cleanup utility)
- Description of the MSI clean up utility



