Sage Error Code 00005 | +1-866-973-9785

When there is a problem with the card’s authorization or with banking details such account information.

How log files are maintained in Sage CRM

The tracking of run-time errors is one of the most important elements that should be included in each application. Trapping the error is crucial since it not only alerts the afflicted region but also expedites problem-solving.
Fusion charts based on XML now available via the COM API

Sage CRM records both the actions taken immediately in CRM as well as the errors that are produced. Sage CRM includes many log categories for different types of logs, such as SQL logs,.NET logs, Outlook logs, etc. A user in CRM can see files in the logs folder using the two methods listed below.
1. Sage CRM stores all logs in the path listed below.
Logs can be found under C:Program FilesSageCRMCRM Instance.
2. The user can also view logs from within Sage CRM by going to the route below and choosing the appropriate log file type from the drop-down menu labelled Select Log Files.
System | Administration | Logging

When a user chooses one of the options in the Select Log Files drop-down menu, the

The main distinction between the two methods above is that with option 1, we REQUIRE access to the server where the CRM is hosted. Now, this will only apply to the server administrator or a single user. Option 2 is accessible to CRM users, allowing them to at least grasp the gist of the issue. The standard logs offered by Sage CRM are the log kinds that are listed in the drop-down menu. What happens if we require CRM to display logs from an extended solution, such as our GUMU Sage 100 ERP integration with Sage CRM or GUMU Sage 500 ERP integration with Sage CRM product.

For your information, GUMU can produce its own logs, but right now it’s necessary to view them from CRM.