Troubleshooting
SDL Web is a complex system where the symptoms of a problem can have many possible causes. The troubleshooting section helps you to locate and solve problems.
- Reproducing database problems
Before you submit a persistent problems with an SDL Web database to SDL Customer Support, follow a number of basic steps. - Troubleshooting browser-based user interfaces
If the Content Manager Explorer and Experience Manager browser-based user interfaces do not behave as you would expect, this section can help you zoom in on the source of the problem. The problem may be on the client side in Javascript, or it may be in the user interface back-end (a WCF service). - Troubleshooting Content Manager
To troubleshoot your custom code interacting with the Content Manager server, troubleshoot TOM.NET (only for templating or event handling code) or the Core Service. - Troubleshooting publishing
This section explains ways to resolve publishing problems. - Content Delivery tracing for Unix with LTTng
LTTng is an open-source tracing toolkit for Unix operating systems. Set up LTTng for your microservices with Log4j logging, then use thelttngcommand tool to create, stop and view tracing sessions. - Troubleshooting the Presentation Server
A wide variety of third-party tools can help you troubleshoot your SDL Web-based Web sites. - Troubleshooting Translation Manager
Errors can occur when sending the content from Content Manager to the translation system, or when retrieving translated content. The Troubleshooting section explains how Translation Manager handles translations and resolves content for translation, and suggests problems that can occur and how to fix them.