Backup server returns "Unable to Open Configuration" error message (318259)

IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

CAUSE

The SNABase service that is on the backup server cannot complete copying the configuration file (Com.cfg) from the primary server to the SNABase service configuration folder.

This behavior can occur for multiple reasons, including the following:

The backup server cannot open a named pipe connection to the primary server.
The backup server cannot complete the file copy locally because of incorrect Write or Read permissions.

RESOLUTION

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

Determine which LanManWorkstation provider that both servers are using. You can find this information in the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation

If multiple providers are installed on the servers, a registry subkey indicates the order of the providers. If the ProviderOrder subkey lists NetwareWorkstation;LanmanWorkstation, reverse the order of the providers, and place LanManWorkstation first.

The existence of a Netware workstation value indicates that the Novell Client32 has been installed. This problem occurs in Novell Client32 version 4.60; however, this problem may not occur on more recent versions.

MORE INFORMATION

For additional information about providers, click the article number below to view the article in the Microsoft Knowledge Base:

171386 Connectivity Delay with Multiple Redirectors Installed

Troubleshooting

To trace the initial startup of the SNABase service, follow these steps:

In SNA Manager, click Trace or Trace Initiator on the Tools menu to open the SNATrace program.
Click SNABase from the list of trace items, and then click Properties.
Select all the trace items that appear in all windows, click Apply, and then click Yes to exit with tracing on.
Restart the SNABase service.
After you receive the error message, open the SNA trace program, and then click the Clear all tracing check box to stop tracing.

To isolate the problem, follow these steps:

To search for this error in the SNABase Internal and Message trace files (Napint1.atf and Napmsg1.atf, respectively), search for the msgnum string, which indicates the posted event (Event 671).
Search earlier in the trace to find the actual error, which in this case is:
Path Not Found
To test whether the issue is a copying problem, follow these steps:
1. Try to manually copy the file to the Universal Naming Convention (UNC) name.
2. Create a mapping to the share.
3. Retest. If this is the issue, the system does not complete copying the file to a UNC path.

The system successfully copies the file to a mapped drive because Microsoft Windows NT and Microsoft Windows 2000 handle the two operations differently. The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.