I am unable to connect to SSRS (for managing reports, etc.) within SSMS (it
throws out a HTTP 401 error). So, I thought the configuration may have been
set up wrong or something so I opened up the SQL Surface Area Configuration
tool. The RS service was running and when I went to SAC for Features->
Reporting Services->Windows Integrated Security, it won't connect either
throwing out "The request failed with HTTP status 401: Unauthorized
(SQLSAC).

So, I'm guessing there is a problem with Windows Integrated Security???
Anyone have a clue as to what is going on?

Thanks.

Hi Don

The reporting services news group may be a better place to post this, but
you already have other posts in the IIS newsgroup http://tinyurl.com/2ktslr
and it is usually taken as bad form to post to multiple newsgroups
separately. Your other post does say that you are connecting to an SSL only
server which was not mentioned here. Have you made sure that the connection
options specify SSL?

John

"Don Miller" wrote:

> I am unable to connect to SSRS (for managing reports, etc.) within SSMS (it
> throws out a HTTP 401 error). So, I thought the configuration may have been
> set up wrong or something so I opened up the SQL Surface Area Configuration
> tool. The RS service was running and when I went to SAC for Features->
> Reporting Services->Windows Integrated Security, it won't connect either
> throwing out "The request failed with HTTP status 401: Unauthorized
> (SQLSAC).
>
> So, I'm guessing there is a problem with Windows Integrated Security???
> Anyone have a clue as to what is going on?
>
> Thanks.
>
>
>

Thank you very much for at least responding.

I understand newsgroup netiquette but I have posted to the reporting
services newsgroup several times without any responses with RS-specific
questions. The problems I am having with RS also seemed to carry over to
the SQL Server SAC tool and SSMS. I thought that maybe the root of the
problem was NOT RS but something to do with Windows Integrated Security as
configured within SQL Server. I cannot understand why when I sign on to a
server as Administrator, with Windows Integrated Security options set in RS,
why I cannot even connect to RS using SSMS.

I am grasping at straws here because I'm dead in the water. I thought about
calling MS for $500 but I've been there before and it often takes a month
going through multiple layers of folks who follow a script and, in the
beginning level of calls, don't know any more than me (and think you can
reboot a production computer at-will during peak times, and when you
reconfigure RS it resets IIS).

> Have you made sure that the connection
> options specify SSL?

Yes. My frustration is that I configured my dev server to do all of this in
less than a minute, so I can't even debug the problem because I cannot
recreate the same environment apparently.

>Your other post does say that you are connecting to an SSL only
> server which was not mentioned here.

With SAC, I tried almost every permutation and quickly found that if I did
NOT configure for SSL with RS I received a HTTP 403 error (ssl required).
What I cannot recreate is the HTTP 401 error I get on the production
machine.


"John Bell" <jbellnewsposts@hotmail.com> wrote in message
news:A688DC56-5EDF-42C5-B829-1C04FAE3EE65@microsoft.com...
> Hi Don
>
> The reporting services news group may be a better place to post this, but
> you already have other posts in the IIS newsgroup
> http://tinyurl.com/2ktslr
> and it is usually taken as bad form to post to multiple newsgroups
> separately. Your other post does say that you are connecting to an SSL
> only
> server which was not mentioned here. Have you made sure that the
> connection
> options specify SSL?
>
> John
>
> "Don Miller" wrote:
>
>> I am unable to connect to SSRS (for managing reports, etc.) within SSMS
>> (it
>> throws out a HTTP 401 error). So, I thought the configuration may have
>> been
>> set up wrong or something so I opened up the SQL Surface Area
>> Configuration
>> tool. The RS service was running and when I went to SAC for Features->
>> Reporting Services->Windows Integrated Security, it won't connect either
>> throwing out "The request failed with HTTP status 401: Unauthorized
>> (SQLSAC).
>>
>> So, I'm guessing there is a problem with Windows Integrated Security???
>> Anyone have a clue as to what is going on?
>>
>> Thanks.
>>
>>
>>

Hi

If you have a system that is supposed to be the same and it works, then
there must be some difference as why it works. What are the SQL server
versions/service packs etc What is the operating system and differences? Are
there group policies? Are there network differences e.g. firewalls, domains
etc. ?

You mentioned that you can not connect to a specific host, if you can use
the same client to connect to a similarly configured host it would rule out
the client.

John

"Don Miller" wrote:

> Thank you very much for at least responding.
>
> I understand newsgroup netiquette but I have posted to the reporting
> services newsgroup several times without any responses with RS-specific
> questions. The problems I am having with RS also seemed to carry over to
> the SQL Server SAC tool and SSMS. I thought that maybe the root of the
> problem was NOT RS but something to do with Windows Integrated Security as
> configured within SQL Server. I cannot understand why when I sign on to a
> server as Administrator, with Windows Integrated Security options set in RS,
> why I cannot even connect to RS using SSMS.
>
> I am grasping at straws here because I'm dead in the water. I thought about
> calling MS for $500 but I've been there before and it often takes a month
> going through multiple layers of folks who follow a script and, in the
> beginning level of calls, don't know any more than me (and think you can
> reboot a production computer at-will during peak times, and when you
> reconfigure RS it resets IIS).
>
> > Have you made sure that the connection
> > options specify SSL?
>
> Yes. My frustration is that I configured my dev server to do all of this in
> less than a minute, so I can't even debug the problem because I cannot
> recreate the same environment apparently.
>
> >Your other post does say that you are connecting to an SSL only
> > server which was not mentioned here.
>
> With SAC, I tried almost every permutation and quickly found that if I did
> NOT configure for SSL with RS I received a HTTP 403 error (ssl required).
> What I cannot recreate is the HTTP 401 error I get on the production
> machine.
>
>
> "John Bell" <jbellnewsposts@hotmail.com> wrote in message
> news:A688DC56-5EDF-42C5-B829-1C04FAE3EE65@microsoft.com...
> > Hi Don
> >
> > The reporting services news group may be a better place to post this, but
> > you already have other posts in the IIS newsgroup
> > http://tinyurl.com/2ktslr
> > and it is usually taken as bad form to post to multiple newsgroups
> > separately. Your other post does say that you are connecting to an SSL
> > only
> > server which was not mentioned here. Have you made sure that the
> > connection
> > options specify SSL?
> >
> > John
> >
> > "Don Miller" wrote:
> >
> >> I am unable to connect to SSRS (for managing reports, etc.) within SSMS
> >> (it
> >> throws out a HTTP 401 error). So, I thought the configuration may have
> >> been
> >> set up wrong or something so I opened up the SQL Surface Area
> >> Configuration
> >> tool. The RS service was running and when I went to SAC for Features->
> >> Reporting Services->Windows Integrated Security, it won't connect either
> >> throwing out "The request failed with HTTP status 401: Unauthorized
> >> (SQLSAC).
> >>
> >> So, I'm guessing there is a problem with Windows Integrated Security???
> >> Anyone have a clue as to what is going on?
> >>
> >> Thanks.
> >>
> >>
> >>
>
>
>