Cognos ReportNetTM Installation and Configuration Guide

More documents

Recommendations

Info

Appendix B: Troubleshooting DPR-ERR-2022 and DPR-ERR-2058 Errors Appear in Web Browser When Starting the Web Portal After you start the services in Cognos Configuration and then try to open the portal, one of the following or similar messages may appear: DPR-ERR-2022 No response generated. This may be due to an incorrect configuration, a damaged installation, or the dispatcher not having finished initializing. DPR-ERR-2058 The dispatcher encountered an error while servicing a request. XTS handler must be initialized before being invoked. DPR-ERR-2058 The dispatcher cannot service the request at this time. The dispatcher is still initializing. This can occur if you try to open the portal before the ReportNet services are initialized. You can avoid these error messages. After you start the services in Cognos Configuration and the configuration tool shows that the services are running, wait a few minutes for all services to start before you open the portal. Report Link in Email Notification Does Not Work If a report link in an email notification does not work, the Gateway URI may not be configured correctly. You must change the host name portion of the Gateway URI from localhost to either the IP address of the computer or the computer name. If the URL in the email contains localhost, remote users cannot open the report. Unable to Uninstall Another Version of ReportNet Service on Windows You install ReportNet, but another version of the ReportNet service continues to run. You can install more than one instance of ReportNet in different locations on the same computer. If the instances use the same ports, the Installation wizard may not upgrade the service correctly. Cognos Configuration upgrades to the most recently configured service for ReportNet. You must manually remove the service. To see if the correct ReportNet service is running, check the version number in the About window in Cognos Configuration. Steps 1. Start Cognos Configuration. 2. From the Action menu, click Stop. 3. Open a Command Prompt window. 4. Go to the crn_location/bin directory. 5. Uninstall the service: • If you used the default name for the service, type cogbootstrapservice -u • If you specified another name, type cogbootstrapservice -u -name="crn_service_name" 6. Close the Command Prompt window. 7. Restart Cognos Configuration to upgrade to the correct service. 114 Cognos ReportNet TM
Appendix B: Troubleshooting Database Connectivity Errors When Running Reports You receive a database connectivity error (for example, Oracle service name could not be resolved) when you run a report. This may occur if the ReportNet server computer is not configured for connectivity with the query database computer. In a distributed environment, requests can be sent to any ReportNet server computer. You must install database API software on every ReportNet server and configure the servers identically, to access all defined data sources. Unable to Exit a Tab Sequence When Using Keyboard-Only Navigation in Cognos Configuration If you use the Tab key to navigate in Cognos Configuration, you may experience problems exiting a tab sequence. For example, in the Properties window, you can press the Tab key to move from one property to another. However, because Cognos Configuration is a Java application, when you want to close the Properties window, you must press Ctrl+Tab. PDF Report Does Not Print But Print Status Shows Succeeded You chose to Print the Report in PDF Format on a network printer using a Windows installation of ReportNet, but it did not print. When you start the ReportNet service using Cognos Configuration, the account under which ReporNet runs, usually the local system account, may not have access to network resources. If you use a network printer, you must either specify an account that has access to the printer or configure the ReportNet service so that it can access the printer. PDF Outputs Too Large Your chose to run PDF reports, but they are too large. By default, all fonts are embedded to ensure they display properly. More specifically, the minimum number of glyphs required from a given font are embedded. This may result in increased network resource consumption due to the size of the font information. To limit the number of embedded fonts to a specific list, you must manually edit and then rename a configuration file. If a font you have chosen not to embed does not display properly, you must either change the configuration to embed the font, or use a different font. Steps 1. Go to the crn_location/configuration directory. 2. Open the PdfDefaults.cps.noEmbed file in an editor. 3. If you want to add fonts to the current list of fonts to embed, which includes the Arial, Times New Roman, Courier New font families, add the font name to the list beside the dfltFontEmbeded property. For example, dfltFontEmbeded = "Arial;Times New Roman;Courier New;NewFont" Tip: Ensure each font family is separated by a semi-colon (;). 4. Change the default setting for the dfltUseEmbeded property, if required: • To embed all fonts, change the value to "0". • To embed only the fonts listed for the dfltFontEmbeded property, use the default value, "1". Installation and Configuration Guide 115
Page 1 and 2:
COGNOS (R) ENTERPRISE BUSINESS INTE
Page 3 and 4:
Table of Contents Introduction 7 Ad
Page 5 and 6:
Chapter 10: Uninstalling Cognos Rep
Page 7 and 8:
Introduction This document is avail
Page 9 and 10:
Additional Materials In this guide,
Page 11 and 12:
Chapter 1: ReportNet Before impleme
Page 13 and 14:
Chapter 1: ReportNet Installing Rep
Page 15 and 16:
Chapter 1: ReportNet Framework Mana
Page 17 and 18:
Chapter 2: Installing ReportNet on
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Chapter 4: Configuring ReportNet Af
Page 35 and 36:
Chapter 4: Configuring ReportNet St
Page 37 and 38:
Chapter 4: Configuring ReportNet 3.
Page 39 and 40:
Chapter 4: Configuring ReportNet Co
Page 41 and 42:
Chapter 4: Configuring ReportNet Wh
Page 43 and 44:
Chapter 4: Configuring ReportNet Th
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Chapter 4: Configuring ReportNet Ad
Page 57 and 58:
Chapter 4: Configuring ReportNet Ex
Page 59 and 60:
Chapter 4: Configuring ReportNet Sp
Page 61 and 62:
Page 63 and 64: Chapter 5: Installing Framework Man
Page 65 and 66: Chapter 5: Installing Framework Man
Page 67 and 68: Chapter 6: Configuring Framework Ma
Page 77 and 78: Chapter 7: Advanced Configuration O
Page 91 and 92: Chapter 8: Setting Up the Samples Y
Page 93 and 94: Chapter 8: Setting Up the Samples 7
Page 95 and 96: Chapter 8: Setting Up the Samples S
Page 97 and 98: Chapter 9: Setting Up an Unattended
Page 99 and 100: Chapter 9: Setting Up an Unattended
Page 101 and 102: Chapter 10: Uninstalling Cognos Rep
Page 103 and 104: Appendix A: Manually Configuring Re
Page 105 and 106: Appendix A: Manually Configuring Re
Page 107 and 108: Appendix B: Troubleshooting Use thi
Page 109 and 110: Appendix B: Troubleshooting Unable
Page 111 and 112: Appendix B: Troubleshooting For Con
Page 113: Appendix B: Troubleshooting 2. If y
Page 117 and 118: Appendix C: Database Schema for Log
Page 119 and 120: Appendix D: Database Clean Up Scrip
Page 121 and 122: Glossary anonymous access A method
Page 123 and 124: Glossary In Framework Manager, name
Page 125 and 126: Index A adding resources, 103 AIX e
Page 127 and 128: Index Framework Manager components,
Page 129 and 130: Index server administration logging
show all

Cognos ReportNetTM Installation and Configuration Guide

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?