Deployment problem?
-
I have a VB.NET Application that consumes a webMethods web service. This web service is called over https. I can successfully call the web service in all instances (dev, test, prod, & dr) on my development machine. When I try to deploy the exe (this is the only thing created in the bin directory) to other machines I am getting the following error: The underlying connection was closed: Could not establish secure channel for SSL/TLS. Inner Exception: The function completed successfully, but must be called again to complete the context I have installed all the certs on the non development machines, but still receive this error. Is this a deployment issue? Is this a certificate issue? Can anyone point me in the right direction to fix this problem? Thanks in Advance. Mike
-
I have a VB.NET Application that consumes a webMethods web service. This web service is called over https. I can successfully call the web service in all instances (dev, test, prod, & dr) on my development machine. When I try to deploy the exe (this is the only thing created in the bin directory) to other machines I am getting the following error: The underlying connection was closed: Could not establish secure channel for SSL/TLS. Inner Exception: The function completed successfully, but must be called again to complete the context I have installed all the certs on the non development machines, but still receive this error. Is this a deployment issue? Is this a certificate issue? Can anyone point me in the right direction to fix this problem? Thanks in Advance. Mike
Well, I haven't done anything with secured WebServices yet, but my first guess would be that your not supplying a correct Certificate. You might also be missing the CA's certificate. Can you test the web service methods directly out of IE on these machines? Building Secure ASP.NET Applications: Authentication, Authorization, and Secure Communication[^] Dave Kreskowiak Microsoft MVP - Visual Basic
-
I have a VB.NET Application that consumes a webMethods web service. This web service is called over https. I can successfully call the web service in all instances (dev, test, prod, & dr) on my development machine. When I try to deploy the exe (this is the only thing created in the bin directory) to other machines I am getting the following error: The underlying connection was closed: Could not establish secure channel for SSL/TLS. Inner Exception: The function completed successfully, but must be called again to complete the context I have installed all the certs on the non development machines, but still receive this error. Is this a deployment issue? Is this a certificate issue? Can anyone point me in the right direction to fix this problem? Thanks in Advance. Mike
Well, I haven't done anything with secured WebServices yet, but my first guess would be that your not supplying a correct Certificate. You might also be missing the CA's certificate. Can you test the web service methods directly out of IE on these machines? Dave Kreskowiak Microsoft MVP - Visual Basic
-
Well, I haven't done anything with secured WebServices yet, but my first guess would be that your not supplying a correct Certificate. You might also be missing the CA's certificate. Can you test the web service methods directly out of IE on these machines? Dave Kreskowiak Microsoft MVP - Visual Basic
I finally got some time do to more testing. I was able to pull these sites up uinsg internet explorer. But I noticed the following which seems odd. On Windows 2000 machine I can call my development instance (no security or certs) On XP SP1 at work the same code gives an 503 Internet Error Service Unavailable On XP SP2 at home (logged in using VPN) code works fine. This is really going to become a problem, since they are upgrading my machine at work and I might not be able to test any longer from my testing tool. To make matters worse I am moving to a different position and would like to have this working before I move (If I could only find the time). Any ideas? My development Web Service runs on port 5595 on a webMethods Integration Server. If my company has shut down communication of port 5595 for XP machines I shouldn't be able to get there from IE, right? Mike Lasseter
-
I finally got some time do to more testing. I was able to pull these sites up uinsg internet explorer. But I noticed the following which seems odd. On Windows 2000 machine I can call my development instance (no security or certs) On XP SP1 at work the same code gives an 503 Internet Error Service Unavailable On XP SP2 at home (logged in using VPN) code works fine. This is really going to become a problem, since they are upgrading my machine at work and I might not be able to test any longer from my testing tool. To make matters worse I am moving to a different position and would like to have this working before I move (If I could only find the time). Any ideas? My development Web Service runs on port 5595 on a webMethods Integration Server. If my company has shut down communication of port 5595 for XP machines I shouldn't be able to get there from IE, right? Mike Lasseter
mr_12345 wrote:
If my company has shut down communication of port 5595 for XP machines I shouldn't be able to get there from IE, right?
Correct, but it wouldn't make any difference which O/S your machine is running. After that, I'm not real clear on what machine is where and on what machine the web service is running and where that is. Dave Kreskowiak Microsoft MVP - Visual Basic
-
mr_12345 wrote:
If my company has shut down communication of port 5595 for XP machines I shouldn't be able to get there from IE, right?
Correct, but it wouldn't make any difference which O/S your machine is running. After that, I'm not real clear on what machine is where and on what machine the web service is running and where that is. Dave Kreskowiak Microsoft MVP - Visual Basic
OK. Let me try to make it clearer. Web Service runs on webMethods B2B Integration Server on port 5595. Call it eai2:5595. This box does not need any certs to connect to it. Client (Win2000) Calling web service on eai2:5595 works with out a problem. Client (XP SP 1) Calling web service on eai2:5595 gives me the following error: The request failed with HTTP status 503: Service Unavailable. Client (XP SP 2) Calling web service on eai2:5595 gives me the following error: Request for the permission of type System.Net.WebPermission .... failed Hope this helps. Mike Lasseter
-
OK. Let me try to make it clearer. Web Service runs on webMethods B2B Integration Server on port 5595. Call it eai2:5595. This box does not need any certs to connect to it. Client (Win2000) Calling web service on eai2:5595 works with out a problem. Client (XP SP 1) Calling web service on eai2:5595 gives me the following error: The request failed with HTTP status 503: Service Unavailable. Client (XP SP 2) Calling web service on eai2:5595 gives me the following error: Request for the permission of type System.Net.WebPermission .... failed Hope this helps. Mike Lasseter
Dave, I got the problem figured out. The problem was in the machine.config file. The proxy setting on the XP SP1 machines was set to true. I changed it to default and it now works. I also installed the certs on the XP SP1 machine for connecting to test, prod, and dr. And all calls work like a champ. Thanks for your help. Mike Lasseter