Cognos Analytics

​"The latest package information could not be loaded. The package this report is referencing may no longer exist. Package metadata is required for proper operation of the user interface. Certain elements of the report definition may not be viewable or editable."

This only happens in Reporting, works fine in Dashboard, Story telling, as well as legacy studios.  Log file is totally worthless, even with full logging turn one. 

Add a stranger thing, is that if you open a report based on the package, you get same error, however if you try view the tabular data, the error appears again, however it will then actually return the data without a problem.

DQM is not used, works fine in 10.2.x as well as 11.0.10.  Web searches result in some very old information, regarding moving, and having to relink.  The set up is exactly as it was in previous version, and if that were the case you would still expect a New Report to work. 

Other imported packages work without a problem.  I have seen some similar problems, in the past with clients (sorry used to be consultant/support), with the original releases of 11.0.x with either a dashboard not working, or a report not working, and traced back to FM, but nothing is popping out here to try and change something in FM to test, and grasping at straws by the old standard of stripping back and going 1 by  1 is not an option.

Straight forward package, not a cube, no external data, since this is dev, security is wide open, Oracle database.

Any ideas would be great!

------------------------------
Kurt Blevins
------------------------------

#CognosAnalyticswithWatson

​Hi @Kurt Blevins, what happens when you open a brand new report and then use the same package? Is this happening with just one report using this package or any report using this package?

Another thought is that perhaps if the report is some legacy report, maybe there is one or even a few elements that ​refer to something that no longer exists in the package or even pointing to another package. I would go through the data items in the queries and use the Find All to figure out if they are used in the report. I have seen issues with old elements stuck in reports. I really wish that we had a cleanup function in the queries to easily find all of the objects not used in the report, to easily remove them. This is a recurring problem for me with legacy reports.

Good luck!


------------------------------
Adrienne Beronilla
Senior Financial Systems Analyst
Franklin Templeton
------------------------------

Original Message:
Sent: Tue August 20, 2019 10:44 AM
From: Kurt Blevins
Subject: 11.1.3 Unable to Load Current Package

​"The latest package information could not be loaded. The package this report is referencing may no longer exist. Package metadata is required for proper operation of the user interface. Certain elements of the report definition may not be viewable or editable."

This only happens in Reporting, works fine in Dashboard, Story telling, as well as legacy studios.  Log file is totally worthless, even with full logging turn one. 

Add a stranger thing, is that if you open a report based on the package, you get same error, however if you try view the tabular data, the error appears again, however it will then actually return the data without a problem.

DQM is not used, works fine in 10.2.x as well as 11.0.10.  Web searches result in some very old information, regarding moving, and having to relink.  The set up is exactly as it was in previous version, and if that were the case you would still expect a New Report to work. 

Other imported packages work without a problem.  I have seen some similar problems, in the past with clients (sorry used to be consultant/support), with the original releases of 11.0.x with either a dashboard not working, or a report not working, and traced back to FM, but nothing is popping out here to try and change something in FM to test, and grasping at straws by the old standard of stripping back and going 1 by  1 is not an option.

Straight forward package, not a cube, no external data, since this is dev, security is wide open, Oracle database.

Any ideas would be great!

------------------------------
Kurt Blevins
------------------------------

#CognosAnalyticswithWatson

Hi Adrienne,
    Thanks for the tips, sadly,  I can't even build a new report off the package, same error pops up, and if you try to load a different package, it tells you that one is already open, albeit, nothing is displaying.  When I open any existing report, and go to any of the queries, and view the tabular data, get the same message, but then it actually displays the data without a problem.  I have gone through the package, and it really does not have anything complicated at least from the FM side, it has been republished 2x, even with different name, other packages based on the presentation layer work fine.  I was even was able to 'Enhance the Package' and build an exploration, it is just reporting.  ​

------------------------------
Kurt Blevins
------------------------------

Original Message:
Sent: Wed August 21, 2019 12:05 PM
From: Adrienne Beronilla
Subject: 11.1.3 Unable to Load Current Package

​Hi @Kurt Blevins, what happens when you open a brand new report and then use the same package? Is this happening with just one report using this package or any report using this package?

Another thought is that perhaps if the report is some legacy report, maybe there is one or even a few elements that ​refer to something that no longer exists in the package or even pointing to another package. I would go through the data items in the queries and use the Find All to figure out if they are used in the report. I have seen issues with old elements stuck in reports. I really wish that we had a cleanup function in the queries to easily find all of the objects not used in the report, to easily remove them. This is a recurring problem for me with legacy reports.

Good luck!


------------------------------
Adrienne Beronilla
Senior Financial Systems Analyst
Franklin Templeton

