Report Studio -- attempting to run the report in any type of Excel format fails

A report runs without issue in HTML format but attempting to run the report in any type of Excel format fails.  A temporary solution is to restart the Cognos services.

Error Message:

CM-REQ-4034 An error occurred while reading or formatting data in a property value.

This can be caused if no cm folder exists in the <c8install>\temp directory.   You would have to manually create a folder called 'cm' under the Cognos 8 temp directory.  Using windows explorer navigate to the c8/temp directory.  Create a new folder under this temp directory called cm.

 

Report Studio -- attempting to run the report in any type of Excel format fails

A report runs without issue in HTML format but attempting to run the report in any type of Excel format fails.  A temporary solution is to restart the Cognos services.

Error Message:

CM-REQ-4034 An error occurred while reading or formatting data in a property value.

This can be caused if no cm folder exists in the <c8install>\temp directory.   You would have to manually create a folder called 'cm' under the Cognos 8 temp directory.  Using windows explorer navigate to the c8/temp directory.  Create a new folder under this temp directory called cm.

 

Links to Referenced Content Objects are Broken Following Deployment

After you import a deployment archive to a new location, some links for objects associated with reports do not work.  When you import content objects which contain references to other objects that are not in the target environment, these references are removed. For example, if you deploy an archive containing reports based on a metadata package that is not in the deployment archive or the target environment, then the links will remain broken even if the referenced object is subsequently created.

 

To solve this problem, try one of the following:

 

• Re-import your deployment package after the target objects have been created. The objects will be automatically linked

• Manually reconnect the links to an object. For more information about manually resetting links

 

Links to Referenced Content Objects are Broken Following Deployment

After you import a deployment archive to a new location, some links for objects associated with reports do not work.  When you import content objects which contain references to other objects that are not in the target environment, these references are removed. For example, if you deploy an archive containing reports based on a metadata package that is not in the deployment archive or the target environment, then the links will remain broken even if the referenced object is subsequently created.

 

To solve this problem, try one of the following:

 

• Re-import your deployment package after the target objects have been created. The objects will be automatically linked

• Manually reconnect the links to an object. For more information about manually resetting links

 

Lead Systems Analyst

latest Cognos opportunity

Lead Systems Analyst

latest Cognos opportunity

Cognos 8 -- Java Error When Starting Cognos Configuration

When you start Cognos Configuration, you may receive an error message that the Java Runtime Environment (JRE) has changed and that the current cryptographic information is not compatible with the new JRE. This may force you to be prompted to regenerate the cryptographic information for the new JRE or exit to switch back to the previous JRE.

This error may occur for one of these reasons:

• Your configuration data was encrypted using a different JRE than the one Cognos 8  components are currently using.

• The cryptographic information may have been corrupted.

If you click Regenerate in the error dialog, the Cognos 8 service is stopped and the cryptographic information is regenerated.

If you click Exit in the error dialog, you must set the JAVA_HOME environment variable to point to the JRE that you used to save your configuration.

On Windows, if you want Cognos 8 components to use the JRE that is installed by default, unset JAVA_HOME or set JAVA_HOME to c8_location/bin/jre.

Cognos 8 -- Java Error When Starting Cognos Configuration

When you start Cognos Configuration, you may receive an error message that the Java Runtime Environment (JRE) has changed and that the current cryptographic information is not compatible with the new JRE. This may force you to be prompted to regenerate the cryptographic information for the new JRE or exit to switch back to the previous JRE.

This error may occur for one of these reasons:

• Your configuration data was encrypted using a different JRE than the one Cognos 8  components are currently using.

• The cryptographic information may have been corrupted.

If you click Regenerate in the error dialog, the Cognos 8 service is stopped and the cryptographic information is regenerated.

If you click Exit in the error dialog, you must set the JAVA_HOME environment variable to point to the JRE that you used to save your configuration.

On Windows, if you want Cognos 8 components to use the JRE that is installed by default, unset JAVA_HOME or set JAVA_HOME to c8_location/bin/jre.

Cognos 8 -- Cognos Connection -- New user does not see any items

During your project maintenance cycle you may be requested to add in a new user to a group.  If the new user has issues with being able to view items in Cognos Connection then you should validate the permissions for the group to which they have just been added.

 

1. Log on to Cognos Connection as a system administrator.

2.

Click Directory.

3.

Click Set Properties next to the namespace.

4.

Click the Permissions tab.

5.

If it is not already there, add the Query Users group to the namespace.

6.

Click the check box for Query Users and ensure that Traverse permission is granted.

7.

Click Apply, and click OK.

8.

Test with a user.

Cognos 8 -- Cognos Connection -- New user does not see any items

During your project maintenance cycle you may be requested to add in a new user to a group.  If the new user has issues with being able to view items in Cognos Connection then you should validate the permissions for the group to which they have just been added.

 

1. Log on to Cognos Connection as a system administrator.

2.

Click Directory.

3.

Click Set Properties next to the namespace.

4.

Click the Permissions tab.

5.

If it is not already there, add the Query Users group to the namespace.

6.

Click the check box for Query Users and ensure that Traverse permission is granted.

7.

Click Apply, and click OK.

8.

Test with a user.

BI Centre April Newsletter

http://bicentrenewsletter.blogspot.com/

BI Centre April Newsletter

http://cognos8helpnewsletter.blogspot.com/

New Cognos resource posted!

http://cognosconsulting.blogspot.com/2008/03/cognos-data-warehouse-20080322-0001.html

New Cognos resource posted!

