OS/2 Shareware BBS: 8 Other

home *** CD-ROM | disk | FTP | other *** search

/ OS/2 Shareware BBS: 8 Other / 08-Other.zip / nw2ls10.zip / ERRORMSG.MSG (.txt) < prev next >

Wrap

OS/2 Message File | 1994-10-18 | 58KB | 932 lines

MKMSGF -Y.:/:0'1C2 <5>&?z@ GLI&J [_]J^ q!q$q'q*q-q0q s+uEv errormsg.msg %1. CAUSE - See message text. ACTION - Informational message only. Unable to open a necessary migration file CAUSE - The migration program was unable to access the file %1 which is required for the migration to continue in function %2. ACTION - Call support and report the problem. A Netware 0x0001 error occurred. CAUSE - Unable to obtain double-byte character information. ACTION - A failure occurred when attempting to initialize the Netware requester calls. The failure is normally due to the Netware Requester for OS/2 not being started. Start the requester and restart the migration. A Netware 0x8800 error occurred. CAUSE - An attempt to attach to a server for which a connection already existed. ACTION - This is an informational message and can be ignored. A Netware 0x8801 error occurred. CAUSE - An attempt was made to request data from the Netware server with an invalid connection handle in function %1. ACTION - Contact support and report the problem. A Netware 0x8806 error occurred. CAUSE - An non-specific NW error occurred in function %1. ACTION - Contact support and report the problem. A Netware 0x8807 error occurred. CAUSE - An attempt was made to contact a NW server with an invalid NW requester connection slot in function %1. ACTION - Contact support and report the problem. A Netware 0x8808 error occurred. CAUSE - An attempt was made to connect to a server which did not have a connection slot available. ACTION - Disconnect users from the server and restart the migration. If the problem persists, repeat until the number of users on the server is below the number licensed to access that server. A Netware 0x880a error occurred. CAUSE - An attempt was made to find a route to a server where no route exists. ACTION - Verify that the requester workstation has ROUTE.SYS loaded in the CONFIG.SYS and any routers or bridges are configured to allow IPX traffic. Also, verify that the workstation is communicating on the network. A Netware 0x880e error occurred. CAUSE - A buffer overflow condition exists from a receive buffer not being large enough in function %1. ACTION - Call support and report the problem. A Netware 0x880f error occurred. CAUSE - A request for a connection handle to a server was made where the server was not currently connected. ACTION - Rerun the migration utility, verifying the Netware server name that is being migrated to LAN Server. If the problem still exists, call support and report the problem. A Netware 0x8811 error occurred. CAUSE - An illegal function call was issued in function %1. ACTION - Call support and report the problem. A Netware 0x8830 error occurred. CAUSE - An internal server request was attempted across different server connections in function %1. ACTION - Call support and report the problem. A Netware 0x8831 error occurred. CAUSE - A request for information about the primary connection caused an error because the primary connection has not been established. ACTION - Verify that you are logged into the Netware server and not just attaching to it. If the problem persists, call support and report the problem. A Netware 0x8833 error occurred. CAUSE - An internal buffer had an invalid length in function %1. ACTION - Call support and report the problem. A Netware 0x8834 error occurred. CAUSE - An attempt was made to login to the Netware server without specifying a user name with which to login. ACTION - Specify a user name so that login can proceed. A Netware 0x8836 error occurred. CAUSE - An invalid parameter was used in a function call in function %1. ACTION - Call support and report the problem. A Netware 0x883c error occurred. CAUSE - A request was made for a resource that is not defined to this Netware server. The resource name was %1. ACTION - Record the resource name. This resource is not defined to the Netware server which is part of this migration. Verify that the resource is not part of the server and that the bindery files on this Netware server are not corrupted. A Netware 0x883f error occurred. CAUSE - An attempt was made to allocate a connection handle on the local requester when the local connection table was full. ACTION - Disconnect some of your sessions with Netware servers other than the one being migrated. A Netware 0x8841 error occurred. CAUSE - A function was attempted on a connection with an invalid transport selected. ACTION - Check to be sure that all protocols defined on the OS/2 system bound properly. The error logging for OS/2 system binding is LANTRAN.LOG located in the \IBMCOM subdirectory. Any errors that are reported will be documented in the LAN Error Messages document available with LAN Server. A Netware 0x8847 error occurred. CAUSE - No Netware server was found on the network. ACTION - 1. Verify that ROUTE.SYS is loaded in the CONFIG.SYS Netware Requester section. 2. Verify that the Netware server is loaded and operational. 3. Verify that the Netware Requester software was successfully loaded. A Netware 0x884f error occurred. CAUSE - An attempt was made to re-use a Netware connection entry that was still in use. ACTION - Call support and report the problem. A Netware 0x8851 error occurred. CAUSE - An attempt was made to enter a name into the name table after the name table was full. ACTION - Terminate applications that use the name table to allow the migration to proceed. The migration must be restarted after room has been made in the name table. A Netware 0x8855 error occurred. CAUSE - The preferred directory server has not been established, but another directory server was returned. ACTION - Setup a preferred directory server and restart the migration. If the migration is continued without restarting, the accuracy of the data cannot be guaranteed. A Netware 0x8857 error occurred. CAUSE - The network type specified in function %1 does not match the server version. ACTION - The network type (bindery or directory services) does not match the server version that will be used during this migration. A Netware 0x8858 error occurred. CAUSE - An error occurred while opening the file %1. The error can be caused by access denied, invalid path, corrupt file, etc. ACTION - Fix the problem with the stated file and restart the migration. A Netware 0x8859 error occurred. CAUSE - No preferred server has been specified. ACTION - Setup a preferred directory server and restart the migration. If the migration is continued without restarting the migration, the accuracy of the data cannot be guaranteed. A Netware 0x885a error occurred. CAUSE - An error occurred while attempting to open a socket. ACTION - 1. Verify that the Netware Requester has been installed correctly and is operating. 2. Verify that all protocols have been bound to the correct adapters by checking the LANTRAN.LOG file in the \IBMCOM subdirectory. Any error messages should be referred to the LAN Error Messages manual that accompanies LAN Server. A Netware 0x88ff error occurred. CAUSE - The Netware requester has not been properly installed on this workstation. ACTION - Correct any problems with the Netware requester installation or operation and restart the migration. A Netware 0x8901 error occurred. CAUSE - Sufficient space to process the request is not available on the server. ACTION - Refer to the Netware server documentation regarding necessary procedures to solve the problem. If the problem persists, call support and report the problem. A Netware 0x8977 error occurred. CAUSE - A buffer was too small to hold the data that the server had available to transmit. ACTION - This is an informational message. The migration utility will automatically retry and correct this problem. A Netware 0x8978 error occurred. CAUSE - The service requested is not available on the selected volume in function %1. ACTION - Call support and report the problem. A Netware 0x8979 error occurred. CAUSE - No items were found in the search. ACTION - This is an informational message stating that a search for data returned no items meeting the search criteria. A Netware 0x897a error occurred. CAUSE - An attempt was made to establish a temporary server connection where one already existed. ACTION - Call support and report the problem. A Netware 0x897b error occurred. CAUSE - An attempt was made to login to a connection which had already been logged in. ACTION - Log out of the connection and then log back in and restart the migration. A Netware 0x897c error occurred. CAUSE - An attempt was made to use a connection that had not been authenticated. ACTION - You were attached to a Netware server but not logged into it when a request which required login access occurred. Logout, login and restart the migration. A Netware 0x897d error occurred. CAUSE - You are not currently logged into the Netware server. ACTION - This is an informational message. The migration utility provides for login to the Netware server. A Netware 0x8980 error occurred. CAUSE - An attempt was made to open or create the file %1 that is already open. ACTION - Record the file name and call support to report the problem. A Netware 0x8981 error occurred. CAUSE - No more file handles are available at the Netware server because the network file handle table is full. ACTION - Too many files are open at the server. Close some files to free up entries in the table and restart the migration. A Netware 0x8983 error occurred. CAUSE - A hard disk input/output error occurred on a Netware volume. A bad sector was encountered and could be fatal. ACTION - Fix the disk on the Netware server and restart the migration. A Netware 0x8988 error occurred. CAUSE - An attempt was made to close or perform I/O on a file with an invalid file handle. ACTION - This problem normally occurs when an attempt is made to access a file that has been closed. A Netware 0x8995 error occurred. CAUSE - Access to the file %1 was denied because the file was detached. ACTION - Reattach the file and restart the migration. If the problem persists, contact your Novell support provider. A Netware 0x8996 error occurred. CAUSE - An attempt was made to use a file server which does not have enough free dynamic memory to process the request. ACTION - Stop processes on the server to free enough memory and restart the migration. If the problem persists, add more memory to the file server. A Netware 0x8998 error occurred. CAUSE - The network operating system has tried to access a volume but cannot find the volume in the system definition files. The volume name is %1. ACTION - The volume either no longer exists or has been detached. Reattach the volume and restart the migration. A Netware 0x8999 error occurred. CAUSE - The entry table for the directory %1 is full. ACTION - Remove some files from the directory and restart the migration. A Netware 0x899b error occurred. CAUSE - An attempt was made to use an invalid directory handle. This error occurs when the server has been brought down and back up without rebooting the workstation. ACTION - Reboot the workstation and restart the migration. A Netware 0x899c error occurred. CAUSE - 1. A directory path was used that does not exist on the server. The directory is %1. 2. No more trustees were found during a recursive file or directory trustee search. ACTION - 1. Log the directory path and move it manually after the migration has finished. 2. This message is an informational message only. The message states that all trustees searched for were found and that the migration is continuing. A Netware 0x899d error occurred. CAUSE - The directory handle table for this user is full. Each user may have up to 255 directory handles. ACTION - End applications running on the workstation which access files on the Netware server. Restart the migration and select to re-scan the directory structure. A Netware 0x899e error occurred. CAUSE - An attempt was made to create a file that contained invalid characters in the filename. ACTION - Contact support and report the problem. A Netware 0x89a1 error occurred. CAUSE - A non-recoverable I/O error has occurred in the directory area. This error has occurred in both copies of the directory and is fatal. ACTION - Correct the problem on the fixed disk if possible. After the disk problem is fixed, restart the migration. If the problem reoccurs, rebuild the server from tape and restart the migration, electing to re-scan the directory structure. A Netware 0x89a2 error occurred. CAUSE - An attempt was made to read a file where data is physically locked. ACTION - The migration program should not be ran from a diskette. If the migration program is being ran from a fixed disk, call support and report the problem. A Netware 0x89a6 error occurred. CAUSE - The Netware server returned an already in use error in function %1. ACTION - Contact support and report the problem. A Netware 0x89a8 error occurred. CAUSE - The Netware server returned an access denied error when attempting to access a server resource. ACTION - You must be a Netware supervisor equivalent to run this migration utility. If the error persists, contact support and report the problem. A Netware 0x89c1 error occurred. CAUSE - An attempt was made to log in by a bindery object without an accounting balance, and accounting was enabled. ACTION - Log in to the Netware server with a bindery object with an account balance, or disable accounting. A Netware 0x89c2 error occurred. CAUSE - An attempt was made to log in to an account with no credit available. ACTION - Log in to the Netware server with an account with credit or disable accounting. A Netware 0x89c4 error occurred. CAUSE - Accounting is disabled on the server. ACTION - Message is informational in nature and will not impact the migration. A Netware 0x89c5 error occurred. CAUSE - A log in attempt was made after the system had locked the account because of intruder detection. ACTION - Log in with a different account or unlock the locked account and restart the migration. A Netware 0x89d9 error occurred. CAUSE - 1. The number of logins the server can accept has been exceeded. 2. Login was denied because the account has limits on the number of concurrent connections and that number has been reached. ACTION - 1. Log out users until the server can accept new logins. 2. Disconnect some of the connections that the account is using and restart the migration. A Netware 0x89da error occurred. CAUSE - An attempt to login outside authorized login hours for this account was made. ACTION - Change the authorized login hours or login with an account which does not have these restrictions and restart the migration. A Netware 0x89db error occurred. CAUSE - An attempt to login from an unauthorized station using an account with limits to a specific network and/or station was made. ACTION - Log in from an authorized workstation or network, disable the restriction for this account, or log in with an account without this restriction and restart the migration. A Netware 0x89dc error occurred. CAUSE - An attempt was made to log in using an account which as expired or has been disabled by a supervisor. ACTION - Re-enable the account or use an account which is not expired or disabled. A Netware 0x89de error occurred. CAUSE - An attempt was made to log in using an account using a password which has expired and all grace logins have also expired. ACTION - Change the password on the account or use an account without an expired password and restart the migration. A Netware 0x89df error occurred. CAUSE - An attempt was made to log in using an account using a password which has expired but log in was allowed because the account had a grace login. ACTION - No action is required by the user. A Netware 0x89e7 error occurred. CAUSE - The Netware server has reported an error condition of NO_MORE_USERS in function %1. ACTION - Contact support and report the problem. A Netware 0x89e8 error occurred. CAUSE - An attempt to use an item not associated with this property group or an item which has been deleted from this group. The item is %1. ACTION - Contact support and report the problem. A Netware 0x89ea error occurred. CAUSE - An attempt to access an object of a group property was made where the object was not a member of the group property. The object name is %1. ACTION - Record the object name and move the object manually after the migration has finished. A Netware 0x89ec error occurred. CAUSE - An attempt was made to use a server segment which did not exist or is damaged. ACTION - Repair the bindery and restart the migration. A Netware 0x89ef error occurred. CAUSE - A request was made with an object or property name that contained illegal characters. The object or property name is %1. ACTION - Record the name and move the object manually after the migration has finished. A Netware 0x89f0 error occurred. CAUSE - An invalid wildcard character was used in an internal function call that occurred in function %1. ACTION - Contact support and report the problem. A Netware 0x89f2 error occurred. CAUSE - A request was made to access an object's information or scan the object's properties by a station without the necessary security to access the information. ACTION - Verify that you are logged on with a supervisor equivalent id. A Netware 0x89f9 error occurred. CAUSE - A request was made to access a property's information without the necessary security to access the information. ACTION - Verify that you are logged on with a supervisor equivalent id. A Netware 0x89fa error occurred. CAUSE - The server does not have an available slot to handle the request. ACTION - Disconnect users from the server so that the server will have available connection slots to handle the migration utilities connection slot needs. A Netware 0x89fb error occurred. CAUSE - An invalid parameter was used during a set drive path call in function %1. ACTION - Contact support and report the problem. A Netware 0x89fc error occurred. CAUSE - 1. An attempt was made to attach to a server using an invalid server name. 2. An attempt was made to access an object which does not exist, or the calling station does not have the proper security to access the object. The object name is %1. ACTION - 1. Verify the server name and restart the migration. 2. Verify that the object exists and that you are logged in as a supervisor equivalent. If the object exists, it will be need to be migrated manually after the migration utility has finished. A Netware 0x89fe error occurred. CAUSE - 1. The bindery is locked. This condition is normally caused by a supervisor doing maintenance at the same time that the migration utility is requesting data from the binderies. 2. The server socket table is full. 3. A directory is locked. 4. A supervisor has disabled login. ACTION - 1. Stop all maintenance while the migration utility is running. 2. Disconnect users from the server to free up sockets and restart the migration utility. 3. Stop all maintenance while the migration utility is running. 4. Enable login at the Netware server with the command ENABLE LOGIN and restart the migration. A Netware 0x89ff error occurred. CAUSE - 1. You used an incorrect password when attempting to login to the Netware server. 2. No response was received from the Netware server in function %1. 3. A miscellaneous Netware server error occurred in function %1. 4. A hardware failure occurred on the Netware server. ACTION - 1. Login with a correct userid and password combination. 2. Verify that the server is up and processing network requests. Verify that the requester is communicating on the network. If the problem persists, contact support and report the problem. 3. Record the function and error number. Contact the support center and report the problem. 4. Fix the failing component and restart the migration. An unexpected NW error %2 occurred in the function %1. CAUSE - Unknown. ACTION - Call support and report the problem. A command completed successfully but returned no data. CAUSE - No data was available from the internal API. ACTION - No action is required. Information message in nature. A SYS0002 error has occurred. CAUSE - The file %1 does not exist. ACTION - Verify that the file name is correct, the path is correct, and/or the directory appears in the PATH entry in CONFIG.SYS. A SYS0004 error has occurred. CAUSE - The system cannot open the file %1. ACTION - The number of files specified in the CONFIG.SYS statement FILES= is not sufficient enough to handle the number of open files. Raise the value, reboot the system and restart the migration. A SYS0005 error has occurred. CAUSE - An administrator id is required to continue. You are not currently logged on with an administrator id on the LAN Server. ACTION - Logon with an administrator id. A SYS0008 error has occurred. CAUSE - An out of storage condition exists. ACTION - The drive containing the migration files is full. Erase unnecessary files from the drive or close programs to free storage. If swap file is also on this drive, move either the swap file or the migration program to another drive. A SYS0013 error has occurred. CAUSE - Invalid data was passed to an internal data structure in function %1. ACTION - Call support and report the problem. A SYS0015 error has occurred. CAUSE - An invalid drive letter was detected on the LAN Server machine. The drive letter was %1. ACTION - If the drive letter is not attached to the server or is invalid, the error will not affect the migration. If the drive is valid, verify that the operating system recognizes the drive and that the drive has been formatted properly. A SYS0050 error has occurred. CAUSE - The issued network request is not supported by the network. An operation was attempted from this computer which cannot be performed or that is not supported on the specified remote server. ACTION - Verify that you are using at least LAN Requester 3.0, that the server is up and running, and that the server name specified is correct. A SYS0053 error has occurred. CAUSE - The server specified does not exist or has not been started. ACTION - 1. Verify that the path and servername are correct. 2. Verify that the server has been started. 3. Check your server and requester configuration to verify that LAN communications are taking place. A SYS0065 error has occurred. CAUSE - Network access is denied. The requester has not been started or is paused. ACTION - Resume or restart the requester. Verify that the adapter card is functioning properly and is inserted into the network. A SYS0086 error has occurred. CAUSE - The specified password is not correct for the account or resource being accessed. ACTION - Verify that the password being used is correct for the userid logged into the system and that the account has administrative authority. A SYS0087 error has occurred. CAUSE - An invalid parameter was passed to an internal LAN Server API call in function %1. ACTION - Call support and report the problem. A NET124 error has occurred. CAUSE - The level of an internal API is incorrect in function %1. ACTION - Call support and report the problem. A NET161 error has occurred. CAUSE - The path name specified when adding an alias was incorrect or did not exist. The alias name was %1 and the specified path name %2. ACTION - The alias was not added. The alias and all associated data must be entered manually after the migration has finished. A NET234 error has occurred. CAUSE - An internal buffer was too small to hold the data returned from the API call in function %1. ACTION - Call support and report the problem. A NET255 error has occurred. CAUSE - Command completed successfully. The return code is a bug in the LS 3.0 WR07040 level of code. ACTION - Call the support center and request APAR #IC06738 and apply to all machines. A NET2102 error has occurred. CAUSE - The redirector NETWKSTA.200 has not been started. ACTION - The adapter did not bind correctly. Please check the LANTRAN.LOG file in the \IBMCOM directory where LAPS was installed on this workstation to determine the LAPS error message. Please consult the LAN Error Messages manual for problem determination of the reported problem. A NET2104 error has occurred. CAUSE - An internal LAN Server software error occurred. ACTION - Stop the workstation with the command NET STOP REQ /Y. Restart the workstation with the command NET START REQ. If the problem persists, report the problem to the IBM Support Center for further problem determination. A NET2106 error has occurred. CAUSE - The operation is not supported on requesters. The function reporting the error is %1. ACTION - The machine name you specified as a LAN Server either does not have the server code running or is not a server. Please install the server code on that machine or if the server code is already installed, issue the command NET START SRV to start the server code. A NET2114 error has occurred. CAUSE - The server service has not been started. ACTION - Start the server with the command NET START SRV. If the machine is not a server, then you are attempting a command which requires a server to continue. A NET2123 error has occurred. CAUSE - An internal buffer was too small to hold the fixed-length data information from an API call in function %1. ACTION - Call support and report the problem. A NET2127 error has occurred. CAUSE - A remote API error occurred. ACTION - Ensure that the server is configured with enough resources to continue. Specifically, the NUMBIGBUFS entry in the IBMLAN.INI on the server may need to be increased. After changing the value, the server must be stopped with the command NET STOP REQ /Y and restarted with the command NET START SRV to continue. A NET2134 error has occurred. CAUSE - An internal error occurred when accessing the NETWKSTA.200 driver. ACTION - Stop the requester service on this workstation with the NET STOP REQ /Y command and restart it with the NET START REQ command. If the problem persists, call support and report the problem. A NET2136 error has occurred. CAUSE - A general network error has occurred. ACTION - This is a network hardware problem. Check cables, hubs, bridges, and adapters for problems. If the problem persists, run diagnostics on the network adapter in machine. If adapter checks out, use a network diagnostic tool to determine the cause. A NET2138 error has occurred. CAUSE - The requester service has not been started on this workstation. ACTION - Issue a NET START REQ command from a OS/2 command-line to start the requester. A NET2139 error has occurred. CAUSE - The requested data was unavailable from the server because enough MAILSLOTS were not specified on the requester. ACTION - Change the MAILSLOTS entry in the IBMLAN.INI file to YES and stop and restart the requester with the commands NET STOP REQ /Y and NET START REQ. This problem could also occur if the requester service has not been started or the server is not active. A NET2140 error has occurred. CAUSE - An internal LAN Requester software error has occurred. ACTION - Stop the workstation by going to an OS/2 command prompt and issuing NET STOP REQ. Restart the workstation and the migration. If the problem persists, report the problem and the method by which it can be reproduced to the support center. A NET2141 error has occurred. CAUSE - The server is not configured for transactions. ACTION - 1. Verify that the server is not paused or stopped. 2. Issue a NET SHARE IPC$ command and retry the operation. 3. Issue a NET STOP REQ /Y followed by a NET START SRV to bring the server back to an operational state. A NET2142 error has occurred. CAUSE - The requested API is not supported on the remote server. ACTION - The destination server is not running at least LAN Server 3.0. Previous versions of LAN Server are not supported by this migration utility. A NET2202 error has occurred. CAUSE - A group ID or user ID was invalid. The ID was %1. A possible cause of this error is an ID which contained restricted characters. ACTION - The ID was skipped due to a problem encountered when using it. The ID and all its information must be entered manually at the server after the migration finishes. A NET2203 error has occurred. CAUSE - The specified password is invalid. ACTION - The length of the password was shorter than the required value set at the server. The password contained characters which are not permitted by LAN Server. A NET2219 error has occurred. CAUSE - The file NET.ACC cannot be found at the server. The file should be located in the \IBMLAN\ACCOUNTS directory at the LAN Server machine. ACTION - Verify that the NET.ACC is in the correct subdirectory on the LAN Server. If the file does not exist, copy a backup verion of the file (NETACC.BKP) to NET.ACC and restart the server. If a backup version does not exist, copy the file from the installation diskettes or reinstall the LAN Server server module through the LAN Server installation diskettes. A NET2220 error has occurred. CAUSE - An unknown group name was specified. An attempt was made to access a group at a location other than the domain controller. The group id is %1. ACTION - Verify that the domain controller is up and running. Verify that the group name is spelled correctly, and that the group is in UPM on the domain controller. A NET2221 error has occurred. CAUSE - An unknown user name was specified. An attempt was made to access a user at a location other than the domain controller. The user id is %1. ACTION - Verify that the domain controller is up and running. Verify that the user name is spelled correctly, and that the user is in UPM on the domain controller. A NET2222 error has occurred. CAUSE - An attempt to access the permissions for a resource that is not in the user accounts database was made. An access control for the resource %1 does not exist. ACTION - An access control profile for the resource will be created by the utility. This message is informational in nature. A NET2223 error has occurred. CAUSE - The group %1 already exists. ACTION - The group was %2. If the group was renamed, it was renamed %3. This will flow through the rest of the migration. A NET2224 error has occurred. CAUSE - The user %1 already exists. ACTION - The user was %2. If the user was renamed, it was renamed %3. This will flow through the rest of the migration. A NET2225 error has occurred. CAUSE - An access control already exists for the resource %1. ACTION - The utility will automatically merge the existing access control into the new one. This message is informational in nature. A NET2226 error has occurred. CAUSE - Because the user accounts database is replicated from the domain controller, updates are not allowed locally. ACTION - The specified server is not the domain controller. The domain controller is not available or a backup domain controller intercepted the request for DCDB update. Verify that the domain controller is up and that backup domain controllers are not processing requests during the migration. Also, verify that the role of the domain controller is set to PRIMARY. A NET2227 error has occurred. CAUSE - The user accounts database has not been started. The server is being started and has not started the UPM database. Check the LAN Server error log with the NET ERROR command to determine why the database was not started. A NET2228 error has occurred. CAUSE - The UPM database is full. No new users, groups, or access controls can be added. ACTION - Delete users, groups, or access permissions from the UPM database prior to adding any new users, groups or access permissions. This is an architectural limit of LAN Server, which the migration utility cannot change. A NET2229 error has occurred. CAUSE - A disk I/O failure occurred when attempting to access the NET.ACC file. ACTION - 1. Run CHKDSK to determine if the problem is related to the drive and can be fixed. You may have to boot from the OS/2 installation diskette and go to diskette 2 to run CHKDSK /F:2 if the drive is HPFS or 386HPFS. 2. Restore the NET.ACC from a backup copy if CHKDSK does not fix the problem. 3. Restore the NET.ACC from the LAN Server installation diskettes if a backup is not available. 4. If the drive is faulty, replace it. A NET2230 error has occurred. CAUSE - The limit for the number of access control profiles allowed has been exceeded. The group or user %1 with rights %2 was not added for resource %3. ACTION - Record the ID, rights, and resource. The access control profile has not been added for the resource. If the ID is a user, combine the user into a group and assign access controls at the group level rather than for each user. A NET2231 error has occurred. CAUSE - An attempt was made to delete a user with a session on the server. The user name was %1. The migration utility attempted to replace this user. ACTION - Delete the user manually. All information for this user will have to be defined manually after the migration has finished. A NET2233 error has occurred. CAUSE - The user accounts database has reached its size limit. No further items can be added to it. ACTION - Delete users, groups, or access permissions from the UPM database prior to adding any new users, groups or access permissions. This is an architectural limit of LAN Server, which the migration utility cannot change. A NET2234 error has occurred. CAUSE - An operation was tried on one of the special groups USERS, ADMINS, or GUESTS which is not allowed. The function reporting the problem is %1 and and the group was %2. ACTION - Record the function group and function where the problem occurred. The migration utility does not permit access to the special groups. If a Netware group is named the same as one of the special groups rename the Netware group and add it manually to the LAN Server after the migration has finished. A NET2236 error has occurred. CAUSE - The user %1 already is a member of the group %2. ACTION - This is an informational message only. When an attempt was made to add the user to the group, it was found that the user was already a member of the group. No further action is required. A NET2237 error has occurred. CAUSE - The user %1 is not a member of the group %2. ACTION - Record the information. Call support and report the problem. A NET2239 error has occurred. CAUSE - An attempt was made to perform an operation on an expired account. ACTION - Record the information. Call support and report the problem. A NET2243 error has occurred. CAUSE - The password for user %1 cannot change. ACTION - Record the information. Call support and report the problem. A NET2244 error has occurred. CAUSE - An attempt was made to use a password which has expired and is still contained in the password history for this account. The account is %1. ACTION - The password was not accepted for this user. The password will have to be changed after the migration has finished. A NET2245 error has occurred. CAUSE - The specified password is shorter than required. ACTION - Use a longer password or issue the NET ACCOUNTS /MINPWLEN:x command, where x is the minimum password length allowed to change the minimum password length. A NET2246 error has occurred. CAUSE - An attempt was made to change a password prior to the original password reaching the minimum password age required. ACTION - Use the command NET ACCOUNTS /MINPWAGE:x to set the minimum number of days required before the password can be changed. A NET2247 error has occurred. CAUSE - The NET.ACC file is damaged. ACTION - Copy a backup version of the file NETACC.BKP to NET.ACC and restart the server. If a backup version does not exist, copy the file from the LAN Server installation diskettes or reinstall the LAN Server server module through the LAN Server installation diskettes. A NET2277 error has occurred. CAUSE - The maximum number of message names, as setup as the last parameter on the NET1 line in the IBMLAN.INI file has been exceeded. ACTION - Increase the value of the message names parameter on the NET1 line in the IBMLAN.INI file. It may also be necessary to increase the NAMES parameter in the [netbeui] section of the PROTOCOL.INI file. If the network hardware limit is reached, no additional action is possible. A NET2297 error has occurred. CAUSE - A duplicate name exists on the network. ACTION - Change the COMPUTERNAME parameter in the IBMLAN.INI to a different name and restart the system. A NET2319 error has occurred. CAUSE - A LAN Server software error occurred. ACTION - Stop the workstation and restart it. If the problem persists, report the problem and the method by which it can be reproduced to the support center. A NET2320 error has occurred. CAUSE - The workstation is not active on the domain specified. ACTION - This workstation must be logged onto the domain to which the server you are migrating belongs. To correct this problem, stop the migration, logoff, logon to the correct domain and restart the migration. A NET2351 error has occurred. CAUSE - 1. The specified computer name is not valid. 2. You may not be logged onto the LAN Server domain to which you are migrating. 3. The domain name was entered in place of the server name for this migration group. ACTION - 1. A duplicate machine ID exists on the network. Change the name of one of the workstations by changing the name after the COMPUTERNAME parameter in the IBMLAN.INI file, then stop and restart the requester. 2. A duplicate NetBIOS name exists in the network. Determine where the duplicate machine is and shut it down during this migration. 3. Log off and log on to the domain on which the server you are migrating to belongs. 4. Restart the migration, create a new migration group and specify the server name of the LAN Server rather than the domain name to which it belongs. 5. The additional server's name may not have been defined to the domain controller. Define the machine name of the additional server and restart this migration. A NET2451 error has occurred. CAUSE - The requested operation cannot be performed while the NETLOGON service is running. The function reporting the condition is %1. ACTION - Record the information. Call the support center and report the problem. A NET2452 error has occurred. CAUSE - An attempt was made to delete the last account with administrator privilege. An attempt to replace the account %1 is not possible. ACTION - The specified account will need to be replaced manually when the migration has finished. A NET2453 error has occurred. CAUSE - The domain controller could not be contacted. ACTION - 1. Verify any bridges or routers in the network path are up and running. 2. Verify that the domain controller is up and running. 3. Verify that the migration machine is logged into the correct domain controller. 4. Verify that the NETLOGON service is started on the domain controller. 5. Call support and report the problem. A NET2456 error has occurred. CAUSE - No more information could be added to the user accounts database because the server fixed disk is full. ACTION - Remove unnecessary and outdated files from the server disk and restart the migration. A NET2782 error has occurred. CAUSE - The alias %1 already exists. ACTION - The alias was %2. If the alias was renamed, it was renamed %3. This will flow through the rest of the migration. A NET2786 error has occurred. CAUSE - The domain control database is unreadable or cannot be accessed at this time. This problem can be caused by more than one person updating the DCDB at one time. ACTION - This migration requires that it be the only user updating the DCDB at a given time. If the DCDB is damaged, restore it from a backup copy and restart the migration. If a backup is unavailable, reinstall the LAN Server from the LAN Server installation diskettes. A NET2795 error has occurred. CAUSE - An attempt was made to access the domain control files on a server which was not the primary domain controller. ACTION - Ensure that a backup domain controller is not reporting as the domain controller. If the problem persists, record the information in the SETUP.DAT file and report the problem to the support center. An unexpected LS error %2 occurred in the function %1. CAUSE - Unknown ACTION - Call support and report the problem.