Original Message:
Sent: Tue August 20, 2019 10:44 AM
From: Kurt Blevins
Subject: 11.1.3 Unable to Load Current Package

​"The latest package information could not be loaded. The package this report is referencing may no longer exist. Package metadata is required for proper operation of the user interface. Certain elements of the report definition may not be viewable or editable."

This only happens in Reporting, works fine in Dashboard, Story telling, as well as legacy studios.  Log file is totally worthless, even with full logging turn one. 

Add a stranger thing, is that if you open a report based on the package, you get same error, however if you try view the tabular data, the error appears again, however it will then actually return the data without a problem.

DQM is not used, works fine in 10.2.x as well as 11.0.10.  Web searches result in some very old information, regarding moving, and having to relink.  The set up is exactly as it was in previous version, and if that were the case you would still expect a New Report to work. 

Other imported packages work without a problem.  I have seen some similar problems, in the past with clients (sorry used to be consultant/support), with the original releases of 11.0.x with either a dashboard not working, or a report not working, and traced back to FM, but nothing is popping out here to try and change something in FM to test, and grasping at straws by the old standard of stripping back and going 1 by  1 is not an option.

Straight forward package, not a cube, no external data, since this is dev, security is wide open, Oracle database.

Any ideas would be great!

------------------------------
Kurt Blevins
------------------------------

#CognosAnalyticswithWatson

One last thought: you mentioned that you could publish the same package with a different name and the new package was fine. Could you re-point the report to the new package? ​

------------------------------
Adrienne Beronilla
Senior Financial Systems Analyst
Franklin Templeton
------------------------------

Original Message:
Sent: Thu August 22, 2019 09:03 AM
From: Kurt Blevins
Subject: 11.1.3 Unable to Load Current Package

Hi Adrienne,
    Thanks for the tips, sadly,  I can't even build a new report off the package, same error pops up, and if you try to load a different package, it tells you that one is already open, albeit, nothing is displaying.  When I open any existing report, and go to any of the queries, and view the tabular data, get the same message, but then it actually displays the data without a problem.  I have gone through the package, and it really does not have anything complicated at least from the FM side, it has been republished 2x, even with different name, other packages based on the presentation layer work fine.  I was even was able to 'Enhance the Package' and build an exploration, it is just reporting.  ​

------------------------------
Kurt Blevins

Original Message:
Sent: Wed August 21, 2019 12:05 PM
From: Adrienne Beronilla
Subject: 11.1.3 Unable to Load Current Package

​Hi @Kurt Blevins, what happens when you open a brand new report and then use the same package? Is this happening with just one report using this package or any report using this package?

Another thought is that perhaps if the report is some legacy report, maybe there is one or even a few elements that ​refer to something that no longer exists in the package or even pointing to another package. I would go through the data items in the queries and use the Find All to figure out if they are used in the report. I have seen issues with old elements stuck in reports. I really wish that we had a cleanup function in the queries to easily find all of the objects not used in the report, to easily remove them. This is a recurring problem for me with legacy reports.

Good luck!


------------------------------
Adrienne Beronilla
Senior Financial Systems Analyst
Franklin Templeton

Original Message:
Sent: Tue August 20, 2019 10:44 AM
From: Kurt Blevins
Subject: 11.1.3 Unable to Load Current Package

​"The latest package information could not be loaded. The package this report is referencing may no longer exist. Package metadata is required for proper operation of the user interface. Certain elements of the report definition may not be viewable or editable."

This only happens in Reporting, works fine in Dashboard, Story telling, as well as legacy studios.  Log file is totally worthless, even with full logging turn one. 

Add a stranger thing, is that if you open a report based on the package, you get same error, however if you try view the tabular data, the error appears again, however it will then actually return the data without a problem.

DQM is not used, works fine in 10.2.x as well as 11.0.10.  Web searches result in some very old information, regarding moving, and having to relink.  The set up is exactly as it was in previous version, and if that were the case you would still expect a New Report to work. 

Other imported packages work without a problem.  I have seen some similar problems, in the past with clients (sorry used to be consultant/support), with the original releases of 11.0.x with either a dashboard not working, or a report not working, and traced back to FM, but nothing is popping out here to try and change something in FM to test, and grasping at straws by the old standard of stripping back and going 1 by  1 is not an option.

Straight forward package, not a cube, no external data, since this is dev, security is wide open, Oracle database.

Any ideas would be great!

------------------------------
Kurt Blevins
------------------------------

#CognosAnalyticswithWatson

Hi Adrienne,
     Yes, if I point the existing reports to the new package name, it works fine.... I even went back to FM, and renamed the old package, and gave the new package the same name, published that, and it still throws same error.​

