Intermittent 401: Not Authorized

The first time I try to access a RS report after an IISreset, I get a
"System.Net.WebException: The request failed with HTTP status 401:
Unauthorized." error. If I try to access it again, I get in without a
problem.
In addition to the "first attempt after the iisreset", which happens
consistently, we also intermittently experience the same error, infrequently.
Any idea what is going on here? Caching of Credentials?
Michael DorfmanHello Michael,
To understand the issue better, I'd like to know the following information:
1. Does the issue only occur with a specific RS report or any RS report
such as sample reports including in RS installation?
2. Do you have anonymous access enabled on Report Manager or Report Server
virtual directories?
Also, this issue might be related to a known issue in .Net framework 1.1
sp1, I suggest that you contact CSS to get 887563 installed hotfix 887563
to see if it helps:
884537 FIX: You may receive a "System.Net.WebException" error message when
you
http://support.microsoft.com/?id=884537
887563 Availability of the .NET Framework 1.1 Post-Service Pack 1 rollup
http://support.microsoft.com/?id=887563
Also, please search if there are multiple copies of security.dll on your
SQL Reporting Services machine. If there are security.dll other than
%windir%\system32 folder, please tempoarily rename them to test the
situation.
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
| Thread-Topic: Intermittent 401: Not Authorized
| thread-index: AcVTuOW2QlsDZxZ1SwW4LqLFvzorxw==| X-WBNR-Posting-Host: 62.97.217.178
| From: =?Utf-8?B?TWljaGFlbCBEb3JmbWFu?= <mercatus2004@.online.nospam>
| Subject: Intermittent 401: Not Authorized
| Date: Sun, 8 May 2005 03:30:04 -0700
| Lines: 11
| Message-ID: <E81A662F-4F37-45EB-8174-9C17787D5295@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.reportingsvcs
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.reportingsvcs:43126
| X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
|
| The first time I try to access a RS report after an IISreset, I get a
| "System.Net.WebException: The request failed with HTTP status 401:
| Unauthorized." error. If I try to access it again, I get in without a
| problem.
|
| In addition to the "first attempt after the iisreset", which happens
| consistently, we also intermittently experience the same error,
infrequently.
|
| Any idea what is going on here? Caching of Credentials?
|
| Michael Dorfman
||||Are you using 2003 server and applied SP1? If so, I did the following and
solved my same problem:
"create a DWORD entry called DisableLoopbackCheck to
HKLM\System\CurrentControlSet\Control\Lsa. Set this key to a value of 1"
This is an issue which occures after appling SP1 to 2003 server.
I hope, this helps.
Barbaros Saglamtimur
MCDBA, MCAD
"Peter Yang [MSFT]" <petery@.online.microsoft.com> wrote in message
news:wrpXrMFVFHA.2476@.TK2MSFTNGXA01.phx.gbl...
> Hello Michael,
> To understand the issue better, I'd like to know the following
> information:
> 1. Does the issue only occur with a specific RS report or any RS report
> such as sample reports including in RS installation?
> 2. Do you have anonymous access enabled on Report Manager or Report Server
> virtual directories?
> Also, this issue might be related to a known issue in .Net framework 1.1
> sp1, I suggest that you contact CSS to get 887563 installed hotfix 887563
> to see if it helps:
> 884537 FIX: You may receive a "System.Net.WebException" error message when
> you
> http://support.microsoft.com/?id=884537
> 887563 Availability of the .NET Framework 1.1 Post-Service Pack 1 rollup
> http://support.microsoft.com/?id=887563
> Also, please search if there are multiple copies of security.dll on your
> SQL Reporting Services machine. If there are security.dll other than
> %windir%\system32 folder, please tempoarily rename them to test the
> situation.
>
> Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
> --
> | Thread-Topic: Intermittent 401: Not Authorized
> | thread-index: AcVTuOW2QlsDZxZ1SwW4LqLFvzorxw==> | X-WBNR-Posting-Host: 62.97.217.178
> | From: =?Utf-8?B?TWljaGFlbCBEb3JmbWFu?= <mercatus2004@.online.nospam>
> | Subject: Intermittent 401: Not Authorized
> | Date: Sun, 8 May 2005 03:30:04 -0700
> | Lines: 11
> | Message-ID: <E81A662F-4F37-45EB-8174-9C17787D5295@.microsoft.com>
> | MIME-Version: 1.0
> | Content-Type: text/plain;
> | charset="Utf-8"
> | Content-Transfer-Encoding: 7bit
> | X-Newsreader: Microsoft CDO for Windows 2000
> | Content-Class: urn:content-classes:message
> | Importance: normal
> | Priority: normal
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> | Newsgroups: microsoft.public.sqlserver.reportingsvcs
> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> | Xref: TK2MSFTNGXA01.phx.gbl
> microsoft.public.sqlserver.reportingsvcs:43126
> | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> |
> | The first time I try to access a RS report after an IISreset, I get a
> | "System.Net.WebException: The request failed with HTTP status 401:
> | Unauthorized." error. If I try to access it again, I get in without a
> | problem.
> |
> | In addition to the "first attempt after the iisreset", which happens
> | consistently, we also intermittently experience the same error,
> infrequently.
> |
> | Any idea what is going on here? Caching of Credentials?
> |
> | Michael Dorfman
> |
>|||I have 4 different security.dll files...
C:\WINDOWS\system32 - version 5.2.3790.0
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET
Files\reportserver\28ed0657\f12b7b77\assembly\dl2\d011044e\8fb1f7af_6dc3c401
C:\WINDOWS\system32\dllcache
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportServer\bin - version 1.0.1770.24267
should I keep the Reporting Services version or the Windows version?
"Peter Yang [MSFT]" wrote:
> Hello Michael,
> To understand the issue better, I'd like to know the following information:
> 1. Does the issue only occur with a specific RS report or any RS report
> such as sample reports including in RS installation?
> 2. Do you have anonymous access enabled on Report Manager or Report Server
> virtual directories?
> Also, this issue might be related to a known issue in .Net framework 1.1
> sp1, I suggest that you contact CSS to get 887563 installed hotfix 887563
> to see if it helps:
> 884537 FIX: You may receive a "System.Net.WebException" error message when
> you
> http://support.microsoft.com/?id=884537
> 887563 Availability of the .NET Framework 1.1 Post-Service Pack 1 rollup
> http://support.microsoft.com/?id=887563
> Also, please search if there are multiple copies of security.dll on your
> SQL Reporting Services machine. If there are security.dll other than
> %windir%\system32 folder, please tempoarily rename them to test the
> situation.
>
> Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> --
> | Thread-Topic: Intermittent 401: Not Authorized
> | thread-index: AcVTuOW2QlsDZxZ1SwW4LqLFvzorxw==> | X-WBNR-Posting-Host: 62.97.217.178
> | From: =?Utf-8?B?TWljaGFlbCBEb3JmbWFu?= <mercatus2004@.online.nospam>
> | Subject: Intermittent 401: Not Authorized
> | Date: Sun, 8 May 2005 03:30:04 -0700
> | Lines: 11
> | Message-ID: <E81A662F-4F37-45EB-8174-9C17787D5295@.microsoft.com>
> | MIME-Version: 1.0
> | Content-Type: text/plain;
> | charset="Utf-8"
> | Content-Transfer-Encoding: 7bit
> | X-Newsreader: Microsoft CDO for Windows 2000
> | Content-Class: urn:content-classes:message
> | Importance: normal
> | Priority: normal
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> | Newsgroups: microsoft.public.sqlserver.reportingsvcs
> | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.reportingsvcs:43126
> | X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
> |
> | The first time I try to access a RS report after an IISreset, I get a
> | "System.Net.WebException: The request failed with HTTP status 401:
> | Unauthorized." error. If I try to access it again, I get in without a
> | problem.
> |
> | In addition to the "first attempt after the iisreset", which happens
> | consistently, we also intermittently experience the same error,
> infrequently.
> |
> | Any idea what is going on here? Caching of Credentials?
> |
> | Michael Dorfman
> |
>

