For example, adjusting indexes for a SQL Server query.
You will need to modify two configuration files to determine the duration of a query.
This may show errors and other related information.
When using the gateway for scheduled refresh, Refresh History can help you see what errors have occurred, as well as provide useful data if you should need to create a support request.
(Exception from HRESULT: 0x8013141A or something like that.) )throwing out. Note: Disable strong name verification will of course introduce security vulnerability, A malicious assembly could use the fully specified assembly name (assembly name, version, culture, and public key token) of the assembly added to the skip verification list to fake its identity.
Just had this error while trying to import a solution to Dynamics CRM 2013.
These counters can be access through the Windows Performance Monitor tool. You may find that response through the gateway is slow.
This could be for Direct Query queries or when refreshing your imported dataset.
On checking the log file I found that the error was with regard to a chart.
It was easy to see which chart it was in relation to, so what was the issue?
These can be helpful to understanding if we have a large load of activity and may need to make a new gateway.
These counters will not reflect how long something takes.
It is not recommended to leave this setting enabled long term. Enterprise Gateway Information: 0 : 2016-09-15T.2664967Z DM.