------------------------------
Kurt Blevins
------------------------------

Original Message:
Sent: Thu August 22, 2019 11:48 AM
From: Adrienne Beronilla
Subject: 11.1.3 Unable to Load Current Package

One last thought: you mentioned that you could publish the same package with a different name and the new package was fine. Could you re-point the report to the new package? ​

------------------------------
Adrienne Beronilla
Senior Financial Systems Analyst
Franklin Templeton

Original Message:
Sent: Thu August 22, 2019 09:03 AM
From: Kurt Blevins
Subject: 11.1.3 Unable to Load Current Package

Hi Adrienne,
    Thanks for the tips, sadly,  I can't even build a new report off the package, same error pops up, and if you try to load a different package, it tells you that one is already open, albeit, nothing is displaying.  When I open any existing report, and go to any of the queries, and view the tabular data, get the same message, but then it actually displays the data without a problem.  I have gone through the package, and it really does not have anything complicated at least from the FM side, it has been republished 2x, even with different name, other packages based on the presentation layer work fine.  I was even was able to 'Enhance the Package' and build an exploration, it is just reporting.  ​

------------------------------
Kurt Blevins

Original Message:
Sent: Wed August 21, 2019 12:05 PM
From: Adrienne Beronilla
Subject: 11.1.3 Unable to Load Current Package

​Hi @Kurt Blevins, what happens when you open a brand new report and then use the same package? Is this happening with just one report using this package or any report using this package?

Another thought is that perhaps if the report is some legacy report, maybe there is one or even a few elements that ​refer to something that no longer exists in the package or even pointing to another package. I would go through the data items in the queries and use the Find All to figure out if they are used in the report. I have seen issues with old elements stuck in reports. I really wish that we had a cleanup function in the queries to easily find all of the objects not used in the report, to easily remove them. This is a recurring problem for me with legacy reports.

Good luck!


------------------------------
Adrienne Beronilla
Senior Financial Systems Analyst
Franklin Templeton

Original Message:
Sent: Tue August 20, 2019 10:44 AM
From: Kurt Blevins
Subject: 11.1.3 Unable to Load Current Package

​"The latest package information could not be loaded. The package this report is referencing may no longer exist. Package metadata is required for proper operation of the user interface. Certain elements of the report definition may not be viewable or editable."

This only happens in Reporting, works fine in Dashboard, Story telling, as well as legacy studios.  Log file is totally worthless, even with full logging turn one. 

Add a stranger thing, is that if you open a report based on the package, you get same error, however if you try view the tabular data, the error appears again, however it will then actually return the data without a problem.

DQM is not used, works fine in 10.2.x as well as 11.0.10.  Web searches result in some very old information, regarding moving, and having to relink.  The set up is exactly as it was in previous version, and if that were the case you would still expect a New Report to work. 

Other imported packages work without a problem.  I have seen some similar problems, in the past with clients (sorry used to be consultant/support), with the original releases of 11.0.x with either a dashboard not working, or a report not working, and traced back to FM, but nothing is popping out here to try and change something in FM to test, and grasping at straws by the old standard of stripping back and going 1 by  1 is not an option.

Straight forward package, not a cube, no external data, since this is dev, security is wide open, Oracle database.

Any ideas would be great!

------------------------------
Kurt Blevins
------------------------------

#CognosAnalyticswithWatson

Update, I have now found 2 reports that actually will run straight away​ when clicking and return data, however, when you click to edit it, it fails to load the package.

------------------------------
Kurt Blevins
------------------------------

Original Message:
Sent: Tue August 20, 2019 10:44 AM
From: Kurt Blevins
Subject: 11.1.3 Unable to Load Current Package

​"The latest package information could not be loaded. The package this report is referencing may no longer exist. Package metadata is required for proper operation of the user interface. Certain elements of the report definition may not be viewable or editable."

This only happens in Reporting, works fine in Dashboard, Story telling, as well as legacy studios.  Log file is totally worthless, even with full logging turn one. 

Add a stranger thing, is that if you open a report based on the package, you get same error, however if you try view the tabular data, the error appears again, however it will then actually return the data without a problem.

DQM is not used, works fine in 10.2.x as well as 11.0.10.  Web searches result in some very old information, regarding moving, and having to relink.  The set up is exactly as it was in previous version, and if that were the case you would still expect a New Report to work. 

Other imported packages work without a problem.  I have seen some similar problems, in the past with clients (sorry used to be consultant/support), with the original releases of 11.0.x with either a dashboard not working, or a report not working, and traced back to FM, but nothing is popping out here to try and change something in FM to test, and grasping at straws by the old standard of stripping back and going 1 by  1 is not an option.