Intermittant Connection Errors

I have a Merge-Pull subscription setup between two SQL 2005 databases. While watching the status messages display for the subscription, I am constantly seeing the following message being displayed:

"The merge process could not connect to the Publisher '{server}:{database}'. Check to ensure that the server is running."

It will display for anywhere between 15 seconds to a few minutes, then it will display the standard "Waiting 60 seconds..." message which is what I'm used to seeing when all is working well.

There doesn't seem to be any network issues that I can identify. I ran a quick script to run ping continuously against the publisher server and verified that the server was constantly "pingable", even when the above message was displayed (which, by the way, was being displayed by using SSMS while connected to the publisher).

Does anyone know what would cause this message to appear all the time - for extended amounts of time, with occasional glimpses of a non-error status?

It's a wild guess but failing to login / authenticate ?|||I thought of that but am not sure that it applies. The reason being that I can leave the subscription/synchronization status window open in SSMS and it will toggle back and forth (seemingly randomly over time) between the message I mentioned above and some type of valid message.|||What about Timeouts (Connection or Query)? I have seen similar issues in Web Sync. If the amount of data changed since the last sync operation then I have experienced Timeouts while the sync is initialized. Not exactly as you describe but another parameter worth checking.

Rab
|||

I'm not sure what the issue was but it seems to have resolved itself - at least for the time being. If it happens again, I'll be looking for more answers :-)

