ZenDM7Sp1 Inventory Rollup NFG.

Question

Hello:
I have a Zen7 SP1 DM Deployment with dedicated Zen Servers.
1 Root Server with Database and workstations Connected at one site.
2 leaf servers w/o dB and workstations connected at WAN sites
WAN sites are 1) 100Mb FDX and 2) a Full T1 to the other leaf server
(50 users)
The STR and ZIP files get created at the Leaf Servers.
The Inventory Service Objects re the leaf servers show a last storage
time in root server of July 2006.
There is a storer error 335:Socket Input-Output error occurred while
getting the zeninvRollupTime.
The usual stuff (DOES NOT WORK) re using ip address instead of DNS Name
in the Inventory Service Object re:
--*-335: Socket Input-Output error occurred while getting the
zeninvRollupTime
Source: ZENworks for Desktops; Workstation Inventory; Sender
Severity: Critical
Explanation: An internal error occurred while getting the
zeninvRollupTime. The Sender retries connecting to the Receiver for
approximately 23 hours before it discontinues trying.
Possible Cause: The next-level Inventory server is not up and running.
Action: Ensure that the next-level Inventory serve is up and running.
Possible Cause: The next-level Inventory server is not reachable.
Action: Ensure that the next-level Inventory server is reachable.
Possible Cause: The ZEN Web Server is not running on the next-level
Inventory server.
Action: Ensure that the ZEN Web Server and the Inventory services are
running on the next-level Inventory server.
Possible Cause: This problem might occur on a NetWare Inventory server
with Native File Access Pack installed. This NetWare server has one or
more volumes exposed as CIFS shares and does not have a DNS name
configured.
If the NetWare server does not have a DNS name configured, the CIFS
service is given a NetBIOS name, and the Roll-up policy assigns the
NetBIOS name as the host name.
This error occurrs if the Sender on the NetWare server fails to resolve
the NetBIOS name to an IP address.
Action: Choose an IP address instead of the NetBIOS name in the
Roll-up policy. For more information, see "Configuring the Roll-Up
Policy" in "Setting Up Workstation Inventory "in the ZENworks for
Desktops 4.0.1 Administration Guide.
etc etc makes no difference.
DNS is working in our env. I can ping from one server to the next
using IP addresses and DNS names.-*--
Anyone have any ideas about this
rdseepaul

Answer 1

Hello Marcus:
It is working as far as I can tell.
A zero byte zfs-startup.xml file prevented the Zenworks web server from
starting on the Root Inventory Server.
i.e. Thie server was not listening on TCP port 8089 (TCPCON is my
friend)
I found the zero byte xml file after wondering why the server was not
listening on port 8089. And could not manually start the Zen Web
Server.
I replaced the file with one from one of the leaf Servers ( There is no
server specific Info in this file and the install volumes are the same
on all the zen servers).
Now the leaf server inventory service objects show a current date for
last storage time in Root Server. The 335 Error message has
disappeared. etc.
I can theorize that perhaps the zero byte xml file was caused by a
server power button reboot after freez up or some similar event.
The University of Hard Knocks is a good Product Architecture Teacher.
Thanks
Richard
rdseepaul