NewsBot
1
Hi all, new here and a realative newbie to some things I'm learning in VS2008 and .NET.
After finding that a wcf service I wrote wouldn;t run when I deployed it to my web site (was fine on my development system) I decided to try*a most trivial example of a method that returns a string.* Still wouldn't run when deployed to web.
Wondering if it had something to do with credientials, I changed wsHttpBindings to basicHttpBindings.* Same result.* Then I*implemented a custom validator class, and on my machine it is using that valiator fine, using UserName as clientCredentialType, and the service behaves as I woudl predict.* But I am getting one exception all the time from the web-deployed channel...
999 No hacking.
What's weird, searches on web give me not one reference to that error.* The stack trace in this present incarnation, using a custom validator, basicHttpBindings etc is simply...
at System.Net.HttpWebRequest.GetResponse()
** at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
Can anyone suggest possible reasons*that services running fine on my devleopment system are continually throwing this error when deployed to web?
By the way, the means I am using of testing is a simple form, the code something like..
----
Private client As New ServiceReference2.Service1Client
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
Try
'client.InnerChannel.Open()
client.ClientCredentials.UserName.UserName = "blahblah"
client.ClientCredentials.UserName.Password = "etcetc"
Me.Label1.Text = client.GetData(1)
Catch ex As Exception
End Try
-----
The name and password are handled by my custom validator, and on my development system this is defintely working OK.*
Any pointers to possibilities greatly appreciated.
David
More...
View All Our Microsoft Related Feeds
After finding that a wcf service I wrote wouldn;t run when I deployed it to my web site (was fine on my development system) I decided to try*a most trivial example of a method that returns a string.* Still wouldn't run when deployed to web.
Wondering if it had something to do with credientials, I changed wsHttpBindings to basicHttpBindings.* Same result.* Then I*implemented a custom validator class, and on my machine it is using that valiator fine, using UserName as clientCredentialType, and the service behaves as I woudl predict.* But I am getting one exception all the time from the web-deployed channel...
999 No hacking.
What's weird, searches on web give me not one reference to that error.* The stack trace in this present incarnation, using a custom validator, basicHttpBindings etc is simply...
at System.Net.HttpWebRequest.GetResponse()
** at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
Can anyone suggest possible reasons*that services running fine on my devleopment system are continually throwing this error when deployed to web?
By the way, the means I am using of testing is a simple form, the code something like..
----
Private client As New ServiceReference2.Service1Client
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
Try
'client.InnerChannel.Open()
client.ClientCredentials.UserName.UserName = "blahblah"
client.ClientCredentials.UserName.Password = "etcetc"
Me.Label1.Text = client.GetData(1)
Catch ex As Exception
End Try
-----
The name and password are handled by my custom validator, and on my development system this is defintely working OK.*
Any pointers to possibilities greatly appreciated.
David
More...
View All Our Microsoft Related Feeds