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

I have a C# windows service that uses MSMQ, DTC Transactions, SQL server
2005 and Notification services.
I am doing the following in the service:
OnStart
Create the queue
set the P Complete event
call Begin P
PComplete
WaitHandle[] waitHandle = new WaitHandle[] { new
AutoResetEvent(false) };
ThreadPool.QueueUserWorkItem(ProcessMessage, waitHandle[0])
Call End P
WaitHandle.WaiteAll(waitHandle)
queue.BeginP
ProcessMessage(object stateInfo)
AutoResetEvent are = (AutoResetEvent)stateInfo;
Create DTC Transaction
try
Message msg =
callResultQueue.Receive(MessageQueueTransactionType.Automatic);
are.Set();
retreive Message Body
Using (SQLConnection conn = new SQLConnection(connectionString))
conn.open
Write Message Body to database
If Messagebody.Status = 20
Update Notification Services
Commit DTC transaction
catch
Roll Back DTC Transaction
Quite often I am receiving the above message, I've googled it and all I've
come up with is people asking how to solve the error. Any information would
be greatly appreciated. I know the above is mixed psudeo code with code, if
additional code is required please let me know, I'll provide what I can.
Thanks
WayneIt would be helpful if you could post working code...
Noel
Wayne Sepega wrote:
> I have a C# windows service that uses MSMQ, DTC Transactions, SQL server
> 2005 and Notification services.
> I am doing the following in the service:
> OnStart
> Create the queue
> set the P Complete event
> call Begin P
> PComplete
> WaitHandle[] waitHandle = new WaitHandle[] { new
> AutoResetEvent(false) };
> ThreadPool.QueueUserWorkItem(ProcessMessage, waitHandle[0])
> Call End P
> WaitHandle.WaiteAll(waitHandle)
> queue.BeginP
> ProcessMessage(object stateInfo)
> AutoResetEvent are = (AutoResetEvent)stateInfo;
> Create DTC Transaction
> try
> Message msg =
> callResultQueue.Receive(MessageQueueTransactionType.Automatic);
> are.Set();
> retreive Message Body
> Using (SQLConnection conn = new SQLConnection(connectionString))
> conn.open
> Write Message Body to database
> If Messagebody.Status = 20
> Update Notification Services
> Commit DTC transaction
> catch
> Roll Back DTC Transaction
>
> Quite often I am receiving the above message, I've googled it and all I've
> come up with is people asking how to solve the error. Any information woul
d
> be greatly appreciated. I know the above is mixed psudeo code with code, i
f
> additional code is required please let me know, I'll provide what I can.
> Thanks
> Wayne

New request is not allowed to start

