Microsoft KB Archive/139676

= How to determine which user has the SNA Server configuration file locked in a Host integration Server 2000 environment or in an SNA 2.11 environment =

Article ID: 139676

Article Last Modified on 3/18/2005

-

APPLIES TO


 * Microsoft SNA Server 3.0
 * Microsoft Host Integration Server 2000 Standard Edition
 * Microsoft Host Integration Server 2000 Service Pack 1

-



This article was previously published under Q139676





SUMMARY
In a Microsoft Windows NT environment, a Microsoft Windows 2000 domain environment, or a Microsoft Host Integration Server environment, all SNA Servers in the domain must share a common configuration file. This is true when only one SNA Server in the domain is designated as the primary configuration server. The configuration file contains the following important access information:
 * The names of users and the names of groups
 * The LUs or LU pools that the users and the groups can use

When you start the SNA Server Manager program in Host Integration Server 2000 or in the SNA Admin program in Microsoft SNA 2.11 or later versions, the SNA Server Manager program and the SNA Admin program try to open the SNA Server configuration file in Read/Write mode. The SNA Server configuration file is named Com.cfg. If the Com.cfg file successfully opens, all other users who try to run the SNA Server Manager program or the SNA Admin program can only access the configuration file in Read-only mode.

Note Read access and Write access are required to update the configuration file. However, Read-only access lets the administrator start SNA Server services or stop SNA Server services. Also, the administrator can view the status of the SNA Server services.

By default, in SNA Server 2.11 and later versions, you may receive one of the following error messages. You may receive error message 1 if the SNA Server configuration file is already open for Read/Write access. Then, another SNA Administration program tries to open the configuration file.

Error message 1

Insufficient privilege or the file is locked. The file is locked by on computer. Click OK to open the configuration in read only mode?

Additionally, when you make a configuration change in SNA Manager, and you click OK to confirm the change, you may receive the following error message:

Error message 2

Unable to obtain a write lock on the config file.

In both cases, you can only open the SNA Server configuration file for Read access.

If the SNA Admin program or the SNA Manager program is not locally running on the primary configuration server, you can use Windows NT Server Manager to determine which user has the configuration file open in Write mode. To do this, follow these steps:
 * 1) Click Start, point to Programs, point to Administrative Tools, and then click Server Manager.
 * 2) In the Server Manager   dialog box, double-click the computer name that you want.
 * 3) In the Properties for   dialog box, click In Use.

In the Open Resources on  dialog box, the name of the user who has locked the SNA Server configuration file appears under the Opened by column. The SNA Server configuration file is named Com.c$$.

In a Windows 2000 environment, you can use the Computer Management MMC snap-in to determine which user has the configuration file open in Write mode. To do this, follow these steps:
 * 1) Log on to the computer that is acting as the primary SNA 2.11 server or the Host Integration Server 2000 server. Use an account that has administrative permissions.
 * 2) Click Start, point to Programs, point to Administrative Tools, and then click Computer Management.
 * 3) In the Computer Management MMC snap-in, expand Systems Tools, expand Shared Folders, and then click Open Files.

In the Details pane, the name of the user who has the Com.cfg file open appears under the Accessed By column.

Note By default, earlier version of the SNA Administrator program do not show the current user who has the SNA Server configuration file locked for Write access.



MORE INFORMATION
When you use the SNA Server Admin program in SNA Server 2.11 or later versions, the SNA Server Admin program can determine who has the configuration file open. You determine this by parsing the Com.lok file. The Com.lok file is created when the configuration file is opened for Read/Write access. The Com.lok file is deleted when the SNA Server Admin program that has locked the configuration file is shut down.

The following is a sample Com.lok file:

SNASERVER\Snauser SNAUSER

If the Com.lok file is deleted while the Com.cfg file is still locked by the SNA Server Admin program, any other SNA Server Admin program cannot verify the user who has the configuration file opened for Read/Write access.

Note You can use the SNA Server Admin program version 2.1 and the SNA Server Admin program version 2.11 to configure SNA Server administration rights. You can do this by using the SNA Admin Security options. You can grant users the following rights:
 * No access

Does not let a particular user or a particular group administer the SNA Server.
 * Read (manage only)

Lets the user open the configuration file in Read mode. Then, the user can view the server status. The user can start services or stop services.
 * Read/Write

Lets the user manage the server and change the SNA Server configuration file.
 * Full control

Lets the user view SNA Server status, start services and stop services, change SNA Server configuration information, and assign configuration permissions to other users.

You can also use the SNA Manager program in Host Integration Server to configure SNA Server permissions. In the Host Integration Server server properties dialog box, click the Security tab.

Important The SNA Server administrator must never try to set Windows NT file system file permissions on the primary SNA Server configuration file. The SNA Server Admin program and the SNA Manager program must be exclusively used to manage the SNA Administration rights of users.

Additional query words: prodsna

Keywords: kbhowto kbinfo kbtshoot KB139676

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.