New bank feeds feature in Sage 100 2018.5

I know it is early as this update only was delivered yesterday,  but has anyone successfully gotten past the welcome screen for setting up bank feeds?

Put in my e-mail address, accepted the terms and conditions and clicked on Get Started and wait and wait and ….

Eventually it comes back claiming an unexpected error occurred setting up your account in Sage Bank Feeds.  Please try again later.

I'm assuming that it is some kind of hiccup in the roll out, but I really don't know.

Help screens really don't have any information after the welcome screen.

Parents Reply Children
  • 0 in reply to JamieConnolly

    I'm using Sage 100 Advanced.   Initially tried from Window 10 workstation that has both Edge and IE11.

    Just tried from Server (2008 R2) with no luck.  Also tried running in standard mode with no luck.

    I am noticing that today I'm getting to a CAPTCHA screen that I was not getting on Friday, however it still ultimately fails.

    Last try from the workstation resulted in the following.

    I note an error indicating no matching customer could be found.  Is there some place else that an account needs to be set up first that I have missed in the documentation?

    [2018-11-18 17:45:01,772] [INFO ] [Thread#4     ] [BankDriveClientLibrary] sending request to: https://www.sagetokenservice.com/api/v1/requestToken
    [2018-11-18 17:45:55,268] [INFO ] [Thread#9     ] [BankDriveClientLibrary] sending request to: https://www.sagebankdrive.com/api/v1/organisations/25f21274-ad73-441c-abdf-71f12975a31f
    [2018-11-18 17:46:01,173] [INFO ] [Thread#9     ] [BankDriveClientLibrary] preparing request
    [2018-11-18 17:46:01,178] [INFO ] [Thread#9     ] [BankDriveClientLibrary] generating signature
    [2018-11-18 17:46:01,180] [INFO ] [Thread#9     ] [BankDriveClientLibrary] request signed with SignatureBase: GET&https%3A%2F%2Fwww.sagebankdrive.com%2Fapi%2Fv1%2Forganisations%2F25f21274-ad73-441c-abdf-71f12975a31f&&c0b51a1b-806d-4891-a94e-e0aa691e9f02
    [2018-11-18 17:46:01,180] [INFO ] [Thread#9     ] [BankDriveClientLibrary] sending request to: https://www.sagebankdrive.com/api/v1/organisations/25f21274-ad73-441c-abdf-71f12975a31f
    [2018-11-18 17:46:01,851] [ERROR] [Thread#12    ] [BankDriveClientLibrary] caught exception sending request: The remote server returned an error: (400) Bad Request.
    [2018-11-18 17:46:01,865] [ERROR] [Thread#8     ] Failed to create Org:
    WEB EXCEPTION RESPONSE:
    {"$diagnoses":[{"$severity":"Error","$sdataCode":"ApplicationDiagnosis","$applicationCode":"CustomerNotFound","$message":"No matching customer could be found"}]}
    EXCEPTION:
    System.AggregateException: One or more errors occurred. ---> System.Net.WebException: The remote server returned an error: (400) Bad Request.
       at Sage.BankingCloud.Client.ApiWrapper.<SendRequest>d__138`1.MoveNext()

  • 0 in reply to TomTarget

    Greetings Tom,

    There isn't anything more that a customer should need to do.  I did duplicate the issue on Sage 100 2018.5 Advanced by using a test product registration that could not be validated by the Bank Feed Service and I received the same log error as you shared above.

    This indicated that the issue you are encountering is because the Sage 100 product registration information you are using cannot be located by the Bank Feed service to validate the Sage 100 installation as being valid for Bank Feeds.  Would you please open a case with our Customer Support Team so that they can verify the license information and work with you to resolve this.

    Thank you,
    Kent