Hi folks,
We have an Access front end that happily does all its reading, riting
and rithmetic onto a SQL Server 2005 BE.
There is a timer event on one of the user forms that polls to see if
the DBA wants to kick you out (a flag on a table that gets set by an
Administrators task, and if it is on, then users get a message).
This all works fine, unless the user is running one of the two stored
procedures that take a long while to execute (up to 60 seconds).
When that happens, if the execution time of the sp is longer than the
polling time interval (20 seconds), a conflict seems to occur, and we
get the message "New request is not allowed to start because it should
come with a valid transaction descriptor."
We have tried putting the statement SET TRANSACTION ISOLATION LEVEL
READ UNCOMMITTED; into the stored proc, but it doesn't seem to have
helped.
Any ideas on how we can solve the problem?
Can we somehow run the procedure as a batch that is initiated by the
front-end, but doesn't need to maintain a connection with it?
We were required by the Powers That Be to open a single connection on
our front end for any DB access, rather than open a connection for
each form or process. Could this have something to do with it?
Any ideas gratefully received, Ray<ray@.aic.net.au> wrote in message
news:1194497708.231234.313780@.z24g2000prh.googlegroups.com...
> Hi folks,
> We have an Access front end that happily does all its reading, riting
> and rithmetic onto a SQL Server 2005 BE.
> There is a timer event on one of the user forms that polls to see if
> the DBA wants to kick you out (a flag on a table that gets set by an
> Administrators task, and if it is on, then users get a message).
> This all works fine, unless the user is running one of the two stored
> procedures that take a long while to execute (up to 60 seconds).
> When that happens, if the execution time of the sp is longer than the
> polling time interval (20 seconds), a conflict seems to occur, and we
> get the message "New request is not allowed to start because it should
> come with a valid transaction descriptor."
> We have tried putting the statement SET TRANSACTION ISOLATION LEVEL
> READ UNCOMMITTED; into the stored proc, but it doesn't seem to have
> helped.
> Any ideas on how we can solve the problem?
> Can we somehow run the procedure as a batch that is initiated by the
> front-end, but doesn't need to maintain a connection with it?
> We were required by the Powers That Be to open a single connection on
> our front end for any DB access, rather than open a connection for
> each form or process. Could this have something to do with it?
> Any ideas gratefully received, Ray
>
Have you considered using
ALTER DATABASE SET SINGLE_USER WITH
[
ROLLBACK AFTER integer [ SECONDS ]
| ROLLBACK IMMEDIATE
| NO_WAIT
];
?
David Portas|||Well, no, I hadn't considered that because the problem can occur when
only one user is connected to the database.
I'm sure that the conflict is not between User A and User B.
As far as I can see (and our error trapping seems to confirm this),
the problem is that Stored Proc 1 executed by User A causes a conflict
with Stored Proc 2 also executed by User A (the polling process).
So thanks for your suggestion, but I am hoping to find a way to allow
the user to initiate and receive notifications from two separate
processes. Perhaps one needs to run independently somehow, just by
being initiated at the front end? Or do we need multiple connections
from the front end?
Thanks,
Ray|||Just for the record, in case anybody else encounters this, we opened a
separate connection in the Access front end and did the polling
through it, which resolved the problemo.

New request is not allowed to start

Hi folks,
We have an Access front end that happily does all its reading, riting
and rithmetic onto a SQL Server 2005 BE.
There is a timer event on one of the user forms that polls to see if
the DBA wants to kick you out (a flag on a table that gets set by an
Administrators task, and if it is on, then users get a message).
This all works fine, unless the user is running one of the two stored
procedures that take a long while to execute (up to 60 seconds).
When that happens, if the execution time of the sp is longer than the
polling time interval (20 seconds), a conflict seems to occur, and we
get the message "New request is not allowed to start because it should
come with a valid transaction descriptor."
We have tried putting the statement SET TRANSACTION ISOLATION LEVEL
READ UNCOMMITTED; into the stored proc, but it doesn't seem to have
helped.
Any ideas on how we can solve the problem?
Can we somehow run the procedure as a batch that is initiated by the
front-end, but doesn't need to maintain a connection with it?
We were required by the Powers That Be to open a single connection on
our front end for any DB access, rather than open a connection for
each form or process. Could this have something to do with it?
Any ideas gratefully received, Ray
Well, no, I hadn't considered that because the problem can occur when
only one user is connected to the database.
I'm sure that the conflict is not between User A and User B.
As far as I can see (and our error trapping seems to confirm this),
the problem is that Stored Proc 1 executed by User A causes a conflict
with Stored Proc 2 also executed by User A (the polling process).
So thanks for your suggestion, but I am hoping to find a way to allow
the user to initiate and receive notifications from two separate
processes. Perhaps one needs to run independently somehow, just by
being initiated at the front end? Or do we need multiple connections
from the front end?
Thanks,
Ray
|||Just for the record, in case anybody else encounters this, we opened a
separate connection in the Access front end and did the polling
through it, which resolved the problemo.

New request is not allowed to start

