x Want to participate? Join the group to interact
Options
  • State Not Answered
  • Replies 6 replies
  • Subscribers 106 subscribers
  • Views 2514 views
  • Users 0 members are here
Browse Forums
Announcements
293
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
45
topics
92
replies
Payroll, Time Tracking, and Job Cost
777
topics
1k
replies
Reporting and Analytics
963
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
Terry Bumgardner

Why does the Mas90 ODBC Driver keep showing up in Sage Intelligence?

Posted By

We are having a problem with report totals doubling because the 'Mas90 4.0 ODBC Driver'  driver keeps showing up as one of the connection types. 

Example - The Tenant Viewer looks similar to the following listings - 

TENANT,      CONNECTION TYPE,           DB SERVER,      DB CATALOG,   DB UID,               DB PSWD

MAS_AII,      ODBC Driver SQL Server,    APPSERVER,     MAS_AII,            MAS_Reports,     ************

MAS_RCS,   ODBC Driver SQL Server, APPSERVER,    MAS_RCS,         MAS_Reports,     *********** 

MAS_MPL,   ODBC Driver SQL Server, APPSERVER,    MAS_MPL,         MAS_Reports,     **********

MAS_AII,      MAS 90 4.0 ODBC Driver,     APPSERVER,    MAS_AII,            MAS_Reports,     *********

The last driver should not be included. Why is this happening? And what can we do to get rid of this issue?

Thanks, 

Terry

Parents
  • 0

    OK.  I qualify as confused.  I believe the ODBC driver is how Sage Intelligence accessed the data.

    What or where is this Tenant Viewer?   I can't claim that I have ever seen it.  Maybe I will learn something new today?

  • 0 in reply to TomTarget

    I banged my head against this wall recently for a Premium customer.  We basically had to scrub the workstation of all references to the Providex ODBC driver, so only the SQL connections existed.  (It is workstation specific, so you can also try running SI from somewhere else).

    I believe there is a KB article with some details too (how to reset and re-try).

Reply
  • 0 in reply to TomTarget

    I banged my head against this wall recently for a Premium customer.  We basically had to scrub the workstation of all references to the Providex ODBC driver, so only the SQL connections existed.  (It is workstation specific, so you can also try running SI from somewhere else).

    I believe there is a KB article with some details too (how to reset and re-try).

Children

*Community Hub is the new name for Sage City