This article describes the manual actions which are be required in the following situations to bootstrap an active distribution server that is configured to poll for jobs:
1. The active distribution server is running on Windows NT; or
2. The name of the distribution server as specified in the ManageSoft distribution hierarchy is different from the fully qualified DNS hostname that the distribution server determines for itself; or
3. The distribution server must be reparented in the ManageSoft distribution hierarchy.
Problem
An active distribution server that is configured to poll for jobs is unable to automatically configure itself in the distribution hierarchy the following situations:
1. The active distribution server is running on Windows NT; or
2. The name of the distribution server as specified in the ManageSoft distribution hierarchy is different from the fully qualified DNS hostname that the distribution server determines for itself; or
3. The distribution server has been reparented in the ManageSoft distribution hierarchy.
Symptoms
The primary symptom of this problem is that packages cannot be distributed to or through an affected distribution server, since the server will not receive any information from its parent about distribution jobs. Further diagnosis of the problem can be done by checking the following symptoms:
1. Locate the ManageSoft replication agent log file. By default this will be in $(TempDirectory)\ManageSoft\ndrplag.log, although may have been customized by the registry setting HKLM\SOFTWARE\ManageSoft Corp\ManageSoft\Replication Agent\CurrentVersion\LogFile.
2. The log file should show an attempt every minute to poll the distribution server's parent for jobs.
3. Search in the log file for the following message: Could not find DS UID for hostname If this message appears, it indicates that the specified name cannot be found in the ManageSoft distribution hierarchy, and that this problem is affecting the distribution server.
4. Search for the most recent (last) entry in the log file that contains the following message: Polling http:///ManageSoftJQ/mgsjobsrv.exe? for jobs, ...
5. If the hostname specified in this message is NOT the current parent of the distribution server, this suggests that the distribution server has been reparented and is being affected by this problem.
6. If the contains the string "hostname=" without being followed by the hostname of the computer, this indicates that ManageSoft was unable to determine the hostname of the computer and that this problem is affecting the distribution server.
Solutions
Possible ways to resolve this problem are:
1. Symptom 5: Change the parent hostname to the correct value in the registry entry HKLM\SOFTWARE\ManageSoft Corp\ManageSoft\Replication Agent\CurrentVersion\JobQueueLocation.
2. Symptom 3: Change the hostname in the distribution server's properties in the ManageSoft distribution hierarchy to match the name specified in the log message.
3. Symptom 3 or 6: Manually copy the file $(WarehouseDirectory)\Repository\DeploymentLocations\Common\hierarchy.cfg from your warehouse to the same location on the distribution servers. This may (but is not guaranteed to) provide enough information to the distribution server to enable it to bootstrap itself.
4. Symptom 3 or 6 (if none of the above solutions work):
a. Open the ManageSoft hierarchy configuration file (hierarchy.cfg) from the warehouse in a text editor such as Notepad. This file is an XML file.
b. Find the element for the distribution server in the hierarchy; this element will appear similar to the following:
c. On the distribution server, set the registry entry HKLM\Software\ManageSoft Corp\ManageSoft\Replication Agent\CurrentVersion\LocalAddress to the value of the SERVER attribute (including the curly braces '{' and '}'). For the above example, LocalAddress would be set to the value {F4D153B2-C6A0-4C6D-AC3D-EE5E10CB7CE5} The LocalAddress setting will then by used by the distribution server to identify itself in the distribution hierarchy.
Comments
0 comments
Article is closed for comments.