Symptom
When importing SAP Analytics Cloud Business Content, the import fails with the following error:
"The resource does not exist, or you do not have permission to read it."
This can occur for any content package that includes classic stories. In some cases, the corresponding models are imported successfully or are already available, but the stories are missing and cannot be restored through the Business Content import.
The same content package may import successfully in another tenant, which indicates that the issue is tenant-specific and not caused by a defect in the Business Content package itself.
Environment
SAP Analytics Cloud
Reproducing the Issue
-
Log on to the affected SAP Analytics Cloud tenant.
-
Open the Content Network.
-
Navigate to Business Content.
-
Select any package that contains classic stories.
-
Start the import.
-
Observe that the import fails with the message:
"The resource does not exist, or you do not have permission to read it." -
Review the imported content and note that the related stories are missing or only partially imported.
Cause
The content package contains objects (stories) created in the Classic Story Experience.
If the tenant has the setting Access content created in the Classic Experience disabled, SAP Analytics Cloud cannot access those classic stories during the import. This results in the resource/permission error, even though the content itself is valid.
This behavior is consistent with the package importing successfully in tenants where access to Classic Experience content is enabled.
Resolution
Enable access to content created in the Classic Experience:
- In SAP Analytics Cloud, open System.
- Select Administration.
- Open System Configuration.
- Enable the setting Access content created in the Classic Experience.
- Save the setting.
- Retry the Business Content import.
After enabling this option, the classic stories should import successfully.
Additional Information:
- The Access content created in the Classic Experience setting is a temporary compatibility option and is expected to become unavailable after Q4 2026. Classic stories are also planned for deletion after Q4 2026.
- Enabling this setting only allows classic stories to be imported; it does not convert them to the Optimized Story Experience.
- Recommended operational approach:
- Enable the setting temporarily.
- Import the required content.
- Convert the imported classic stories to the Optimized Story Experience before the Classic Experience retirement deadline (Q4 2026).
- Validate the converted stories, including layout, visualizations, filters, input controls, calculations, linked analysis, navigation, data access, authorizations, and bookmarks/prompts.
- If the same package imports successfully in another tenant, this further confirms a tenant configuration issue rather than a content package defect.
See Also
Keywords
OAA, Business Content, stories missing, import failed, resource does not exist, RESOURCE_NOT_EXIST, HTTP 500, Classic Experience, classic stories, enable classic content access, Content Network, optimized story experience, SAP_Content folder, overwrite objects and data , KBA , LOD-ANA-ACN , SAC Content Network , Problem
SAP Knowledge Base Article - Public