Sage 100

 View Only
Back to discussions
Expand all | Collapse all

Removing the SOTAMAS90 driver from ODBC Data Source Admin.

  • 1.  Removing the SOTAMAS90 driver from ODBC Data Source Admin.

    Posted 12-02-2019 15:17
    New Terminal Server and v2018 Sage 100 Premium (was on 2017 advanced on another server/tserver)
    I'm having some problems with Sage Intelligence and thinking it's due to a Driver MAS90 4.0 ODBC Driver in the ODBC Data Source Administrator (32 bit).  
    I haven't installed a non premium workstation setup (old version) so not sure how this even got here.  I do have eFiling installed and Paya Desktop.  It's possible but don't remember accessing old Sage via the 'mas90' method.
    There is no User or System DSN SOTAMAS90 setup, rather the Driver just shows up.  

    In my Sage Intelligence, my Tenant Cache keeps adding companies with a connection type of the MAS90 4.0 ODBC Driver.  I clear the cache and it comes back immediately (I close SI, open Report Manager and access Tenant Cache and the add'l company is listed).  

    Screenshots attached.

    So Frustrating!
    any Ideas?

    ------------------------------
    Nancy Hanson
    Blytheco LLC
    Eagan MN
    ------------------------------


  • 2.  RE: Removing the SOTAMAS90 driver from ODBC Data Source Admin.

    Posted 12-02-2019 15:26
    I hope someone has a solution for this! I have a client with the same issue (has been happening for 2 years now. For them, it also creates a duplicate entry on the accounts page, and the reports will error out saying there are duplicate account keys. That's how we know it created the company with the wrong ODBC Source. We originally placed the blame on an old workstation or something lingering on the server, but recently they moved both the application and the SQL database to a new server. So, nothing Standard or Advanced hanging out. It leads me to believe maybe it is something hard-coded on the report itself? Could there be some formula on the back end tied to a report? For my client, it doesn't happen all the time, only rarely, so we can't find a common denominator. 

    Hopefully some of that info will help someone figure out what's going on. I have reached out to Alec Burke at Sage, and he has no ideas outside of whats been documented already in the KB

    ------------------------------
    Michelle Forsey
    Eide Bailly, Inc.
    801-456-5470
    ------------------------------



  • 3.  RE: Removing the SOTAMAS90 driver from ODBC Data Source Admin.

    Posted 12-02-2019 15:29
    (A colleague is handling our case... next step is getting South Africa programmers to take a look, if / when it happens again).

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


  • 4.  RE: Removing the SOTAMAS90 driver from ODBC Data Source Admin.

    Posted 12-02-2019 15:27
    Open a case with Sage.  We have the same thing with a Premium customer who has never installed Providex drivers on the workstations in question... and the extra entries keep coming back into the Tenant Cache.
    It's been an issue off and on for years.  Customer is on the verge of abandoning SI because it is so frustrating / time consuming... permissions breaking with every Windows Update, and the mysterious recurring DSN's. I don't blame them.

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------



  • 5.  RE: Removing the SOTAMAS90 driver from ODBC Data Source Admin.

    Posted 12-02-2019 15:28
    You have to create a SOTAMAS90 system dsn.  Use the SQL server native client driver and configure the connection to point to the SQL server.

    ------------------------------
    Doug Higgs
    Midwest Commerce Solutions, Inc
    (312) 315-0960
    "Would you tell me, please, which way I ought to go from here?"
    "That depends a good deal on where you want to get to."
    Oscar Wilde - Alice in Wonderland
    ------------------------------



  • 6.  RE: Removing the SOTAMAS90 driver from ODBC Data Source Admin.

    Posted 12-02-2019 15:30
    Doug
    Why would I want to create one? 
    Creating one will resolve my Tenant Cache Issue?
    N​

    ------------------------------
    Nancy Hanson
    Blytheco LLC
    Eagan MN
    ------------------------------

    Original Message


  • 7.  RE: Removing the SOTAMAS90 driver from ODBC Data Source Admin.

    Posted 12-02-2019 15:32
    ll give it a shot @Doug Higgs and report back @Nancy Hanson. (although it might be a while). If using the SQL ODBC would take the place of the potential Standard ODBC Sage creates because something is "missing" it makes perfect sense! ​​

    ------------------------------
    Michelle Forsey
    Eide Bailly, Inc.
    801-456-5470
    ------------------------------

    Original Message


  • 8.  RE: Removing the SOTAMAS90 driver from ODBC Data Source Admin.

    Posted 12-02-2019 15:34
    Although... usually when creating a SQL System DSN, I would change the Default Database (so it's pointing to just one company), in this case they have the connector, and report on multiple companies... so just leave it as the default(master)???

    ------------------------------
    Michelle Forsey
    Eide Bailly, Inc.
    801-456-5470
    ------------------------------

    Original Message


  • 9.  RE: Removing the SOTAMAS90 driver from ODBC Data Source Admin.

    Posted 12-02-2019 15:33
    It is not "SOTAMAS90"... it is DSN's being duplicated in the Tenant Cache, using the MAS 90 driver on a Premium system.


    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


  • 10.  RE: Removing the SOTAMAS90 driver from ODBC Data Source Admin.

    Posted 12-02-2019 15:37
    I tried it anyway, can't hurt anything to have an extra System DSN in there. (Lord knows I have quite a few on my system!). If anything changes I will let you know.

    ------------------------------
    Michelle Forsey
    Eide Bailly, Inc.
    801-456-5470
    ------------------------------

    Original Message


  • 11.  RE: Removing the SOTAMAS90 driver from ODBC Data Source Admin.

    Posted 12-03-2019 09:18
    I did open a case via email support late last night.  We'll see what transpires.​

    ​

    ------------------------------
    Nancy Hanson
    Blytheco LLC
    Eagan MN
    ------------------------------

    Original Message


  • 12.  RE: Removing the SOTAMAS90 driver from ODBC Data Source Admin.

    Posted 12-03-2019 12:08
    Had this a few months ago on a new Premium install. 

    See KB 69723. 

    Creating a new repository and re-registering fixed it for this customer. This was new, so no existing reports to export/import. 

    ------------------------------
    Eric Lunceford
    First Mate Business Solutions
    Oklahoma City, OK
    877-880-8960
    https://www.firstmatellc.com/
    ------------------------------

    Original Message


  • 13.  RE: Removing the SOTAMAS90 driver from ODBC Data Source Admin.

    Posted 12-03-2019 22:22
    So interesting observation tonight.  Showed customer how to delete the 1 row in the Tenant Cache but the reports were still not running due to Duplicate Rows.  So I logged on and cleared the Cache.  I then had to open Report Manager in every company that I wanted to Cache as usual for Consolidated Designer.  After doing this and looking at the Tenant Cache, noticed all the Connection Types are now MAS90 4.0 ODBC and there are no ODBC SQL Drivers listed (in the Tenant Cache).  The DB Server is the Sql Instance, The Catalog is MAS_xxx and the DB UID is MAS_Reports
    Is this a problem?  The report ran successfully.  Are we all sure that even for a Premium we don't want the MAS90 4.0 ODBC connection?  Why would my connection type change?
    I'm so confused!  And of course no response from my support ticket yet.

    ------------------------------
    Nancy Hanson
    Blytheco LLC
    Eagan MN
    ------------------------------

    Original Message


  • 14.  RE: Removing the SOTAMAS90 driver from ODBC Data Source Admin.

    Posted 12-04-2019 09:16
    That happened to us too... very weird. Sage did something for our customer yesterday (running a "Compact" utility?), so fingers crossed.

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


  • 15.  RE: Removing the SOTAMAS90 driver from ODBC Data Source Admin.

    Posted 12-15-2019 14:20
    I may have solved this at least for this customer.  On the server during the upgrade I had a copy of the old version for migration and had run it as MAS90.  I think (although not 100%) that this created the SOTAMAS90 ODBC driver. Workstation Setup had not been run so I have to assume it came just from running old Sage as MAS90.  I deleted the SOTAMAS90 on the server (even though SI is not licensed there) and then cleared the Tenant Cache and recached all the companies.  They all came in as they should with the ODBC Sql Driver and I have not had the problem since doing this.  
    For those us you having this problem, maybe check the server ODBC connections?
    Also, Richard at Sage indicated there could be remnants of the Sage Providex in the Registry that need to be removed. Mine was a new server so didn't go looking.
    Nancy

    ------------------------------
    Nancy Hanson
    Blytheco LLC
    Eagan MN
    ------------------------------

    Original Message


Related Content