Invalid URL Syntax

When an email is sent through Cognos with a link to a Cognos report output, a message with 'Invalid URL syntax' is seen intermittently.

Multi-server environment with a stand alone Content Manager (no gateway URI field in Cognos Configuration).
Issue seen intermittently as it only fails when delivery done through Content Manager.
When delivery through Application Tier service, link works.
Depending on mail client, will either see 'Invalid URL syntax' or the link is simply not 'clickable'. If the URL is visible in the mail client, the server name (gateway) will be missing from the URL.

Cause

By default the Delivery Service is enabled on CM only and App Tier only installs.

When running a report and sending link via email, you must have saved output.

When the Delivery Service is enabled on CM and an email link is sent which points to saved content, you are not able to open the content via the link. There is no Gateway URI field in Cognos Configuration for a stand alone Content Manager and Content Manager is unaware of the gateway location. In Cognos Configuration for Application tier installations, there is a field in Cognos Configuration where the gateway URI is specified and the Application Tier is aware of the Gateway location.

Diagnosing the problem

If the URL is not clickable and the mail client allows you to see the actual URL, check to see if a server name (gateway) is specified in it. If not, it is likely due to the delivery service on the CM (which is unaware of the Gateway) being used.

Resolving the problem

Disable the Delivery Service on the Content Manager and have it active on the Application Tier(s) only.

Comments

Post a Comment

Popular posts from this blog

How can you extract all user information from Cognos Access Manager Namespace Report Utility and create Cognos Report out of it?

The AM_NamespaceReport Utility allows you to extract the namespace to an XML file. 1. Use the AM_NamespaceReport Utility to extract all users from the namespace to an XML file. am_namespacereport -h > -p > -r > -n > -D > -w > -f all -o > e.g am_namespacereport -h cognoscamsevr -p 4004 -r o=cognos.com –n devcam -D admin -w admin -f all -o c:\temp\usrlst.xml 2. This will extract all user information to an XML file 3. Import the xml file into XLS spread sheet 4. Create ODBC connection using the ms-excel spread sheet driver 5. Create Data Source Connection and proceed creating FM Model & Publish 6. Create Report using Report Studio. 7. Save & Share the report The Access Manager Administration Guide (Appendix A) contains further information on this functionality.
Read more

RSV-VAL-0032 expression is not valid. If the item exists in a query but is not referenced in the layout, add it to a property list. CRX-API-0005 An error ocurred at or near the position '0'.

Image
Problem: RSV-VAL-0032 The following expression is not valid: [AdjRowsReturned] = 0. If the item exists in a query but is not referenced in the layout, add it to a property list. CRX-API-0005 An error ocurred at or near the position '0'. The variable named '[AdjRowsReturned]' is invalid Resolution: You might have used the calculated data item in the variable, which needs to be added in the page properties. - Click on the page and go to properties. Make sure you see 'page' on the top of the properties. - Click on properties icon under data section, you'll get pop up icon - Check mark the data item which is used for variable calc. You are good to go.Find the snapshot. .
Read more

BME-EX-0047 Unable to read preferences for the requested interface..

Issue When opening or creating a Framework Manager project the following error message is shown. Additionally, when attempting to create or open a report based on a package is made in Report Studio or Query Studio, the same error message is shown. Error BME-EX-0047 Unable to read preferences for the requested interface. Please use another repository and/or ProjectAccess Interface. Resolving the problem This happens due to a corrupt bmt.ini file in <Install Location>/c8/configuration directory. This issue can be resolved by extracting bmt.ini from last known good backup or even from installation files.
Read more