gmikels Absent Member.
Absent Member.
1807 views

Zen Explorer Configuration Policy Fails

After deploying Windows updates clients begin reporting errors related to the Zen Policy Manager:
Category: PolicyManager
ActionMan.HandlerNotFound: Could not find a Handler associated with the following type: launcher configuration policy.
Category: ActionManager
ActionMan.ActionContinueOnFailure: The action (ID:launcher configuration policy) failed due to the reason : launcher configuration policy, however the action is set to continue on failure.

We are running ZENworks Configuration Manager 11, and this problem has just began within the last week. We can still connect to devices in the console, and machines continue to have access to the Zenworks Explorer. However, there are machines where the Zen Explorer disappears. My concern is that this will become widespread, causing users to lose access to applications.

The following seems to correct the problem, but this fix isn't something that could be deployed. I'm also not sure what this is correcting.

• Open a command line, type “zac fsg –d” and hit Enter.
• Type “zac unr –f” and hit Enter.
• Delete the following files from %ProgramFiles(x86)%\Novell\ZENworks\conf\ if present:
o Devicedata
o Deviceguid
o Guid.txt
o *.sav
• Rename initial-web-service.bak in %ProgramFiles(x86)%\Novell\ZENworks\conf\ to initial-web-service
Labels (2)
0 Likes
4 Replies
Micro Focus Expert
Micro Focus Expert

Re: Zen Explorer Configuration Policy Fails

Most likely some type of cache corruption.
What version of the ZCM Agent? There have been a number of fixes for
cache related issues..........

On 2/24/2014 1:26 PM, gmikels wrote:
>
> After deploying Windows updates clients begin reporting errors related
> to the Zen Policy Manager:
> Category: PolicyManager
> ActionMan.HandlerNotFound: Could not find a Handler associated with the
> following type: launcher configuration policy.
> Category: ActionManager
> ActionMan.ActionContinueOnFailure: The action (ID:launcher
> configuration policy) failed due to the reason : launcher configuration
> policy, however the action is set to continue on failure.
>
> We are running ZENworks Configuration Manager 11, and this problem has
> just began within the last week. We can still connect to devices in the
> console, and machines continue to have access to the Zenworks Explorer.
> However, there are machines where the Zen Explorer disappears. My
> concern is that this will become widespread, causing users to lose
> access to applications.
>
> The following seems to correct the problem, but this fix isn't something
> that could be deployed. I'm also not sure what this is correcting.
>
> � Open a command line, type �zac fsg �d� and hit Enter.
> � Type �zac unr �f� and hit Enter.
> � Delete the following files from
> %ProgramFiles(x86)%\Novell\ZENworks\conf\ if present:
> o Devicedata
> o Deviceguid
> o Guid.txt
> o *.sav
> � Rename initial-web-service.bak in
> %ProgramFiles(x86)%\Novell\ZENworks\conf\ to initial-web-service
>
>



--
Craig Wilson - MCNE, MCSE, CCNA
Novell Technical Support Engineer

Novell does not officially monitor these forums.

Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.
0 Likes
shaunpond Absent Member.
Absent Member.

Re: Zen Explorer Configuration Policy Fails

Gmikels,

> ZENworks Configuration Manager 11


do you mean ZCM 11.0?

--

Shaun Pond
newly reminted as a Knowledge Professional


0 Likes
gmikels Absent Member.
Absent Member.

Re: Zen Explorer Configuration Policy Fails

Thanks for the quick response.

Yes ZCM 11.0. I'm looking at a client right now, and it's showing 11.0.0.41501 for the agent version.

I've tried 'zac cc' to clear the cache, which helps a lot of problems, but doesn't do anything for this one.
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Zen Explorer Configuration Policy Fails

That is an extremely old version.
ZCM 11.3 is scheduled to ship soon.
Possibly this week..........

I would recommend downloading and installing it in a LAB to learn how it
works. Then look at upgrading your deployment.

Version 11.0 is probably close to 2-3 years behind in patches at this
point in time.

On 2/24/2014 2:56 PM, gmikels wrote:
>
> Thanks for the quick response.
>
> Yes ZCM 11.0. I'm looking at a client right now, and it's showing
> 11.0.0.41501 for the agent version.
>
> I've tried 'zac cc' to clear the cache, which helps a lot of problems,
> but doesn't do anything for this one.
>
>



--
Craig Wilson - MCNE, MCSE, CCNA
Novell Technical Support Engineer

Novell does not officially monitor these forums.

Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.
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.