inverseparadox Absent Member.
Absent Member.
1204 views

Satellite server communication failed, unknown-OS error

While upgrading our ZENworks servers to 11.2.4 recently, we discovered that one of our satellite servers is not successfully communicating with the primaries.

This satellite is also the only one of our ZENworks servers which is on Windows Server 2008 64-bit; all of the others are on some variant of Windows Server 2003.

If I unregister the Agent on this satellite and attempt to re-register it via 'zac reg', there is an extended delay, and then the registration attempt fails with the following error message:
Unable to register with the server at: https://servername.
Service Error. code: -21, message: Could not determine device type from <OS> tag: unsupported


Searches seem to indicate that this error message can mean that the device is running an operating system which is not listed in a particular XML file. However, I've checked the relevant XML file on both the satellite and the primary server, and the appropriate operating system is indeed listed.


This satellite, like most of our ZENworks servers, was installed with ZENWORKS_HOME pointing to a location which is not under the C: drive. Instead, it is on a separate drive, intended to serve as a "data" partition of sorts.

If I uninstall the Agent, reboot, and install the Agent to the default location on the C: drive, it does not exhibit this error; it communicates with the server without problems. However, this is not a viable configuration, because there is far too little space available on the C: drive.

If I uninstall the Agent, reboot, set ZENWORKS_HOME appropriately (which may involve another reboot), and install the Agent back to its non-C:-drive install location, it fails to make contact with the primary, and attempting to manually register shows the above error.


Any ideas what may be going on here?

We're looking at migrating our primary servers to this same OS in the near future (as in, within the next few weeks), as the most recent Windows OS which is supported by ZENworks 11.2 (and as a stop on the way to later upgrading to 11.3); since their existing ZENworks installs are _all_ to non-default locations, I find this behavior a bit disturbing.

I'm planning to recommend installing ZENworks to the default location on the new servers and just putting the content repo on a separate partition, but I'm not entirely sure that will be workable, since the migration process is - depending on which set of directions I go by - either complex and daunting or fairly opaque.
Labels (2)
0 Likes
3 Replies
shaunpond Absent Member.
Absent Member.

Re: Satellite server communication failed, unknown-OS error

Inverseparadox,

what do you see in the services-messages.log on the severe, and the
zmd-messages.log on the device when you attempt to register?

--

Shaun Pond
newly reminted as a Knowledge Professional


0 Likes
inverseparadox Absent Member.
Absent Member.

Re: Satellite server communication failed, unknown-OS error

shaunpond;2375847 wrote:

what do you see in the services-messages.log on the severe, and the
zmd-messages.log on the device when you attempt to register?

That put me on what is probably the right track. (I don't know why I didn't check that before posting. I apparently set the logging to maximum verbosity, but then never went back and read the resulting log...)

With full debug verbosity enabled, zmd-messages.log on the satellite server has only a few identifiable error messages from the register attempt. The most prominent one, repeated several times, is a "The file exists" error from under Novell.Zenworks.Zmd.Common.IO.ZenIO.GetUniqueTempFilePath().

This in turn calls System.IO.Path.GetTempFileName(), and Googling on 'GetTempFileName "The file exists"' provides a hint that this can happen when more than 65536 files exist in %TEMP%.

In this case, although %TEMP% is empty, there are 65,718 files in %windir%\Temp\. I will see about getting most of those cleared out, and try the registration again; I suspect that it will succeed.

That wouldn't explain why it worked when installed to the default location, but I'm quite willing to revisit that question only if clearing out the tempfiles doesn't fix the problem.
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Satellite server communication failed, unknown-OS error

inverseparadox;2375780 wrote:
While upgrading our ZENworks servers to 11.2.4 recently, we discovered that one of our satellite servers is not successfully communicating with the primaries.

This satellite is also the only one of our ZENworks servers which is on Windows Server 2008 64-bit; all of the others are on some variant of Windows Server 2003.

If I unregister the Agent on this satellite and attempt to re-register it via 'zac reg', there is an extended delay, and then the registration attempt fails with the following error message:
Unable to register with the server at: https://servername.
Service Error. code: -21, message: Could not determine device type from <OS> tag: unsupported


Searches seem to indicate that this error message can mean that the device is running an operating system which is not listed in a particular XML file. However, I've checked the relevant XML file on both the satellite and the primary server, and the appropriate operating system is indeed listed.


This satellite, like most of our ZENworks servers, was installed with ZENWORKS_HOME pointing to a location which is not under the C: drive. Instead, it is on a separate drive, intended to serve as a "data" partition of sorts.

If I uninstall the Agent, reboot, and install the Agent to the default location on the C: drive, it does not exhibit this error; it communicates with the server without problems. However, this is not a viable configuration, because there is far too little space available on the C: drive.

If I uninstall the Agent, reboot, set ZENWORKS_HOME appropriately (which may involve another reboot), and install the Agent back to its non-C:-drive install location, it fails to make contact with the primary, and attempting to manually register shows the above error.


Any ideas what may be going on here?

We're looking at migrating our primary servers to this same OS in the near future (as in, within the next few weeks), as the most recent Windows OS which is supported by ZENworks 11.2 (and as a stop on the way to later upgrading to 11.3); since their existing ZENworks installs are _all_ to non-default locations, I find this behavior a bit disturbing.

I'm planning to recommend installing ZENworks to the default location on the new servers and just putting the content repo on a separate partition, but I'm not entirely sure that will be workable, since the migration process is - depending on which set of directions I go by - either complex and daunting or fairly opaque.


Is there anything unusual about your Non-C Drive? Is is a physical local disk?
I would sanity check permissions on that drive to make sure there are not any unusual Deny and that permissions for all groups are similar to those in the default location.
--
Please give a hearty thumbs up to any post you find helpful!
To find articles by Craig Wilson simply follow the link: Craig Wilson's Tips!
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.