The information in this Readme includes the following:
The platforms that are supported in ZENworks Reporting 5 include the following:
Operating System Support
Windows Server 2003 SP2 x86_64 (Enterprise and Standard editions)
Windows Server 2003 R2 SP2 x86_64 (Enterprise and Standard editions)
Windows Server 2008 SP2 x86_64 (Enterprise and Standard editions)
Windows Server 2008 R2 x86_64 (Enterprise and Standard editions)
Windows Server 2008 R2 SP1 x86_64 (Enterprise and Standard editions)
Windows Server 2012 Server Standard x86_64 (Foundation, Essential, and Standard edition)
SUSE Linux Enterprise Server 10 (SLES 10) SP3/SP4 x86-_64 (Intel and AMD Opteron processors)
SLES 11 SP1/SP2/SP3 x86_64 (Intel and AMD Opteron processors)
SLES 11 SP2 and SP3 for VMware X86_64
Red Hat Enterprise Linux 5.8, 5.9, 6.3, and 6.4 x86_64
Red Hat Enterprise Linux 6.0/6.1/6.2 x86_64
Firefox ESR version 10 and 17
Firefox version 20, 22, and 23
Internet Explorer versions 8, 9, and 10
The following installation builds are available for download on the ZENworks 11 SP2 Web site:
ZENworks11SP2.iso: Download the full installation of ZENworks 11 SP2 from Novell Web site, if you have not installed ZENworks Configuration Management 11 SP2. For information on installing the build, see the .
zrs-resource.zip: Download the ZENworks resource file from from Novell Web site for ZENworks Reporting 5. This contains domain and reports for ZENworks Configuration Management 11.2.4.
Copy zrs-resource.zip to the ZENworks Configuration Management Primary Server in to the following location:
For Windows: %zenworks_home%\resources\zrs
For Linux: /opt/novell/zenworks/resources/zrs
ZENworks_Reporting_5.iso: Download the ZENworks Reporting installer files from Novell Web site, and extract on your device where you want to install ZENworks Reporting.
For information on installation, see the ZENworks Reporting 5 Installation Guide.
For all ZENworks 11 SP2 documentation, see Novell ZENworks 11 SP2 documentation Web site.
The languages that are supported in ZENworks Reporting 5 include the following:
For ZENworks Reporting Installer and ZENworks Reporting Configuration Tool
Chinese Simplified - zh_CN
Chinese Traditional - zh_TW
English - en
French - fr
German - de
Italian - it
Japanese - ja
Portuguese - pt
Spanish - es
ZENworks Reporting UI Console
Chinese Simplified - zh_CN
Chinese Traditional - zh_TW
English - en
French - fr
German - de
Italian - it
Japanese - ja
Romanian - ro
Spanish - es
IMPORTANT: In ZENworks Reporting 5 only English language is supported for Tool tips and reports or domain.
To replace the Novell logo, perform the following:
Launch .jrxml file.and open the
Click image (Novell logo) and go to properties.
In the image, change the path of the image, that needs to be replaced.
Replace the old .jrxml file with the modified .jrxml file.
Launch the report.
This section contains information about issues that might occur while you work with ZENworks Reporting 5:
Section 1.7.1, Unable to log in as an edirectory user in ZENworks Reporting
Section 1.7.2, Missing languages in the ZENworks Reporting installation wizard
Section 1.7.3, An error message is displayed if you filter the Input Control with the All option
Section 1.7.4, ZENworks Reporting administrator role not mapped to the nested groups
Section 1.7.5, Custom patches are not displayed correctly in the report
Section 1.7.6, The old and new XML values display incorrect data
Section 1.7.12, Measures does not provide the correct value in the Crosstab report
Section 1.7.13, Invalid Credentials Supplied error message is displayed
Section 1.7.15, Some of the Field data might not appear in the Crosstab report
Section 1.7.16, LDAP Organization Unit and User name with some Special characters are not accepted by the ZENworks Reporting Installer
Section 1.7.17, ZENworks Reporting Web Interface does not login for a user with no password
Section 1.7.18, Probable Cause of Enforcement Failure messages displaying incorrect data
Section 1.7.19, ZENworks Reporting install does not create the default Topics folder
Section 1.7.21, Custom report does not display complete data
Section 1.7.22, Crosstab report Totals of the measure fields with Distinct count does not match
Section 1.7.23, Dashboard with multiple reports does not load the data
Section 1.7.24, Error message appears while saving the Ad Hoc View, a report, or a Dashboard with special characters
Section 1.7.26, Using Prefilters in an Ad Hoc report sometimes displays an error
Section 1.7.27, LDAP Groups with special characters do not appear in ZENworks Reporting if the CLI method is used
Section 1.7.28, ZENworks Reporting Installer hangs if available space is low in the Windows drive
Section 1.7.29, Some reports might fail to generate due to a default limit
Section 1.7.30, Dashboard displays multiple reports with the same name
Section 1.7.31, Increasing the "crosstab.bucket.measure.limit" value makes the generated report export operation fail
Section 1.7.32, Some Ad Hoc View report create action keeps loading; the ZENworks Reporting create window does not time out
NOTE:In the ZENworks Reporting Solution, some strings are not localized.
You cannot log in as an edirectory user in ZENworks Reporting when eDirectory contains multiple user instances with the same user name.
In the ZENworks Reporting installation wizard, double byte languages that are supported by ZENworks Reporting are not displayed in the language drown-down on single byte device or vice-versa.
Workaround: Execute the ZENworks Reporting application by using the setup.sh -L <locale> command. The <locale> is code of the language (en_US - English, fr-French, it-Italian, es-Spanish, de-German, ro-Romanian, ja-Japanese, zh_TW-Chinese(Taiwan), and zh_CN-Chinese (China). For example, setup.sh -L fr to install in French.
In ZENworks Reporting, if you filter the Input Control, by using theoption, an error message is displayed as and a blank report is generated.
Workaround: Filter the Input Control, using theoption.
In the ZENworks Reporting installer or the ZENworks Reporting Configuration Tool, if you navigate to the Configure User Source wizard and map the parent group with administrator rights, nested groups that are under the parent group will not be mapped with administrator rights.
For example, a Finance group has the sub-groups, finance_account, finance_purchase, finance_administration and a finance_manager user. If the Finance group is selected, only the finance_manager user will have the mapped rights; none of the sub-groups will have these rights. The rights will not flow to the nested groups.
If you want to specify rights to nested groups, you must map these groups (finance_account, finance_purchase, and finance_administration) separately.
Workaround: Map the sub-groups separately.
Custom patches created from a bundle in the ZPM folder do not display correctly in the report. The original patch bundle gets associated with the bundle and instead of with the custom patch.
Thefield and the field display incorrect data for the event.
While creating an Ad Hoc report, unable to create a custom measure object by using a ZENworks Domain. ZENworks Reporting will not support custom measure on the measure objects for which aggregation function is Count or Distinct count.
When you choose theoption, an incorrect data count is displayed.
Unable to import resources in ZENworks Reporting, by using theoption ( ).
Workaround: Use the CLI mode to import resources.
To import Schedule jobs, specify the following --everything in the import command:
Open a command prompt.
Go to the following path:
For Windows: %ZRS_HOME%\js\buildomatic
For Linux: /opt/novell/zenworks-reporting/js/buildomatic
Run the following js-import –-input-zip “path” command.
Where “path” is the path of the exported zip file. You can use the following js-import –-input-zip “path” --update command to update your repository.
When you export any report in to DOCX or RTF formats then that report loses the format.
Workaround: Select other supported formats in ZENworks Reporting.
On a device if the Symantec Endpoint Protection installer is in progress and if you try to install ZENworks Reporting, it fails. ZENworks Reporting installer internally calls the VC++ library installer that causes the ZENworks Reporting installation failure.
Workaround: In a device do not install ZENworks Reporting, when Symantec Endpoint Protection installer is in progress.
When you create a Crosstab report by using ZENworks Audit Domain, some measures do not provide the correct value.
If you log in to ZENworks Reporting, when the LDAP server is down or not reachable, anerror message is displayed.
Workaround: Ignore the error message, and check whether the LDAP server is down or not reachable.
Themessage is displayed, while using ZENworks Reporting.
Workaround: Delete all the browser cookies specific to the ZENworks Reporting server.
When you create a Crosstab report by using ZENworks Audit Domain, some of the field data might not appear.
Active Directory allows to create Organization Unit and User name with some special characters. However, when the credentials are passed to the ZENworks Reporting installer (Wizard), it is prevented from proceeding further.
Workaround: Add “\” before special characters. For example, specify userfirstname,userlastname as userfirstname\,userlastname.
Some LDAP directories, such as NetIQ eDirectory, support creating a user without a password. However, logging in without a password is not supported in ZENworks Reporting.
Incorrect data is displayed in thecolumn, while creating a report by using field.
After installing ZENworks Reporting, thefolder is not created under ( ) by default.
Workaround: Manually create thefolder under .
If you exceed the limit (based on the database) while passing parameters value to query from the Input Controls panel, then an “” message is displayed.
Workaround: In thepanel, select the option, then click .
If you create a custom report, sometimes the report might not display complete data.
For example: If you run thepredefined report, and you create a custom report with the same fields used in predefined report, the data in these reports might not match.
Workaround: Increase the.
To increase the Ad Hoc Dataset Row Limit:
Increase the, then click .
On a Crosstab report, the Totals of the measure fields with a Distinct count does not match the actual sum.
Workaround: To match the Totals, you can also use theoption. To enable right click the and to .
If you create a Dashboard with multiple reports, the data for some reports might not be loaded.
Workaround: In the Dashboard, mouseover on the report for which the data is not loaded, then click.
If you save the Ad Hoc View, a report, or a dashboard by using special characters, an error message appears.
Workaround: It is recommended to create the Ad Hoc Views, reports and Dashboards only by using alphanumerics, and ‘-’, ‘_’ in special characters.
If you run a schedule job initially on the server, any subsequent jobs created (output report that have same name), or rerun of the same job, then subsequent iteration of the same job throws the following error message:. .
Workaround: In thepanel, under , select , or .
Sometimes while creating the Ad Hoc reports an error message appears as.
Workaround: When creating the Ad Hoc report, userather than .
When installing ZENworks reporting using the CLI method, if LDAP Groups in the configured LDAP server contain these characters (; , ( ) and [ ] ) then the groups do not appear in thepanel.
Workaround: The LDAP Groups which have that contain the characters indicated above can be configured as administrator groups by modifying the %ZRS_HOME%\js\apache-tomcat\webapps\jasperserver-pro\WEB-INF\applicationContext-multiTenancy-security.xml file.
Perform the following to configure the LDAP group as an administrator group:
Stop the server.
Backup the applicationContext-multiTenancy-security.xml file outside of ZENworks Reporting %ZRS_HOME%.
Open the file %ZRS_HOME%\js\apache-tomcat\webapps\jasperserver-pro\WEB-INF\applicationContext-multiTenancy-security.xml.
Go to the <property name="rootOrganizationRolesMap"> <map> node, then add an entry in the following format:
<entry><key><value> Name of the group which contains the listed special characters</value></key><value>ROLE_ADMINISTRATOR</value></entry>
Perform Step 4 to add more groups.
Restart the server.
When you are installing ZENworks Reporting, if the space available on Windows drive is low, the installer hangs.
Workaround: When installing ZENworks Reporting on any other drive, ensure that at least 2 GB space is available in the Windows drive.
When generating some of the Crosstab reports, a report might fail and display the following error:.
Workaround: Add more filters to reduce the output data. By default, the limit set by ZENworks Reporting measure is 100000.
Multiple reports with the same name might appear when creating a dashboard for ROLE_ADMINISTRATOR.
Workaround: Choose any report and create a dashboard.
Increasing the default value ofmakes the generated report export (pdf, Excel and so on) operation fail.
Workaround: By default, the limit set by ZENworks Reporting measure is 100000. If the number of records exceeds the default limit, the report fails to generate. Increasing the default ZENworks Reporting measure limit might able to generate the report. However, the export operation of the generated report might fail. Therefore, changing the default value is not recommended. Instead, increase the number of filters to reduce the output data.
Some Ad Hoc report create actions (such as a adding column, creating a filter, and so on) take a long time to complete or sometimes fail to complete the action. As a result, the specified operation does not time out.
Workaround: Refresh the browser.
Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please refer to the Novell International Trade Services Web page for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.
Copyright © 2013 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.
For Novell trademarks, see the Novell Trademark and Service Mark list.
All third-party trademarks are the property of their respective owners.