Cognos Analytics

Hi Ayanda,

Did you try to restart your Cognos server? Is it working for another user? Do you have access to cognosserver.log so you can check other errors around CM-REQ-4023.
Do you have special characters within the file you are trying to upload? How large is your file?

Best regards,
Patrick Neveu

Have you ever uploaded anything prior?  If yes, how many files have you uploaded and what is the total size of all uploaded files?

Under manage, there is a setting that limits the total size of the files to be uploaded.  If you exceed that limit, then that might explain the error that you received of not being able to upload.

Depending on your version, there is a way to determine how much data you have uploaded to see if u have exceeded the limit or not.  If you are not an admin, you may need to check with them to see if you have exceeded the limit or not. 

Another option would be to clean up some other uploaded files and retry your upload (assuming you have uploaded files previously).

Off the top of my head, i believe the default setting for total file size per user is set to 500mb.  So if you are attempting to upload a file that is 550mb in size...it should fail.  Likewise if you uploaded 10 files each that are 50mb in size and are attempting the 11th...that is gonna exceed the limit and fail.

Hope that helps.

It seems to be a "Trial version". I don't know if you can get some support with the trial version.

Hi, I experienced a similar situation back in April.  I was using CAoC so the environment was not necessarily under my control.  I did open a case and apparently there was an issue with a service, but I wasn't provided a 100% explanation of what the cause was.  It had nothing to do with my file. I am including the case no# and what I was told at the time.  If you can open a case, maybe you can reference this number, and they may be able to drill down more quickly on what might be causing your situation.  Hopefully you have already solved the issue. Case TS021960208 - "There was an issue with a service on a subset of dispatchers that required redeployment to restore normal functionality. We are continuing to investigate, as there are several known potential causes for the error observed in the logs."