Reputation: 1667
Some users are getting an error message when trying to attach a file to a case but it's not very helpful. It just says SQL Server Error. A SQL Server error occurred.
Is there a recommended place to go to find more information on why an error happened? The user has a "Download Log File" button their screenshot of the error but it is greyed out. I assume someone with higher permissions would be able to download this log file?
I have read about Stunnware as a good tool for reading logs? Is this the best one to use?
Upvotes: 2
Views: 5021
Reputation: 1482
An alternative approach that doesn't require a SQL Server trace is to use the Dynamics CRM 'trace logging' feature that you can enable for on-premises servers.
Here are details on trace logging and how to set it up:
If you set it up once, with all default settings only, you will get a log entry for generic SQL errors that includes the actual message SQL Server threw. It's not as detailed as a SQL Server SQL trace (e.g. you can't look at the query that is failing) but it gives you a more specific error message. We have trace logging enabled for all our Dynamics CRM development machines and it can speed up this kind of debugging nicely.
Upvotes: 2
Reputation: 4111
More than likely, the CRM log will just have the same error like "Generic SQL Error" or "SQL Server error." We have had success starting a trace on the SQL Server and then execute the action that is causing the error. The trace will usually give you much more information about the actual error.
Upvotes: 3