This document replaces the outdated article with the ID 94L13 and the title Information to Provide when Opening a New Intershop Customer Support Incident.
This article is meant to serve as a checklist for opening Technical Support & Service Desk tickets. By providing the following information, our engineers can resolve tickets more quickly.
A new ticket can be opened by using the web form on the Customer Support Web site under Support Tickets | Open New Ticket. Alternatively, use the known e-mail addresses.
Please provide as much information as possible from the list below. Please see also the Additional Hints.
1. Administrative Information
2. Technical Information
Optionally provide a priority.
3. Information Regarding the Problem
1.1 You find your support contract number on your support contract or in the Support portal after log in.
1.3 The Customer Support trouble ticket system groups all e-mails containing the same ticket ID to an 'interaction'. So if you reply on an e-mail belonging to another 'interaction' (or ticket) to register a new problem then this e-mail is automatically added to the existing ticket, and no new ticket is opened.
2.1 You find the Intershop product version at the following places:
INTERSHOP 7: in the SMC site after having logged in
INTERSHOP 7, Gradle based versions see or send the $IS_HOME and $IS_SHARE ivy.xml for "revision" number of the <info> tag AND the "rev" number of the <dependency org="com.intershop.assembly"...> tag.
2.2 For example, CaaS, SLES 12 or Windows 2018 Server
2.3 For example, CaaS or Oracle/MSSQL Client / Oracle/MSSQL Server 126.96.36.199
3.1 For example, "Transmission Problems" error messages in the Browser (Storefront)
3.2 For example, the error message: "... no configuration service for request ..." in webadapter.log
The most important log files are located in the following places:
INTERSHOP 7: $IS_SHARE/share/system/log (error-*.log, debug-*.log), $IS_HOME/webadapter/log (webadapter.log), $IS_HOME/log (appserver#.log)
some older Linux systems: /var/opt/intershop/eserver1/log/...
For CaaS see below:
3.3 For example, the error message "... no configuration service for request ..." indicates that the appliction server can't be contacted, maybe it isn't started? Solution: start the Application Server
3.4 Please compress log files before you attach them to an e-mail. Alternatively, when the log file size is bigger than 10 MB, upload the archived log files to the Intershop Customer Support FTP server.
3.5. For example
Steps to repeat:
1. In B2B, create a Pricelist PL1, assigned "Everyone" as target group
2. Choose a product (e.g. 10809311) and add a pricelist price for our pricelist of 333 USD for 1 item (click "Special Prices to add the price")
3. Check the storefont, search for G3610 and see that the price is 333 USD (OK)
4. Login as pmiller and see that the price is now 993 (WRONG)
5. Log out again, price is 333 (OK)
Sometimes, problems occur when trying to change configuration parameters or add functionality to the system. Do not just tell the support engineer about the problem but also about the goal you have in mind. Sometimes, a different approach can lead to better results and avoid problems.
The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.