Purchase your Section 508 Compliance Support guide now!

Purchase your Section 508 Compliance Support guide now!

Cognos 8 -- scheduled entries

You can view entries of a specified status, such as pending, running, or failed. You can then permanently cancel entries that are running or pending, or delay the running of a pending report.  This can be useful when several reports are pending, but you need a specific entry to run immediately.  You can then cancel or suspend entries that are scheduled to run first.  You must have read, write, and traverse permissions for an entry to modify or cancel its schedule.  Traverse permission is used to access the status information from the entry or job history.

1.

In Cognos Connection, in the upper right corner, click Tools, Schedule Management.

2.

Click the Activity tab and select the filter options to apply.

3.

Click Apply.

A filtered list of entries appears.

4.

If you want to stop an entry that is currently running or pending, select the entry and click the cancel button. The entry will run again the next time it is scheduled to do so.

5.

If you want to temporarily prevent an entry that is pending from running, click the entry and click the suspend button. Entries that are currently running cannot be suspended. When you are ready to run the suspended entry, click the entry again and then click the release button.

Cognos 8 -- scheduled entries

You can view entries of a specified status, such as pending, running, or failed. You can then permanently cancel entries that are running or pending, or delay the running of a pending report.  This can be useful when several reports are pending, but you need a specific entry to run immediately.  You can then cancel or suspend entries that are scheduled to run first.  You must have read, write, and traverse permissions for an entry to modify or cancel its schedule.  Traverse permission is used to access the status information from the entry or job history.

1.

In Cognos Connection, in the upper right corner, click Tools, Schedule Management.

2.

Click the Activity tab and select the filter options to apply.

3.

Click Apply.

A filtered list of entries appears.

4.

If you want to stop an entry that is currently running or pending, select the entry and click the cancel button. The entry will run again the next time it is scheduled to do so.

5.

If you want to temporarily prevent an entry that is pending from running, click the entry and click the suspend button. Entries that are currently running cannot be suspended. When you are ready to run the suspended entry, click the entry again and then click the release button.

Cognos 8 -- Install Framework Manager

In order to install Framework Manager you use the installation wizard to copy all of the components to your computer.

1. If Cognos 8 is also installed on the Windows computer, stop the Cognos 8 service.
2. Insert the CD for your Cognos modeling product, and then open the installation menu.  The Welcome page of the installation wizard appears. If the Welcome page does not appear, in the win32 directory on the CD, double-click issetup.exe.
3. Select the language to use.
4. Follow the directions in the installation wizard.  Install Framework Manager to the same directory as other Cognos 8 components.  In order to ensure the security and integrity of Cognos 8, it is also important to protect the installation directory from unauthorized or inappropriate access. 
 
Before you can use Framework Manager, you must start the Cognos 8 service.

1. Start the Cognos 8 service.
2. From the Start menu, click Programs, Cognos 8, Framework Manager.  You may be prompted to upgrade if the model schema version is older than the currently supported version.

If you see the Welcome page of Framework Manager, your installation is working.

 

 

 

 

 

 

 

 

 

 

Cognos 8 -- Install Framework Manager

In order to install Framework Manager you use the installation wizard to copy all of the components to your computer.

1. If Cognos 8 is also installed on the Windows computer, stop the Cognos 8 service.
2. Insert the CD for your Cognos modeling product, and then open the installation menu.  The Welcome page of the installation wizard appears. If the Welcome page does not appear, in the win32 directory on the CD, double-click issetup.exe.
3. Select the language to use.
4. Follow the directions in the installation wizard.  Install Framework Manager to the same directory as other Cognos 8 components.  In order to ensure the security and integrity of Cognos 8, it is also important to protect the installation directory from unauthorized or inappropriate access. 
 
Before you can use Framework Manager, you must start the Cognos 8 service.

1. Start the Cognos 8 service.
2. From the Start menu, click Programs, Cognos 8, Framework Manager.  You may be prompted to upgrade if the model schema version is older than the currently supported version.

If you see the Welcome page of Framework Manager, your installation is working.

 

 

 

 

 

 

 

 

 

 

