Environment
Novell ZENworks 11 Configuration Management with ZCM 11 Cumulative Agent Patch 2a
Novell ZENworks 11 Configuration Management Support Pack 1 - ZCM 11 SP1 Bundles
Novell ZENworks 11 Configuration Management Support Pack 1 - ZCM 11 SP1 Bundles
Situation
Any bundle that is using a system requirement "file exists" fails.
The problem does not occur on devices using agents prior to ZCM 11 with Cumulative Agent Patch 2a
The problem does not occur on devices using agents prior to ZCM 11 with Cumulative Agent Patch 2a
Resolution
For ZCM 11.1:This is fixed in version 11.2 - see KB 7010044 "ZENworks Configuration Management 11.2 - update information and list of fixes" which can be found at https://www.novell.com/support
Workaround: if it is not possible to upgrade to 11.2 at this time, in the interim, Novell has made a Patch available for testing, in the form of a Field Test File (FTF): it can be obtained at https://download.novell.com/Download?buildid=sx157dy45_4~ as "ZCM 11.1/11.1a fix for "File exists" – see KB 7009330 and bundles not available for 5 minutes - see TID 7009945". This Patch should only be applied if the symptoms above are being experienced, and are causing problems.
For ZCM 11.0: A fix for this issue is intended to be included in a future update to the product: however, in the interim, , Novell has made a Patch available for testing, in the form of a Field Test File (FTF): it can be obtained at https://download.novell.com/Download?buildid=JMF_ucHev-M~ as "ZCM 11.0 - NAL fixes post-Cumulative Agent Patch 2a". This Patch should only be applied if the symptoms above are being experienced, and are causing problems.
This Patch has had limited testing, and should not be used in a production system without first being checked in a test environment. Some Patches have specific requirements for deployment, it is very important to follow any instructions in the readme at the download site. Please report any problems encountered when using this Patch, by using the feedback link on this TID.
Workaround: if it is not possible to upgrade to 11.2 at this time, in the interim, Novell has made a Patch available for testing, in the form of a Field Test File (FTF): it can be obtained at https://download.novell.com/Download?buildid=sx157dy45_4~ as "ZCM 11.1/11.1a fix for "File exists" – see KB 7009330 and bundles not available for 5 minutes - see TID 7009945". This Patch should only be applied if the symptoms above are being experienced, and are causing problems.
This Patch has had limited testing, and should not be used in a
production system without first being checked in a test environment.
Some Patches have specific requirements for deployment, it is very
important to follow any instructions in the readme at the download site.
Please report any problems encountered when using this Patch, by using
the feedback link on this TID.
For ZCM 11.0: A fix for this issue is intended to be included in a future update to the product: however, in the interim, , Novell has made a Patch available for testing, in the form of a Field Test File (FTF): it can be obtained at https://download.novell.com/Download?buildid=JMF_ucHev-M~ as "ZCM 11.0 - NAL fixes post-Cumulative Agent Patch 2a". This Patch should only be applied if the symptoms above are being experienced, and are causing problems.
This Patch has had limited testing, and should not be used in a production system without first being checked in a test environment. Some Patches have specific requirements for deployment, it is very important to follow any instructions in the readme at the download site. Please report any problems encountered when using this Patch, by using the feedback link on this TID.
Cause
The failure was due to the inability to parse macros like%ProgramFiles(x86)% (which has "(" in between two "%" characters).
Additional Information
The issue was due to incorrect regular expression to match Macro
values.
Allowed macro combinations:
1. Macros like ${MACRO_NAME}
2. Macros like %MACRO_NAME%
3. Macros like %%MACRO_NAME%%
4. All the above cases with some special characters like '(' in the macro name.
for e.g., %PROGRAMFILES(X86)%
Allowed macro combinations:
1. Macros like ${MACRO_NAME}
2. Macros like %MACRO_NAME%
3. Macros like %%MACRO_NAME%%
4. All the above cases with some special characters like '(' in the macro name.
for e.g., %PROGRAMFILES(X86)%