Cognos Analytics

Cognos Analytics

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

 View Only
Back to discussions
Expand all | Collapse all

Dreaded Error: Could not save module: An unknown error has occurred

  • 1.  Dreaded Error: Could not save module: An unknown error has occurred

    Posted Tue December 21, 2021 10:17 AM
    Hi all,

    Has anyone figured out how to avoid the dreaded, "Could not save module: An unknown error has occurred" error message that seems to pop up eventually every data module with seemingly no way to recreate?

    Very frustrating! 


    ------------------------------
    Jeremy Aude
    ------------------------------

    #CognosAnalyticswithWatson


  • 2.  RE: Dreaded Error: Could not save module: An unknown error has occurred

    Posted Tue December 21, 2021 10:41 AM
    Just to note, for those of you not familiar with the message, the module does save even though the error persists.

    ------------------------------
    Jeremy Aude
    ------------------------------

    Original Message


  • 3.  RE: Dreaded Error: Could not save module: An unknown error has occurred

    Posted Wed December 22, 2021 03:48 AM
    Hi Jeremy, We're facing the same and we're investigating the version (11.1.7 IF6) as well as a possible Motio CI impact. Are you using Motio CI as well? Which version are you using?

    ------------------------------
    Philipp Hornung
    ------------------------------

    Original Message


  • 4.  RE: Dreaded Error: Could not save module: An unknown error has occurred

    Posted Wed December 22, 2021 09:55 AM
    Hi Philipp,

    No I do not have any Motio products installed. It's just a simple single server environment...happens on development and production environments. We are on 11.2.1, but like you, the issue surfaced in 11.1.7.

    I opened a ticket with IBM, TS004774473, in Jan 2021. They finally closed the case in April with this comment:
    "So I was investigating this and was able to see several internal bugs related to this, some resolved, some unresolved. It looks like it's an ongoing issue and development is definitely aware of it. Unfortunately, nothing is external so don't have any relevant links to share with you but will be updating this case with relevant internal information in case anyone in the future comes across this case from experiencing similar issues."

    And a suggestion provided:

    "When seeing this issue try doing a "Save as" and just append any letter to the end of the name and save it. If the above succeeds then open the Data Module again, make a small change and this time Overwrite it and notice if you encounter this error."

    I am tired of doing the save as as it always gets back to the same issue. I just hoped IBM would address since there are several internal bugs. 

    Thanks,
    Jeremy



    ------------------------------
    Jeremy Aude
    ------------------------------

    Original Message


  • 5.  RE: Dreaded Error: Could not save module: An unknown error has occurred

    Posted Wed December 22, 2021 12:06 PM

    Hi Jeremy and Philipp,

    Sorry about the trouble with this issue.
    I've asked around, but nobody has come back with a reproducible scenario, which makes it frustrating.
    I reviewed the bugs and TS# quoted above, but nothing jumps out.
    Are there any permissions that you modify?
    From what I understand it happens in 11.1.7 and 11.2.1., correct?
    Are there any settings that you change, e.g. mark an entry as hidden ?
    Are there any messages in the log files on the server that are related to this event?



    ------------------------------
    Kind regards,
    HENK CAZEMIER
    ------------------------------

    Original Message


  • 6.  RE: Dreaded Error: Could not save module: An unknown error has occurred

    Posted Wed December 22, 2021 12:27 PM
    Edited by System Admin Fri January 20, 2023 04:42 PM
    Hi Henk, Thanks for your feedback. It only happens with "older" data modules (also created in 11.1.7 but with an earlier fix level). Copies of them or new data modules don't show the "false" error. Maybe something changed in the data module metadata between 11.1.7.0 and interim fix 6?

    UPDATE: I compared the XML of an old data module and a new copy and there's none (except the name of course)

    ------------------------------
    Philipp Hornung
    ------------------------------

    Original Message


  • 7.  RE: Dreaded Error: Could not save module: An unknown error has occurred

    Posted Wed December 22, 2021 02:21 PM
    Hi all,

    For me it started happening in 11.1.7, but has continued through all versions. I've had a variety of data sources in a model, including data server, tables linked from other modules, FM package. I haven't been able to isolate to a particular behavior or source type.

    I have been working on a new model, based solely on objects from an FM package, over the past several days. It was saving fine until yesterday...then I got the error.

    Unfortunately I don't know when it's going to happen to be able to pinpoint to a specific behavior. Also, the logs don't mention any further details than the error message.

    ------------------------------
    Jeremy Aude
    ------------------------------

    Original Message


  • 8.  RE: Dreaded Error: Could not save module: An unknown error has occurred

    Posted Thu December 23, 2021 12:14 AM
    Edited by System Admin Fri January 20, 2023 04:23 PM
    I could replicated two different problems where the error occurs for me:
    • Adding screen tips to a column
    • Adding optional, reusable filters to a table
    I did this on two different use cases: I created a new module with imported tables from an FM model. I used the Gregorian calendar to add relative dates, organized some of the columns into folders. All was fine with that and I was able to save with no error.

    In the first case,  I tried to add screen tips to columns and things got strange. Keystrokes were delayed when typing in the tip and only a couple of characters that I typed actually showed in the text field. After this I tried to save the model and was presented with that error: Could not save module: An unknown error has occurred

    In the second case it was just adding an optional filter to a table, just like the steps I would perform to add a new calculation. It was a simple filter like this: item code = xyz. The filter validated. But after closing the filter dialog and attempting to save my changes, I received the error message.

    I undid the typing (using the undo button) and tried to save, but I still get the error.

    So it seems, in my experience at least, trying to add a screen tip or optional filters cause some instability and error to be displayed for all future changes. Again, the model changes actually save, I just continue to get that error message.

    ------------------------------
    Jeremy Aude
    ------------------------------

    Original Message


  • 9.  RE: Dreaded Error: Could not save module: An unknown error has occurred

    Posted Thu December 23, 2021 07:04 AM
    Hi Jeremy, I dind't find a reliable pattern yet. With a small test sample it appears like this: 
    • data modules sourced by linked data modules and derived view tables show the error message
      • also copies of these data modules copied in the portal
      • but not these data modules edited and saved under a new name
    • data modules with about the same age but only containing data server tables don't show the error message (especially those being linked by the affected ones)
    • we're whether using screen tips nor optional reusable filters (except if the calendar is linked, but that's not the case for all affected data modules)
    • we're further not using FM packages as data sources
    • as the only intersection between our cases I can identify the usage of linked data modules and folders
    For this year I won't do any further investigation. Have a Merry Christmas and a Happy New Year!

    ------------------------------
    Philipp Hornung
    ------------------------------

    Original Message


  • 10.  RE: Dreaded Error: Could not save module: An unknown error has occurred

    Posted Thu December 23, 2021 10:22 AM
    Edited by System Admin Fri January 20, 2023 04:31 PM

    Hi Jeremy, 

    I had this issue happening to me last year.  I opened a case with IBM.  Turns out I was not using FQDN in my config settings in all 3 enviros (Dev, QA, Prod).   I updated all of my config settings to use FQDN and the problem went away.  

    Case# TS004517061

    I'm on v11.1.7

    Something else that gave me headaches.... the url is case sensitive... this one is silly but it wreaked havoc with me by making weird things occur within my Cognos environments. 

    Thanks, 

    ------------------------------
    Joseph Bankston
    Cognos Administrator / Sr Data Engineer

    Texas
    ------------------------------

    Original Message


  • 11.  RE: Dreaded Error: Could not save module: An unknown error has occurred

    Posted Wed January 05, 2022 01:09 PM
    Hi Joseph,

    That doesn’t seem to be my issue. All properties have the FQDN defined. Can you elaborate on the case sensitivity? The environment settings are case-sensitive?


    Thanks,
    Jeremy


    Original Message


  • 12.  RE: Dreaded Error: Could not save module: An unknown error has occurred

    Posted Wed January 05, 2022 05:24 PM
    And just happened again with a new model! 

    I have to say I am very frustrated with the amount of bugs in the product and vague errors that make it nearly impossible to troubleshoot. We are a small organization and I do not always have weeks to go back and forth with support.

    Very disappointed.

    ------------------------------
    Jeremy Aude
    ------------------------------

    Original Message


  • 13.  RE: Dreaded Error: Could not save module: An unknown error has occurred

    Posted Fri January 07, 2022 01:33 PM
    Quick update: I had a call with IBM and they were able to reproduce the issue on their side and logged an APAR. The workaround is to do a "save as" and overwrite the model as opposed to a save.

    Thank you to @HENK CAZEMIER and the rest of the IBM team for reaching out and working with me to troubleshoot.​

    ------------------------------
    Jeremy Aude
    ------------------------------

    Original Message


  • 14.  RE: Dreaded Error: Could not save module: An unknown error has occurred

    Posted Mon January 10, 2022 03:22 AM
    Hi @Jeremy Aude, Thanks for sharing. Could you please also share the APAR?​ Looks like the data module storage changed and the current validation doesn't work for all old versions.

    ------------------------------
    Philipp Hornung
    ------------------------------

    Original Message


  • 15.  RE: Dreaded Error: Could not save module: An unknown error has occurred

    Posted Wed January 12, 2022 09:24 AM
    Hi Philipp, 

    The APAR is PH43196. 

    Thanks,
    Jeremy

    ------------------------------
    Jeremy Aude
    ------------------------------

    Original Message


  • 16.  RE: Dreaded Error: Could not save module: An unknown error has occurred

    Posted Wed November 01, 2023 02:29 PM

    Jeremy, Philipp,

    Thanks for pursuing this issue with support! I have also been experiencing it fairly frequently and never feel comfortable still seeing the modified * next to my data module after I have saved. In my case the error does not display for a couple of minutes which leads me to believe it is some sort of timeout occurring during the save. I did notice that the Save as ... work but as you say this is very annoying!

    @HENK CAZEMIER, IBM is lucky to still have talented people like you around. Thanks for caring about us customers!

    Cheers!



    ------------------------------
    Mike A
    ------------------------------

    Original Message


  • 17.  RE: Dreaded Error: Could not save module: An unknown error has occurred

    Posted Thu November 02, 2023 02:46 AM

    Hi Mike, We don't see this with CA 11.2.4 FP2 any more. Best, Philipp



    ------------------------------
    Philipp Hornung
    Business Intelligence Manager
    Techniker Krankenkasse
    Hamburg Germany
    #IBMChampion
    ------------------------------

    Original Message