D.27 162 0xa2 IO LOCKED

Source: NCP Engine

Explanation: IO is locked. An attempt was made to write to a file where data is physically locked. The file is in use and already in a locked state.

(This error code might be the result of Linux to NetWare Error Code conversion. The actual error could be in a system call.)

Possible Cause: The file is not currently locked by a user that has the file open.

Action: You can ask the other user to close the file, or retry the action later.

Possible Cause: The file is not currently locked by another process that holds the file open for Writes, such as a database.

Action: You might be able to stop the other process to close the file, or retry the action later.

Possible Cause: The file is not currently locked by another process that has terminated.

Action: If no valid user or process has the file open, delete the connection to unlock the file.