Cognos Report Studio issue with CSVs

Comma Separated Values (CSV) refers to text items separated by commas. CSV format, however, does not work well in countries where the decimal point is a comma. To make this feature more international, Query Studio uses tabs rather than commas to separate text values in CSV files. Cognos maintains the term CSV for its recognition value.

Cognos Report Studio issue with CSVs

Comma Separated Values (CSV) refers to text items separated by commas. CSV format, however, does not work well in countries where the decimal point is a comma. To make this feature more international, Query Studio uses tabs rather than commas to separate text values in CSV files. Cognos maintains the term CSV for its recognition value.

Cognos Query Studio Error

You apply a filter to a report item in Query Studio and get the following error message:
 
"A filter cannot be based on the selected report item."

This can occur if data items are imported from Framework Manager with no data type set.  To resolve this problem, in Framework Manager, select the item and set the data type to match the table item.
 

Cognos Query Studio Error

You apply a filter to a report item in Query Studio and get the following error message:
 
"A filter cannot be based on the selected report item."

This can occur if data items are imported from Framework Manager with no data type set.  To resolve this problem, in Framework Manager, select the item and set the data type to match the table item.
 

Cognos Authentication

The session information for an authenticated user in Cognos 8 is maintained in a passport. The passport contains one or more visas. A visa exists for each namespace in which the user is currently authenticated. The passport remains active for the duration of a session and has a configurable idle time-out setting.
 
Cognos 8 sets a session cookie in the user's browser that refers to the passport.  The process of authenticating a user in the Cognos 8 environment includes the following:

• Passport verification or creation
A passport is required to process all requests in the Cognos 8 environment. The passport is created for a user after the first successful authentication.
Named users must log on to one of the configured namespaces. The logon process depends on the authentication methods available for a namespace. For example, an LDAP namespace may be configured to prompt for a user ID and password, or to retrieve identity information for the user from an HTTP header variable.
 
• Creation of a passport visa
After a successful logon, a visa is created to hold the namespace-specific user information for the duration of a session. Users can have one visa per session for each namespace to which they successfully log on.
 

Cognos Authentication

The session information for an authenticated user in Cognos 8 is maintained in a passport. The passport contains one or more visas. A visa exists for each namespace in which the user is currently authenticated. The passport remains active for the duration of a session and has a configurable idle time-out setting.
 
Cognos 8 sets a session cookie in the user's browser that refers to the passport.  The process of authenticating a user in the Cognos 8 environment includes the following:

• Passport verification or creation
A passport is required to process all requests in the Cognos 8 environment. The passport is created for a user after the first successful authentication.
Named users must log on to one of the configured namespaces. The logon process depends on the authentication methods available for a namespace. For example, an LDAP namespace may be configured to prompt for a user ID and password, or to retrieve identity information for the user from an HTTP header variable.
 
• Creation of a passport visa
After a successful logon, a visa is created to hold the namespace-specific user information for the duration of a session. Users can have one visa per session for each namespace to which they successfully log on.
 

Cognos Connection -- specify the order of entries

You can specify the order of folders and entries in the Cognos Connection portal. You may decide to organize entries by level of usage and place entries that you use daily at the top of the list.  By default, existing entries are sorted alphabetically. Entries added after the order is specified are shown at the end of the list.  In order to specify the order of entries, you must have read and write permissions for all entries in the folder and read and traverse permissions for the folder containing the entries.
 
1. In Cognos Connection, click the tab you want.
2. Click the order button on the toolbar.
3. Select the entries in the Shown in default order list box and click the right-arrow button to move them to the Shown first list box. 
Note: You specify the order of folders and entries independently.
4. Click the Up, Down, To top, and To bottom links to move the folders and entries within the list.
5. Click OK.

Cognos Connection -- specify the order of entries

You can specify the order of folders and entries in the Cognos Connection portal. You may decide to organize entries by level of usage and place entries that you use daily at the top of the list.  By default, existing entries are sorted alphabetically. Entries added after the order is specified are shown at the end of the list.  In order to specify the order of entries, you must have read and write permissions for all entries in the folder and read and traverse permissions for the folder containing the entries.
 
