"Travich" <travich@gmail.com> wrote in message
news:1160515095.212572.146790@h48g2000cwc.googlegroups.com...
>I have a .NET 1.1 WinForms application that used to only hit SQL Server
> 2000. We are now contemplating moving to SQL Server 2005.
>
> To test this, we set up a SQL Server 2005 box and installed the web
> services and client application on the same box. When the application
> tries to call a web service that it could normally call in the past, it
> get's the following error:
>
> System.Web.Services.Protocols.SoapException: User Not Authorized
>
> I have a feeling that something in IIS is not configured correctly, but
> I've been looking at it all day and with no luck. I appreciate if
> anyone can help me solve this mystery...

John Saunders wrote:
> "Travich" <travich@gmail.com> wrote in message
> news:1160515095.212572.146790@h48g2000cwc.googlegroups.com...
> >I have a .NET 1.1 WinForms application that used to only hit SQL Server
> > 2000. We are now contemplating moving to SQL Server 2005.
> >
> > To test this, we set up a SQL Server 2005 box and installed the web
> > services and client application on the same box. When the application
> > tries to call a web service that it could normally call in the past, it
> > get's the following error:
> >
> > System.Web.Services.Protocols.SoapException: User Not Authorized
> >
> > I have a feeling that something in IIS is not configured correctly, but
> > I've been looking at it all day and with no luck. I appreciate if
> > anyone can help me solve this mystery...
>
> It looks like a case of too many variables. You moved the web services and
> the client, and changed databases. Remove some of those variables so you can
> see which one is causing the problem.
>
> John