Skip to Content

Import .tgz File gives errors only at the stories in SAC->Objects deleted/do not exist!

Hello experts,

when I export and import contents from my old SAC-Tenant to my new SAC-Tenant, everything get exported/imported except the stories. When I check the error, I get something like this: "Objects CUBE:t.D:safljafdjasdkfsadfss3k might already be deleted or did not exist in the system". When I check the ID of the object above, I see that is included in the .tgz-Package I see that everything is sucessfully imported, however the SAC still gives me the issue and cannot import the stories. Everything else get imported.

Does anyone has perhaps the same issue?

Any help is appreciated.

Thanks a lot,


Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    Posted on Aug 05, 2020 at 12:40 PM

    Hopefully they can find the root cause quickly.

    After further thought, I can think of two other possible reasons for this error, not sure if these have been explored yet via your incident.

    1) Are any of the models for the exported stories not in the root public folder? Since deployment can only export from the public folder, if you select a story in a public folder and export it but the model is in a private folder the model will not be exported and can result in this or similar errors. From your description I don't think this is likely but just wanted to mention it for clarity.

    2) If any objects that were at one time associated with the story in any way have been deleted but NOT purged. This can be more subtle, for instance there was a case where a story was moved from a folder and then the folder was deleted but not purged. For some reason there was still a reference to the folder somewhere in the story that interfered with the export / import. Check the deleted files in the Files Browser and see if there are any models, folders or other objects that have been associated with the problem stories in the past and delete them. Keep in mind that it is not possible to recover these objects once purged from the deleted files so please be sure that you want to definitively delete the object.

    If neither of these conditions apply then wait for the development team to investigate and hopefully they can quickly find the root cause.



    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Peter,

      thank you for your tips!

      Regarding the first point, all of our development is done basically in subfolders of the public folder. They also have the necessary read authorisations to be exported and imported.

      Regarding the second points, I checked the files that are marked for deletion, however I see there only some stories and nothing else except them (in both system: old and new). So I assume they should not lead to that issue. We will be waiting the reply of the SAP OSS and as a last scenario, I would just empty the deletion folder in both systems and retry again the export/import.

      Best regards,


  • Posted on Aug 05, 2020 at 10:53 AM


    I've seen this error a few times before.

    Unfortunately this usually means there is an inconsistency in the tenant regarding an object that has been previously deleted but is still registered in the database.

    I'm not aware of any customer facing action that can resolve this issue. You will have to open a support incident with SAP and attach a sample export and the details of the tenant you are trying to import into for us to analyze the issue and try to fix it via the backend.



    Add a comment
    10|10000 characters needed characters exceeded

    • Hello Peter,

      thank you so much for your prompt reply. We contacted the SAP Support, however untill now there was not a solution provided and because our old tenant is about to expire in about a week from now, I thought someone from Community could have a fast solution for that.

      I just saw an update from the OSS Note and the ticket is being forward further so we are exited to see if that will work.



Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.