Hi folks,
We have an Access front end that happily does all its reading, riting
and rithmetic onto a SQL Server 2005 BE.
There is a timer event on one of the user forms that polls to see if
the DBA wants to kick you out (a flag on a table that gets set by an
Administrators task, and if it is on, then users get a message).
This all works fine, unless the user is running one of the two stored
procedures that take a long while to execute (up to 60 seconds).
When that happens, if the execution time of the sp is longer than the
polling time interval (20 seconds), a conflict seems to occur, and we
get the message "New request is not allowed to start because it should
come with a valid transaction descriptor."
We have tried putting the statement SET TRANSACTION ISOLATION LEVEL
READ UNCOMMITTED; into the stored proc, but it doesn't seem to have
helped.
Any ideas on how we can solve the problem?
Can we somehow run the procedure as a batch that is initiated by the
front-end, but doesn't need to maintain a connection with it?
We were required by the Powers That Be to open a single connection on
our front end for any DB access, rather than open a connection for
each form or process. Could this have something to do with it?
Any ideas gratefully received, Ray<ray@.aic.net.au> wrote in message
news:1194497708.231234.313780@.z24g2000prh.googlegroups.com...
> Hi folks,
> We have an Access front end that happily does all its reading, riting
> and rithmetic onto a SQL Server 2005 BE.
> There is a timer event on one of the user forms that polls to see if
> the DBA wants to kick you out (a flag on a table that gets set by an
> Administrators task, and if it is on, then users get a message).
> This all works fine, unless the user is running one of the two stored
> procedures that take a long while to execute (up to 60 seconds).
> When that happens, if the execution time of the sp is longer than the
> polling time interval (20 seconds), a conflict seems to occur, and we
> get the message "New request is not allowed to start because it should
> come with a valid transaction descriptor."
> We have tried putting the statement SET TRANSACTION ISOLATION LEVEL
> READ UNCOMMITTED; into the stored proc, but it doesn't seem to have
> helped.
> Any ideas on how we can solve the problem?
> Can we somehow run the procedure as a batch that is initiated by the
> front-end, but doesn't need to maintain a connection with it?
> We were required by the Powers That Be to open a single connection on
> our front end for any DB access, rather than open a connection for
> each form or process. Could this have something to do with it?
> Any ideas gratefully received, Ray
>
Have you considered using
ALTER DATABASE SET SINGLE_USER WITH
[
ROLLBACK AFTER integer [ SECONDS ]
| ROLLBACK IMMEDIATE
| NO_WAIT
];
?
--
David Portas|||Well, no, I hadn't considered that because the problem can occur when
only one user is connected to the database.
I'm sure that the conflict is not between User A and User B.
As far as I can see (and our error trapping seems to confirm this),
the problem is that Stored Proc 1 executed by User A causes a conflict
with Stored Proc 2 also executed by User A (the polling process).
So thanks for your suggestion, but I am hoping to find a way to allow
the user to initiate and receive notifications from two separate
processes. Perhaps one needs to run independently somehow, just by
being initiated at the front end? Or do we need multiple connections
from the front end?
Thanks,
Ray|||Just for the record, in case anybody else encounters this, we opened a
separate connection in the Access front end and did the polling
through it, which resolved the problemo.

New Project - Should I use MS technology?

