Environment
Novell ZENworks for Servers
Novell Tiered Electronic Distribution (TED)
Novell ZENworks for Servers 3.0
Novell ZENworks 7 Server Management Support Pack 1 - ZSM7 SP1
Novell Tiered Electronic Distribution (TED)
Novell ZENworks for Servers 3.0
Novell ZENworks 7 Server Management Support Pack 1 - ZSM7 SP1
Situation
There are several possible causes for this problem.
A. Error message: "Failed to process package. Details: Error processing package variables. Variable "<variable name>" has not been defined." the end result is that variables are not being pushed to the subscriber.
B. The revision number of the Subscriber object in NDS is lower than the configuration of the Subscriber in iManager (object revision).
C. a. The Subscriber was deleted, but not completly.
b. Attempting to do new variables, or modifications to the existing variables, after they have already been sent in a Distribution.
c. The new variables are not seen by the Subscriber.
d. The changed or modified variables are not seen by the Subscriber.
B. The revision number of the Subscriber object in NDS is lower than the configuration of the Subscriber in iManager (object revision).
C. a. The Subscriber was deleted, but not completly.
b. Attempting to do new variables, or modifications to the existing variables, after they have already been sent in a Distribution.
c. The new variables are not seen by the Subscriber.
d. The changed or modified variables are not seen by the Subscriber.
Resolution
A. If the Subscriber was deleted, the TED.CFG needs to be deleted as well, that way, when a Distributor sends a Distribution to the newly created Subscriber, it also sends down a fresh configuration file (TED.CFG), so that the Subscriber has the accurate information from the Distributor.
B. This can be worked around by making enough modifications to the Subscriber variables to make NDS have a larger revision that what is seen by the Subscriber in iManager.
C. Stop the Distributor(s) and affected Subscriber(s), ones that have new or modified variables, including any Parent Subscribers 'above' the affected Subscriber(s), and delete the Distributor's and affected Subscriber's TED.CFG. Restart the Distributor and Subscriber(s) so the variables can be reread and built into the Distribution processes.
B. This can be worked around by making enough modifications to the Subscriber variables to make NDS have a larger revision that what is seen by the Subscriber in iManager.
C. Stop the Distributor(s) and affected Subscriber(s), ones that have new or modified variables, including any Parent Subscribers 'above' the affected Subscriber(s), and delete the Distributor's and affected Subscriber's TED.CFG. Restart the Distributor and Subscriber(s) so the variables can be reread and built into the Distribution processes.
Additional Information
A. Possible cause is that the ZfS Subscriber was deleted. If the Subscriber was deleted, the TED.CFG needs to be deleted as well, that way, when a distributor sends a distribution to the newly created subscriber, it also sends down a fresh configuration file (TED.CFG), so that the subscriber has the accurate information from the distributor.
B. n/a
C. The Distributor reads the Subscribers variables before sending a Distribution and puts the variables in the Distributor's TED.CFG and the Subscriber's TED.CFG as part of the Distribution. New and modified variables will need new TED.CFG files to include them.
Formerly known as TID# 10090558
B. n/a
C. The Distributor reads the Subscribers variables before sending a Distribution and puts the variables in the Distributor's TED.CFG and the Subscriber's TED.CFG as part of the Distribution. New and modified variables will need new TED.CFG files to include them.
Formerly known as TID# 10090558