Error 17883 - Scheduler appears to be hung - related to linked server or HT??

We have been getting the following errors on our production environment
lately.
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x021B55C0
It appears that this error shows whenever we run a query with a linked
server. This error appears concurrently with an application popup on the
SQL server.
Application popup: SQL Server OLEDB provider support error : Unable to load
SQL Server OLEDB provider resource DLL. The application cannot continue.
We had this issue earlier with another machine which had parallelization
turned on. We turned it off because we believed the Hyperthreading w/
Parallelization was confusing this. Our old servers never had these issues
and were not HT enabled. The one box that was experiencing the problems
was/is behaving normally. However another box (same CPU, same no
parallelization settings) is having the issue when running a query using a
linked server to another SQL Server.
Our servers are SQL Server 2000 SP3, on Windows2000 SP4. With 2 3.2Ghz, HT
Enabled and 1.5GB RAM.
Thanks,
DanWe've seen the 17883 happen for a variety of reasons and symptoms.
It almost always comes down to disk i/o - contention issues. We had a
msde show this after being bombarded with query requests and with an 8
concurrent query limit.
Check to make sure that SQL Server is the ONLY one messing with
its' files. Make sure that on-access virus scan is off. As well as
backups or anything that might be going after the data and log files.
The last time this happened was because of virus scan and a policy set
that kept re-enabling on access scan.
Frankm
dan wrote:
> We have been getting the following errors on our production environment
> lately.
> Error: 17883, Severity: 1, State: 0
> The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x021B55C0
> It appears that this error shows whenever we run a query with a linked
> server. This error appears concurrently with an application popup on the
> SQL server.
> Application popup: SQL Server OLEDB provider support error : Unable to load
> SQL Server OLEDB provider resource DLL. The application cannot continue.
> We had this issue earlier with another machine which had parallelization
> turned on. We turned it off because we believed the Hyperthreading w/
> Parallelization was confusing this. Our old servers never had these issues
> and were not HT enabled. The one box that was experiencing the problems
> was/is behaving normally. However another box (same CPU, same no
> parallelization settings) is having the issue when running a query using a
> linked server to another SQL Server.
> Our servers are SQL Server 2000 SP3, on Windows2000 SP4. With 2 3.2Ghz, HT
> Enabled and 1.5GB RAM.
> Thanks,
> Dan
>|||Hey Dan,
Your problem is almost exactly what we are facing.
I did not know you had posted your question when I posted
mine ( I usually do a search before posting questions, but
I missed doing it this time). Check out 'my' thread on the
21st & 22nd with 17883 in the subject line.
Did you resolve your problem?
Did you go through any of the suggestions in my thread?
Hotfix to get a more precise indication?
Thanks very much.
Sam
>--Original Message--
>We have been getting the following errors on our
production environment
>lately.
>Error: 17883, Severity: 1, State: 0
>The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS
Context 0x021B55C0
>It appears that this error shows whenever we run a query
with a linked
>server. This error appears concurrently with an
application popup on the
>SQL server.
>Application popup: SQL Server OLEDB provider support
error : Unable to load
>SQL Server OLEDB provider resource DLL. The application
cannot continue.
>We had this issue earlier with another machine which had
parallelization
>turned on. We turned it off because we believed the
Hyperthreading w/
>Parallelization was confusing this. Our old servers
never had these issues
>and were not HT enabled. The one box that was
experiencing the problems
>was/is behaving normally. However another box (same CPU,
same no
>parallelization settings) is having the issue when
running a query using a
>linked server to another SQL Server.
>Our servers are SQL Server 2000 SP3, on Windows2000 SP4.
With 2 3.2Ghz, HT
>Enabled and 1.5GB RAM.
>Thanks,
>Dan
>
>.
>

Error 0x800C0008 with multiple subreports

Hi,

strange behaviour in our production environment, while in the test servers all goes ok:

web application with web report viewer, the report is fine but clicking on "preview" or "print" an error 0x800C008 occurs.

The report include 3 subreports, and here's the problem: after some attempts i realized that each subreport (alone in the master report) works fine, but more than 1 in the same master report produces the error!

Here is the log:

w3wp!library!7!04/17/2007-11:23:55:: i INFO: Call to RenderNext( '/WRReports/Orders' )
w3wp!processing!7!04/17/2007-11:23:55:: a ASSERT: Assertion failed! Call stack:
Microsoft.ReportingServices.ReportProcessing.Persistence.IntermediateFormatReader.Assert(Boolean condition)
Microsoft.ReportingServices.ReportProcessing.Persistence.IntermediateFormatReader.RegisterDefinitionObject(IDOwner idOwner)
Microsoft.ReportingServices.ReportProcessing.Persistence.IntermediateFormatReader.ReadReportItemBase(ReportItem reportItem)
...
Microsoft.ReportingServices.Library.AsyncExecution.AsyncStartMain(Object state)
Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper()
Microsoft.ReportingServices.Diagnostics.ThreadWorkItem.SafeThreadPoolCallback(Object ctx)
System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state)
System.Threading.ExecutionContext.runTryCode(Object userData)
System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)

w3wp!library!7!04/17/2007-11:23:55:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: Errore interno nel server di report. Per ulteriori informazioni, vedere il log degli errori., un-named assertion fired for component processing;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: Errore interno nel server di report. Per ulteriori informazioni, vedere il log degli errori.

Any ideas?

Thanks in advance to anyone

Hi all,

we found the solution and so we can post it for public utility.

