If I change the baseurl to https://+2001/tms/xdata I get the error message:
Could not add the following Url to the server:
Be sure that you have reserved the Url in Http.Sys with the proper permissions.
Error: Cannot create a file when that file already exists.
If it is just http, it is fine. What do I need to do. This is on a Windows server.
I have found out about TMSHttpConfig Tool and after following the instructions the server now starts correctly but when I try to connect to it at design time I get the error:
Could not perform WinHttp operation.
Error: (12030) The connection with the server has been reset or terminated or an incompatible SSL protocol was encountered.
There are instructions in the doc about setting it up for SSL. Does it work with a standard http?
Yes, it does work for http, just not https. I can't find anything about SSL in either the Wb Core or XData Manual about SSL.
This seems to be a CORS issue again. In IIS 8 I have edited web.config and added the following:
Why do you say it seems to be a CORS issue? Have you solved it?
It might be something to do with your SSL certificate. Maybe this can help:
Wagner R. Landgraf2019-05-16 14:24:06
Because I am getting the error message: Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://mtdready.com:2001/tms/xdata/$model. (Reason: CORS request did not succeed)
The certificate is valid when accessing the site.
I see already three different error messages. What is exactly the error message you get, and in which situation?
I get the cross originn blocked message when running the web app at the point I try to connect to the xdata server.
I get the Error: (12030) The connection with the server has been reset or terminated or an incompatible SSL protocol was encountered when I try to connect at design time.
On the client side do I have to put entries in the TXDataWebConnection.DesignData.Headers?
If so what do you recommend?
"The certificate is valid when accessing the site" - what does that mean, exactly?
Then you say
"I get the cross origin blocked message when running the web app at the point I try to connect to the xdata server."
So this happens in the browser as well? What is different than "accessing the site", then?
Do you see any extra information in browser console?
Then you say
"I get the Error: (12030) The connection with the server has been reset or terminated or an incompatible SSL protocol was encountered when I try to connect at design time."
I provided you with a link regarding this issue at social msdn, might something with SSL. You didn't provide feedback about this?
Then you ask
"On the client side do I have to put entries in the TXDataWebConnection.DesignData.Headers?"
DesignData.Headers is just in case you want to add HTTP headers to your request at design-time, for example if you want to add authentication headers to connect at design-time providing authentication information.
Hope it helps, but I'm still confused with several different and sometimes not detailed information.
All in all it seems something in your SSL certificate, but without more details and the current exact situation I can't tell.
Your server is not responding.
Your CORS test didn't work here, and in any case, you are trying to access the server in a different port. Have you bound the SSL certificate to port 2001, which is the one you are using?
No, I had not bound the certificate as I did not know that I had to. I think the biggest problem is that there is not an up-to-date concise list of step-by-step instructions on how to create, configure, and install an xdata server for use by TMS Web Core or, if there is, I can't find it!
Sorry. I did use TMSHttpConfig.exe to do this but I was looking at this post https://www.tmssoftware.com/site/blog.asp?post=454 at the time which I guess is now outdated.
It's not outdated. What was your configuration in TMSHttpConfig? How was your certificate generated? Let's Encrypt?
I'm going to give up on XData for now and do it another way. I may revisit this later. Thanks for trying to help me.