Sage 100

I have an implementation of a 3rd party service module to Sage 100 Standard that uses SDATA. It's a group effort between the 3rd party add-on, the Sage consultant (me) and the end-users IT company. I have the SDATA adapter installed, the IIS server configured. I can connect at the server using the https://mymachinename/sdata/MasApp/MasContract/TST/AR_Customer and get a login prompt and can see the tables, however if the 3rd party service module tries to access the Sage100 tables from an external url https://sdata.company.com/sdata/MasApp/MasContract/TST/AR_Customer, they get access to the IIS web page, but trying to get to the Sage 100 data they get ""Server Error"" 404 - File or directory not found. Any ideas or suggestions to look at or try? I've been in contact with Sage Corporate support and while they have been helpful, it has not been easy getting a fast response.

A search came up with this don't know if it will help...opening the thread, the last image was IIS Manager, they added items to ISAPI and CGI Restrictions, ASP.Net v2.0.50727 for both 32 and 64 bit.https://sagecity.na.sage.com/support_communities/sage100_erp/f/sage-100-business-object-interface/72926/sdata-install-training/230903

Thanks Moira, will take a look at it!

Here's a follow up on this issue, in case some one else runs into it. and now for the keyword search SDATA, SDATA Connection Error, For God's Sake Please Make it Stop, This install has a Domain Controller Server and an application server for Sage 100, we could get the internal communication to work from the application server using https://mymachinename/sdata/MasApp/MasContract/TST/AR_Customer. An external url communication would not connect and would give ""Server Error"" File or directory not found. I found out that SDATA requires port 443 for connecting from the outside, and in this case port 443 (default port for https) was being used for their exchange server. So the fix was to get the end user to get another IP address from their ISP and change the WAN IP on firewall, reconfigure DNS records, change the sdata A record and change the firewall IP. My take-away, this will probably be the last time I use anything connected with SDATA, it was a colossal PITA . Got the Vibe from Sage that SDATA for Sage100 is a sun-setted product (will be maintained but not updated as time goes on) and would encourage folks to use other options like Web Services parts and BOI.

Wow, wore me out just reading about your (mis)adventures. Can't even imagine how you feel. Thanks for the update. Is it just me or does Sage have a tendency to bet on ponies that don't last.... Or do they just buy a single bale of hay for the long haul?

Version 0.1b becomes the final, aka extreme minimum viable product