1. In Cognos Connection, click the tab you want.
2. Click the order button on the toolbar.
3. Select the entries in the Shown in default order list box and click the right-arrow button to move them to the Shown first list box. 
Note: You specify the order of folders and entries independently.
4. Click the Up, Down, To top, and To bottom links to move the folders and entries within the list.
5. Click OK.

Cognos 8 -- The Report Output Contains Unexpected Prompt Values

The report output for a scheduled report or a report for which you have not been prompted for values shows unexpected results.  Another user may have modified the saved prompt values. If you have write access to a report and change the prompt values, those values are saved for everyone running the report after you.

To select different prompt values, you can run the report with options and select the check box next to Prompt for Values.  If you consistently use prompts that differ from the majority of users, create a report view of the report in your personal folders.

Cognos 8 -- The Report Output Contains Unexpected Prompt Values

The report output for a scheduled report or a report for which you have not been prompted for values shows unexpected results.  Another user may have modified the saved prompt values. If you have write access to a report and change the prompt values, those values are saved for everyone running the report after you.

To select different prompt values, you can run the report with options and select the check box next to Prompt for Values.  If you consistently use prompts that differ from the majority of users, create a report view of the report in your personal folders.

Cognos 8 -- Unable to Select Multiple Report Formats When Running a Report

When running a report with options, you cannot select multiple formats when the delivery option is to view the report.  Before selecting multiple formats on the Run with advanced options page, you must first change the Delivery option to Save the report, print it, or send an email.

Cognos 8 -- Unable to Select Multiple Report Formats When Running a Report

When running a report with options, you cannot select multiple formats when the delivery option is to view the report.  Before selecting multiple formats on the Run with advanced options page, you must first change the Delivery option to Save the report, print it, or send an email.

Cognos 8 SDK -- clearing the conversationContext

The first time a report is run the runOption for locale (RunOptionEnum.outputLocale) is set to "en-us". After the results have been obtained, the same report is run, but this time with the locale set to "fr-fr". The second report still uses the first locale ("en-us"). This also applies to other runOptions, for example RunOptionEnum.outputFormat.  This can be caused by the conversationContext from the first run being used for all subsequent run commands within the program. It has this session affinity to provide the query reuse functionality. 
 
You should clear the conversationContext prior to subsequent run commands.
 
Sample code:

  // Scrub the header to remove the conversation context.
  BiBusHeader bibus =
   (BiBusHeader) ((Stub)repService).getHeaderObject("", "biBusHeader");
  
  if (bibus != null)
  {
   if (bibus.getTracking() != null)
   {
    if (bibus.getTracking().getConversationContext() != null)
    {
     bibus.getTracking().setConversationContext(null);
    }
   }

  }

Cognos 8 SDK -- clearing the conversationContext

The first time a report is run the runOption for locale (RunOptionEnum.outputLocale) is set to "en-us". After the results have been obtained, the same report is run, but this time with the locale set to "fr-fr". The second report still uses the first locale ("en-us"). This also applies to other runOptions, for example RunOptionEnum.outputFormat.  This can be caused by the conversationContext from the first run being used for all subsequent run commands within the program. It has this session affinity to provide the query reuse functionality. 
 
You should clear the conversationContext prior to subsequent run commands.
 
Sample code:

  // Scrub the header to remove the conversation context.
  BiBusHeader bibus =
   (BiBusHeader) ((Stub)repService).getHeaderObject("", "biBusHeader");
  
  if (bibus != null)
  {
   if (bibus.getTracking() != null)
   {
    if (bibus.getTracking().getConversationContext() != null)
    {
     bibus.getTracking().setConversationContext(null);
    }
   }

  }

Cognos 8 SDK -- conversation context

The conversation context defines the class for the state information of each asynchronous operation. Information contained by instances of this class is used by the dispatcher to properly route requests in the same asynchronous operation to the appropriate Simple Object Access Protocol (SOAP) node.

