Sage 100

 View Only

  • 1.  sage intelligence error "failed to locate the mas_system directory"

    Posted 07-10-2024 20:12

    Hello

    Having issues with Sage Intelligence installation at the client level. I get the error " Failed to locate the MAS_System directory". When I get this error and then in view the Tenant Viewer I can see an Providex ODBC Connection. They are now on Sage Premium, so all I should see is the ODBC Driver SQL Server.

    When I run Sage Intelligence on the server, I do not get this error it is just on the clients workstations. I thought it was because of prior Sage 100 installation but we've uninstalled and reinstalled Sage removing the ODBC registries. I've followed the KB on how to do a clean uninstall and reinstall of Sage Intelligence. 

     Has anyone seen this or have a suggestion?



    ------------------------------
    Tina Meacham
    RKL eSolutions, LLC
    ------------------------------


  • 2.  RE: sage intelligence error "failed to locate the mas_system directory"

    Posted 07-11-2024 08:12

    Ugh, I had a similar experience and could run Sage OUTSIDE of SI.  It turns out that something was pointing to the wrong SQL instance.  I'm not a SQL person and Sage is who found this, so I can't give you any more details that that.



    ------------------------------
    Beth Bowers
    (269) 358-0989
    ------------------------------



  • 3.  RE: sage intelligence error "failed to locate the mas_system directory"

    Posted 07-11-2024 08:13

    Oh, I can tell you I worked with Nathan Shaw at Sage on it and he figured it out.



    ------------------------------
    Beth Bowers
    (269) 358-0989
    ------------------------------



  • 4.  RE: sage intelligence error "failed to locate the mas_system directory"

    Posted 07-11-2024 12:24

    Beth,

    Thank you,  I'll go create a case and ask Nathan. He's got another SI case for me opened. 



    ------------------------------
    Tina Meacham
    RKL eSolutions, LLC
    ------------------------------

    Original Message


  • 5.  RE: sage intelligence error "failed to locate the mas_system directory"

    Posted 07-11-2024 10:40

    In Report Manager, double-click the Home icon at upper left, then click on the Tools tab, Tenant Cache, View Tenant Cache. Select and delete any entries using the Providex ODBC connection.



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



  • 6.  RE: sage intelligence error "failed to locate the mas_system directory"

    Posted 07-11-2024 12:21

    Hi Kevin, I've cleared it out multiple times. Each time it errors, the old ODBC connection shows up. 



    ------------------------------
    Tina Meacham
    RKL eSolutions, LLC
    ------------------------------

    Original Message


  • 7.  RE: sage intelligence error "failed to locate the mas_system directory"

    Posted 07-11-2024 12:28

    I have a similar situation where customer went from providex to premium and the tenant cache constantly needs to be cleared out to be able to run reports. I opened a case with Sage and apparently if you send them your SVD/MetaData they can manually remove this connection for you. I have yet to send it as the person I was working with is not in until Monday.



    ------------------------------
    Dana Halpin
    Vrakas/Blum Computer Consulting, Inc.
    ------------------------------

    Original Message


  • 8.  RE: sage intelligence error "failed to locate the mas_system directory"

    Posted 07-11-2024 17:58

    Dana,

    I created a case and I'm waiting on the same person to come back into the office to assist. Hopefully that is the fix for me as well. 



    ------------------------------
    Tina Meacham
    RKL eSolutions, LLC
    ------------------------------

    Original Message


  • 9.  RE: sage intelligence error "failed to locate the mas_system directory"

    Posted 07-17-2024 09:54
      |   view attached

    I found a work around and the issue. When creating the new repository, the old 4.0 Driver was getting created with all of the reports and nothing under the SQL Driver. I found this by opening the connector and reviewing the connections. I was able to export out a GL Detail from a SQL install, then import into their system and it created under the correct driver.
    I took a copy of the SI folders from a dev system I had and repointed the repository to that file directory. Then used the clients keys to re-register. No more error.  Not sure if this is the "right" way to correct, but Sages responses was to uninstall, reinstall and create a new repository. 



    ------------------------------
    Tina Meacham
    RKL eSolutions, LLC
    ------------------------------



Related Content