ODBC connection with "Invalid user id specified"

Hello everyone I am a new IT person to involve with sage50

I want connect to database by using 3rd party application such as Excel, Access, Power bi through ODBC to create real time and interactive report by power BI, I following this article https://support.na.sage.com/selfservice/viewContent.do?externalId=12693&

I have created password for 3rd party application but once when I try to login by password that I created ODBC said "Invalid user id specified"

even I configure to read only mode, I still cannot connect to the data

ps. my company use sage50 version 2022 installed on window server 2012R2

  • 0
    Hi Blake, 

    Thank you for reaching out. Our cloud based software solution, Sage Accounting appears to have a connector in place for PowerBI.
     
    So far I've been unable to find something similar in place for your software solution, Sage 50 US. I've forwarded your inquiry onto the team to double check. Note that Sage Customer Support does not provide assistance for issues related to third party products or enhancements, hardware, report customizations, state or federal tax-related questions, or specific accounting questions.
     
    KB 15362 may offer you some alternate solutions. Logicim XLGL is a Microsoft Excel add-in that makes Sage 50 U.S. Edition reporting easy and flexible and is perhaps something to review in place of PowerBI.
     
    Will update you with any news.

    Warm Regards, 
    Erzsi
  • 0 in reply to Erzsi_I

    Update that although it's not specific to PowerBI, the Sage 50 US Support Team shared KB 12693 (same one you already tried) on how to connect to the program using ODBC/OLEDB.

    For  "Section I: Allow Data Access from your Sage 50 Company" the team advised that the user ID will always be Peachtree - the password must be exactly 7 characters alpha-numeric.

  • 0 in reply to Erzsi_I

    Any update ?

    I still cannot connect to database by ODBC

  • 0

    User Name should = Peachtree   (this is fixed; you can't change it)

    Password -  Make sure you using a 7 character password.  There is some funky logic that truncates anything longer.

    If you can't connect after this, it's related to the ODBC connection protocol you are using in the application you are attempting to connect from.