<div>
Check your FRS event logs for errors in the 13000's<br />
<br />
It sounds like you are having problems with DNS. This will cause problems with replication and can put you in journal Wrap. That will cause 1030 and 1058 event errors. So, we will need to fix DNS prior to fixing Journal Wrap issues. But, let's see if you are in Journal Wrap, first. 
</div>


Check your FRS event logs for errors in the 13000's

It sounds like you are having problems with DNS. This will cause problems with replication and can put you in journal Wrap. That will cause 1030 and 1058 event errors. So, we will need to fix DNS prior to fixing Journal Wrap issues. But, let's see if you are in Journal Wrap, first.

<div>
<div class="content wysiwyg-content">
A few days ago I rebooted a server and upon booting back up, it hung at &quot;Preparing Network Connections&quot; for hours. Today, I looked in the APPLICATION event log and see about 1000 errors that read the following:<br />
<br />
EVENT ID: 1058<br />
<br />
Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945<wbr />F-00C04FB9<wbr />84F9},CN=P<wbr />olicies,CN<wbr />=System,DC<wbr />=SHCC,DC=l<wbr />ocal. The file must be present at the location &lt;\\SHCC.local\sysvol\SHCC.<wbr />local\Poli<wbr />cies\{31B2<wbr />F340-016D-<wbr />11D2-945F-<wbr />00C04FB984<wbr />F9}\gpt.in<wbr />i&gt;. (The semaphore timeout period has expired. ). Group Policy processing aborted.<br />
<br />
I am also gettings EVENT ID: 1030<br />
<br />
Please throw some suggestions my way
</div>
</div>


A few days ago I rebooted a server and upon booting back up, it hung at "Preparing Network Connections" for hours. Today, I looked in the APPLICATION event log and see about 1000 errors that read the following:

EVENT ID: 1058

Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=SHCC,DC=local. The file must be present at the location <\\SHCC.local\sysvol\SHCC.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>. (The semaphore timeout period has expired. ). Group Policy processing aborted.

I am also gettings EVENT ID: 1030

Please throw some suggestions my way

Event log error &quot;Windows cannot access the file gpt.ini&quot; on SBS Server 2003

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

Small Business Server (SBS) is a line of server operating systems targeted at small businesses by bundling the operating system with a number of other Microsoft products that would normally need to be purchased or licensed separately. The most notable inclusions are Exchange, SQL Server, SharePoint and ISA/TMG (Microsoft's firewall and proxy server).

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.

Event log error &quot;Windows cannot access the file gpt.ini&quot; on SBS Server 2003

Event log error "Windows cannot access the file gpt.ini" on SBS Server 2003