Thanks for everyone's help.

|||I have this problem as well. It works sometimes and then fails with this error message which leads me to believe it isn't a login problem. I'm still new to replication so I could be wrong, but I think once I get this message, replication is broken and requires someone to intervene to reinitialize. Has anyone figured out what is going on?

Intermittant Connection Errors

I have a Merge-Pull subscription setup between two SQL 2005 databases. While watching the status messages display for the subscription, I am constantly seeing the following message being displayed:

"The merge process could not connect to the Publisher '{server}:{database}'. Check to ensure that the server is running."

It will display for anywhere between 15 seconds to a few minutes, then it will display the standard "Waiting 60 seconds..." message which is what I'm used to seeing when all is working well.

There doesn't seem to be any network issues that I can identify. I ran a quick script to run ping continuously against the publisher server and verified that the server was constantly "pingable", even when the above message was displayed (which, by the way, was being displayed by using SSMS while connected to the publisher).

Does anyone know what would cause this message to appear all the time - for extended amounts of time, with occasional glimpses of a non-error status?

It's a wild guess but failing to login / authenticate ?|||I thought of that but am not sure that it applies. The reason being that I can leave the subscription/synchronization status window open in SSMS and it will toggle back and forth (seemingly randomly over time) between the message I mentioned above and some type of valid message.|||What about Timeouts (Connection or Query)? I have seen similar issues in Web Sync. If the amount of data changed since the last sync operation then I have experienced Timeouts while the sync is initialized. Not exactly as you describe but another parameter worth checking.

Rab|||

I'm not sure what the issue was but it seems to have resolved itself - at least for the time being. If it happens again, I'll be looking for more answers :-)

Thanks for everyone's help.

|||I have this problem as well. It works sometimes and then fails with this error message which leads me to believe it isn't a login problem. I'm still new to replication so I could be wrong, but I think once I get this message, replication is broken and requires someone to intervene to reinitialize. Has anyone figured out what is going on?sql

Integrity Check set in Maintenance Plan failed....

I'm trying to troubleshoot why this job failed. Welcome any suggestion
DURATION: 0 hours, 0 minutes, 49 second
STATUS: Faile
MESSAGES: The job failed. The Job was invoked by Schedule 35 (Schedule 1). The last step to run was step 1 (Step 1)Make sure that you have defined a report file for the maint job and check for error messages in the
report file.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Janice" <anonymous@.discussions.microsoft.com> wrote in message
news:EDF91295-5A27-43C3-AA1C-402F35FB629F@.microsoft.com...
> I'm trying to troubleshoot why this job failed. Welcome any suggestions
>
> DURATION: 0 hours, 0 minutes, 49 seconds
> STATUS: Failed
> MESSAGES: The job failed. The Job was invoked by Schedule 35 (Schedule 1). The last step to run
was step 1 (Step 1).
>|||Thanks TIBOR - I viewed the report and discovered that db needs to be in single user mode.
-- Tibor Karaszi wrote: --
Make sure that you have defined a report file for the maint job and check for error messages in the
report file.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Janice" <anonymous@.discussions.microsoft.com> wrote in message
news:EDF91295-5A27-43C3-AA1C-402F35FB629F@.microsoft.com...
> I'm trying to troubleshoot why this job failed. Welcome any suggestions
>> DURATION: 0 hours, 0 minutes, 49 seconds
> STATUS: Failed
> MESSAGES: The job failed. The Job was invoked by Schedule 35 (Schedule 1). The last step to run
was step 1 (Step 1).
>|||The maint plan will try to set the db in single user, but that will fail if there are users in the
database. Also, some of the system databases cannot be set in single user mode.
I suggest you remove the option "attempt to repair minor problems" from the integrity checks. If you
do run into problems, you want to be there and contemplate over what you want to do to fix it.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Janice" <anonymous@.discussions.microsoft.com> wrote in message
news:8FF8A86A-F50A-4EB8-BF6D-058B99EF2455@.microsoft.com...
> Thanks TIBOR - I viewed the report and discovered that db needs to be in single user mode.
> -- Tibor Karaszi wrote: --
> Make sure that you have defined a report file for the maint job and check for error messages
in the
> report file.
> --
> Tibor Karaszi, SQL Server MVP
> Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "Janice" <anonymous@.discussions.microsoft.com> wrote in message
> news:EDF91295-5A27-43C3-AA1C-402F35FB629F@.microsoft.com...
> > I'm trying to troubleshoot why this job failed. Welcome any suggestions
> >> DURATION: 0 hours, 0 minutes, 49 seconds
> > STATUS: Failed
> > MESSAGES: The job failed. The Job was invoked by Schedule 35 (Schedule 1). The last step
to run
> was step 1 (Step 1).
> >