Search for DFeller aka Dawn on here. She has done work with SData and should be able to assist.

Thanks Big Louie.  I'll reach out to Dawn.

SData seems really cool, but not much info. yet.

Greetings,

The full demo code was only available to those that attended the SData session at Sage Summit last year.  I need to check if that can be made generally available at this point.

MWilliams:

I did not have to change the contract in order to get this to work. I just had to grant permissions in Role Maintenance.

Thanks,

Kent

Greetings,

Just wanted to post a status update:  We have approval to post the SData Demo information and I am working with our PM Team to make this available.  As soon as I have details on where/how it can be downloaded, I will post back.

Thank you,

Kent

That is great news!  I think SData can be a powerful extension to Sage 100.

Thank you Kent.

Hi Kent,

Just checking to see if you have anymore information on where the SData Demo information can be downloaded from.

Thanks for your help,

Danny

Greetings,

Still waiting on the official link.  I will post it when I get it.

Thanks,

Kent

Greetings,

I just posted a messsage with the link to Sage Sell for the SData demo website.  Please see this post: sagecity.na.sage.com/.../73490.aspx

HI Kent, I attended your seminar.  May I have access to this material please?

Thank you

Bruce

Greeings Bruce,

If I had your email information from the registration for the Summitt 2013 Partner session on SData you should have received the information in an email I sent out after Summitt.  If you didn't recieve that email, you should be able to download the information from SageSell.  Just login (or register) to SageSell using your partner information.

If you aren't a Partner, then please contact your Partner/Reseller and ask them to download the information for you.

Thank you,

Kent Mackall

Hello!

We have the same issue, we have Sage 100 2013 Erp and SDATA enabled, but when we access:

10.28.0.18/.../TST$schema

we get:

Server Error

404 - File or directory not found.

The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.

I think the request is not processed by IIS correctly.

When we trying to access:

https://10.28.0.18/SData/

it's just show us a subdirectory MasApp

When we trying to access:

10.28.0.18/.../MasApp

we get:

Server Error

404 - File or directory not found.

The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.

In IIS we have a separate application pool running for SDATA and we have SDATA entry point added.

Also we have checkbox in MAS config - enable SDATA set and we have a MAS role with all permissions to access SDATA.

Can you please help us?

Thanks a lot.

Dmitry

Greetings,

The error 404 generally means that the website or resource cannot be found.  Make sure you are specifying the URL properly.  In particular, the case of MasApp and MasContract is important.

To get the schema:

https://machinename/sdata/MasApp/MasContract/companycode/$schema

     - Replace machinename and companycode with proper values

To get a spceeific resource (table):

https://machinename/sdata/MasApp/MasContract/companycode/tablename

     - Replace machinename, companycode and tablename with proper values

If correcting the URL does not work, then you need to check your IIS setup and make sure the SData site is setup properly.  You may even have to try uninstalling and reinstalling the SData Native Adapter.

Thank you,

Kent Mackall

Greetings,

The error 404 generally means that the website or resource cannot be found.  Make sure you are specifying the URL properly.  In particular, the case of MasApp and MasContract is important.

To get the schema:

https://machinename/sdata/MasApp/MasContract/companycode/$schema

     - Replace machinename and companycode with proper values

To get a spceeific resource (table):

https://machinename/sdata/MasApp/MasContract/companycode/tablename

     - Replace machinename, companycode and tablename with proper values

If correcting the URL does not work, then you need to check your IIS setup and make sure the SData site is setup properly.  You may even have to try uninstalling and reinstalling the SData Native Adapter.

Thank you,

Kent Mackall

Hello Kent!

Thanks for your response. it still returns file not found.

Can you pls tell me how to uninstall and reinstall SDATA Native Adapter? is it some program? Is it part of the main Sage ERP installation?

Thanks a lot.

Dmitry

In Windows Programs and Feeatures, there should be an entry for '5.0 SData' with Sage as the Publisher.  Right Click on it and select uninstall.  After uininstall, check IIS Manager to make sure that the SData site you installed is gone.

Thank you,

Kent

Thanks Kent! We'll try to uninstall and re-install SDATA today to see if that will help. I will update here the results.

Thanks.

Dmitry

We re-installed SData and still no luck. Still the same as before.

Here are some screenshots.

When we call sdata url (/sdata) via HTTPS we see folder listing and then if we open next level urls (/sdata/MasApp etc) we see file not found:

If we call main sdata url (/sdata) or any next level url (/sdata/MasApp) with HTTP, then we see access denied error:

In IIS management I see SData application pool working and I also see new website /SData:

Can you pls help us? maybe we need to see for some specific settings?

In Sage ERP I double-checked - "Enable Native SDATA adapter" is enabled and SData permissions assigned for support user.

Thank you!

Have you tried actually connecting to a resource instead of trying to list directory contents?

What happens if you use Internet Explorer and try the following?

To get a speceific resource (table):

https://machinename/sdata/MasApp/MasContract/companycode/tablename

    - Replace machinename, companycode and tablename with proper values

Thank you,

Kent

Yes, I tried 10-20 different urls from manual (schema, resource urls etc) too - it shows "file or directory not found" too. :-(

Hello everyone!

One of tech guys said that it's probably because we use IIS7 and IIS6 compatibility were not installed prior to MAS installation.

Could it be a reason?

Okay guys we fixed it!

All that was required was to add two allowed items to ISAPI and CGI Restrictions, ASP.Net v2.0.50727 for both 32 and 64 bit. (See Screen Shot below.)