If it is not empty, it will cause the report server to associate some other queries that resulted to "not found" failure.  

            static void setUpHeader( reportService1 c8RS, string user, string pass, string name )

            {

                  // Scrub the header to remove the conversation context.

                  if( c8RS.biBusHeaderValue != null )

                  {

                        if( c8RS.biBusHeaderValue.tracking != null )                     

                              if( c8RS.biBusHeaderValue.tracking.conversationContext != null )                            

                                    c8RS.biBusHeaderValue.tracking.conversationContext = null;                                          

                        return;

                  }

                                    ……

                        }

Cognos 8 SDK -- conversation context

The conversation context defines the class for the state information of each asynchronous operation. Information contained by instances of this class is used by the dispatcher to properly route requests in the same asynchronous operation to the appropriate Simple Object Access Protocol (SOAP) node.

If it is not empty, it will cause the report server to associate some other queries that resulted to "not found" failure.  

            static void setUpHeader( reportService1 c8RS, string user, string pass, string name )

            {

                  // Scrub the header to remove the conversation context.

                  if( c8RS.biBusHeaderValue != null )

                  {

                        if( c8RS.biBusHeaderValue.tracking != null )                     

                              if( c8RS.biBusHeaderValue.tracking.conversationContext != null )                            

                                    c8RS.biBusHeaderValue.tracking.conversationContext = null;                                          

                        return;

                  }

                                    ……

                        }

Cognos 8 -- Framework Manager SPROCs

Here are the steps in order to create a Framework Manager query subject that uses prompts.
 
1. Create a stored procedure query subject that uses the sp_FIND_ORDER_DATE stored procedure.

The Query Subject Definition dialog box appears.

2. On the Definition tab, select the @order_number argument, and click the ellipsis (...) button.

3. In the Value box, type the following macro syntax and then click OK:

#(prompt('Order Number','integer'))#

Note: Framework Manager removes anything that is outside the number signs when running the macro.

4. To test the prompt for the variable, click the Test tab, and then click Test Sample.

The Prompt Values dialog box appears.

5. In the Name column, click Order Number.

6. In the Value field, type 1234 and click OK.

One record is returned, showing the date for Order Number 1234.  Framework Manager uses this value for the duration of the current session or until you clear the prompt value.

7. Click OK.

Cognos 8 -- Framework Manager SPROCs

Here are the steps in order to create a Framework Manager query subject that uses prompts.
 
1. Create a stored procedure query subject that uses the sp_FIND_ORDER_DATE stored procedure.

The Query Subject Definition dialog box appears.

2. On the Definition tab, select the @order_number argument, and click the ellipsis (...) button.

3. In the Value box, type the following macro syntax and then click OK:

#(prompt('Order Number','integer'))#

Note: Framework Manager removes anything that is outside the number signs when running the macro.

4. To test the prompt for the variable, click the Test tab, and then click Test Sample.

The Prompt Values dialog box appears.

5. In the Name column, click Order Number.

6. In the Value field, type 1234 and click OK.

One record is returned, showing the date for Order Number 1234.  Framework Manager uses this value for the duration of the current session or until you clear the prompt value.

7. Click OK.

Cognos 8 -- Setting up a Multilingual Reporting Environment

Here is the process for creating a multilingual reporting environment:

Use multilingual metadata.
The data source administrator can store multilingual data in either individual tables, rows, or columns. 
 
Create a multilingual model.

Modelers use Framework Manager to add multilingual metadata to the model from any data source type except OLAP. They add multilingual metadata by defining which languages the model supports, translating text strings in the model for things such as object names and descriptions, and defining which languages are exported in each package. If the data source contains multilingual data, modelers can define queries that retrieve data in the default language for the report user.

Create multilingual maps.

Administrators and modelers use a Windows utility named Map Manager to import maps and update labels for maps in Report Studio. For map features such as country and city names, administrators and modelers can define alternative names to provide multilingual versions of text that appears on the map.

Create a multilingual report.

