"The request failed with HTTP status 401: Unauthorized" SQl server reports

I am using SQL Server Reporting. All reports are deployed on REPORTING SERVER.

I want to implement security roles as same as in Active directory. Currently reports are being accessed using Anonymous user setting in IIS.

I have added users in SQL Server security as well as data base level. But when user accesses report following error occurs:

The request failed with HTTP status 401: Unauthorized

Please reply with solution as soon as possible. I will be very thankful to you

So, this is an IIS error which means that the request doesn't event make it to the Report Server. You can try creating a simple website with a single page in it and configure this website for Windows Integrated security. You will probably get the same error. You need to find why IIS is rejecting the web request.

"New request is not allowed to start because it should come with valid transaction descript

Hi all,
We are getting "New request is not allowed to start because it should come with valid transaction descriptor" when using transactions against SQL 2005. As I understand it, it's a bug that occurs after some statement has terminated against the database; see http://lab.msdn.microsoft.com/productfeedback/ViewWorkaround.aspx?FeedbackID=FDBK46530#1

Now, I wonder if there is a hotfix coming soon on this?

/Daniel

I have the same error description but within a different setup. Running SQL Server 2005 on Windows Server 2003 R2. Connecting to database use SNAC from VC6 application. Application is written still with old ODBC technology. I have switched back to the SQL Server driver in the odbc connection. Anyone have any ideas surrounding this problem, I also get a lot of query timeouts and have done the usual checks. Ensure no deadlocks occurs. Set query timeout value higher. Doing a google revealed that everyone getting this error has a managed code app using sqlclient, I geuss that this is the same classes MS used within the sql native client driver and therefore the hotfix will sort out this problem?

|||http://support.microsoft.com/kb/916002|||If you contact customer support directly they should be able to provide you with more information about how to resolve this issue.

"New request is not allowed to start because it should come with valid transaction descript

Hi all,
We are getting "New request is not allowed to start because it should come with valid transaction descriptor" when using transactions against SQL 2005. As I understand it, it's a bug that occurs after some statement has terminated against the database; see http://lab.msdn.microsoft.com/productfeedback/ViewWorkaround.aspx?FeedbackID=FDBK46530#1

Now, I wonder if there is a hotfix coming soon on this?

/Daniel

I have the same error description but within a different setup. Running SQL Server 2005 on Windows Server 2003 R2. Connecting to database use SNAC from VC6 application. Application is written still with old ODBC technology. I have switched back to the SQL Server driver in the odbc connection. Anyone have any ideas surrounding this problem, I also get a lot of query timeouts and have done the usual checks. Ensure no deadlocks occurs. Set query timeout value higher. Doing a google revealed that everyone getting this error has a managed code app using sqlclient, I geuss that this is the same classes MS used within the sql native client driver and therefore the hotfix will sort out this problem?

|||http://support.microsoft.com/kb/916002|||If you contact customer support directly they should be able to provide you with more information about how to resolve this issue.

"New request is not allowed to start because it should come with valid transaction descript

Hi all,
We are getting "New request is not allowed to start because it should come with valid transaction descriptor" when using transactions against SQL 2005. As I understand it, it's a bug that occurs after some statement has terminated against the database; see http://lab.msdn.microsoft.com/productfeedback/ViewWorkaround.aspx?FeedbackID=FDBK46530#1

Now, I wonder if there is a hotfix coming soon on this?

/Daniel

I have the same error description but within a different setup. Running SQL Server 2005 on Windows Server 2003 R2. Connecting to database use SNAC from VC6 application. Application is written still with old ODBC technology. I have switched back to the SQL Server driver in the odbc connection. Anyone have any ideas surrounding this problem, I also get a lot of query timeouts and have done the usual checks. Ensure no deadlocks occurs. Set query timeout value higher. Doing a google revealed that everyone getting this error has a managed code app using sqlclient, I geuss that this is the same classes MS used within the sql native client driver and therefore the hotfix will sort out this problem?

|||http://support.microsoft.com/kb/916002|||If you contact customer support directly they should be able to provide you with more information about how to resolve this issue.

"Bad Request" error

Hi,

I've installed Reporting Services and configured it without any problem.
When I browse to http://x.x.x.x/reports I'm getting "Bad Request" error.

