Since afternoon today, this nagging message popped up again - every time I tried to bind web services dynamically. I thought "Oh God, why am I going backwards when I dont have proper time to go forward?"
---------------------------
Error
---------------------------
The underlying connection was closed: Unable to connect to the remote server.
---------------------------
OK
---------------------------
I thought there is something I changed - oh yes, I changed the namespaces of both web services. But that did not work. I tried changing proxy settings in machine.config and web.config files. No use.
I tried running the webservice directly from their original location - http://localhost/webservice1/service1.asmx/HelloConcept - this gave me a cute string output!
All this while, I noticed from the corner of my eyes at the taskbar icons - the Skype messenger was trying to login continously - but for some reason it couldn't.
Were they co-related? You bet...I remember changing the VPN server today since my regular server disconnected twice early in the morning.
Now - I disconnected from the VPN tunnel - with just the Internet connectivity on. You know what - Skype connected!
And you know what what - my application was able to bind to web services dynamically - without any unwanted messages!
Now you know the cat is out of the bag - VPN - now I can't help wondering if this might've been the reason from some nasty errors a few days back??!!
Lesson: You never know if one's solution is a problem to something else, or if one's problem is somebody else's solution!!! So, focus on whether you want to deal with a solution or a problem - one at a time. So much for peace and harmony!
[1-Mar-2015] Solo Bullet Ride to Lepakshi
11 years ago
No comments:
Post a Comment