COC-ERR-2005 The Import Failed
An unknown issue caused the import of report content to fail or the value for CognosGateway0 is not correct. Another possibility is that the logon requirements for Cognos 8 are not available. You may already be logged onto this namespace, or the target namespace does not exist.
First, check the value of CognosGateway0. If this is correct, check that your report uses standard practices. Revise and resave the report, ensuring that text and images are not located in the same cell.
COC-ERR-2013 This Is an Unsupported Office Application
Cognos 8 Go! Office supports the following Microsoft Office applications: Microsoft Office Excel 2003 (Professional or Standard), Microsoft Office Excel XP, Microsoft Office Word 2003 (Professional or Standard), Microsoft Office Word XP, Microsoft Office PowerPoint 2003, and Microsoft Office PowerPoint XP. You cannot load Cognos 8 Go! Office content to another
Microsoft Office application, such as Microsoft Access even when there is an add-in that enables these applications to interoperate.
Load the report content into one of the supported applications and environments.
COC-ERR-2005 The Import Failed
An unknown issue caused the import of report content to fail or the value for CognosGateway0 is not correct. Another possibility is that the logon requirements for Cognos 8 are not available. You may already be logged onto this namespace, or the target namespace does not exist.
First, check the value of CognosGateway0. If this is correct, check that your report uses standard practices. Revise and resave the report, ensuring that text and images are not located in the same cell.
COC-ERR-2013 This Is an Unsupported Office Application
Cognos 8 Go! Office supports the following Microsoft Office applications: Microsoft Office Excel 2003 (Professional or Standard), Microsoft Office Excel XP, Microsoft Office Word 2003 (Professional or Standard), Microsoft Office Word XP, Microsoft Office PowerPoint 2003, and Microsoft Office PowerPoint XP. You cannot load Cognos 8 Go! Office content to another
Microsoft Office application, such as Microsoft Access even when there is an add-in that enables these applications to interoperate.
Load the report content into one of the supported applications and environments.
Prompt to Change Passwords When Logging On to an Active Directory Security
When logging on to Cognos 8 using a Microsoft Active Directory security source, the submitted password is recognized as expired and you are prompted to change it. This occurs even if the password should still be valid. If the password is successfully changed, the behavior still occurs.
The following error message appears:
Your password has expired
. Please change it. Please type your credentials for authentication.The solution is to set up the authority for delegated administration for Cognos 8. Ensure that the server name or named account for starting the Cognos 8 service is set up in the Active Directory properties as an authority for delegated administration. Without these permissions, Cognos 8 is unable to read all user properties from the Active Directory server.
Prompt to Change Passwords When Logging On to an Active Directory Security
When logging on to Cognos 8 using a Microsoft Active Directory security source, the submitted password is recognized as expired and you are prompted to change it. This occurs even if the password should still be valid. If the password is successfully changed, the behavior still occurs.
The following error message appears:
Your password has expired
. Please change it. Please type your credentials for authentication.The solution is to set up the authority for delegated administration for Cognos 8. Ensure that the server name or named account for starting the Cognos 8 service is set up in the Active Directory properties as an authority for delegated administration. Without these permissions, Cognos 8 is unable to read all user properties from the Active Directory server.
Error Messages in SAP Log When Using Data Manager
the SAP log:
DATASET_CANT_CLOSE
To resolve this problem, on computers where you have Data Manager components installed,
create a system level environment variable named SAPCOMPRESSION and set the value to OFF.
Access to Entries is Denied During Deployment
If you deploy data using the Reports Administrator role, access to security entries may be denied.
By default, the Reports Administrator role does not have write access to the Cognos namespace.
Before you deploy, modify the permissions of this role to ensure that it has read and write permissions to the Cognos namespace.
Error Messages in SAP Log When Using Data Manager
the SAP log:
DATASET_CANT_CLOSE
To resolve this problem, on computers where you have Data Manager components installed,
create a system level environment variable named SAPCOMPRESSION and set the value to OFF.
Access to Entries is Denied During Deployment
If you deploy data using the Reports Administrator role, access to security entries may be denied.
By default, the Reports Administrator role does not have write access to the Cognos namespace.
Before you deploy, modify the permissions of this role to ensure that it has read and write permissions to the Cognos namespace.
Cognos 8 for Microsoft Office
General Known Issues 1. bo:heap Buffer Overflow Error After long sessions, Microsoft Office may stop responding by generating a bo:heap Buffer Overflow error. This error may be falsely identified as a potential virus by some virus-monitoring programs. #557292 2. Cognos 8 Go! Office workbook references to reports might not refresh properly after the reports are upgraded to version 8.2 Cognos 8 Go! Office-enabled workbooks that reference reports from a version 8.1 Cognos 8 server may not refresh properly after the reports are upgraded to Cognos 8 version 8.2. Objects in the report may have the name attribute modified by the report upgrade procedures. When the workbook is refreshed, the object is not updated, data is missing, and no error is reported. To rectify this situation, you must install the Cognos 8 version 8.2 server hotsite that fixes the report upgrade procedure. After you rerun the report upgrade procedure from 8.1 to 8.2, the workbooks are refreshed correctly. Alternately, you can recreate the workbook references to the reports that are not updated. #569301 3. Prompted to log on for each imported report When refreshing all data in a document before logging on to the required servers you are automatically prompted to log on for each report in the document even if the reports come from the same server. To log on only once per server use the Log On toolbar button to log on to the required servers before refreshing report data. #573884 4. Unable to open a report in Analysis or Report Studio when using Siteminder authentication Form Based and Anonymous Access security is not allowed in Cognos 8 Configuration. When attempting to view the reports in Analysis or Report Studio you may see the following error message: "Due to the presence of characters known to be used in Cross Site Scripting attacks, access is forbidden. This web site does not allow Urls which might include embedded HTML tags." #571324 5. The namespace parameter is case sensitive When entering the namespace information, you must be aware that this parameter is case sensitive. #573749 6. Cognos 8 Go! Office Automation does not support SiteMinder Form-Based Authentication Because Cognos 8 Go! Office does not support Siteminder form-based authentication when using automation, you must update documents using the UI instead of via automation. #574640
Cognos 8 for Microsoft Office
General Known Issues 1. bo:heap Buffer Overflow Error After long sessions, Microsoft Office may stop responding by generating a bo:heap Buffer Overflow error. This error may be falsely identified as a potential virus by some virus-monitoring programs. #557292 2. Cognos 8 Go! Office workbook references to reports might not refresh properly after the reports are upgraded to version 8.2 Cognos 8 Go! Office-enabled workbooks that reference reports from a version 8.1 Cognos 8 server may not refresh properly after the reports are upgraded to Cognos 8 version 8.2. Objects in the report may have the name attribute modified by the report upgrade procedures. When the workbook is refreshed, the object is not updated, data is missing, and no error is reported. To rectify this situation, you must install the Cognos 8 version 8.2 server hotsite that fixes the report upgrade procedure. After you rerun the report upgrade procedure from 8.1 to 8.2, the workbooks are refreshed correctly. Alternately, you can recreate the workbook references to the reports that are not updated. #569301 3. Prompted to log on for each imported report When refreshing all data in a document before logging on to the required servers you are automatically prompted to log on for each report in the document even if the reports come from the same server. To log on only once per server use the Log On toolbar button to log on to the required servers before refreshing report data. #573884 4. Unable to open a report in Analysis or Report Studio when using Siteminder authentication Form Based and Anonymous Access security is not allowed in Cognos 8 Configuration. When attempting to view the reports in Analysis or Report Studio you may see the following error message: "Due to the presence of characters known to be used in Cross Site Scripting attacks, access is forbidden. This web site does not allow Urls which might include embedded HTML tags." #571324 5. The namespace parameter is case sensitive When entering the namespace information, you must be aware that this parameter is case sensitive. #573749 6. Cognos 8 Go! Office Automation does not support SiteMinder Form-Based Authentication Because Cognos 8 Go! Office does not support Siteminder form-based authentication when using automation, you must update documents using the UI instead of via automation. #574640
Cognos Framework Manager SPROC issue
Unable to View the Result Set of a Stored Procedure
If the result set of a stored procedure contains a CLOB (character large object) or BLOB (binary large object), you must modify the stored procedure before running it.
Steps to Use CLOBS
1.
Create a model query subject that references the stored procedure.2.
Insert a Cast or Substring function to calculate a string based on the CLOB.Steps to Use BLOBS
1.
Create a model query subject that references the stored procedure.2.
Remove the BLOB from the Select statement of the query subject.3.
Add query items to the Select statement that perform a lookup on the table that contains the BLOB data.
Full Outer Joins in Oracle
Full Outer Joins in Oracle
When using an Oracle RDBMS data source prior to version 9.2.02, full outer joins return incorrect data results. To avoid this problem, Cognos 8 processes these as local operations.
As a result of this processing, you must set the query processing to limitedLocal for any projects that expect explicit or implicit outer joins.
Cognos Framework Manager SPROC issue
Unable to View the Result Set of a Stored Procedure
If the result set of a stored procedure contains a CLOB (character large object) or BLOB (binary large object), you must modify the stored procedure before running it.
Steps to Use CLOBS
1.
Create a model query subject that references the stored procedure.2.
Insert a Cast or Substring function to calculate a string based on the CLOB.Steps to Use BLOBS
1.
Create a model query subject that references the stored procedure.2.
Remove the BLOB from the Select statement of the query subject.3.
Add query items to the Select statement that perform a lookup on the table that contains the BLOB data.
Full Outer Joins in Oracle
Full Outer Joins in Oracle
When using an Oracle RDBMS data source prior to version 9.2.02, full outer joins return incorrect data results. To avoid this problem, Cognos 8 processes these as local operations.
As a result of this processing, you must set the query processing to limitedLocal for any projects that expect explicit or implicit outer joins.
Cognos Framework Manager modelling best practices
- Design your presentation view so that your users will naturally do the right thing, based on the names of the objects, and where they appear in the tree structure.
- Keep it simple. Complexity makes things hard to understand and predict. If you can't understand the result, you've probably outsmarted yourself.
- Present a star schema view to report authors. Build it by following the arrows.
- Where complexity is unavoidable, encapsulate it in a model query subject, and test that query subject thoroughly. Use query item folders inside it where necessary to make clear the purpose of each item and the relationships between them.
- Make sure that the model information is complete. When in doubt, specify all dimensional information.
- Whenever you have to make the model lie about the underlying data, make sure you've thought out the consequences.
- Use the Description and Screen Tip properties help yourself and your users to understand things that otherwise may not be obvious.
- Be careful what you expose. In particular, avoid directly exposing parts of the data source modelling layer that contain multiple join paths, or are otherwise incompletely modelled.
- Test thoroughly.
Cognos Framework Manager modelling best practices
- Design your presentation view so that your users will naturally do the right thing, based on the names of the objects, and where they appear in the tree structure.
- Keep it simple. Complexity makes things hard to understand and predict. If you can't understand the result, you've probably outsmarted yourself.
- Present a star schema view to report authors. Build it by following the arrows.
- Where complexity is unavoidable, encapsulate it in a model query subject, and test that query subject thoroughly. Use query item folders inside it where necessary to make clear the purpose of each item and the relationships between them.
- Make sure that the model information is complete. When in doubt, specify all dimensional information.
- Whenever you have to make the model lie about the underlying data, make sure you've thought out the consequences.
- Use the Description and Screen Tip properties help yourself and your users to understand things that otherwise may not be obvious.
- Be careful what you expose. In particular, avoid directly exposing parts of the data source modelling layer that contain multiple join paths, or are otherwise incompletely modelled.
- Test thoroughly.
Developing models in Cognos Framework Manager
Modellers should be careful to present a view that guides their users (especially QS users) away from building reports that violate these conditions. Techniques that can help:
· Use the star schema approach. The view that you expose to modelers should always be a set of stars or snowflakes, each in its own folder or namespace. (Refer to the FM User Guide section on Star Schema Grouping.)
· Never put two fact tables in the same folder or namespace.
· In a fact table query subject, avoid exposing any query items that are not facts (measures with an aggregation rule). If necessary, expose them as a separate model query subject that looks like a dimension.
· In each fact namespace, put only the dimensions that relate to it. Do not put dimensions anywhere else, such as in a common location.
· Always give conformed dimensions the same name in each namespace where they appear. That's the only way your users can tell that they are conformed.
· If two fact tables have conformed dimensions, but different levels of granularity for that dimension, include for each fact table only the relevant levels.
· If a dimension is based on a denormalized table, for each fact table create a model query that omits query items for levels below the level of granularity for that fact table.
For example, if inventory is only recorded at the month level, the time dimension for inventory should include years and months, but not days.
· Use naming and grouping conventions that make it clear what is a fact (which can be aggregated), what is a dimension identifier (unique, usable for grouping), and what is an attribute (anything else).
Developing models in Cognos Framework Manager
Modellers should be careful to present a view that guides their users (especially QS users) away from building reports that violate these conditions. Techniques that can help:
· Use the star schema approach. The view that you expose to modelers should always be a set of stars or snowflakes, each in its own folder or namespace. (Refer to the FM User Guide section on Star Schema Grouping.)
· Never put two fact tables in the same folder or namespace.
· In a fact table query subject, avoid exposing any query items that are not facts (measures with an aggregation rule). If necessary, expose them as a separate model query subject that looks like a dimension.
· In each fact namespace, put only the dimensions that relate to it. Do not put dimensions anywhere else, such as in a common location.
· Always give conformed dimensions the same name in each namespace where they appear. That's the only way your users can tell that they are conformed.
· If two fact tables have conformed dimensions, but different levels of granularity for that dimension, include for each fact table only the relevant levels.
· If a dimension is based on a denormalized table, for each fact table create a model query that omits query items for levels below the level of granularity for that fact table.
For example, if inventory is only recorded at the month level, the time dimension for inventory should include years and months, but not days.
· Use naming and grouping conventions that make it clear what is a fact (which can be aggregated), what is a dimension identifier (unique, usable for grouping), and what is an attribute (anything else).
Calculating Number of Report Connections (for a 4-CPU server)
Calculating Number of Report Connections (for a 4-CPU server)
Interactive Report Processes
No. of BIBUS processes = 2 x CPUs
Hi Affinity connections = 1/BIBUS
Lo Affinity connections = 2/BIBUS
Batch Report Processes
No. of BIBUS = 1 x CPUs
Hi Affinity connections = 1
Lo Affinity connections = 2/BIBUS
Therefore on a 4 CPU server, we will have the following number of connections
8 BIBUS (interactive)
8 Hi affinity
16 Lo affinity
______________
24 connections
4 BIBUS (batch)
1 Hi affinity
8 Lo affinity
_____________
9 connections
Calculating Number of Report Connections (for a 4-CPU server)
Calculating Number of Report Connections (for a 4-CPU server)
Interactive Report Processes
No. of BIBUS processes = 2 x CPUs
Hi Affinity connections = 1/BIBUS
Lo Affinity connections = 2/BIBUS
Batch Report Processes
No. of BIBUS = 1 x CPUs
Hi Affinity connections = 1
Lo Affinity connections = 2/BIBUS
Therefore on a 4 CPU server, we will have the following number of connections
8 BIBUS (interactive)
8 Hi affinity
16 Lo affinity
______________
24 connections
4 BIBUS (batch)
1 Hi affinity
8 Lo affinity
_____________
9 connections
C8 Tuning and Administration
Processing Capacity
1.0The appropriate value for this setting is a function of the number of CPUs, CPU clock rate, memory, etc in relation to other servers in the topology. It is a relative setting. This setting dictates the number of BI requests that will be handled by a particular a server in the Cognos 8 topology.
By default, requests will be distributed so that each server is expected to handle an equivalent number of requests.
While it may be difficult to estimate a precisely correct set of values for heterogeneous server environments, there are several methods that can improve the relative accuracy of this task.
1) Use the relative performance ratings of a server (provided by hardware vendors).
2) Estimate the process capacity for a server using one variable at a time in the order of (#of CPUs, clock rate of CPUs)
It is important to monitor the request rate through the Server Administration tool of Cognos Connection. Isolate the Report services to monitor interactive usage. This will indicate whether the applied process capacity settings lead to expected behavior. Key metrics to observe include Latency and Requests per second. If latency is building up on one report service while others are functioning freely, reduce the process capacity on the high latency server. In general, monitor the requests per second metric so that the number is proportional to the capacity of each server in the topology.
C8 Tuning and Administration
Processing Capacity
1.0The appropriate value for this setting is a function of the number of CPUs, CPU clock rate, memory, etc in relation to other servers in the topology. It is a relative setting. This setting dictates the number of BI requests that will be handled by a particular a server in the Cognos 8 topology.
By default, requests will be distributed so that each server is expected to handle an equivalent number of requests.
While it may be difficult to estimate a precisely correct set of values for heterogeneous server environments, there are several methods that can improve the relative accuracy of this task.
1) Use the relative performance ratings of a server (provided by hardware vendors).
2) Estimate the process capacity for a server using one variable at a time in the order of (#of CPUs, clock rate of CPUs)
It is important to monitor the request rate through the Server Administration tool of Cognos Connection. Isolate the Report services to monitor interactive usage. This will indicate whether the applied process capacity settings lead to expected behavior. Key metrics to observe include Latency and Requests per second. If latency is building up on one report service while others are functioning freely, reduce the process capacity on the high latency server. In general, monitor the requests per second metric so that the number is proportional to the capacity of each server in the topology.
Phishing
How They Attack
Phishing is essentially an online con game and phishers are nothing more than tech-savvy con artists and identify thieves. They use SPAM, malicious Web sites, email messages and instant messages to trick people into divulging sensitive information, such as bank and credit card accounts. How Do You Know
- Phishers, pretending to be legitimate companies, may use email to request personal information and direct recipients to respond through malicious web sites
- Phishers tend to use emotional language using scare tactics or urgent requests to entice recipients to respond
- The phish sites can look remarkably like legitimate sites because they tend to use the copyrighted images from legitimate sites
- Requests for confidential information via email or Instant Message tend to not be legitimate
- Fraudulent messages are often not personalized and may share similar properties like details in the header and footer
How Can You Help
If a legitimate Web page has been misidentified as a known or suspicious phish site, please report this misidentified page to the Symantec Security Response team at Submit false positive phish Web page.
A Norton Authenticated Web page has been verified by Symantec as belonging to the company represented. Please use the Norton Authenticated Request Form for legitimate Web sites you want to be evaluated as Norton Authenticated.
Phishing
How They Attack
Phishing is essentially an online con game and phishers are nothing more than tech-savvy con artists and identify thieves. They use SPAM, malicious Web sites, email messages and instant messages to trick people into divulging sensitive information, such as bank and credit card accounts. How Do You Know
- Phishers, pretending to be legitimate companies, may use email to request personal information and direct recipients to respond through malicious web sites
- Phishers tend to use emotional language using scare tactics or urgent requests to entice recipients to respond
- The phish sites can look remarkably like legitimate sites because they tend to use the copyrighted images from legitimate sites
- Requests for confidential information via email or Instant Message tend to not be legitimate
- Fraudulent messages are often not personalized and may share similar properties like details in the header and footer
How Can You Help
If a legitimate Web page has been misidentified as a known or suspicious phish site, please report this misidentified page to the Symantec Security Response team at Submit false positive phish Web page.
A Norton Authenticated Web page has been verified by Symantec as belonging to the company represented. Please use the Norton Authenticated Request Form for legitimate Web sites you want to be evaluated as Norton Authenticated.
Symantec QuickImage
How to create an image with QuickImage
You can use QuickImage to configure image creation tasks while Windows is running. To create the image files, QuickImage must restart to DOS.
To configure an image creation task
- On the Windows task bar, click Start > Programs > PowerQuest Drive Image > QuickImage.
- In the Image Filename box, type the full path to which you want to save the image.
- In the Image Description box, type any comments that you want to save with this image.
- Click Select Partitions.
- In the partition list, click the partition that you want to add to the image.
To add multiple partitions to the image, hold Ctrl and click the partitions that you want to add. - Click OK.
- If you need to set advanced options such as file system error checking, disk write verification, verifying image contents, splitting the image into multiple segments, compression level or password protection, click Advanced Options. Otherwise, continue to the next step.
- Click OK.
- Do one of the following:
- Click Create Image to begin creating the image immediately.
- Click Schedule Task to schedule the image creation for a specified time.
- Click OK.
Symantec QuickImage
How to create an image with QuickImage
You can use QuickImage to configure image creation tasks while Windows is running. To create the image files, QuickImage must restart to DOS.
To configure an image creation task
- On the Windows task bar, click Start > Programs > PowerQuest Drive Image > QuickImage.
- In the Image Filename box, type the full path to which you want to save the image.
- In the Image Description box, type any comments that you want to save with this image.
- Click Select Partitions.
- In the partition list, click the partition that you want to add to the image.
To add multiple partitions to the image, hold Ctrl and click the partitions that you want to add. - Click OK.
- If you need to set advanced options such as file system error checking, disk write verification, verifying image contents, splitting the image into multiple segments, compression level or password protection, click Advanced Options. Otherwise, continue to the next step.
- Click OK.
- Do one of the following:
- Click Create Image to begin creating the image immediately.
- Click Schedule Task to schedule the image creation for a specified time.
- Click OK.
Subscribe to:
Posts (Atom)