Hi Rick
Been using Web connection to run a data collecting web service to update VFP tables for almost a year now and it has been brilliant !! 😃
We want to add another webservice to the same server and in local testing it works great but on the production server - the new webservice hears nothing.
We have added another virtual directory to match the new app - nothing.
Any thoughts? What have we missed? is there some extra routine we need to run?
Thanks in advance
Simon
Just upgraded to latest Web Connection but that has not helped.
We have also tried to add a 2nd function (endpoint) to the original webservice (rebuilt from scratch for new version of WC) and it all seems to build like it should and the code looks right but when we run it we get an error that it cannot find the 2nd function which is called "DataImport"
Function made when project created works fine.
Error details :
WWJSONSERVICE.CALLMETHOD PROGRAM LINE NUMBER : 187 ERROR NUMBER : 1734 ERROR MESSAGE : Property DATAIMPORT is not found.
We don't really mind whether we do this as 1 webservice or 2 as long as we can get it running.
Any thoughts?
Thanks
Simon
Hi Rick
Please ignore these messages.
For reasons unknown it now seems to work. Don't you just love windows server?
Thanks
Simon
Hi Rick
Still struggling to get 2 webservices to run at the same time on the same server 2008R2.
We have reinstalled and all are latest v7.06 ersion. Both work fine in dev.
However on the production server :
WebService 1 runs fine - it seems really reliable.
WebService 2 cannot be reached from outside. We have looked at IIS but the 2 different named webservice settings look identical. If we try to run the testpage from the non functioning application, it says it is just waiting for localhost and times out.
Should we complile the launch.prg into an exe and run it first?
Any thoughts as to how we can get this up & running? We really need this webservice up now.
Thanks in advance
Simon
P.S. All our efforts to add an extra endpoint/function to the existing webservice failed. It is probably best they are separate anyway, if both can be run on the same server.
Not sure without more detail. Based on your messages I'd say IIS is not configured properly.
I can take a look if you need help,
https://west-wind.com/contact/#PaidSupport
+++ Rick ---