You may not be able to start the Group Policy snap-in on your Microsoft Windows Small Business Server 2003 computer, and the following Error events may be logged in the System event log.

Back to the top

Event 1030

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1030
Description:
Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this.

Back to the top

Event 1058

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1058
Description:
Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=domain,DC=local. The file must be present at the location <\\Random_Domain_Name.local\sysvol\domain.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.i ni>

Note that in event 1058, two different domain names are displayed for the domain. One name is the correct domain name. The other domain name appears to be a random name in a format that is similar to OEMSBSDN-9601.

Back to the top

This issue may occur when a procedure to repair the Group Policy objects (GPO) and the GPO references in the Active Directory directory service on a Windows Small Business Server 2003 computer has not been performed or was not successful. This kind of procedure is typically performed by the original equipment manufacturer (OEM) in a production environment where multiple installations of Windows Small Business Server 2003 are performed.

Back to the top

To resolve this issue, correct the domain name entry by using the ADSI Edit snap-in.
Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft Windows Server 2003, Microsoft Exchange 2000 Server, Microsoft Exchange Server 2003, or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk. Follow these steps to correct the domain name entry:

1.	Click Start, point to All Programs, point to Windows Support Tools, and then click Command Prompt. Note Install the Microsoft Windows Server 2003 Support Tools from Windows Small Business Server 2003 installation CD number 2 if these tools are not installed on your Small Business Server 2003 computer.
2.	To start the ADSI Edit snap-in, type adsiedit.msc at the command prompt.
3.	Expand the path that is indicated in the event 1058 message. For example, expand the following containers: • Domain [Random_Domain_Name] • DC=Random_Domain_Name, DC=local • CN=System • CN=Policies
4.	Right-click CN={31B2F340-016D-11D2-945F-00C04FB984F9}, and then click Properties.
5.	Click the Attribute Editor tab. In the Attributes box, locate and then double-click gPCFileSysPath.
6.	In the String Attribute Editor dialog box, change the incorrect domain name to the correct domain name.
7.	Click OK two times, and then quit the ADSI Edit snap-in.
8.	At the command prompt, type gpupdate, and then press ENTER.

Back to the top

For more information about how to resolve event 1058 and event 1030 issues, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top