Wow, this is exciting. I've just got a new project request. It's for
building a statement processing system. Customer send us data, we merge the
data with an existing report layout, then we print and send back to the
customer for distibution.
Sounds simple enough right? Use Crystal or SQL Server Reporting to create
the reports, convert the data to a standardized dataset, merge with the
report and send to the printer. But wait (and this is the part that scares
me), how many statements are we talking about? As little as 50, but up to
150,000, and we're talking about 4-8 pages, with images and graphs.
I've worked with Crystal and SQL Reporting Services, but I just don't think
either of them can handle jobs of this magnatued. Anybody used either of
these for something of that scale? I'm thinking of telling the project
sponsor that it would be better to call our IBM Rep and get them to put us a
solution together. What do you think?
DaveHi posted a request for help in scaling RS a couple of days ago but as yet
no responses.
"David Young" <REMOVE_THIS.dmy75252@.yahoo.com> wrote in message
news:OXvzfAdQFHA.3144@.tk2msftngp13.phx.gbl...
> Wow, this is exciting. I've just got a new project request. It's for
> building a statement processing system. Customer send us data, we merge
> the
> data with an existing report layout, then we print and send back to the
> customer for distibution.
> Sounds simple enough right? Use Crystal or SQL Server Reporting to create
> the reports, convert the data to a standardized dataset, merge with the
> report and send to the printer. But wait (and this is the part that
> scares
> me), how many statements are we talking about? As little as 50, but up to
> 150,000, and we're talking about 4-8 pages, with images and graphs.
> I've worked with Crystal and SQL Reporting Services, but I just don't
> think
> either of them can handle jobs of this magnatued. Anybody used either of
> these for something of that scale? I'm thinking of telling the project
> sponsor that it would be better to call our IBM Rep and get them to put us
> a
> solution together. What do you think?
> Dave
>
>|||>> sounds like a good project indeed !
>> I guess MSFT only can say whether RS can handle loads of this magnitude but in the meantime, have you looked at the data-driven subscription feature in RS ? --
>> RS can be installed in load-balanced farm -- you may have to write code to receive data from customers and then send it to a load-balanced reporting servers -
>> It is not easy to automatically send reports to the printer in SQL2000RS -- there is a printer delivery extension that you need to compile and install and make it work - instead you can setup a schedule to save the reports to a fileshare and email the reports to your customers
>>Also, before calling the IBM rep, you might want to take a look at BizTalk2004 server - just a quick-read thru its documentation may give you more ideas.
>> Another idea before calling the IBM rep - is to call someone like Hitachi Consulting and see if they can handle this project.
regards
ranga raghuram
"David Young" wrote:
> Wow, this is exciting. I've just got a new project request. It's for
> building a statement processing system. Customer send us data, we merge the
> data with an existing report layout, then we print and send back to the
> customer for distibution.
> Sounds simple enough right? Use Crystal or SQL Server Reporting to create
> the reports, convert the data to a standardized dataset, merge with the
> report and send to the printer. But wait (and this is the part that scares
> me), how many statements are we talking about? As little as 50, but up to
> 150,000, and we're talking about 4-8 pages, with images and graphs.
> I've worked with Crystal and SQL Reporting Services, but I just don't think
> either of them can handle jobs of this magnatued. Anybody used either of
> these for something of that scale? I'm thinking of telling the project
> sponsor that it would be better to call our IBM Rep and get them to put us a
> solution together. What do you think?
> Dave
>
>

New Install Problem