http://cognosconsulting.blogspot.com/2008/03/cognos-data-warehouse-20080322-0001.html

Did you check out the latest Cognos jobs?

http://c8jobs.blogspot.com/

Did you check out the latest Cognos jobs?

http://c8jobs.blogspot.com/

Cognos 8 -- Daylight Savings Time (DST)

Here is a discussion about resolving any issues related to the recent DST change.

DST INFO

Cognos 8 -- Daylight Savings Time (DST)

Here is a discussion about resolving any issues related to the recent DST change.

DST INFO

Cognos 8 -- Report Studio error with conditional variable

If there is a conditional variable that is based on a query item which is not displayed within the current container on the report layout then Cognos may generate an error message, such as "CRX-API-0005 An error on or around the position '0'".

This can be related to Cognos 8 optimizing a report's queries to eliminate unused data items from the resulting query's SQL or MDX. In order to include a query item on the layout without displaying the object you should try adding the query item to the properties of the container in the layout. This can be done by using the "Properties" property.

Steps:
Select the report object that has the conditional variable being used for formatting or any other object that the report author may be using with the conditional variable.

1. Use the control above the properties pane to navigate the ancestor objects from the layout. For a list report, select the List object. For a crosstab report, select the Crosstab Node Member.
2. Locate the Data section in the Properties pane for the List or Crosstab Node Member object.
3. Within the Data section, click on the elipses "..." next to the Properties entry.
4. Select the query item that is being used in the conditional variable expression.
5. Click OK to return to your report layout. The data item should now be available within the scope of your List or Crosstab Node when the report is executed.

If the error still appears when a data item is being used directly on the page without a query container such as a list or crosstab then similar steps can be taken to set the available query items at the Page level. To do so:

1. Select the Page object from the ancestor control after selecting any object in the page layout.
2. Set the Query property of the Page object to reference the query containing the required data item.
3. The list of available query items can now be set for the Page using the Properties entry in the Data section of the Page object properties.

Cognos 8 -- Report Studio error with conditional variable

If there is a conditional variable that is based on a query item which is not displayed within the current container on the report layout then Cognos may generate an error message, such as "CRX-API-0005 An error on or around the position '0'".

This can be related to Cognos 8 optimizing a report's queries to eliminate unused data items from the resulting query's SQL or MDX. In order to include a query item on the layout without displaying the object you should try adding the query item to the properties of the container in the layout. This can be done by using the "Properties" property.

Steps:
Select the report object that has the conditional variable being used for formatting or any other object that the report author may be using with the conditional variable.

1. Use the control above the properties pane to navigate the ancestor objects from the layout. For a list report, select the List object. For a crosstab report, select the Crosstab Node Member.
2. Locate the Data section in the Properties pane for the List or Crosstab Node Member object.
3. Within the Data section, click on the elipses "..." next to the Properties entry.
4. Select the query item that is being used in the conditional variable expression.
5. Click OK to return to your report layout. The data item should now be available within the scope of your List or Crosstab Node when the report is executed.

If the error still appears when a data item is being used directly on the page without a query container such as a list or crosstab then similar steps can be taken to set the available query items at the Page level. To do so:

1. Select the Page object from the ancestor control after selecting any object in the page layout.
2. Set the Query property of the Page object to reference the query containing the required data item.
3. The list of available query items can now be set for the Page using the Properties entry in the Data section of the Page object properties.

Cognos job posting update!

http://c8jobs.blogspot.com/2008/03/business-systems-project-manager.html

 

 

Cognos job posting update!

http://c8jobs.blogspot.com/2008/03/business-systems-project-manager.html

 

 

Cognos 8 Security

If you wanted to prevent users from inadvertently making modifications, while they are in the Cognos namespace then you can restrict 'write' access for all entries in a hierarchy to only Report Administrators.

Steps

1.

In Cognos Connection, locate the top-level folder in the hierarchy.

2.

In the Actions column, click the set properties button for the folder.

3.

In the set properties page, click the Permissions tab.

4.

Select the Override the access permissions acquired from the parent entry check box.

5.

Click Add, then click the Cognos namespace, and then select the check boxes next to all the

users, groups, or roles.

6.

Click the right-arrow button, then click OK.

7.

To grant Report Administrators write permission, select the Report Administrator check box,

select the grant write access check box, and click

Apply.

8.

To deny all other listed users, groups, or roles write permission, select the check boxes, click

the deny write access check box, and click

Apply.

9.

Select the Delete the access permissions of all child entries check box.

10.

Click OK.

 

This will allow only Report Administrators have write access to the content of the top-level folder and all its subfolders.

Cognos 8 Security

If you wanted to prevent users from inadvertently making modifications, while they are in the Cognos namespace then you can restrict 'write' access for all entries in a hierarchy to only Report Administrators.

Steps

1.

In Cognos Connection, locate the top-level folder in the hierarchy.

2.

In the Actions column, click the set properties button for the folder.

3.

In the set properties page, click the Permissions tab.

4.

Select the Override the access permissions acquired from the parent entry check box.

5.

Click Add, then click the Cognos namespace, and then select the check boxes next to all the

users, groups, or roles.

6.

Click the right-arrow button, then click OK.

7.

To grant Report Administrators write permission, select the Report Administrator check box,

select the grant write access check box, and click

Apply.

8.

To deny all other listed users, groups, or roles write permission, select the check boxes, click

the deny write access check box, and click

Apply.

9.

Select the Delete the access permissions of all child entries check box.

10.

Click OK.

 

This will allow only Report Administrators have write access to the content of the top-level folder and all its subfolders.