Cognos Analytics

Cognos Analytics

Connect, learn, and share with thousands of IBM Cognos Analytics users!Β 

Β View Only

  • 1.  RSV-PMG-0006: The model or module versions can't be determined for /content/folder[real-name-deleted] so the parameter cache will not be used

    Posted 8 days ago

    Hi,

    I am reading the cognosserver.log from a customer, and I have multiple lines with:

    RSV-PMG-0006: The model or module versions can't be determined for /content/folder[real-name-deleted] so the parameter cache will not be used.

    I did not find anything close to RSV-PMG-0006 in Google.

    Any idea would be appreciated.

    Best regards,



    ------------------------------
    Patrick Neveu
    BSL Consulting
    IBM Champion
    ------------------------------


  • 2.  RE: RSV-PMG-0006: The model or module versions can't be determined for /content/folder[real-name-deleted] so the parameter cache will not be used

    Posted 7 days ago

    I asked the AI Android App, Perplexity, the following question,

    "using IBM Cognos, I get the error code RSV-PMG-0006 can you explain what causes this?"

     and this was the response:

    The IBM Cognos error code RSV-PMG-0006 indicates that there is an issue in your report related to prompt or parameter management. This error specifically points to a problem where a prompt parameter is not correctly defined or referenced, often in cascading prompt setups. Common causes include:

    Cyclic or self-referential prompt cascade: 

    The parameter may be set up to cascade on itself, or there could be a looping reference between prompt parameters, which is not allowed in Cognos.Incorrect parameter definitions or references in the report specification: Double-check that all prompt parameters are logically organized and don't reference themselves or form a circular dependency.

    To resolve it

     

    Review your prompt page(s) and cascading prompt settings for possible cycles or self-references.

    Fix any cyclic references or reconfigure your prompt logic.

    If you have recently edited your report's prompts, that is likely where the issue originated.



    ------------------------------
    Alan S Bluck
    Director
    ASB Software Development Limited
    Ringwood, Hampshire, England
    0044 7710612479
    ------------------------------

    Original Message


  • 3.  RE: RSV-PMG-0006: The model or module versions can't be determined for /content/folder[real-name-deleted] so the parameter cache will not be used

    Posted 7 days ago

    Hi,

    Another 'AI' driven response - as always it may not be accurate or even helpful

    What it means

    • RSV errors come from the Report Server (the rendering service).

    • It's saying Cognos can't determine the version of the model package (FM model or data module) that the report depends on.

    • When that happens, Cognos skips parameter caching (which normally speeds things up by reusing parameter prompts/values).

    • The report should still run, but performance can be slower, especially if there are prompts.

    Common causes

    1. Model/package was moved or renamed in Content Store (e.g., copied outside of deployment or renamed manually).

    2. Package not published correctly - perhaps the publish got interrupted or didn't overwrite fully.

    3. Multiple packages with same name - Cognos might be confused which one to link.

    4. Data module upgraded between Cognos versions (mismatch in internal version identifiers).

    5. Corrupt Content Store entry (rare but possible).

    Fixes / Workarounds

    1. Republish the package

      • Open Framework Manager and republish the model to the content store.

      • If it's a Data Module, save and publish again.

    2. Check report-package linkage

      • In Cognos Portal β†’ open the report in Report Authoring β†’ verify the package it points to.

      • Make sure that package exists and is published.

    3. Clean up duplicates

      • If there are multiple packages with the same name, delete/archive old ones and keep a single authoritative version.

    4. Clear Content Store cache (if possible, with admin rights)

      • Restart Cognos services (especially Report/Query services) to clear stale parameter cache references.

    5. Content Store repair (last resort)

      • Export report/package β†’ delete from Cognos β†’ re-import.

      • If it's widespread, Content Store may need a consistency check.

    βœ… Bottom line: this isn't a fatal error - reports will still run - but it's a performance warning that Cognos can't cache prompts because it can't verify the package version. The most common fix is republishing the package/model and making sure reports are pointed to the correct published object.

    Do you want me to outline the exact steps to check which package your report is using in Cognos Portal (so you can confirm if it's pointing to the right one)?

    You said:
    yes
    ChatGPT said:

    Perfect πŸ‘ - here's how you can check which package a report is using in Cognos Analytics (and confirm if it matches what you expect).

    πŸ” Steps to check the report's package

    1. Log in to Cognos Analytics.

      • Go to the web portal where your reports are stored.

    2. Locate the report.

      • Browse to the folder in Team Content or My Content where the report is saved.

    3. Edit the report.

      • Hover over the report β†’ click the More (three dots) menu β†’ choose Edit (sometimes "Edit report").

      • This opens the report in Report Authoring mode.

    4. Check the package name.

      • In Report Authoring, look at the upper-left corner (just above the report layout).

      • You should see something like:

        

        vbnet
        

        

        

        

        

        

        Package: Sales (Published on: /content/folder...)

      • That shows exactly which package the report is tied to, and where it lives in the content store.

    5. Verify the package exists.

      • Open another browser tab β†’ go to the folder path listed in the package reference.

      • Make sure the package is there and published correctly.

    πŸš‘ If the package is wrong or missing

    • If the report is pointing to an old or moved package:

      1. In Report Authoring, click File β†’ Report properties.

      2. Go to Source or Model (depending on version).

      3. Use Select another package to re-bind the report to the correct, current package.

    • If you republish the package from Framework Manager, make sure you overwrite the existing one in the same location so the linkage doesn't break.



    ------------------------------
    Bob Smith
    ------------------------------

    Original Message


  • 4.  RE: RSV-PMG-0006: The model or module versions can't be determined for /content/folder[real-name-deleted] so the parameter cache will not be used

    Posted 7 days ago

    Hi Patrick,

    That RSV-PMG-0006 message isn't actually an error so much as an informational warning. It shows up when Cognos can't identify the exact model or module version for the content in question, so it skips using the parameter cache. The end result is simply that queries against that package/module may run without the slight performance gain you'd normally get from the cache.

    If you're seeing it repeatedly, the common causes are:

    • The package/module was recently updated or redeployed.

    • There's a mismatch between the content store entry and the cached version.

    • The model has dependencies Cognos can't resolve at cache-check time.

    In most cases it's harmless and won't break reports - clearing/redeploying the package or restarting services usually resolves it if you want to clean up the logs.



    ------------------------------
    James Thompson
    ------------------------------

    Original Message


Related Content