Ordinarily you can enable SQL Server tracing from within an X3 User session, by navigating to Help> Diagnostics and then selecting “Activation Timing”
There are several reasons why SQL tracing may not be able to be launched using this method. For example, if your database is on a different server to the X3 Process server, then you will see an error message “Error accessing database server (-138)”
The simplest way to overcome this message is to manually identify and trace the X3 user session using the database tools, either SQL Server Extended events, or the Oracle SQL trace
- Solution ID
- 220924260102484
- Last Modified Date
- Tue Mar 22 08:06:14 UTC 2022
- Attributes
-
Product Details
Version: 12
Version: 11
Version: 9
Version: 8
Version: 7
- Views
- 0