Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 857
  • Last Modified:

WEB SERVICE GIVING "The request failed with HTTP status 406: Not Acceptable". ERROR

Hi All,
I have made a webservice and it is working fine on the local server but when I upload to our main SERVER and add its reference to winform and try to call it, it is giving a strange error and I am not able to debug what the problem is. the error that appears is

Server Error in '/WebApplication2' Application.
--------------------------------------------------------------------------------

The request failed with HTTP status 406: Not Acceptable.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Net.WebException: The request failed with HTTP status 406: Not Acceptable.

I couldn't find what the problem is all about. Kindly help
0
brainstogether
Asked:
brainstogether
  • 4
  • 2
1 Solution
 
majodioCommented:
Make sure that any references to old URLs in your web service have been changed to match your production server.

Very strange that I could not find anything on Google about this problem.
0
 
majodioCommented:
Also, in order to debug the program you might want to write Debug messages into a log file of some type.  Here's a function that you can use to do that:

    Private Sub WriteLog(ByVal Msg)
        Dim SW As StreamWriter
        Dim M As Mutex
        Dim Created As Boolean
        Try
            'Ensure that only one thread has access to the log file at any given time
            M = New Mutex(False, "WriteLog", Created)
            M.WaitOne()
            ' This text is added only once to the file.
            If Not File.Exists("LogFileFullPath") Then
                ' Create a file to write to.
                SW = File.CreateText("LogFileFullPath")
            Else
                SW = File.AppendText("LogFileFullPath")
            End If
            SW.WriteLine(DateTime.Now & " - " & Msg)
            SW.Flush()
        Finally
            M.ReleaseMutex()
            If Not IsNothing(SW) Then
                SW.Close()
                SW = Nothing
            End If
        End Try
    End Sub
0
 
brainstogetherAuthor Commented:
Yes majodio I also didnt find anything on google so its too hard for me...so just want some Ideas from fellow experts.
Actually this error is coming when I try to call the webservice from within an ASP application folder....I made it a virtual directory though and I can browse the webservice but at the time of calling ...it gives error in the invoke function in references.cs.
When I made it a virtual directory in a folder that contains the dotnet application it did run well....so I checked the folder permissions but they were all same.
The jist is that it is creating the object of the class in webservice too but when I try to call the function it gives that 406 Error and points to the invoke function in reference.cs file.
please let me know anything u can think of...I will also try out and if even the guesses are correct.... I will be happy to give u the points.
0
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

 
majodioCommented:
Hmmm...  Interesting...  I guess that your testing so far points to a permissions problem.  Are you running the web service in the root of the web server?  Are you sure that the ASP.Net user has Read/List permissions to that folder?
0
 
brainstogetherAuthor Commented:
yes the webservice is in root and the folder under which I have made it a virtual directory is also having the ASP.Net user Read/List permission
0
 
majodioCommented:
Can you invoke the web service by hand?  In essence without using the Winform and just browsing to it with a web browser?  Also, are you sure that you're handling any error correctly in your code?

I'm guessing you've tried all of these things, but I don't have a clue on this one.  I'll continue to think about it, though.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now