<div>
This is MS's solution: Ask your network administrator if the server is configured properly. The administrator may choose to share the server's IPC$ resource to correct this problem. <br />
<br />
As the administrator, what do I do to share the server IPC$? It does appear in Net Share and in Managed Shared folders. How do I know if it is enabled?
</div>


<div>
Hidden shares (those with a $ at the end) are not visible when viewing shares. However, &nbsp;to enable the IPC$ share you need to run this command on the server from a command prompt: <br />
<br />
net share IPC$<br />
<br />
If it is already shared, it will say so. If it is not, it will be now.
</div>


<div>
<div class="content wysiwyg-content">
Windows SBS 2003 Server lost a hard drive on the RAID, it was set as a single drive for RAID 0. We will replace with 2 drives RAID 1. &quot;File &amp;&nbsp;Print Sharing' was uninstaleld &amp;&nbsp;re-installed on server. Then shared folders were re-established. We CANNOT access the shared folders from the clients, we get &quot;The server is not configured for transactions&quot;. <br />
<br />
I was able to setup a shared folder on a client &amp;&nbsp;access it from the server. The client comptuers can now be seen from the server. <br />
<br />
It appears most all the Services are now working ok on the server. What do you suggest?<br />
<br />
johng@deanindustrial.com
</div>
</div>


Windows SBS 2003 Server lost a hard drive on the RAID, it was set as a single drive for RAID 0. We will replace with 2 drives RAID 1. "File & Print Sharing' was uninstaleld & re-installed on server. Then shared folders were re-established. We CANNOT access the shared folders from the clients, we get "The server is not configured for transactions". 

I was able to setup a shared folder on a client & access it from the server. The client comptuers can now be seen from the server. 

It appears most all the Services are now working ok on the server. What do you suggest?

johng@deanindustrial.com

Windows 2003 &quot;The server is not configured for transactions&quot;

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.

Microsoft Server OS

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

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.

Windows 2003 &quot;The server is not configured for transactions&quot;

Windows 2003 "The server is not configured for transactions"