>I had this one once. It turned out that a brand new installation like that did not enable to proper Web Service Extensions. This is under IIS. The .NET related version you are running on should be Allowed. When I did it, the new installation put it to Prohibited. When I changed it to Allowed, it allowed .NET to be processed under the IIS layer.
I think you hit the nail on the head. I found that the ISAPI and CGI Restrictions is not showing in the features of the application. Which is, according to an on-line page I found, where we need to specify Web Service Extensions Allowed. The problem now (and this is not technical) that the customer's web admin does not want to do anything. He is either busy or just lazy and keeps saying, "I already tried this." It is frustrating to argue with him. Dealing with people is more difficult than with computers <g>. Thank you for your suggestions.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
