Novell Home

My Favorites

Close

Please to see your favorites.

Automatic Workstation Import/Removal Errors and Suggested Remedies

(Last modified: 29Nov2005)

This document (10056909) is provided subject to the disclaimer at the end of this document.

goal

Automatic Workstation Import/Removal Errors and Suggested Remedies

fact

Novell ZENworks for Desktops 3.0

Novell ZENworks for Desktops 3.2 - ZfD 3.2

Novell ZENworks Automatic Workstation Import

Errors are located in WSREG32.LOG on the local workstation.

symptom

Error "An error occurred while attempting to apply the naming rules."

cause

If the Naming rules in the Import Policy of the server package are set to use the MAC address as the first part of the workstation name, the problem may be caused because NETBIOS support or emulation is not installed as a client service.   Windows uses NETBIOS to get the NIC address.

fix

Add "NWLink NETBIOS" as a service.  Otherwise consider another workstation naming convention.

symptom

Error: "An unknown error occurred in the workstation creation service."

Error: "Could not parse the cookie."

Error: "Error: The service could not determine its platform."

fix

Restart the import or removal service.

symptom

Error: "The workstation import server is not in the same tree as the user."

fix

The user needs to log into the tree that the server package and server object are in.

symptom

Error: "No import policy found."

Error: "No removal policy found."

fix

Make sure that the server package is created, associated to the import server, and that the import or removal policy is enabled.

If a server package is associated and a search policy is configured correctly, and this error is still reported, check the replica ring in which the import server is a part.  In one case the server running the import service thought it held a R/W of the partition, but none of the other servers recognized this.  DSREPAIR -XK2  -XK3  was performed. The copy was basically deleted from the server, then (after synchronization between the other members was successful)  the import server was given a r/w copy again, and the problem was gone.

symptom

Error: "Could not authenticate as policy: "

Error: "Missing attribute in removal policy: "

Error: "The removal policy is invalid.  Please create a new server package."

Error: "An error occurred while attempting to apply the naming rules."

fix

Delete the server package and create a new one.  For the Naming issue, change the Naming Order on the Naming Tab under the Platform tab.

See Workstations fail to import due to -669 error in ZENWSIMP.LOG.

symptom

Error: "Only NetWare, Microsoft Windows NT 4.0 and Microsoft Windows 2000 are supported"

fix

The service needs to run on a NetWare or Microsoft Windows NT4 or Windows 2000 machine.

symptom

Error: "There was no resource file found. Program will run without logging messages."

cause

WSREG32R.DLL is missing or an outdated version.  WSREG32R.DLL is found in C:\WINNT\SYSTEM32  or C:\WINDOWS\NLS\ENGLISH

fix

Reinstall the client, or copy it from SYS:PUBLIC\NLS\ENGLISH

symptom

Error: "A tree name is required since the naming and/or location is based on the user."

Error: "A user name is required to create the workstation according to policy: "

cause

The "Tree name is required" and "User name is required" messages can occur when the import of the workstation object is dependent on user information.  For example, if the name of the workstation being created is composed of the NDS user name ("user") in the Naming tab of the Server Package, or if the User's container is being used as an import container, these messages will occur when the user has not yet logged into NDS.  Automatic Workstation Import will not occur until the user has logged into NDS.  If the Naming tab specifies a user name, check the Limits tab as well to make sure the user has logged in the required number of times specified in this tab.  These messages can also occur if the Tree name is incorrect on the properties of Workstation Manager on NT/2000 workstations.  NOTE: It is normal to see these messages in WSREG32.LOG when the event is "<UNKNOWN_EVENT>".  Running WSREG32.LOG manually is considered an UNKNOWN EVENT by DS because Workstation Manager did not trigger the start of WSREG32.EXE.  Also the WSREG32.LOG will recreate its self once it hits a file size of approximately 2kb.

fix

Not necessarily an error.  User and tree names are provided only when WSREG is triggered by a login event.  The workstation will not be created until the user logs in.

Login into NDS with the correct user name if the Naming tab of the Workstation Import Policy specifies "user".

Login into NDS with the correct user name as many times as is required by the Limits tab in the Workstation Import Policy.

Verify that Novell Workstation Manager has the correct Tree Name on NT/2000 workstations.

symptom

