ZFD agent hangs after splash screen
Patrick Farrell
thread going on about uninstalling/reinstalling in this forum.
I have a classic example on my bench. I have 3 identical machines. I
had just "fixed" the agent by uninstalling/reinstalling. 2 of them are
now broken again. What happens is you see the splash screen, and the
zen icon in the tray has the "off line" appearance. You can't get a
menu by right clicking. Applications don't appear, nor do start menu
entries, nor does Application Explorer. Running Naldiag will cause it
to hang in the background.
Uninstalling and reinstalling the agent fixes this, however it will
happen again. I also deleted the workstation objects in the tree just
in case and let them reregister with the new agent.
Any suggested trouble shooting tactics to try?
Patrick Farrell
Grrr... another one went down this morning. Reload the agent, and it's
fine.
Chris
version specific problem?
>>> On 10/14/2009 at 9:59 AM, in message
<pPkBm.18495$7G7....@kovat.provo.novell.com>, Patrick
Patrick Farrell
> Have you tried back-revving the agent to see if this is a
> version specific problem?
I'm going to have to. I have a 100% failure rate on the new agent.
Every machine I've tried it on will fail within a week. I even made a
fresh image with a machine that never had Zen on it. Same problem.
Works initially then fails. I have 3 on my bench, one still working, 2
failed yesterday.
None of the older agents exhibit this issue.
Patrick Farrell
will reveal anything related to the current issue. It does however
reveal some other problem and I now I have to go figure out why my zen
server is getting down to a window size of zero at some points.. Grrr.
That issue shouldn't be related to the current problem however as older
agents don't have the issue. Machine 3 of 3 on my bench started doing
it this morning, so that's now 100% failure based on a fresh load. Odd
that it differs in the amount of time it takes for the problem to occur.
Jared Jennings
>Uninstalling and reinstalling the agent fixes this, however it will happen
>again. I also deleted the workstation objects in the tree just in case
>and let them reregister with the new agent.
Check your policy objects and applications. Either could be corrupt. So I
would try unassociating all, clearing cache and a reboot :)
--
Jared Jennings
Novell Support Forums Sysop
Senior Systems Architect, Data Technique, Inc.
http://www.datatechnique.com
My Blog and Wiki with Tips, Tricks, and Tutorials
http://jaredjennings.org
Twitter@ http://twitter.com/jaredljennings
Patrick Farrell
> Patrick Farrell,
>
>> Uninstalling and reinstalling the agent fixes this, however it will
>> happen again. I also deleted the workstation objects in the tree just
>> in case and let them reregister with the new agent.
>
> Check your policy objects and applications. Either could be corrupt. So
> I would try unassociating all, clearing cache and a reboot :)
>
Any idea how to track that down other than 1 at a time? It seems odd
that the other 150 or so machines with slightly earlier agents would
have no problems. I have a LOT of applications. Yesterday I
uninstalled and went back to the IR4 agent on 5 machines. They worked
fine all day yesterday. I just found out this morning that all 5 have
now failed identically. I'm going to roll them back to IR 3A Hp2 to
test that. Unfortunately I'm out of time messing with this batch, I'll
have to get another one to fail, which shouldn't be hard.
Patrick Farrell
> Patrick Farrell,
>
>> Uninstalling and reinstalling the agent fixes this, however it will
>> happen again. I also deleted the workstation objects in the tree just
>> in case and let them reregister with the new agent.
>
> Check your policy objects and applications. Either could be corrupt. So
> I would try unassociating all, clearing cache and a reboot :)
>
It's not the applications. Removed all of them from a test user and
cleared the cache and rebooted. I'll have to create a new policy for
them and try that.
Patrick Farrell
Created a brand new user and workstation policy as well, no change.
Jared Jennings
>Created a brand new user and workstation policy as well, no change.
Yuck!
Can you easily get a packet trace?
Does it matter if you login workstation only?
Patrick Farrell
> Patrick Farrell,
>
>> Created a brand new user and workstation policy as well, no change.
>
> Yuck!
> Can you easily get a packet trace?
> Does it matter if you login workstation only?
>
I posted one in this thread.
Jared Jennings
>I posted one in this thread.
Sorry, I missed it.
Patrick Farrell
> Patrick Farrell,
>
>> I posted one in this thread.
>
> Sorry, I missed it.
>
No worries. Unfortunately I needed to put the 3 machines on my bench
back into production. I back revved those to IR3a_HP3, we'll see what
we see.
I know the agent 7.0.163.81104 works fine but I'm not sure which pack
that's from. (I have all of them stored locally.)
I have another machine now that I've managed to free up and re-image and
upgrade the agent. It hasn't failed yet despite a half a dozen reboots,
but then again neither did the others. I'll probably come in tomorrow
and log it in and find it not working any longer. Once that one breaks
I'll have a dedicated "broken" machine to work with again.
Jared Jennings
>
>I have another machine now that I've managed to free up and re-image and
>upgrade the agent. It hasn't failed yet despite a half a dozen reboots,
>but then again neither did the others. I'll probably come in tomorrow and
>log it in and find it not working any longer. Once that one breaks I'll
>have a dedicated "broken" machine to work with again.
What about AV software? A re-install of the agent already fixes this right?
Patrick Farrell
> Patrick Farrell,
>
>>
>> I have another machine now that I've managed to free up and re-image
>> and upgrade the agent. It hasn't failed yet despite a half a dozen
>> reboots, but then again neither did the others. I'll probably come in
>> tomorrow and log it in and find it not working any longer. Once that
>> one breaks I'll have a dedicated "broken" machine to work with again.
>
> What about AV software? A re-install of the agent already fixes this right?
>
Mcafee 8.7i
A reinstall of the same version of the agent will fix it temporarily.
It will break again anywhere from 1 day to one week.
Patrick Farrell
> Patrick Farrell,
>
>> Created a brand new user and workstation policy as well, no change.
>
> Yuck!
> Can you easily get a packet trace?
> Does it matter if you login workstation only?
>
One of my laptops just failed with this. If you log in workstation
only, it's fine.
Jared Jennings
>One of my laptops just failed with this. If you log in workstation only,
>it's fine.
Good that helps. I will look at the log more closely then.
How about any workstation logs?
Patrick Farrell
> Patrick Farrell,
>
>> One of my laptops just failed with this. If you log in workstation
>> only, it's fine.
>
> Good that helps. I will look at the log more closely then.
> How about any workstation logs?
>
I will turn on debugging and put up a set of logs tomorrow.
Jared Jennings
>I will turn on debugging and put up a set of logs tomorrow.
Cool
Patrick Farrell
> Patrick Farrell,
>
>> I will turn on debugging and put up a set of logs tomorrow.
>
> Cool
>
Sorry it took so long on this, busy day..
http://66.147.134.189/nallogs.zip
Let me know if that's what you are looking for.
Patrick Farrell
> Patrick Farrell,
>
>> I will turn on debugging and put up a set of logs tomorrow.
>
> Cool
>
Any thoughts? Are those the logs you were looking for?
Jared Jennings
>Any thoughts? Are those the logs you were looking for?
I hadn't gotten anything out of the packet trace :(
Sorry, I haven't gone through the logs yet.
Patrick Farrell
> Patrick Farrell,
>
>> Any thoughts? Are those the logs you were looking for?
>
> I hadn't gotten anything out of the packet trace :(
> Sorry, I haven't gone through the logs yet.
No worries, I appreciate you taking the time. I just wanted to make
sure that I got you what you asked for.
Jared Jennings
>No worries, I appreciate you taking the time. I just wanted to make sure
>that I got you what you asked for.
Just keep knocking :)
Jared Jennings
>Sorry it took so long on this, busy day..
>
>http://66.147.134.189/nallogs.zip
>
>Let me know if that's what you are looking for.
Can you get a log of a working machine? I see the following error in
nwgina.log that I suspect is the cause. (GUessing)
10/21/2009 16:41:24:921 GetShellProcessID() called
10/21/2009 16:41:24:937 KERNEL32LoadDLL called!
10/21/2009 16:41:24:937 EnumProcessesModules Failed: 299
10/21/2009 16:41:24:953 EnumProcessesModules Failed: 299
10/21/2009 16:41:24:953
Failed to find the process ID for : EXPLORER.EXE
Patrick Farrell
> Patrick Farrell,
>
>> Sorry it took so long on this, busy day..
>>
>> http://66.147.134.189/nallogs.zip
>>
>> Let me know if that's what you are looking for.
>
> Can you get a log of a working machine? I see the following error in
> nwgina.log that I suspect is the cause. (GUessing)
>
> 10/21/2009 16:41:24:921 GetShellProcessID() called
> 10/21/2009 16:41:24:937 KERNEL32LoadDLL called!
> 10/21/2009 16:41:24:937 EnumProcessesModules Failed: 299
> 10/21/2009 16:41:24:953 EnumProcessesModules Failed: 299
> 10/21/2009 16:41:24:953
> Failed to find the process ID for : EXPLORER.EXE
>
>
Sure, I can get one tomorrow. I noticed that too but I didn't know if
it was significant. Obviously explorer is running because I have a
desktop and start menu, so I'm not sure why it can't get the process ID.
Jared Jennings
>Sure, I can get one tomorrow. I noticed that too but I didn't know if it
>was significant. Obviously explorer is running because I have a desktop
>and start menu, so I'm not sure why it can't get the process ID.
No clue either. I didn't find any known bugs on it. An older version of
the agent doesn't have the issue correct?
Patrick Farrell
> Patrick Farrell,
>
>> Sure, I can get one tomorrow. I noticed that too but I didn't know if
>> it was significant. Obviously explorer is running because I have a
>> desktop and start menu, so I'm not sure why it can't get the process ID.
>
> No clue either. I didn't find any known bugs on it. An older version of
> the agent doesn't have the issue correct?
>
http://66.147.134.189/nalloggood.zip
That's a log off a working machine (with the new agent). It hasn't
broken yet.
I've probably used every publicly released agent from zen 4 up to
7sp1ir4hp1 and I've never seen this before on any of them.
Jared Jennings
>I have tried reinstalling the Desktop Management client, Novell Client,
>re-registering the workstation and clearing the NAL Cache. The only
>thing that fixes it is reloading Windows"
I am sure you will get help with the SR, but if you feel like it feel free
posting the debug logs from the workstation.
Patrick Farrell
> neil france,
>
>> I have tried reinstalling the Desktop Management client, Novell Client,
>> re-registering the workstation and clearing the NAL Cache. The only
>> thing that fixes it is reloading Windows"
>
> I am sure you will get help with the SR, but if you feel like it feel
> free posting the debug logs from the workstation.
>
Just remember, I've already claimed naming rights on the future patch
for this... zfd7sp1ir4hp1wtf1
Jared Jennings
>Just remember, I've already claimed naming rights on the future patch for
>this... zfd7sp1ir4hp1wtf1
Well I don't think the answer is coming from me. I think you need debug
files.
Jared Jennings
>Just remember, I've already claimed naming rights on the future patch for
>this... zfd7sp1ir4hp1wtf1
LOL
Patrick Farrell
> Patrick Farrell,
>
>> Just remember, I've already claimed naming rights on the future patch
>> for this... zfd7sp1ir4hp1wtf1
>
> Well I don't think the answer is coming from me. I think you need debug
> files.
>
How do I get that?
Jared Jennings
>
>How do I get that?
Open a SR <G>
Patrick Farrell
> Patrick Farrell,
>
>>
>> How do I get that?
>
> Open a SR <G>
You're confusing me with someone who has maintenance. I guess I'll wait
for the other guys SR to get resolved.
Jared Jennings
>You're confusing me with someone who has maintenance. I guess I'll wait
>for the other guys SR to get resolved.
In the mean time try using regmon or filemon from sysinternals.. Who
knows. <G>
Shaun Pond
you do know your SR was closed because you didn't respond?
--
Shaun Pond
Patrick Farrell
> Neil,
>
> you do know your SR was closed because you didn't respond?
>
I'm sure he doesn't. He sent me a PM indicating he's been unavailable
for a few weeks. I'll let him know in a reply. Can they re-open that
for him if he calls in?
Shaun Pond
sure - he need to phone, though
--
Shaun Pond
Patrick Farrell
> Patrick,
>
> sure - he need to phone, though
I sent him a note about it via pm in the web forums site.
Shaun Pond
OK
--
Shaun Pond
DE
Maybe same issue for Craig Wellman's unanswered post also (1 Oct)?
Patrick Farrell
> Maybe same issue for Craig Wellman's unanswered post also (1 Oct)?
If it's unanswered, does it really matter? :p
DE
<no response>
Patrick Farrell
To my knowledge the issue remains unsolved.