mkoeppl Absent Member.
Absent Member.
2420 views

Terminal Server W2k3Sp2 Win32 Collector problem error

After manual installation of the agent on a TS W2K3 SP2 we get the Win32 Collector encountered a problem error.
I hoped this error go away with 10.0.3.2 but it is not.

The greatest problem is that i do not see a object for this server.
The zoneserver etc. are reported unavailable in the agent and there is no object name shown. With zac zc i do see the correct zone configuration.

I´m not sure if 10.0.3.2 really created a updated deploy agent. On the other hand i´m not sure why this error prevents registration of the server.
The os is coorectly found during a check against the supported os´s.

Anyone with the same problem?

I already opened a call at novell but they are also lost at the moment.
I need this terminal server in the pilot test and not getting an device object is really a showstopper.

Michael Koeppl Germany
Labels (2)
0 Likes
10 Replies
jaredljennings Absent Member.
Absent Member.

Re: Terminal Server W2k3Sp2 Win32 Collector problem error

mkoeppl said on 6/30/2008,

>After manual installation of the agent on a TS W2K3 SP2 we get the Win32
>Collector encountered a problem error.
>I hoped this error go away with 10.0.3.2 but it is not.


Is this problem related to this TID?
http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=7000499&sliceId=1&docTypeID=DT_TID_1_1&dialogID=35648686&stateId=0%200%2035646429

--
Jared Jennings - Data Technique, Inc.
Novell Support Forums Sysop
My Blog and Wiki with Tips, Tricks, and Tutorials
http://jaredjennings.org
0 Likes
mkoeppl Absent Member.
Absent Member.

Re: Terminal Server W2k3Sp2 Win32 Collector problem error

jaredjennings;1589691 wrote:
mkoeppl said on 6/30/2008,

>After manual installation of the agent on a TS W2K3 SP2 we get the Win32
>Collector encountered a problem error.
>I hoped this error go away with 10.0.3.2 but it is not.


Is this problem related to this TID?
Colw32 Error running scan on Windows XP or Vista device.

--
Jared Jennings - Data Technique, Inc.
Novell Support Forums Sysop
My Blog and Wiki with Tips, Tricks, and Tutorials
Main Page - ZENWorks Wiki


I´m not shure. On one side it´s a W2k3 SP2 server. On the other side the primary server is patched to 10.0.3.2 and the agents got a new timestamp and i thought the TID 7000499 error should be solved in that version.
This is exactly the thing i wanted to find out.

And there always is the question to me - is a faulty win collector responsible for not getting registered?

Michael Koeppl Germany
0 Likes
jaredljennings Absent Member.
Absent Member.

Re: Terminal Server W2k3Sp2 Win32 Collector problem error

mkoeppl said on 7/1/2008,

>And there always is the question to me - is a faulty win collector
>responsible for not getting registered?


I don't see how. They are completely different.

Can you manually register?

How about a zcm-messages.log?

--
Jared Jennings - Data Technique, Inc.
Novell Support Forums Sysop
My Blog and Wiki with Tips, Tricks, and Tutorials
http://jaredjennings.org
0 Likes
mkoeppl Absent Member.
Absent Member.

Re: Terminal Server W2k3Sp2 Win32 Collector problem error

jaredjennings;1589875 wrote:
mkoeppl said on 7/1/2008,

>And there always is the question to me - is a faulty win collector
>responsible for not getting registered?


I don't see how. They are completely different.

Can you manually register?

How about a zcm-messages.log?

--
Jared Jennings - Data Technique, Inc.
Novell Support Forums Sysop
My Blog and Wiki with Tips, Tricks, and Tutorials
Main Page - ZENWorks Wiki


The zcm-message log shows no error as far as i remember. But the zmd-message log on the w2k3 terminal server shows some strange things.
First there is a proper connection to the registration server and than it states:

[DEBUG] [6/27/2008 3:42:02 PM] [] [RegistrationManager] [] [Unexpected exception calling registration soap service: Unable to connect to the remote server



and some lines later :
[DEBUG] [6/27/2008 3:42:02 PM] [] [ConnectMan] [] [ Exception causing location name 192.168.233.109 to be marked Bad: .... connection failed because connected host has failed to respond 10.1.206.5:8080

and no one in our network knows this ip address 10.1.206.5

Michael Koeppl Germany
0 Likes
jaredljennings Absent Member.
Absent Member.

Re: Terminal Server W2k3Sp2 Win32 Collector problem error

mkoeppl said on 7/1/2008,

>and some lines later :
>[DEBUG] [6/27/2008 3:42:02 PM] [] [ConnectMan] [] [ Exception causing
>location name 192.168.233.109 to be marked Bad: .... connection failed
>because connected host has failed to respond 10.1.206.5:8080
>
>and no one in our network knows this ip address 10.1.206.5


Does the correct ZCM server address show if you examine the ZCM agent
properties on the terminal server?

Did you try re-registering the terminal server?

--
Jared Jennings - Data Technique, Inc.
Novell Support Forums Sysop
My Blog and Wiki with Tips, Tricks, and Tutorials
http://jaredjennings.org
0 Likes
mkoeppl Absent Member.
Absent Member.

Re: Terminal Server W2k3Sp2 Win32 Collector problem error

jaredjennings;1589955 wrote:
mkoeppl said on 7/1/2008,

>and some lines later :
>[DEBUG] [6/27/2008 3:42:02 PM] [] [ConnectMan] [] [ Exception causing
>location name 192.168.233.109 to be marked Bad: .... connection failed
>because connected host has failed to respond 10.1.206.5:8080
>
>and no one in our network knows this ip address 10.1.206.5


Does the correct ZCM server address show if you examine the ZCM agent
properties on the terminal server?

Did you try re-registering the terminal server?

--
Jared Jennings - Data Technique, Inc.
Novell Support Forums Sysop
My Blog and Wiki with Tips, Tricks, and Tutorials
Main Page - ZENWorks Wiki


The agent shows no zcm server address in the agent gui but if i do "zac zc "it shows the correct addresses.

If i try to unreg and reg again (via zac reg ) i get a error message (in german and nothing usefull or specific). I try to get the exact error message tomorrow.

Michael Koeppl Germany
0 Likes
mkoeppl Absent Member.
Absent Member.

Re: Terminal Server W2k3Sp2 Win32 Collector problem error

The agent shows no zcm server address in the agent gui but if i do "zac zc "it shows the correct addresses.

If i try to unreg and reg again (via zac reg ) i get a error message (in german and nothing usefull or specific):

- Registration at the server not possible
- URL of registration service
- RegisterUser Registration with service not possible

attached is the zmd-message log of this time from the terminal server.

Michael Koeppl Germany
0 Likes
jaredljennings Absent Member.
Absent Member.

Re: Terminal Server W2k3Sp2 Win32 Collector problem error

mkoeppl said on 7/3/2008,

>If i try to unreg and reg again (via zac reg ) i get a error message
>(in german and nothing usefull or specific):


Is this the ZCM servers domain name or did you replace the real with a fake?
zcm-server.domain.com

This error appears to be the problem.
[DEBUG] [03.07.2008 10:35:59] [] [CertManager] [] [No certificate found for host: 192.168.233.109] [] []

--
Jared Jennings - Data Technique, Inc.
Novell Support Forums Sysop
My Blog and Wiki with Tips, Tricks, and Tutorials
http://jaredjennings.org
0 Likes
Highlighted
mkoeppl Absent Member.
Absent Member.

Re: Terminal Server W2k3Sp2 Win32 Collector problem error

jaredjennings;1591016 wrote:
mkoeppl said on 7/3/2008,

>If i try to unreg and reg again (via zac reg ) i get a error message
>(in german and nothing usefull or specific):


Is this the ZCM servers domain name or did you replace the real with a fake?
zcm-server.domain.com

This error appears to be the problem.
[DEBUG] [03.07.2008 10:35:59] [] [CertManager] [] [No certificate found for host: 192.168.233.109] [] []

--
Jared Jennings - Data Technique, Inc.
Novell Support Forums Sysop
My Blog and Wiki with Tips, Tricks, and Tutorials
http://jaredjennings.org


This is just a fake name.
Why is the dns name not used for certification checks?
And why can XP Workstations register and connect to that server?
Really Strange. On the other side. Is the certificate which is autogenerated not only based on the dns name. I thought a had an issue with certificates and dns names with version 10.0.2 or earlier.

I even tried to register with an agent which has only the dns name as zcm server all - without success.

Can i manually create certificates for the primary server to better get control of the involved names.

Michael Koeppl Germany
0 Likes
mkoeppl Absent Member.
Absent Member.

Re: Terminal Server W2k3Sp2 Win32 Collector problem error

jaredjennings;1589875 wrote:
mkoeppl said on 7/1/2008,

>And there always is the question to me - is a faulty win collector
>responsible for not getting registered?


I don't see how. They are completely different.

Can you manually register?

How about a zcm-messages.log?

--
Jared Jennings - Data Technique, Inc.
Novell Support Forums Sysop
My Blog and Wiki with Tips, Tricks, and Tutorials
Main Page - ZENWorks Wiki


The zcm-message log shows no error as far as i remember. But the zmd-message log on the w2k3 terminal server shows some strange things.
First there is a proper connection to the registration server and than it states:

[DEBUG] [6/27/2008 3:42:02 PM] [] [RegistrationManager] [] [Unexpected exception calling registration soap service: Unable to connect to the remote server



and some lines later :
[DEBUG] [6/27/2008 3:42:02 PM] [] [ConnectMan] [] [ Exception causing location name 192.168.233.109 to be marked Bad: .... connection failed because connected host has failed to respond 10.1.206.5:8080

and no one in our network knows this ip address 10.1.206.5

Michael Koeppl Germany
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.