The report author uses Report Studio to create a report that can be viewed in different languages. For example, the report author can specify that text, such as the title, appears in German when the report is opened by a German user. Report authors can also add translations for text objects, and create other language-dependent objects.

Specify the language in which a report is viewed.

You can use Cognos Connection to do the following:

• Define multilingual properties, such as a name, screen tip, and description, for each entry in the portal.

• Specify the default language to be used when a report is run.

Cognos 8 -- Setting up a Multilingual Reporting Environment

Here is the process for creating a multilingual reporting environment:

Use multilingual metadata.
The data source administrator can store multilingual data in either individual tables, rows, or columns. 
 
Create a multilingual model.

Modelers use Framework Manager to add multilingual metadata to the model from any data source type except OLAP. They add multilingual metadata by defining which languages the model supports, translating text strings in the model for things such as object names and descriptions, and defining which languages are exported in each package. If the data source contains multilingual data, modelers can define queries that retrieve data in the default language for the report user.

Create multilingual maps.

Administrators and modelers use a Windows utility named Map Manager to import maps and update labels for maps in Report Studio. For map features such as country and city names, administrators and modelers can define alternative names to provide multilingual versions of text that appears on the map.

Create a multilingual report.

The report author uses Report Studio to create a report that can be viewed in different languages. For example, the report author can specify that text, such as the title, appears in German when the report is opened by a German user. Report authors can also add translations for text objects, and create other language-dependent objects.

Specify the language in which a report is viewed.

You can use Cognos Connection to do the following:

• Define multilingual properties, such as a name, screen tip, and description, for each entry in the portal.

• Specify the default language to be used when a report is run.

Cognos 8 -- Report Studio Does Not Start

You may not be able to start Report Studio if you are using pop-up blocking software on your computer.  When you start Report Studio, it opens in a new browser window. In addition, a new browser window opens when you run a report and when an error is detected.

To correct the problem, disable any pop-up blocking software when working in Report Studio.

Cognos 8 -- Report Studio Does Not Start

You may not be able to start Report Studio if you are using pop-up blocking software on your computer.  When you start Report Studio, it opens in a new browser window. In addition, a new browser window opens when you run a report and when an error is detected.

To correct the problem, disable any pop-up blocking software when working in Report Studio.

CFG-ERR-0106 Error When Starting the Cognos 8 Service in Cognos Configuration

CFG-ERR-0106 Error When Starting the Cognos 8 Service in Cognos Configuration

When you start the Cognos 8 service, you may receive the following error message:

CFG-ERR-0106 Cognos Configuration received no response from the Cognos 8 service in the

allotted time

. Check that Cognos 8 service is available and properly configured.

There are two possible causes for this problem:

• The Cognos 8 service needs more time to start.

• A standby Content Manager computer may be configured incorrectly.

The Cognos 8 Service Needs More Time

By default, Cognos Configuration checks the progress of the start request every half second for three minutes. If Cognos Configuration does not receive a response within this time, the error message appears.

To avoid this error, you can change the amount of time that Cognos Configuration waits to receive a response from the Cognos 8 service. You do this by configuring the ServiceWaitInterval and ServiceMaxTries properties in the

c8_location/configuration/cogconfig.prefs file.
The ServiceWaitInterval property represents the time interval, in milliseconds, at which Cognos Configuration checks the progress of the start request. By default, its value is 500, which is equivalent to half a second.  The ServiceMaxTries property represents the number of times that Cognos Configuration checks the progress of the start request. By default, its value is 360.
 

Content Manager Is Configured Incorrectly

If the error message appears on a standby Content Manager computer, the setting for storing the symmetric keys may be incorrect.  To avoid this problem, configure the standby Content Manager computer to store the symmetric keys locally.

Steps to Change the Wait Time

1.

Using Cognos Configuration, stop the Cognos 8 service.

2.

Open the c8_location/configuration/cogconfig.prefs file in an editor.  This file is created automatically the first time you open Cognos Configuration.

3.

Add the following code to the file:

ServiceWaitInterval=

number of milliseconds

ServiceMaxTries=

number of times

Tip:

Add the numeric values that correspond to your configuration needs.

4.

Save the file.

5.

Using Cognos Configuration, start the Cognos 8 service.

Steps to Store Symmetric Keys Locally

1.

On the standby Content Manager computer, start Cognos Configuration.

2.

In the Explorer window, under Security, click Cryptography.

3.

In the Properties window, under CSK settings, set Store symmetric key locally to True.

4.

From the File menu, click Save.

5.

From the Actions menu, click Start.

This action starts all installed services that are not running. If you want to start a particular service, select the service node in the

Explorer window and then click Start from the Actions menu.

CFG-ERR-0106 Error When Starting the Cognos 8 Service in Cognos Configuration

CFG-ERR-0106 Error When Starting the Cognos 8 Service in Cognos Configuration

When you start the Cognos 8 service, you may receive the following error message:

CFG-ERR-0106 Cognos Configuration received no response from the Cognos 8 service in the

allotted time

. Check that Cognos 8 service is available and properly configured.

There are two possible causes for this problem:

• The Cognos 8 service needs more time to start.

• A standby Content Manager computer may be configured incorrectly.

The Cognos 8 Service Needs More Time

By default, Cognos Configuration checks the progress of the start request every half second for three minutes. If Cognos Configuration does not receive a response within this time, the error message appears.

To avoid this error, you can change the amount of time that Cognos Configuration waits to receive a response from the Cognos 8 service. You do this by configuring the ServiceWaitInterval and ServiceMaxTries properties in the

c8_location/configuration/cogconfig.prefs file.
The ServiceWaitInterval property represents the time interval, in milliseconds, at which Cognos Configuration checks the progress of the start request. By default, its value is 500, which is equivalent to half a second.  The ServiceMaxTries property represents the number of times that Cognos Configuration checks the progress of the start request. By default, its value is 360.
 

Content Manager Is Configured Incorrectly

If the error message appears on a standby Content Manager computer, the setting for storing the symmetric keys may be incorrect.  To avoid this problem, configure the standby Content Manager computer to store the symmetric keys locally.

Steps to Change the Wait Time

1.

Using Cognos Configuration, stop the Cognos 8 service.

2.

Open the c8_location/configuration/cogconfig.prefs file in an editor.  This file is created automatically the first time you open Cognos Configuration.

3.

Add the following code to the file:

ServiceWaitInterval=

number of milliseconds

ServiceMaxTries=

number of times

Tip:

Add the numeric values that correspond to your configuration needs.

4.

Save the file.

5.

Using Cognos Configuration, start the Cognos 8 service.

Steps to Store Symmetric Keys Locally

1.

On the standby Content Manager computer, start Cognos Configuration.

2.

In the Explorer window, under Security, click Cryptography.

3.

In the Properties window, under CSK settings, set Store symmetric key locally to True.

4.

From the File menu, click Save.

5.

From the Actions menu, click Start.

This action starts all installed services that are not running. If you want to start a particular service, select the service node in the

Explorer window and then click Start from the Actions menu.

Cognos 8 SDK error messages

RSV-DST-0012

An error occured while saving the output for the burst instance <param index="1" type="string"/>

with the recipients (<param index="2" type="string"/>). Here are the details: <param index="3"

type="string"/>

The most likely cause is that the burst recipient list contains an invalid recipient. For more information, see the details. If the problem is recipient related, correct the report or update the data in the database to generate valid recipients

RSV-PMG-0000

Parameter '<param type="string" index="1"/>' cannot cascade on itself.

One of the prompt controls associated with the parameter cascades on itself. Remove the self-referential cascade from that prompt control or change the cascade parameter.

RSV-PMG-0001

There is a cyclic condition in the cascading prompt setup relating to parameter '<param type="string" index="1"/>'. This cyclic condition is not allowed.

One of the prompt controls associated with the parameter specifies a cascade that results in a cyclical cascade. Remove the cascade from that prompt control or change the cascade parameter.

RSV-QM-0002

Bursting is not allowed on charts.

Modify the report so that the burst query is not used as a query for a chart.