WSREG-v3.0  This log file is reporting activity on a WM_SERVICE_START_EVENT event.
WSREG-v3.0  The tree <Tree_Name> contains the workstation object <Workstation_Object_Information>.  Workstation Registration must be authenticated as the object to update the object.
WSREG-v3.0  This workstation currently does not have a DS Authenticated Connection to the trusted tree.  This program is unable to complete the registration or to update the workstation properties.

WSREG-v3.0  This log file is reporting activity on a WM_USER_LOGIN_EVENT event.
WSREG-v3.0  This workstation has been updated.

fix

These messages occur in sequence and are normal.  The first group of messages "Workstation Registration must be authenticated as the object to update the object" will occur normally when the workstation object has not yet logged into the tree and Workstation Manager has already loaded as a service (as indicated by the event  WM_SERVICE_START_EVENT) and is looking for the imported workstation object in the tree.  The next message is the next normal message to occur when the user logs in (WM_USER_LOGIN_EVENT) and the workstation object is updated.

See ZENworks Workstation Object fails to login to NDS [no longer available].

Another fix was configuring the Container Package > Search Policy to extend its search.

symptom

Error: "An import was denied because the maximum number of imports has been reached."

fix

Wait a while (1 hour recommended) and try again to import.

symptom

Error: "Could not locate the target container."

fix

Check the location tab in the import policy and make sure that a valid container is specified.

The Container where the workstation object are being created need to be of Object Class Organizational Unit, check in DSBROWSE that the Object Class entry is Organizational Unit. If not then try to merge the partition and then partition it back.

symptom

Error: "Could not create the workstation.  Make sure that you provide rights for the service by adding the appropriate containers to the containers list in the import policy."

fix

Add the target container (or a parent container) to the containers list in the import policy.  

If this does not correct the problem then right click on the container where the workstations are supposed to be imported to, and select "Trustees of this object" One of the trustees should be: Server Package:Workstation Import.context.   The trustee should have the following effective rights:

[All Attributes Rights]  Compare, Read, Write, Add Self
[Entry Rights]   Browse, Create

symptom

Error: "Could not get last registered time of workstation: "

fix

This workstation will not be removed automatically.  Delete it manually if it is unused.

symptom

Error "No containers specified for workstation removal."

fix

Add at least one container to the containers list in the removal policy.

symptom

Error: "Could not write to the log file."

fix

Make sure that the SYS:zenworks\zenwsimp.log or SYS:zenworks\zenwsrem.log (C:\zenwsimp.log or C:\zenwsrem.log for NT) are not locked by another application.

symptom

Error: "Could not remove container attribute value."

Error: "Could not find workstation: "

fix

These are innocuous errors; no action needs to be taken.

note

This error has been known to coincide with High utilization on the AWI import process.  The issue was a workstation sending a corrupt packet to the import server.  Note the time of the error and within the zenwsimp.log find the workstation that is associated to the error.  Delete the workstation object, unregister it using UNREG32.EXE, and import the workstation again.  This seems to address the high utilization issue on the server.

symptom

Error: "Could not set the password.  The workstation must be removed and imported again.'

Error: "Could not give the workstation entry rights to itself."

Error: "Could not apply workstation group: "

Error: "Could not apply the workstation groups."

fix

Delete the workstation, unregister it, and try to import it again.

symptom

Error: Winsock recv () failed

cause

The AUTOEXEC.NCF file was open during the installation of ZENworks for Desktops 3.

fix

Make sure you have this path statement in the AUTOEXEC.NCF: SEARCH ADD SYS:\JAVA\NJCLV2\BIN.

symptom

Error: Winsock connect () failed

cause

The registration agent attempted to make a TCP connection (on TCP port 8039) to the address returned by the server. If the port is unavailable, the service is not loaded; if the server is down, this may fail.  If a TCP connection to the server could not be created, then an error is returned in the log file indicating that Winsock connect () failed.

fix

Check that the workstation can get through the router to the Import server.  Most likely a connectivity issue rather than configuration of AWSI.

Refer to this document to be sure Automatic Workstation Import is configured correctly.

Another thing to try is to make sure you have ConsoleOne version 1.2d.1 and Service Pack 1 for ZENworks 3 installed and recreate the Server Package with that installed.

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.

  • Document ID:
  • 10056909
  • Solution ID: NOVL26358
  • Creation Date: 15Sep2000
  • Modified Date: 29Nov2005
    • NovellManagement Products

      NetWare

Did this document solve your problem? Provide Feedback