The Troubleshooting section includes topics covering various issues, solutions, and troubleshooting techniques for Sugar.
PHP provides various levels of feedback to developers in the form of notices, warnings and on occasion errors. Some of these can be ignored and are only used to inform programmers of best practices (and violations there of) and others, such as errors, as you suspect, need to be addressed.
When managing records in Sugar®, some fields pertain to a relationship and as you type text in the field, a search is performed to find relevant matches. On high-performance systems, this method of querying can lead to unintended results because the query returns quickly before the user has finished typing the full string they wish to search.
Sugar uses your internet browser's cache to optimize page-load speeds and general performance by saving and reloading visited pages instead of pulling the same data over and over again each time you revisit a page or site. If you tend to open Sugar pages in multiple tabs, frequently update records, or make system-wide changes, you run the risk of viewing a cached version of Sugar and not seeing the most recent changes. When you experience unexpected behavior in the application, try clearing your cache as a first defense.
Sugar® has the ability to constantly log information about its actions depending on the logging level the administrator has chosen. When an issue or unexpected behavior is encountered while using Sugar, the Sugar log can be a valuable source of insight. While it is recommended to leave the logging level at "Fatal" for daily use, the level can be adjusted as necessary when attempting to troubleshoot a particular issue.
The Quick Repair and Rebuild function in Sugar® allows administrators to perform common maintenance routines in their Sugar instance. The Repair menu is available only to system administrators and can be accessed by navigating to Admin > Repair.
When I attempt to log into Sugar, I cannot log into the system. There is no error message. If I switch browsers or empty my cache, then I am able to log into Sugar. Why does this problem occur?
Occasionally, you may encounter an error or unexpected behavior in Sugar® such as the page not loading properly. This article will go over some high-level troubleshooting tips based on common symptoms.
Upon logging into your instance, you see that the icons are not displaying correctly on the Admin panel or that the "Next Page" button in a legacy module does not work or is showing the wrong icon.
While attempting to access a Sugar® page, you see the following error message: "Possible Cross Site Request Forgery (XSRF) Attack Detected".
While using Sugar, you may occasionally encounter a database error or unexpected behavior. This article will go over how on-site clients can recognize symptoms of database errors, locate the database errors, and apply common solutions to resolve issues.
An incorrect count is shown when selecting "All records" as well as in a module's listview count.
This article describes the first steps to try when attempting to access a Sugar page results in an "Internal Server Error - 500" or "Page Cannot Be Displayed" error.
A user is unable to browse the Knowledge Base tree past the parent tags. An error message is not always returned, but may include one of the following:
The Knowledge Base Tag Browsing window hangs when attempting to expand a tag. A spinner icon appears next to the tab being expanded but nothing else happens.
Traceroute is a commonly used network tool that helps identify bottlenecks in speed and connectivity when experiencing issues connecting to a website or server from a computer. Traceroute tracks the route packets taken from an IP network on their way to a given host. It utilizes the IP protocol's time to live (TTL) field and attempts to elicit an ICMP TIME_EXCEEDED response from each gateway along the path to the host. This article covers using traceroute to test latency issues when connecting to your Sugar® instance.
In Sugar, when stock or custom modules do not appear within the navigation bar, they may have been hidden from view via Admin > Display Modules and Subpanels.This article will cover how to verify if a module is hidden from view and the steps required to make a module visible to users in the instance.
If you are experiencing issues with latency or uploading files, you can troubleshoot your internet connectivity using this article.
When deploying Sugar, the PDF engine only has the capability to display specific characters. This article covers how to add additional language support for PDF rendering.
When developing with Sugar, you may experience an API request returning a 500 error of . The request's response will be as follows:
As more records are added to an instance, errors like this may begin to appear for non-admin users: "Query limit of XXXX reached for Calls module"
While utilizing Sugar, users may be unexpectedly logged out of the system. This article covers several reasons that the browser may automatically log a user out as well as some high-level troubleshooting tips.
Attempting to upload a large file to a Sugar module fails; the page may simply continuously load, or fail with "file too large" type of error.
There may be occasions where you experience unexpected behavior in the Sugar® application. Accessing Sugar using your browser's privacy mode and checking if the issue persists can help you determine the source of the problem. A browser's privacy mode opens a new browsing session which has no access to cached data, cookies, or history. In addition, it disables all plugins, extensions, and add-ons for the browser, allowing you to access your Sugar instance using a completely clean browser. This article will cover how to access the privacy mode when troubleshooting via the various supported browsers in Sugar.