RSV-QM-0003

Bursting is not allowed on crosstabs.

Modify the report so that the burst query is not used as a query for a crosstab.

Cognos 8 SDK error messages

RSV-DST-0012

An error occured while saving the output for the burst instance <param index="1" type="string"/>

with the recipients (<param index="2" type="string"/>). Here are the details: <param index="3"

type="string"/>

The most likely cause is that the burst recipient list contains an invalid recipient. For more information, see the details. If the problem is recipient related, correct the report or update the data in the database to generate valid recipients

RSV-PMG-0000

Parameter '<param type="string" index="1"/>' cannot cascade on itself.

One of the prompt controls associated with the parameter cascades on itself. Remove the self-referential cascade from that prompt control or change the cascade parameter.

RSV-PMG-0001

There is a cyclic condition in the cascading prompt setup relating to parameter '<param type="string" index="1"/>'. This cyclic condition is not allowed.

One of the prompt controls associated with the parameter specifies a cascade that results in a cyclical cascade. Remove the cascade from that prompt control or change the cascade parameter.

RSV-QM-0002

Bursting is not allowed on charts.

Modify the report so that the burst query is not used as a query for a chart.

RSV-QM-0003

Bursting is not allowed on crosstabs.

Modify the report so that the burst query is not used as a query for a crosstab.

Cognos and .NET

You should review this section in the Architecture and Planning Guide.
 
Microsoft .NET Framework allows managed-code applications to interact with server-based applications through the use of Web services. Cognos 8 uses Microsoft .NET Framework to enable users' computers to interact with Cognos 8 server components for access to Cognos Office Connection and its features.

Cognos Office Connection is a managed-code application that takes advantage of the Microsoft .NET Framework. Cognos Office Connection functions like an Office plug-in, but is installed, configured, and deployed as a managed-code application. For Excel 2003 which provides full support for managed-code applications, no Cognos software is installed on the Client machine.

For older versions of Office, an .msi is provided that creates a COM wrapper that enables the .NET software to run.  Cognos Office Connection is installed on the Cognos 8 server. To configure and deploy Cognos Office Connection for your Microsoft Office users, you must ensure that the .NET Framework is installed on the Client machines and that the .NET Run-time security policy has been configured to trust the Cognos Office Connection managed-code that resides on the Cognos 8 server. The .NET Framework and the run-time security policy is a Client requirement. .NET is not required on your Cognos 8 server, and you can install and run Cognos Office Connection on any supported Cognos 8 server platform.

Configuring Cognos Office Connection consists of setting a property in an Excel or PowerPoint template that points to the Cognos 8 server. Deploying Cognos Office Connection can be as simple as emailing this configured template to your Microsoft users who have the required .NET pre-requisites on their Client machines. After the template is saved and opened on a Client machine with the .NET pre-requisites, Cognos Office Connection establishes a connection to the Cognos 8 server using .NET and the code is loaded at run-time on the Client machine. Users are authenticated using their Cognos 8 authentication and can then browse, run, import, or refresh reports that they have access to in their Cognos Connection folders. From Office Connection, they can also publish saved Office documents to Cognos Connection to share them with other users.

For information about configuring this trust, see the

Installation and Configuration Guide.

In addition to the client computers, Microsoft .NET Framework must be installed on the Cognos 8 Web server computer and the Cognos 8 application server computer. You do not need to configure trust on the Cognos 8 application server computers unless you want to run Cognos Office Connection on them.

Cognos and .NET

You should review this section in the Architecture and Planning Guide.
 
Microsoft .NET Framework allows managed-code applications to interact with server-based applications through the use of Web services. Cognos 8 uses Microsoft .NET Framework to enable users' computers to interact with Cognos 8 server components for access to Cognos Office Connection and its features.

Cognos Office Connection is a managed-code application that takes advantage of the Microsoft .NET Framework. Cognos Office Connection functions like an Office plug-in, but is installed, configured, and deployed as a managed-code application. For Excel 2003 which provides full support for managed-code applications, no Cognos software is installed on the Client machine.