The problem were related to the size of reports.

When reports exceed a few bytes, reporting services uses a "transfer-enconding: chunked" header in the http message from the rssclientreport object in the html page.

So, a proxy in the middle of our architecture were unable to do its job because it didn't understand that header; an installation of the last version of that proxy solved the problem.

We didn't found any way to change that behavior of ssrs2005 and forcing it to use standard transfer encoding.

bye.

Error 0x800C0008 with multiple subreports

Hi,

strange behaviour in our production environment, while in the test servers all goes ok:

web application with web report viewer, the report is fine but clicking on "preview" or "print" an error 0x800C008 occurs.

The report include 3 subreports, and here's the problem: after some attempts i realized that each subreport (alone in the master report) works fine, but more than 1 in the same master report produces the error!

Here is the log:

w3wp!library!7!04/17/2007-11:23:55:: i INFO: Call to RenderNext( '/WRReports/Orders' )
w3wp!processing!7!04/17/2007-11:23:55:: a ASSERT: Assertion failed! Call stack:
Microsoft.ReportingServices.ReportProcessing.Persistence.IntermediateFormatReader.Assert(Boolean condition)
Microsoft.ReportingServices.ReportProcessing.Persistence.IntermediateFormatReader.RegisterDefinitionObject(IDOwner idOwner)
Microsoft.ReportingServices.ReportProcessing.Persistence.IntermediateFormatReader.ReadReportItemBase(ReportItem reportItem)
...
Microsoft.ReportingServices.Library.AsyncExecution.AsyncStartMain(Object state)
Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper()
Microsoft.ReportingServices.Diagnostics.ThreadWorkItem.SafeThreadPoolCallback(Object ctx)
System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state)
System.Threading.ExecutionContext.runTryCode(Object userData)
System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)

w3wp!library!7!04/17/2007-11:23:55:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: Errore interno nel server di report. Per ulteriori informazioni, vedere il log degli errori., un-named assertion fired for component processing;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: Errore interno nel server di report. Per ulteriori informazioni, vedere il log degli errori.

Any ideas?

Thanks in advance to anyone

Hi all,

we found the solution and so we can post it for public utility.

The problem were related to the size of reports.

When reports exceed a few bytes, reporting services uses a "transfer-enconding: chunked" header in the http message from the rssclientreport object in the html page.

So, a proxy in the middle of our architecture were unable to do its job because it didn't understand that header; an installation of the last version of that proxy solved the problem.

We didn't found any way to change that behavior of ssrs2005 and forcing it to use standard transfer encoding.

bye.

error : 18452 in clustering; very urgent

We have 2 failover servers and one client in our test environment. We have all the three configured in mixed mode authentication(windows + sql server authentication). But when we are failing over from 1st server to 2nd one, we are getting the following error message,
'Unable to connected to server xxxx: Server : Msg 18452, Level 16, State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'null'. Reason: Not associated with a trusted SQL server connection.'

I got some clue.

For instance we have ser1 and ser2 as clusters. I registered both in the client's EM. Now what I did was, I made ser1 to run and stopped sql service in ser2 (active/passive) through failover. Now in the client's EM I'm able to open ser1 and I cannot access ser2. Now what I did was, I failed over to ser2 ( so sql service in ser1 is stopped). But now I can still be able to access ser1 and also I can access ser2, even I'm able to open query analyzer in ser1 through EM.But when I try to open query analyzer directly, it is giving the same error message. ser1 is the virtual name given to both ser1 and ser2. So I think when connecting through EM, failover is occuring fine.I'm just wondering why is this happening only with dsn. Can anybody help me?

You can get this particular error in a number of scenarios -- the common scenario is when one attempts SQL authentication using an NT login account. If the system is unable to find the login account it will raise this error. It is not clear the scenario behind this error.

|||The information you provided is not sufficient to diagnose the problem. Do you get this error only after failover? If you start the SQL Server serive on node ser2 (using net start and not via cluster admin) do you still get the same error when the client is also running on node2? Do you get this error only when the client is running on a different node than the SQL Server?
The error will be raised when SQL authentication is tried using an NT login account and it seems like the system is not able to find the login account. Make sure you are using the same account to connect after failover.

Error "Physical Database Not found" When Loading Report

Hi, i'm using CR 8.5, vb6, using acces 2000, data environment and win xp.
i have installed my application to another computer, which use win98 and don't have access 2000.
when i'm installing my application i got this error message "craxddrt failed to register" and then i select ignore to continue the installation...
when i run my application and loading report i got this error message "Physical database not found"
my question is
is the first error is causing the second error? or the database path that im using is not right?
i already tried to install seagate crystal report on the computer but when installing it also have the same error, error 1904 failed to register craxddrt.dll..
can somebody help me?Hi
In the Menu, Goto Database-->Verify Database and configure it|||hi, thx btw,
i already select the menu and then verify database, so i select my recordset from my data environment and it is up to date....
and still got the error message, :(|||Goto Database-->Set DataSource Location and configure the DB|||already but still the same, i've installed into 2 computer, the one is with win xp and office 2002 which is success and the second is win 98 with no access application which show this error. but i have installed mdac 2.8 and jet engine 4 sp for win 98 and vb runtime sp5, even seagate crystal report 8.5 it self.,??|||I Already solved it.. thx btw.
some dll files which i included when installing my program is xp/nt version, so it become problems when i'm installing it to win 98..
so then i replace my included dll files xp/nt version with dll files from win 98 version...and it works..:D