Got past other issues.. now getting bad request...
I have this working wonderfully on my local machine... can't get it to work
on a Win2k3 server..
Anyone have any links?
w3wp!ui!690!10/7/2004-15:49:04:: e ERROR: The request failed with HTTP
status 400: Bad Request.
w3wp!ui!690!10/7/2004-15:49:04:: e ERROR: HTTP status code --> 500
--Details--
System.Net.WebException: The request failed with HTTP status 400: Bad
Request.
at
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClient
Message message, WebResponse response, Stream responseStream, Boolean
asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
at
Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
at Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
at Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
at
Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
methodname)
at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
at
Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
level)
at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
sender, EventArgs args)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Web.UI.Control.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain()
w3wp!ui!690!10/7/2004-15:49:04:: e ERROR: Exception in ShowErrorPage:
System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean
preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg) at at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean
preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg)One difference between Win2k3 server and 2000 pro (I've had it on both) is
that for Win2K3 for the service account you get the option of network
service or system. I picked system. Not sure if it makes a difference but I
have successfully installed on two Win2K3 machines this way. I haven't seen
the exact error but this is what worked for me.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
Service Account - use built-in account. Have two choices. Pick system, Not
network service
"CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
news:OBh%23$%23KrEHA.756@.TK2MSFTNGP11.phx.gbl...
> Got past other issues.. now getting bad request...
>
> I have this working wonderfully on my local machine... can't get it to
work
> on a Win2k3 server..
> Anyone have any links?
>
> w3wp!ui!690!10/7/2004-15:49:04:: e ERROR: The request failed with HTTP
> status 400: Bad Request.
> w3wp!ui!690!10/7/2004-15:49:04:: e ERROR: HTTP status code --> 500
> --Details--
> System.Net.WebException: The request failed with HTTP status 400: Bad
> Request.
> at
>
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClient
> Message message, WebResponse response, Stream responseStream, Boolean
> asyncCall)
> at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> methodName, Object[] parameters)
> at
> Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
> at
Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
> at
Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
> at
> Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
> methodname)
> at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
> at
> Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
> level)
> at
Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
> sender, EventArgs args)
> at System.EventHandler.Invoke(Object sender, EventArgs e)
> at System.Web.UI.Control.OnInit(EventArgs e)
> at System.Web.UI.Control.InitRecursive(Control namingContainer)
> at System.Web.UI.Page.ProcessRequestMain()
> w3wp!ui!690!10/7/2004-15:49:04:: e ERROR: Exception in ShowErrorPage:
> System.Threading.ThreadAbortException: Thread was being aborted.
> at System.Threading.Thread.AbortInternal()
> at System.Threading.Thread.Abort(Object stateInfo)
> at System.Web.HttpResponse.End()
> at System.Web.HttpServerUtility.Transfer(String path, Boolean
> preserveForm)
> at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> errMsg) at at System.Threading.Thread.AbortInternal()
> at System.Threading.Thread.Abort(Object stateInfo)
> at System.Web.HttpResponse.End()
> at System.Web.HttpServerUtility.Transfer(String path, Boolean
> preserveForm)
> at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> errMsg)
>|||No dice... still getting bad request.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:%236HPxGLrEHA.192@.tk2msftngp13.phx.gbl...
> One difference between Win2k3 server and 2000 pro (I've had it on both) is
> that for Win2K3 for the service account you get the option of network
> service or system. I picked system. Not sure if it makes a difference but
I
> have successfully installed on two Win2K3 machines this way. I haven't
seen
> the exact error but this is what worked for me.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> Service Account - use built-in account. Have two choices. Pick system, Not
> network service
> "CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
> news:OBh%23$%23KrEHA.756@.TK2MSFTNGP11.phx.gbl...
> > Got past other issues.. now getting bad request...
> >
> >
> > I have this working wonderfully on my local machine... can't get it to
> work
> > on a Win2k3 server..
> >
> > Anyone have any links?
> >
> >
> >
> > w3wp!ui!690!10/7/2004-15:49:04:: e ERROR: The request failed with HTTP
> > status 400: Bad Request.
> > w3wp!ui!690!10/7/2004-15:49:04:: e ERROR: HTTP status code --> 500
> > --Details--
> > System.Net.WebException: The request failed with HTTP status 400: Bad
> > Request.
> >
> > at
> >
>
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClient
> > Message message, WebResponse response, Stream responseStream, Boolean
> > asyncCall)
> >
> > at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> > methodName, Object[] parameters)
> >
> > at
> >
Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
> >
> > at
> Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
> >
> > at
> Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
> >
> > at
> > Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
> > methodname)
> >
> > at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
> >
> > at
> > Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
> > level)
> >
> > at
> Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
> > sender, EventArgs args)
> >
> > at System.EventHandler.Invoke(Object sender, EventArgs e)
> >
> > at System.Web.UI.Control.OnInit(EventArgs e)
> >
> > at System.Web.UI.Control.InitRecursive(Control namingContainer)
> >
> > at System.Web.UI.Page.ProcessRequestMain()
> > w3wp!ui!690!10/7/2004-15:49:04:: e ERROR: Exception in ShowErrorPage:
> > System.Threading.ThreadAbortException: Thread was being aborted.
> > at System.Threading.Thread.AbortInternal()
> > at System.Threading.Thread.Abort(Object stateInfo)
> > at System.Web.HttpResponse.End()
> > at System.Web.HttpServerUtility.Transfer(String path, Boolean
> > preserveForm)
> > at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> > errMsg) at at System.Threading.Thread.AbortInternal()
> > at System.Threading.Thread.Abort(Object stateInfo)
> > at System.Web.HttpResponse.End()
> > at System.Web.HttpServerUtility.Transfer(String path, Boolean
> > preserveForm)
> > at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> > errMsg)
> >
> >
>|||I'm having the same issue. Could you advise on the fix?
Thanks,
John
"CJ Taylor" wrote:
> No dice... still getting bad request.
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:%236HPxGLrEHA.192@.tk2msftngp13.phx.gbl...
> > One difference between Win2k3 server and 2000 pro (I've had it on both) is
> > that for Win2K3 for the service account you get the option of network
> > service or system. I picked system. Not sure if it makes a difference but
> I
> > have successfully installed on two Win2K3 machines this way. I haven't
> seen
> > the exact error but this is what worked for me.
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > Service Account - use built-in account. Have two choices. Pick system, Not
> > network service
> > "CJ Taylor" <[cege] at [tavayn] dit commmmm> wrote in message
> > news:OBh%23$%23KrEHA.756@.TK2MSFTNGP11.phx.gbl...
> > > Got past other issues.. now getting bad request...
> > >
> > >
> > > I have this working wonderfully on my local machine... can't get it to
> > work
> > > on a Win2k3 server..
> > >
> > > Anyone have any links?
> > >
> > >
> > >
> > > w3wp!ui!690!10/7/2004-15:49:04:: e ERROR: The request failed with HTTP
> > > status 400: Bad Request.
> > > w3wp!ui!690!10/7/2004-15:49:04:: e ERROR: HTTP status code --> 500
> > > --Details--
> > > System.Net.WebException: The request failed with HTTP status 400: Bad
> > > Request.
> > >
> > > at
> > >
> >
> System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClient
> > > Message message, WebResponse response, Stream responseStream, Boolean
> > > asyncCall)
> > >
> > > at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> > > methodName, Object[] parameters)
> > >
> > > at
> > >
> Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
> > >
> > > at
> > Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
> > >
> > > at
> > Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
> > >
> > > at
> > > Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
> > > methodname)
> > >
> > > at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
> > >
> > > at
> > > Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
> > > level)
> > >
> > > at
> > Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
> > > sender, EventArgs args)
> > >
> > > at System.EventHandler.Invoke(Object sender, EventArgs e)
> > >
> > > at System.Web.UI.Control.OnInit(EventArgs e)
> > >
> > > at System.Web.UI.Control.InitRecursive(Control namingContainer)
> > >
> > > at System.Web.UI.Page.ProcessRequestMain()
> > > w3wp!ui!690!10/7/2004-15:49:04:: e ERROR: Exception in ShowErrorPage:
> > > System.Threading.ThreadAbortException: Thread was being aborted.
> > > at System.Threading.Thread.AbortInternal()
> > > at System.Threading.Thread.Abort(Object stateInfo)
> > > at System.Web.HttpResponse.End()
> > > at System.Web.HttpServerUtility.Transfer(String path, Boolean
> > > preserveForm)
> > > at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> > > errMsg) at at System.Threading.Thread.AbortInternal()
> > > at System.Threading.Thread.Abort(Object stateInfo)
> > > at System.Web.HttpResponse.End()
> > > at System.Web.HttpServerUtility.Transfer(String path, Boolean
> > > preserveForm)
> > > at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
> > > errMsg)
> > >
> > >
> >
> >
>
>