sql server reporting services: Rendering report through Web Service, W2K - OK, W2K3 - NOT OK!!! -- sql server reporting services

Re: Rendering report through Web Service, W2K - OK, W2K3 - NOT OK!!!

Bruce Loehle-Conger
9/1/2004 10:38:28 AM

sql server reporting services: Not sure if it makes a difference but when I installed with W2K3 I picked
system instead of Network Service. It has two options on the combobox.

Bruce L-C

[quoted text, click to view]

Rendering report through Web Service, W2K - OK, W2K3 - NOT OK!!!

Kolos Daniel
9/1/2004 4:23:11 PM

I had to face a strange behaviour: i am developing an ASP.NET application,
part of the application renders reports through the SOAP API. My machine
runs W2K Server, the application connects to the database and to the reports
via the process identity (machinename\ASPNET). On my machine everything
works fine!

The production server will run W2K3. I tried to simulate this with a virtual
machine. I assigned rights this time to the NT AUTHORITY\Network Service
account in SQL Server and Reporting Services, as i did on the W2K with the
ASPNET account. The application works, but when i try to generate a report i
get the following error message:

The request failed with HTTP status 401: Access Denied

What did I wrong?
Please help!

Another strange thing: when i browse to the localhost/reports page on the
W2K3, I have to authenticate myself althought (of course) Windows
authentication is set. I provide the same username and password
(administrative rights) as I did when I logged on to the machine, and after
that everything works fine. Why is this second authenthication required?

Thanks in advance,
Kolos