Report Troubleshoot: Difference between revisions
Crmtogether (talk | contribs) No edit summary |
Crmtogether (talk | contribs) No edit summary |
||
| Line 8: | Line 8: | ||
[[File:failedtoopenconnection.png]] | [[File:failedtoopenconnection.png]] | ||
If the report connection was made using ODBC, for this to work via Crystal Manager (and IIS) the server needs to have the same connection setup on the "system" level (as opposed to "User") in the ODBC settings | |||
[[File:odbccrystal.png]] | |||
Within Crystal Manager the "server name" value should be the name of the ODBC connection name(in my sample it is TSNTST) | |||
[[File:odbcsettings.png]] | |||
Revision as of 12:49, 3 January 2012
This area will outline how to resolve issues with reports being run in the system.
1. If reports use ODBC connections you must configure the "DB Server Name" to point to the ODBC connection name rather than the servers name.
The ODBC connection must also be created at the "System" level and not the "User level". This is because CRM runs withing IIS and not at a user level so it would not have access to that ODBC connection.
The error you will see in this case is "Failed to open connection".
If the report connection was made using ODBC, for this to work via Crystal Manager (and IIS) the server needs to have the same connection setup on the "system" level (as opposed to "User") in the ODBC settings
Within Crystal Manager the "server name" value should be the name of the ODBC connection name(in my sample it is TSNTST)
