Symptom
- Content has been successfully imported using the Learning import tool.
- Error 404- File or Directory not found encountered when trying to launch the course with the imported content.
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Environment
SAP SuccessFactors Learning
Reproducing the Issue
- Log in as a user > Go to Learning >
- Search and start the course from the learning plan.
Cause
- The 'directory' is missing from the URL prefix.
- An additional space is added during content import at the end of the URL field in the 'Deployment Location'.
- There is an incorrect backend configuration
- The URL Path when launching the content does not match what is in the URL Prefix (extra data between the Customer_e and Self-managed) when a tracing is done.
Resolution
- Check the Directory field. (System Administration > Configuration > Content Deployment Locations > search and edit the affected deployment location ID) >
- The Directory specifies which directory the content will be uploaded to on the content server (iContent).
- The URL prefix specifies the launch path for the content.
- The URL prefix must contain the directory as well.
- Remove the additional blank space after the folder name in the filename (Content > Content Objects > Search and edit the Launch Method of affected content object) >
- Check iContent folder structure path.
- Confirm the folder path inside iContent server is correct by logging in to the iContent account.
- Keep in mind that the Content Object Filename is divided in 2 parts: Prefixes (See this note) and Suffixes (iContent Folder Path).
- Prefixes are always the same*.
- Suffixes will always vary.
- Suffixes will always start after prefix part "self-managed/". Everything after the "self-managed/" is related to the iContent folder structure.
In this scenario, the iContent folder structure is: LMS/Prod_Content/Compliance/index.html.
- Content Object Filename must be: "prefix" + "/LMS/Prod_Content/Compliance/index.html" (e.g. /learning/user/onlineaccess/icontent.do?Course=CUSTOM&url=/self-managed/LMS/Prod_Content/Compliance/index.html)
- Kindly see folder structure below after successfully logging into the iContent account.
Example scenario 1: If the folder structure and/or "index" file does not exist inside the iContent account, that's why the 404 is being thrown.
- To resolve this, create the exact folder structure based on the content object's filename or set up a new folder structure and change it in the content object's filename.
Example scenario 2: If the folder structure exists but there are some divergence in the path (additional folders, index file or folder are named differently, etc.), that's why the 404 is thrown.
- To resolve this, include the additional folders inside iContent folder structure or adjust the content object's filename to match what's inside iContent folder structure.
If all of the above is checked and there are still issues, the backend configuration could be incorrect. Contact SAP Support providing tracing logs (or support access to obtain tracing logs), so the Operations team can be involved.
Note:
- "My folders" folder is not considered for this set up.
- * - It will vary based on the instance's datacenter.
- Take into consideration that SAP doesn't hold any self-managed customer iContent credentials. Even though SAP provide the accounts to customers, it's the customer's responsibility to maintain it.
- If nothing wrong is found after concluding all the checks, verify if the content holds one or more files with the size over 1800 MB (~1.8 GB). Files bigger than 1800 MB (~1.8 GB) aren't supported and will result in the "404 File or Directory not found". Check the KBAs 3165280 and 2318240 for additional details about it.
See Also
Keywords
SF, Success Factors, LMS, learning, 404 File or Directory not found, iContent, filename, structure path, deployment setup, credentials. launch method, directory , KBA , LOD-SF-LMS-CNT , Content , LOD-SF-LMS , Learning Management System , Problem