HI,
I've updated a uniface service to contain a new (public web) operation. I updated the wsdl using /sto and deleted and re-imported the wsdl signature using /sti.
I've copied the wsdl files, and the new programs and signatures to my production environment in both a patch UAR and (when that failed) as individual files, and the calling program is installed on both the prod environment and a customer site.
When calling the service internally (direct to the tomcat server), the new code works.
When calling it from the customer site, which uses https routed through an IIS server, the uniface program returns a -59 error "WSDL Reader error create for operation not found", Looking at the wsdl from a browser on the customer site shows the operation included in the wsdl.
I've restarted the IIS site, and the tomcat server to (hopefully) remove cached files.
Anyone any clues?
Regards,
Iain
------------------------------
Iain Sharp
Head of Technical Services
Pci Systems Ltd
Sheffield GB
------------------------------
Page 1 / 1
HI,
I've updated a uniface service to contain a new (public web) operation. I updated the wsdl using /sto and deleted and re-imported the wsdl signature using /sti.
I've copied the wsdl files, and the new programs and signatures to my production environment in both a patch UAR and (when that failed) as individual files, and the calling program is installed on both the prod environment and a customer site.
When calling the service internally (direct to the tomcat server), the new code works.
When calling it from the customer site, which uses https routed through an IIS server, the uniface program returns a -59 error "WSDL Reader error create for operation not found", Looking at the wsdl from a browser on the customer site shows the operation included in the wsdl.
I've restarted the IIS site, and the tomcat server to (hopefully) remove cached files.
Anyone any clues?
Regards,
Iain
------------------------------
Iain Sharp
Head of Technical Services
Pci Systems Ltd
Sheffield GB
------------------------------
I've updated a uniface service to contain a new (public web) operation. I updated the wsdl using /sto and deleted and re-imported the wsdl signature using /sti.
I've copied the wsdl files, and the new programs and signatures to my production environment in both a patch UAR and (when that failed) as individual files, and the calling program is installed on both the prod environment and a customer site.
When calling the service internally (direct to the tomcat server), the new code works.
When calling it from the customer site, which uses https routed through an IIS server, the uniface program returns a -59 error "WSDL Reader error create for operation not found", Looking at the wsdl from a browser on the customer site shows the operation included in the wsdl.
I've restarted the IIS site, and the tomcat server to (hopefully) remove cached files.
Anyone any clues?
Regards,
Iain
------------------------------
Iain Sharp
Head of Technical Services
Pci Systems Ltd
Sheffield GB
------------------------------
The mentioned error message (-59 - No definition found for operation) seems to suggest that the operation in question does not exist in the signature of the called component. Did you already check if everything is in place in the back-end? Maybe you could increase the I/O message level (i.e. $ioprint) of the UServer to 64 or 127 in order to see what the application is looking for? Enable Proc-tracing might also be helpful.
I hope this helps.
Regards,
------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland
------------------------------
Hi Iain,
The mentioned error message (-59 - No definition found for operation) seems to suggest that the operation in question does not exist in the signature of the called component. Did you already check if everything is in place in the back-end? Maybe you could increase the I/O message level (i.e. $ioprint) of the UServer to 64 or 127 in order to see what the application is looking for? Enable Proc-tracing might also be helpful.
I hope this helps.
Regards,
------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland
------------------------------
The mentioned error message (-59 - No definition found for operation) seems to suggest that the operation in question does not exist in the signature of the called component. Did you already check if everything is in place in the back-end? Maybe you could increase the I/O message level (i.e. $ioprint) of the UServer to 64 or 127 in order to see what the application is looking for? Enable Proc-tracing might also be helpful.
I hope this helps.
Regards,
------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland
------------------------------
The error only shows when calling the web service from outside our LAN. Calling the same web service from inside the LAN returns no error, and the code runs successfully in the debugger on the web server.
The only difference is one call is to http://server:8080/xxxxx/services and the other is to https://external_url/xxxxx/services which is redirected through IIS on a different machine (web-firewall...)
So the operation exists, the operation does show up in the WSDL, and is functional from inside the LAN. I was wondering if there's any cache in the IIS, but as I say I've restarted it.
Oh, and other, older, operations on the same web-service still work okay from outside the LAN.
I will try a different customer and see if it's at the client end.
Regards,
Iain
------------------------------
Iain Sharp
Head of Technical Services
Pci Systems Ltd
Sheffield GB
------------------------------
Hi Daniel,
The error only shows when calling the web service from outside our LAN. Calling the same web service from inside the LAN returns no error, and the code runs successfully in the debugger on the web server.
The only difference is one call is to http://server:8080/xxxxx/services and the other is to https://external_url/xxxxx/services which is redirected through IIS on a different machine (web-firewall...)
So the operation exists, the operation does show up in the WSDL, and is functional from inside the LAN. I was wondering if there's any cache in the IIS, but as I say I've restarted it.
Oh, and other, older, operations on the same web-service still work okay from outside the LAN.
I will try a different customer and see if it's at the client end.
Regards,
Iain
------------------------------
Iain Sharp
Head of Technical Services
Pci Systems Ltd
Sheffield GB
------------------------------
The error only shows when calling the web service from outside our LAN. Calling the same web service from inside the LAN returns no error, and the code runs successfully in the debugger on the web server.
The only difference is one call is to http://server:8080/xxxxx/services and the other is to https://external_url/xxxxx/services which is redirected through IIS on a different machine (web-firewall...)
So the operation exists, the operation does show up in the WSDL, and is functional from inside the LAN. I was wondering if there's any cache in the IIS, but as I say I've restarted it.
Oh, and other, older, operations on the same web-service still work okay from outside the LAN.
I will try a different customer and see if it's at the client end.
Regards,
Iain
------------------------------
Iain Sharp
Head of Technical Services
Pci Systems Ltd
Sheffield GB
------------------------------
"ERROR=-59·;
MNEM=<UACTERR_NO_OPERATION>·;
DESCRIPTION=No definition found for operation·;
COMPONENT=SYF_CUS_DOCS_ORG·;
PROCNAME=8\\DETAIL·;
TRIGGER=DTLF·;
LINE=6·;
PROCLINE=activate "SUS_WEBIOSERVICE"."OP_DEL_CUS_DOCS"( V_COMPANY ) ·;
ADDITIONAL=INSTANCENAME=SUS_WEBIOSERVICE·!·;
OPERATIONNAME=OP_DEL_CUS_DOCS·!·;
DRV=SOP·!·;
LOCATION=REQUEST·!·;
CODE=WSDL·!·;
MESSAGE=WSDL reader error·!·;
DETAIL=Request::create Operation: could not be found in WSDL."------------------------------
Iain Sharp
Head of Technical Services
Pci Systems Ltd
Sheffield GB
------------------------------
Hi Daniel,
The error only shows when calling the web service from outside our LAN. Calling the same web service from inside the LAN returns no error, and the code runs successfully in the debugger on the web server.
The only difference is one call is to http://server:8080/xxxxx/services and the other is to https://external_url/xxxxx/services which is redirected through IIS on a different machine (web-firewall...)
So the operation exists, the operation does show up in the WSDL, and is functional from inside the LAN. I was wondering if there's any cache in the IIS, but as I say I've restarted it.
Oh, and other, older, operations on the same web-service still work okay from outside the LAN.
I will try a different customer and see if it's at the client end.
Regards,
Iain
------------------------------
Iain Sharp
Head of Technical Services
Pci Systems Ltd
Sheffield GB
------------------------------
The error only shows when calling the web service from outside our LAN. Calling the same web service from inside the LAN returns no error, and the code runs successfully in the debugger on the web server.
The only difference is one call is to http://server:8080/xxxxx/services and the other is to https://external_url/xxxxx/services which is redirected through IIS on a different machine (web-firewall...)
So the operation exists, the operation does show up in the WSDL, and is functional from inside the LAN. I was wondering if there's any cache in the IIS, but as I say I've restarted it.
Oh, and other, older, operations on the same web-service still work okay from outside the LAN.
I will try a different customer and see if it's at the client end.
Regards,
Iain
------------------------------
Iain Sharp
Head of Technical Services
Pci Systems Ltd
Sheffield GB
------------------------------
No idea. Sorry. I (luckily) did not have to deal with IIS for quite some time.
But are you sure that you are calling the same back-end in both cases? It seems quite unlikely to me that everything works fine in the back-end and the client is getting an error message that clearly comes from Uniface. Have you already checked the log files of Tomcat and can confirm that the request was received and yielded the said error page? Sorry, I do not have any better ideas at the moment. It all seems is a bit odd. Maybe you should have a chat with Redmond? ;-)
Regards,
------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland
------------------------------
Hi Iain,
No idea. Sorry. I (luckily) did not have to deal with IIS for quite some time.
But are you sure that you are calling the same back-end in both cases? It seems quite unlikely to me that everything works fine in the back-end and the client is getting an error message that clearly comes from Uniface. Have you already checked the log files of Tomcat and can confirm that the request was received and yielded the said error page? Sorry, I do not have any better ideas at the moment. It all seems is a bit odd. Maybe you should have a chat with Redmond? ;-)
Regards,
------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland
------------------------------
No idea. Sorry. I (luckily) did not have to deal with IIS for quite some time.
But are you sure that you are calling the same back-end in both cases? It seems quite unlikely to me that everything works fine in the back-end and the client is getting an error message that clearly comes from Uniface. Have you already checked the log files of Tomcat and can confirm that the request was received and yielded the said error page? Sorry, I do not have any better ideas at the moment. It all seems is a bit odd. Maybe you should have a chat with Redmond? ;-)
Regards,
------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland
------------------------------
Applied this signature over the patch on the customer site, and it worked.
I've rebuilt the patch uar, and resent that to the customer site, and it's working. Somehow the signature as compiled was broken. both as a .sig file, and as part of the UAR.
Regards,
Iain
------------------------------
Iain Sharp
Head of Technical Services
Pci Systems Ltd
Sheffield GB
------------------------------
So, I copied the wsdl name out of the signature definition into notepad, checked it and copied it back to the signature, then recompiled the signature.
Applied this signature over the patch on the customer site, and it worked.
I've rebuilt the patch uar, and resent that to the customer site, and it's working. Somehow the signature as compiled was broken. both as a .sig file, and as part of the UAR.
Regards,
Iain
------------------------------
Iain Sharp
Head of Technical Services
Pci Systems Ltd
Sheffield GB
------------------------------
Applied this signature over the patch on the customer site, and it worked.
I've rebuilt the patch uar, and resent that to the customer site, and it's working. Somehow the signature as compiled was broken. both as a .sig file, and as part of the UAR.
Regards,
Iain
------------------------------
Iain Sharp
Head of Technical Services
Pci Systems Ltd
Sheffield GB
------------------------------
Regards,
Daniel
------------------------------
Daniel Iseli
Principal Technical Support Engineer
Uniface Services
Rocket Software, Switzerland
------------------------------
Sign up
Already have an account? Login
Welcome to the Rocket Forum!
Please log in or register:
Employee Login | Registration Member Login | RegistrationEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.
77 4th Avenue
Waltham, MA 02451 USA