Is it related somehow to the IP mapping issue?
Any other clues?

Thanks,
Mark

ps
SQL 2005 RTM
W2K3 Std

Mark,

IP address should work fine. I just tried it, and I didn't have any problem. What happens when you use the NetBIOS name instead of the IP address?|||Mike - I have the same problem - did you ever figure it out?|||If you want to run Reporting Services under a different port than normal, you have to change these two config files:
rsreportserver.config
and
RSWebApplication.config

Enter the full path (like http://servername:port/ReportServer) to <ReportServerUrl> (delete <ReportServerVirtualDirectory> then!) or resp. <UrlRoot>

The result is then
<Configuration>
<UI>
<ReportServerUrl>http://mbs05:8088/reportserver</ReportServerUrl>
<ReportServerVirtualDirectory></ReportServerVirtualDirectory>
<ReportBuilderTrustLevel>FullTrust</ReportBuilderTrustLevel>
</UI>
.....

and

<Configuration>
... <Service>
....
<MaxQueueThreads>0</MaxQueueThreads>
<UrlRoot>http://mbs05:8088/reportserver</UrlRoot>
<UnattendedExecutionAccount>
...

Hope this helps,
Martin

PS: see also http://msdn2.microsoft.com/en-us/library/ms159261(SQL.90).aspx

"Bad Request" error

Hi,

I've installed Reporting Services and configured it without any problem.
When I browse to http://x.x.x.x/reports I'm getting "Bad Request" error.

Is it related somehow to the IP mapping issue?
Any other clues?

Thanks,
Mark

ps
SQL 2005 RTM
W2K3 Std

Mark,

IP address should work fine. I just tried it, and I didn't have any problem. What happens when you use the NetBIOS name instead of the IP address?|||Mike - I have the same problem - did you ever figure it out?|||If you want to run Reporting Services under a different port than normal, you have to change these two config files:
rsreportserver.config
and
RSWebApplication.config

Enter the full path (like http://servername:port/ReportServer) to <ReportServerUrl> (delete <ReportServerVirtualDirectory> then!) or resp. <UrlRoot>

The result is then
<Configuration>
<UI>
<ReportServerUrl>http://mbs05:8088/reportserver</ReportServerUrl>
<ReportServerVirtualDirectory></ReportServerVirtualDirectory>
<ReportBuilderTrustLevel>FullTrust</ReportBuilderTrustLevel>
</UI>
.....

and

<Configuration>
... <Service>
....
<MaxQueueThreads>0</MaxQueueThreads>
<UrlRoot>http://mbs05:8088/reportserver</UrlRoot>
<UnattendedExecutionAccount>
...

Hope this helps,
Martin

PS: see also http://msdn2.microsoft.com/en-us/library/ms159261(SQL.90).aspx

"Bad Request" error

Hi,

I've installed Reporting Services and configured it without any problem.
When I browse to http://x.x.x.x/reports I'm getting "Bad Request" error.

Is it related somehow to the IP mapping issue?
Any other clues?

Thanks,
Mark

ps
SQL 2005 RTM
W2K3 Std

Mark,

IP address should work fine. I just tried it, and I didn't have any problem. What happens when you use the NetBIOS name instead of the IP address?|||Mike - I have the same problem - did you ever figure it out?|||If you want to run Reporting Services under a different port than normal, you have to change these two config files:
rsreportserver.config
and
RSWebApplication.config

Enter the full path (like http://servername:port/ReportServer) to <ReportServerUrl> (delete <ReportServerVirtualDirectory> then!) or resp. <UrlRoot>

The result is then
<Configuration>
<UI>
<ReportServerUrl>http://mbs05:8088/reportserver</ReportServerUrl>
<ReportServerVirtualDirectory></ReportServerVirtualDirectory>
<ReportBuilderTrustLevel>FullTrust</ReportBuilderTrustLevel>
</UI>
.....

and

<Configuration>
... <Service>
....
<MaxQueueThreads>0</MaxQueueThreads>
<UrlRoot>http://mbs05:8088/reportserver</UrlRoot>
<UnattendedExecutionAccount>
...

Hope this helps,
Martin

PS: see also http://msdn2.microsoft.com/en-us/library/ms159261(SQL.90).aspx