For older versions of Office, an .msi is provided that creates a COM wrapper that enables the .NET software to run.  Cognos Office Connection is installed on the Cognos 8 server. To configure and deploy Cognos Office Connection for your Microsoft Office users, you must ensure that the .NET Framework is installed on the Client machines and that the .NET Run-time security policy has been configured to trust the Cognos Office Connection managed-code that resides on the Cognos 8 server. The .NET Framework and the run-time security policy is a Client requirement. .NET is not required on your Cognos 8 server, and you can install and run Cognos Office Connection on any supported Cognos 8 server platform.

Configuring Cognos Office Connection consists of setting a property in an Excel or PowerPoint template that points to the Cognos 8 server. Deploying Cognos Office Connection can be as simple as emailing this configured template to your Microsoft users who have the required .NET pre-requisites on their Client machines. After the template is saved and opened on a Client machine with the .NET pre-requisites, Cognos Office Connection establishes a connection to the Cognos 8 server using .NET and the code is loaded at run-time on the Client machine. Users are authenticated using their Cognos 8 authentication and can then browse, run, import, or refresh reports that they have access to in their Cognos Connection folders. From Office Connection, they can also publish saved Office documents to Cognos Connection to share them with other users.

For information about configuring this trust, see the

Installation and Configuration Guide.

In addition to the client computers, Microsoft .NET Framework must be installed on the Cognos 8 Web server computer and the Cognos 8 application server computer. You do not need to configure trust on the Cognos 8 application server computers unless you want to run Cognos Office Connection on them.

Cognos Connection -- DPR-ERR-2079 Firewall security rejection. Your request was rejected by the firewall

This error can occur when running a report in Report Studio, however running the report from Cognos Connection does not cause the error.
 
This can be caused by accessing the Cognos portal with an incorrect URI IP address.  In order to resolve the issue you should try and use the IP value that is set in the gateway URI within Cognos Configuration.

Cognos Connection -- DPR-ERR-2079 Firewall security rejection. Your request was rejected by the firewall

This error can occur when running a report in Report Studio, however running the report from Cognos Connection does not cause the error.
 
This can be caused by accessing the Cognos portal with an incorrect URI IP address.  In order to resolve the issue you should try and use the IP value that is set in the gateway URI within Cognos Configuration.

Report Studio -- Error RSV-SRV-0025 when running a crosstab report

Intermittent error encountered when executing a cross tab report.

Error Message:

QE-DEF-0425 Exception was encountered while building the cube

RSV-SRV-0025 Unable to execute this request


The maximum size for a measure in a crosstab and chart is 19 digits. You can use the maximum of 19 integer with 0 decimal precision. The default decimal precision is 7, so 100000000000 works but 1000000000000 would generate the error.  If default precision is already been set properly, increase the cgi script timeouts on the web server.

Steps:

1. Open CQEConfig.xml file from <crn install>\configuration in a text editor. If the has an extension .sample, please rename it to CQEConfig.xml.

2. Change the following line:

<entry name="crosstabDecimalPrecision" value="7"/>

to

<entry name="crosstabDecimalPrecision" value="4"/>

Note: The value="4" may be set lower if needed.

Report Studio -- Error RSV-SRV-0025 when running a crosstab report

Intermittent error encountered when executing a cross tab report.

Error Message:

QE-DEF-0425 Exception was encountered while building the cube

RSV-SRV-0025 Unable to execute this request


The maximum size for a measure in a crosstab and chart is 19 digits. You can use the maximum of 19 integer with 0 decimal precision. The default decimal precision is 7, so 100000000000 works but 1000000000000 would generate the error.  If default precision is already been set properly, increase the cgi script timeouts on the web server.

Steps:

1. Open CQEConfig.xml file from <crn install>\configuration in a text editor. If the has an extension .sample, please rename it to CQEConfig.xml.

2. Change the following line:

<entry name="crosstabDecimalPrecision" value="7"/>

to

<entry name="crosstabDecimalPrecision" value="4"/>

Note: The value="4" may be set lower if needed.