x Want to participate? Join the group to interact
  • State Verified Answer
  • +2 person also asked this people also asked this
  • Replies 4 replies
  • Subscribers 120 subscribers
  • Views 1462 views
  • Users 0 members are here
Browse Forums
Announcements
271
topics
260
replies
Databases and Operating Systems
773
topics
2k
replies
Financials Suite
1k
topics
3k
replies
General Discussion
2k
topics
10k
replies
Operational Suite
854
topics
2k
replies
Reporting and Analytics
1k
topics
3k
replies
Reports, Macros, and Customizations
879
topics
3k
replies
Sage CRM for Sage 300
184
topics
415
replies
KelleyA

Report Execution Error when trying to run reports downloaded from Sage Intelligence Reporting

SOLVED
Posted By

I downloaded the Sage Intelligence Report Utility and installed the PJC reports for Sage 300.  When I try to run the reports on a database, I get the following Execution Error

Description : It was not possible to connect to the database.
The error returned was :

[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.

SQLState = 08001

Please check with the administrator that the connection information configured for this data container is valid.


Number : -1147181502
Source :
Driver Error : Unknown
SQL State : Unknown

Does anyone know how to resolve this error?  Thank you.

Parents
  • +1
    verified answer

    Resolution

    Problem:  Mixed ODBC

    Resolution:  

    In the Report Manager, go to Home, R-Click and look at the Tenant Cache Viewer.  When I did this, I saw most of my connections were using the SQL Server Instance Name.  I had a couple that were using a different ODBC.  In my case, the company I was trying to run reports for was using an ODBC that was different than the Server Instance Name.  

    I went back and from my Home, R-Click and chose the option to "Clear All Cached Connection Information".  I then went to my ODBC setup for this company in database setup.  Changed it to be the Server Name.  When I went back into the Company and Report Manager, everything then worked.  The Connection information was correctly added automatically.

Reply
  • +1
    verified answer

    Resolution

    Problem:  Mixed ODBC

    Resolution:  

    In the Report Manager, go to Home, R-Click and look at the Tenant Cache Viewer.  When I did this, I saw most of my connections were using the SQL Server Instance Name.  I had a couple that were using a different ODBC.  In my case, the company I was trying to run reports for was using an ODBC that was different than the Server Instance Name.  

    I went back and from my Home, R-Click and chose the option to "Clear All Cached Connection Information".  I then went to my ODBC setup for this company in database setup.  Changed it to be the Server Name.  When I went back into the Company and Report Manager, everything then worked.  The Connection information was correctly added automatically.

Children

*Community Hub is the new name for Sage City