1. Introduction
This troubleshooting document is designed to help you understand and resolve various error codes that may occur when using :modulname:.
Error codes serve as valuable clues to identify and address underlying issues within software, hardware or systems.
The following table contains error codes along with a brief description and possible solution approaches.
Please note that while this document covers a number of common error codes, it does not include all errors you may encounter.
2. Error Codes
Code | Description | Possible solutions |
---|---|---|
0000 |
Unknown error. |
|
1010 |
URL already exists. |
Use a different URL that has not been used before. |
1020 |
Template is not mapped. |
Check the template assignment in the bridge. The FirstSpirit templates used must match the templates of the store system. |
1030 |
Field is not unique. |
The input value is already used. Store another input value for the corresponding field. |
1040 |
Mandatory field is not filled out. |
Specify an input value for the missing mandatory field. |
2010 |
Page already exists in FirstSpirit. |
Check if the page already exists in the CaaS. |
2020 |
Template is not mapped. |
Check the reference names of the page templates in the SiteArchitect with the template assignment from the bridge configuration. In the reference project, |
2030 |
Invalid page type. |
Use |
2040 |
Invalid display names format. |
Check the format of |
2050 |
A required parameter is missing. |
Check if the request contains all necessary parameters when creating a shop-driven page. The necessary parameters can be found in the Create Page subsection under Use Cases in the Frontend API documentation. |
3010 |
FirstSpirit cannot connect to the bridge. |
Open the Project Components in the ServerManager and check the input value for the |
3020 |
FirstSpirit receives 401 from the bridge. |
Open the Project Components in the ServerManager and check the input values for the |
3050 |
FirstSpirit cannot connect to the ContentCreator extension. |
Open the Project Components in the ServerManager and check the input value for the |
4010 |
Bridge cannot connect to the shop. |
Check if the shop system is reachable. |
4020 |
Bridge receives 401 from the shop. |
Check the configuration in the bridge implementation with the necessary credentials for the shop system. This varies depending on the shop system. |
8010 |
Frontend API server cannot connect to the CaaS. |
Check the stored CaaS URL of your backend service that includes the frontend-api-server module. In our reference implementation you can find the configuration under config/default.yaml for the You can view the correct CaaS URL under Project Components in ServerManager in the CaaS Connect Project App. Please ensure that your CaaS instance is accessible at the specified URL, for example using Postman. If this is not the case, please contact our Technical Support. |
8020 |
Frontend API server receives 401 from the CaaS. |
Check the stored CaaS API key, project UUID and tenant ID of your backend service that includes the frontend-api-server module. In our reference implementation you can find the configuration at config/default.yaml for the You can view the correct CaaS API key, project UUID, and tenant ID under Project Components in the ServerManager in the CaaS Connect Project App. |
8030 |
Frontend API server cannot connect to the Navigation Service. |
Check the stored navigation service URL of your backend service that includes the frontend-api-server module. In our reference implementation you can find the configuration under config/default.yaml for the You can view the correct navigation service URL under Project Components in the ServerManager in the Navigation Project Configuration. Please ensure that your Navigation Service instance is accessible at the specified URL, for example using Postman. If this is not the case, please contact our Technical Support. |
8040 |
Frontend API server receives 401 from the Navigation Service. |
Check the stored project UUID of your backend service that includes the frontend-api-server module. In our reference implementation you can find the configuration under config/default.yaml for the You can view the correct project UUID either under Project Components in the ServerManager in the CaaS Connect Project App or Navigation Project Configuration. |
8050 |
Cannot create section using TPP. |
Check whether the page already exists in FirstSpirit. If so, the already existing page must be deleted from CaaS. |
8060 |
Page is not found in the CaaS after creation. |
Check if the page was created in CaaS and exists. If this is not the case, the CaaS deployment must be checked. Please ensure that your CaaS instance is accessible, for example using Postman and that the CaaS configuration in the backend service is valid. |
8070 |
Missing parameter in request to Frontend API server for findPage. |
Provide the required parameters in the payload. These can be viewed under FindPageParams in the Frontend API documentation. |
8080 |
Missing parameter in request to Frontend API server for fetchNavigation. |
Provide the required parameters in the payload. These can be viewed under FetchNavigationParams in the Frontend API documentation. |
8090 |
Cannot create page for unknown reasons. |
3. References
Below you will find an overview of all references listed so far:
Template assignment:
APIs:
Reference implementations on GitHub:
4. Legal notices
FirstSpirit Connect for Commerce is a product of Crownpeak Technology GmbH, Dortmund, Germany.
Only a license agreed upon with Crownpeak Technology GmbH is valid for using the module.
5. Help
The Technical Support of the Crownpeak Technology GmbH provides expert technical support covering any topic related to the FirstSpirit™ product. You can get and find more help concerning relevant topics in our community.
6. Disclaimer
This document is provided for information purposes only. Crownpeak Technology GmbH may change the contents hereof without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. Crownpeak Technology GmbH specifically disclaims any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. The technologies, functionality, services, and processes described herein are subject to change without notice.