web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Suggested Answer

Confirmation of Web Services Endpoint Call

(0) ShareShare
ReportReport
Posted on by 959

I'm trying to use a data connector within SQL Server Integration Services (SSIS) to get information out of BC On-Line.
I'm having difficulties getting it to work and have been advised the problem is at Microsoft's end.

Apparently the following call is being made (can be executed in any browser) and it should return the available services to latch onto.
Can those of you out there that have BC on-line (not on-prem) please confirm of deny this works!

The URL is api.businesscentral.dynamics.com/v2.0/{Customer Guid}/{Tenant}/WS/{company}/services

e.g.

api.businesscentral.dynamics.com/v2.0/5981fced-e8e0-437a-8b7f-8663be1d21f1/Production/WS/My%20Company/services

The output I'm getting is and exception that looks like this, I suspect this is an on-prem method only???

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
  <s:Body>
    <s:Fault>
      <faultcode xmlns:a="urn:microsoft-dynamics-schemas/error">
        a:Microsoft.Dynamics.Nav.Service.WebMetadata.MetadataException
      </faultcode>
      <faultstring xml:lang="en-US">The metadata object Page 5396 was not found.</faultstring>
      <detail>
        <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/">The metadata object Page 5396 was not found.</string>
      </detail>
    </s:Fault>
  </s:Body>
</s:Envelope>

I have the same question (0)
  • Suggested answer
    Chris Bulson Profile Picture
    on at

    Hello,

    That URL looks correct and I can confirm it works in my environment.  The error you're getting is in relation to page 5396, which I don't believe is a valid page.  You may want to navigate to your 'Web Services' page and take a look to see if you have that page showing?  If you do I would recommend deleting it from the list.

    Thanks,

    Chris

  • Steve Le Monnier Profile Picture
    959 on at

    Hi Chris

    Thanks for checking. I'm assuming you've verified this with BC on the MS Cloud and not an on-prem install.

    I've tried looking for Page 5396 and even tried adding it via web services with no luck, it doesn't seem to exist. I've even tried googling the page number and very little comes back, and when I say very little I mean nothing!

    Do you know what Page 5396 actual is?

    The only reason I know of this number is that we are trialing KingswaySoft SSIS toolkit to export data out of BC and although we can authenticate against OData4 service, when the tool tries to talk to the endpoint services to get the available list, this is the error it throws up, including this infamous number.

    KingswaySoft say its a problem with Microsoft, but as this is a manged cloud service KB's about about changing IIS settings are not relevant online. So I'm a little stuck, and MS bot service is useless.

    Many thanks for your time and stay safe.

    Steve

  • Chris Bulson Profile Picture
    on at

    Do you have a QuickBooks Synchronization extension installed in this environment, if you do, uninstall it.

    Make sure you don't have page 5396 or 5395 published on the Web Services page.

    Thanks,

    Chris

  • Steve Le Monnier Profile Picture
    959 on at

    Hi Chris, you're good :-)

    I don't have 5395/6 listed in web services. I cannot find any reference to these, and I cannot add the numbers literally.

    The "QuickBooks" reference was a bit left-field, and as it's not my setup, I went and had a look at the extensions management feature.

    We do not have "QuickBooks Synchronization" listed, but we do have "QuickBooks Data Migration" and "Quickbooks Payroll File Import".

    What's the back story here... Why would Quickbooks be screwing with the endpoint service catalogue feature needed to get SSIS to work?

    Cheers

    Steve

  • Chris Bulson Profile Picture
    on at

    I've seen some previous cases where the QB Migration extension can cause problems with Web Services.  Did you try removing the QB Data Migration extension?  The QB File Import extension should be fine to keep.  Assuming you're not trying to migrate from QB you can remove that extension and see if it has any effect on this issue.

    If you remove that and are still having a problem then you may need to open a support request through your CSP to get this fixed.

    Thanks,

    Chris

  • Steve Le Monnier Profile Picture
    959 on at

    Hi Chris

    I'm asking the platform admin to remove these as we speak. I can confirm that nobody installed these, so I guess Microsoft included them as defaults when we span up the BC environment at the back-end of last year.

    I guess 5395/6 must refer to Quickbooks, and as its not configured properly that's why I couldn't add them or find them. The KingswaySoft SSIS tool must be aware of these endpoints but cannot get schemas, so that's why the service call fails with an exception.

    Many thanks for the heads up on this, much appreciated, as soon as I confirm/deny problem I will post update back to this page and also advise KingswaySoft to prevent other developers getting caught out by this.

    Cheers

    Steve

  • 9960725212 Profile Picture
    5 on at

    Hi Steve, did you have any luck fixing this issue?

  • Steve Le Monnier Profile Picture
    959 on at

    We did remove the two QuickBook extensions from our BC environment (that MS included) and it made no difference to what we were doing. The problem persisted.

    We came to the conclusion that this problem may not be unique to QuickBook extensions, there could be other half-installed extension causing the exact same problem.

    So we are now looking to escalate this with Microsoft via a service ticket, as there are at least a dozen other extensions that have been included in our BC environment when we span it up and we don't know if any or all of these are causing a problem.

    Can I ask, are you also trying to use SSIS, or other export tools, and are having problems getting service endpoints from BC on-line.

    So far all the SSIS tools I've tried have fallen foul of this problem.

    Steve

  • gert-jan.terschure Profile Picture
    200 on at

    The error you're getting seems to be that the metadata is referring to an entity that doesn't exist. See if you can get a copy of the metadata that the service is trying to return.

    In our environment we've migrated all SSIS packages for synchronization in favor of Azure Data Factories (Native Odata support).

    If you want to work around this issue, you could try a custom source connector in SSIS and pull the data from the Odata service.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 3,229

#2
Jainam M. Kothari Profile Picture

Jainam M. Kothari 1,867 Super User 2025 Season 2

#3
YUN ZHU Profile Picture

YUN ZHU 1,153 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans