Source: eDirectory or NDS operating system
Explanation: An attempt was made to open or create a file that is already open.
Possible Cause: A container, user, or profile login script can become locked open by a user when the user is executing the login script and the script pauses for user input (for example, using the pause command in the script). If the user does not enter any input when prompted, the login script cannot be edited.
The error code is returned in context of the following messages:
"NWDS-4.0-624: The login script file could not be opened. Return Code: 1729:-128."
"NETADMIN-4.55-110: The utility can't open the script file. Error Code: FF80."
Possible Cause: A container, user, or profile login script can also become locked if the login script file was in use by a user who had not completed the login process. The login script file is still locked to that user which will prevent any writes coming from anyone else. Until the login script file is closed by the user (login is completed), no writes to the file will be allowed.
Action: Until a permanent solution is found, you can use the following steps as a workaround:
After getting the error message in NetWare Administrator, open the login script again and make any changes to it.
Before clicking OK, make a copy of the login script to the clipboard buffer by highlighting the text and pressing Ctrl+C.
Additionally, but only for backup purposes, you can save the script to a new file using an editor like Notepad. Paste the text into the editor by pressing Ctrl+V and save the file.
Delete the entire login script in NetWare Administrator and click OK. The changes will be saved.
Now, open the empty login script in NetWare Administrator and paste the text back into the login script by pressing Ctrl+V.
The information should be saved and the error will not occur.
Action: Because login scripts are stored as part of eDirectory or NDS, the login scripts are replicated on various servers, depending on how the tree has been partitioned and which servers hold replicas of the partition involved. Therefore, it might be possible to edit and save changes to a login script by accessing the data from a different server using the following steps:
Determine which server is returning the error.
Find another server that has a replica of the same partition, log in to that server, and run NetWare Administrator from it.
Edit the login script and save the changes.
NOTE: Tests run by Novell Technical Support have shown that if the login script is opened from a server other than the server where it is locked, the login script should be able to be edited.
Possible Cause: This problem might be caused by calling a TSR, a menu, or Windows* from a login script.
Action: To close the login script, do the following:
Identify the server you are logged in to and which server you are reading the eDirectory or NDS objects from.
If you are in a single server environment, you can locate the user that is holding the login script file open by loading monitor, and looking at each connection to find a user that has a file open in the sys:_netware directory.
Instruct the user to log off, or clear the user's connection.
The login script should now be closed and can be reopened for editing.
Possible Cause: A user inserted a # command that did not terminate in a login script. The login script file will remain open because login is still running. When running a menu type program, inserting a command that will not terminate will cause the file to remain locked open.
Action: In the login script, use an @ command so login can complete and close the script file.