Report errors after parallel install

[actcognosuser]

Hi All,

We installed same version of the Cognos (10.x) on the STAGE server .

After installation , imported a copy of existing content store. All content seems to be imported, but
there are issues running reports.

Below is the error
RSV-SRV-0051
This report specification does not have a version specified.

On further research solution seems to be :
Add a version to the report specification by specifying the namespace on the report element.

How do we add a version to the namespace? Is the version cognos install version?

Thanks in advance!

[MFGF]

Hi All,

We installed same version of the Cognos (10.x) on the STAGE server .

After installation , imported a copy of existing content store. All content seems to be imported, but
there are issues running reports.

Below is the error
RSV-SRV-0051
This report specification does not have a version specified.

On further research solution seems to be :
Add a version to the report specification by specifying the namespace on the report element.

How do we add a version to the namespace? Is the version cognos install version?

Thanks in advance!

Hi,

What version of Cognos are you using exactly? It looks like this was a known defect in 10.1.x and it was fixed in 10.2

Cheers!

MF.

[actcognosuser]

Hi MFGF,

Cognos version is 10.2.1.

How do we fix this issue? Does a config file need to be modified?

[MFGF]

Hi MFGF,

Cognos version is 10.2.1.

How do we fix this issue? Does a config file need to be modified?

It sounds like the report specs have got messed up somewhere in the process of moving from one instance to another. How did you transfer the content from the original instance to the new one? Was it a database backup/restore of the content store database? A deployment archive? If the latter, did you select the option to upgrade the report specs during the import?

Cheers!

MF.

[actcognosuser]

The import was done using the deployment archive.

There was no option of report specs during import.

[actcognosuser]

Hi All,

Does a fix pack need to be applied for 10.2.1 to fix this issue?

Please advise.