Event 1006 Posted When Opening SNA Manager on Backup Server (319784)

MORE INFORMATION

You can test the configuration file for corruption, and you may be able to fix it by exporting the file to text, and then recompiling it by using the SNACFG utility. You can use the /v (for verbose) switch on the recompile to monitor progress or identify a failing location. For additional information about how to pipe out and recompile a configuration file, click the article number below to view the article in the Microsoft Knowledge Base: You can test whether you can reach, read and copy the configuration file on the Primary Server by connecting to the COMCFG share and then trying to copy the Com.cfg file. Test by connecting using the UNC name and by IP Address to determine whether name resolution is working, and then copy the file to the backup server. You can expect the connection to succeed without a logon prompt. If you can make a connection with the UNC name and an IP address, this indicates that a path to the file is not the issue. However, it does not rule out data security as a problem.

If an SNABase trace shows an inability to copy the file and the issues mentioned in the previous paragraph are not issues, then the problem may be data security. The presence of a 705 event in the application event log would indicate that data security is the issue.

IMPORTANT: To resolve a data security issue, you must understand the context in which a file access request is being made. To do so, verify the context under which the SNABase service has been installed. Troubleshooting methods vary a lot, depending on whether the account has been installed in a local account, in the local system account, or in a domain account.

Troubleshooting the local account and domain account are similar and straightforward, except that you must verify a domain account on a domain controller. Troubleshooting the local system account is more complex, but the concept is the same: "is this user (context) permitted access to the file?". Test the access to the file by using the same credentials as are used by the SNA Server and associated services.

When SNA Server or Host Integration Server is running in a local system context as a backup server, the concept and use of "null sessions" becomes important. For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base: It is important to understand that if a service is using the system account to access resources, the service logs on with a set of "null credentials". The null credentials are passed to the primary server with the request to copy the configuration file. Instead of explaining null credentials, "null sessions" and such, this article provides the following solution:

1. Install SNA Server or Host Integration Server 2000 into a domain account.
2. Let the install process create the user with all the appropriate rights.
3. If you use a local account, create the same user name and password combination as a local user on each SNA Server. This will enable "passthrough authentication".
4. If SNA Server is installed in a local system account, Microsoft recommends that you set the permissions on the configuration file to EVERYONE\Read\manage by means of the SNA Manager subdomain properties tool (instead of by setting permissions in the NTFS file system).
   
   Whenever possible, set the configuration file permissions using the SNA Manager. It has been seen that setting permissions through NTFS may cause a "view only" or "unable to open configuration file" issue, which may not be recoverable.