Straight forward package, not a cube, no external data, since this is dev, security is wide open, Oracle database.

Any ideas would be great!

------------------------------
Kurt Blevins
------------------------------

#CognosAnalyticswithWatson

OK, so I deleted the package, that was causing the problems, I then renamed my new package that worked, the same name as the broken package, I then imported the reports only for that package, and told it to Assign New Id's, and now all the reports are working, and there is no error message any longer.  Not sure why that worked, but it did.

------------------------------
Kurt Blevins
------------------------------

Original Message:
Sent: Thu August 22, 2019 11:00 AM
From: Kurt Blevins
Subject: 11.1.3 Unable to Load Current Package

Update, I have now found 2 reports that actually will run straight away​ when clicking and return data, however, when you click to edit it, it fails to load the package.

------------------------------
Kurt Blevins

Original Message:
Sent: Tue August 20, 2019 10:44 AM
From: Kurt Blevins
Subject: 11.1.3 Unable to Load Current Package

​"The latest package information could not be loaded. The package this report is referencing may no longer exist. Package metadata is required for proper operation of the user interface. Certain elements of the report definition may not be viewable or editable."

This only happens in Reporting, works fine in Dashboard, Story telling, as well as legacy studios.  Log file is totally worthless, even with full logging turn one. 

Add a stranger thing, is that if you open a report based on the package, you get same error, however if you try view the tabular data, the error appears again, however it will then actually return the data without a problem.

DQM is not used, works fine in 10.2.x as well as 11.0.10.  Web searches result in some very old information, regarding moving, and having to relink.  The set up is exactly as it was in previous version, and if that were the case you would still expect a New Report to work. 

Other imported packages work without a problem.  I have seen some similar problems, in the past with clients (sorry used to be consultant/support), with the original releases of 11.0.x with either a dashboard not working, or a report not working, and traced back to FM, but nothing is popping out here to try and change something in FM to test, and grasping at straws by the old standard of stripping back and going 1 by  1 is not an option.

Straight forward package, not a cube, no external data, since this is dev, security is wide open, Oracle database.

Any ideas would be great!

------------------------------
Kurt Blevins
------------------------------

#CognosAnalyticswithWatson

Congrtulations! That is really odd but have seen similarly odd behavior from Cognos, though not in a while... ​

------------------------------
Adrienne Beronilla
Senior Financial Systems Analyst
Franklin Templeton
------------------------------

Original Message:
Sent: Wed September 04, 2019 09:46 AM
From: Kurt Blevins
Subject: 11.1.3 Unable to Load Current Package

OK, so I deleted the package, that was causing the problems, I then renamed my new package that worked, the same name as the broken package, I then imported the reports only for that package, and told it to Assign New Id's, and now all the reports are working, and there is no error message any longer.  Not sure why that worked, but it did.

------------------------------
Kurt Blevins

Original Message:
Sent: Thu August 22, 2019 11:00 AM
From: Kurt Blevins
Subject: 11.1.3 Unable to Load Current Package

Update, I have now found 2 reports that actually will run straight away​ when clicking and return data, however, when you click to edit it, it fails to load the package.

------------------------------
Kurt Blevins

Original Message:
Sent: Tue August 20, 2019 10:44 AM
From: Kurt Blevins
Subject: 11.1.3 Unable to Load Current Package

​"The latest package information could not be loaded. The package this report is referencing may no longer exist. Package metadata is required for proper operation of the user interface. Certain elements of the report definition may not be viewable or editable."

This only happens in Reporting, works fine in Dashboard, Story telling, as well as legacy studios.  Log file is totally worthless, even with full logging turn one. 

Add a stranger thing, is that if you open a report based on the package, you get same error, however if you try view the tabular data, the error appears again, however it will then actually return the data without a problem.

DQM is not used, works fine in 10.2.x as well as 11.0.10.  Web searches result in some very old information, regarding moving, and having to relink.  The set up is exactly as it was in previous version, and if that were the case you would still expect a New Report to work. 

Other imported packages work without a problem.  I have seen some similar problems, in the past with clients (sorry used to be consultant/support), with the original releases of 11.0.x with either a dashboard not working, or a report not working, and traced back to FM, but nothing is popping out here to try and change something in FM to test, and grasping at straws by the old standard of stripping back and going 1 by  1 is not an option.

Straight forward package, not a cube, no external data, since this is dev, security is wide open, Oracle database.

Any ideas would be great!

------------------------------
Kurt Blevins
------------------------------

#CognosAnalyticswithWatson