fetch successful resultset after exception

Ok, here is the deal. In T-SQL, an error is handled depending on its severity. For example, a severity of 15 or less (or is it 10 or less? doesn't matter) will only raise a warning that can be caught through the message event. 16 or higher (or whatever) will cause an exception to be thrown on the .NET side, and 20 or higher causes the connection to be closed.

So far so good.

Now here's my issue: I have a stored procedure that does 2 queries (inside the same SP). Sometimes, the first query will succeed, while the second one will cause an error of severity 16. Again, in .NET that will throw an exception, making me unable to fetch the first resultset (which I require for logging purpose). If the error was, let say, severity 9, I could simply subscribe to the message event to get my error, yet still be able to get the first result set. But unfortunately life isn't perfect, and the error is indeed a severity 16.

Anyone know of a way to be able to get the first result set, even if the second query (within the same SP) completly fails?Why don't you wrap the two SQL statements in a transaction, so that if one fails, all attempted changes will be rolled back. You certainly wouldn't want something to work half-way--it should be an all or nothing deal. If you don't mind it working half-way, then perhaps the SQL should be put into separate calls.|||Well, I answered my own question: nothing is stopping me from accessing the data. If using a datareader, the exception isn't thrown until you move to the resultset that errored out. If using a dataset with multiple tables, the tables that succeeded are filled just fine as normal, and the ones that failed have 0 rows. Not the behavior I expected, but it did the trick.

As to why a non-atomic process is wrapped in a single stored procedure? Its because the SP was made for a relatively limited (in features) scheduling software, and it can only call one SP on the trigger. A bit silly, but I'm not the one who set that up originally, I'm just handling a migration. The requirement here was so that we could log what succeeded so we can give the log away to a supplier or some such.

Anyway, seems like ADO.NET handles that requirement just fine after all. I'm surprised, honestly.

FEATURE REQUEST: Jump to Report with rs:, rc: parameters

FEATURE REQUEST (already submitted to sqlwish@.microsoft.com): Allow rs: and
rc: parameters as an exception to the "CLR-compliant parameter name" rule
within Navigation Parameter properties.
Background: I have created a custom report manager that displays reports
within an IFRAME. With URL access, the rc:LinkTarget points to the IFRAME
name.
Problem: Using the "Jump to report" navigation does not carry the
rc:LinkTarget=iframename parameter forward to the linked report. Subsequent
clicks break the report out of the IFRAME. The workaround, dynamically
creating the URL, is cumbersome and limits report portability. In the
Navigation tab (Parameters button), I tried to set rc:LinkTarget as a
parameter with iframename as the value, which produced a compilation error,
that parameter names must be CLR-compliant. This is true except for rs: and
rc: parameters. Please consider allowing a report to compile and publish
with rs: and rc: parameters specified in the Jump to... links.
Thanks,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---I should have mentioned an alternative (also sent to sqlwish):
FEATURE REQUEST ALTERNATIVE: Provide an option to automatically carry
rc:LinkTarget paramters forward in linked (Jump to) reports.
Thanks,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"Jeff A. Stucker" <jeff@.mobilize.net> wrote in message
news:usQBm8DzEHA.2624@.TK2MSFTNGP11.phx.gbl...
> FEATURE REQUEST (already submitted to sqlwish@.microsoft.com): Allow rs:
> and rc: parameters as an exception to the "CLR-compliant parameter name"
> rule within Navigation Parameter properties.
> Background: I have created a custom report manager that displays reports
> within an IFRAME. With URL access, the rc:LinkTarget points to the IFRAME
> name.
> Problem: Using the "Jump to report" navigation does not carry the
> rc:LinkTarget=iframename parameter forward to the linked report.
> Subsequent clicks break the report out of the IFRAME. The workaround,
> dynamically creating the URL, is cumbersome and limits report portability.
> In the Navigation tab (Parameters button), I tried to set rc:LinkTarget as
> a parameter with iframename as the value, which produced a compilation
> error, that parameter names must be CLR-compliant. This is true except for
> rs: and rc: parameters. Please consider allowing a report to compile and
> publish with rs: and rc: parameters specified in the Jump to... links.
> Thanks,
> '(' Jeff A. Stucker
> \
> Business Intelligence
> www.criadvantage.com
> ---
>

Fatal exception while firing a rule

Hi,

I am having a problem when moving our NS application from dev environment to testing environment. What happens, is that when the rule is fired, a fatal exception is generated.

Any hints how I can start hunting down what the source of the problem is. The thing is, this works in dev environment, but not in test. Further, if I try to execute the stored proc manually which fails (NS_MyAppApplication].[NSFire3]) I get the same error: A user request from the session with SPID 63 generated a fatal exception. SQL Server is terminating this session.

Both dev and test environments use same ADF and ICF files. The ADF file is pretty much like in the InventoryTracker sample, using ConditionAction element like this:

<ConditionAction>
<SqlLogin>NSRulesEvaluator</SqlLogin>
<SqlUser>NSRulesEvaluator</SqlUser>
<InputName>InventoryTrackerEvents</InputName>
<InputSchema>NS_InventoryTrackerApplication</InputSchema>
<SqlExpression>

INSERT INTO [NS_InventoryTrackerApplication].[InventoryTrackerNotifications]
(
[SubscriberId],
[DeviceName],
[SubscriberLocale],
[ProductId],
[ProductName],
[ProductNumber],
[Quantity],
[LocationName]
)

(
SELECT
r.[Subscription.SubscriberId],
r.[Subscription.DeviceName],
r.[Subscription.SubscriberLocale],
r.[Input.ProductId],
r.[Input.ProductName],
r.[Input.ProductNumber],
r.[Input.Quantity],
r.[Input.LocationName]

FROM [NS_InventoryTrackerApplication].InventoryTrackerRule AS r
)
</SqlExpression>
</ConditionAction>

I tried changing ADF to little simple version, using action element instead of conditionaction. This time I got it working (and before that normal error messages and not just a stack dump).

Any hints how I can find out what is the problem here, or am I possibly missing something totally?

//sami

Both servers are as below:

Microsoft SQL Server Management Studio 9.00.2047.00
Microsoft Analysis Services Client Tools 2005.090.2047.00
Microsoft Data Access Components (MDAC) 2000.086.1830.00 (srv03_sp1_rtm.050324-1447)
Microsoft MSXML 2.6 3.0 6.0
Microsoft Internet Explorer 6.0.3790.1830
Microsoft .NET Framework 2.0.50727.42
Operating System 5.2.3790

These are entries from application log (in reverse order):

--

Description: The running of the rule failed. Please check the rule.
EventParameters:
Application Name: MyApp
Quantum ID: 4513
Rule Firing ID: 17
Rule Name: MyAppRule
Notification Throttle: 1000
Event Class ID: 1
Subscription Class ID: 1
Rule ID: 3
Rule Action: INSERT INTO [NS_MyAppApplication].[MyAppNotifications]
(
[SubscriberId],
[DeviceName],
[SubscriberLocale],
[SomeData]
)

(
SELECT
r.[Subscription.SubscriberId],
r.[Subscription.DeviceName],
r.[Subscription.SubscriberLocale],
r.[Input.SomeData]
FROM [NS_MyAppApplication].MyAppRule AS r

)
Stored Procedure Name: [NS_MyAppApplication].[NSFire3]

SqlServerError:
Error Number: 0
Source: .Net SqlClient Data Provider
Number: 0
State: 0
Class: 11
Message: A severe error occurred on the current command. The results, if any, should be discarded.
Procedure:
Line Number: 0

Error Number: 1
Source: .Net SqlClient Data Provider
Number: 0
State: 0
Class: 20
Message: A severe error occurred on the current command. The results, if any, should be discarded.
Procedure:
Line Number: 0

Description: A severe error occurred on the current command. The results, if any, should be discarded.
A severe error occurred on the current command. The results, if any, should be discarded.
InstanceName: MyAppInstance
ApplicationName: MyApp
Component: Generator
Thread: 4

--

Notification Services performed a quantum status update.
EventParameters:
Application Name: MyApp
Quantum ID: 4513
Status Code: 128
Quantum Status Code: 135

InstanceName: MyAppInstance
ApplicationName: MyApp
Component: Generator
Thread: 4

--

A user request from the session with SPID 57 generated a fatal exception. SQL Server is terminating this session.

--

The generator has started firing a rule.
EventParameters:
Application Name: MyApp
Quantum ID: 4513
Rule Firing ID: 17
Rule Name: MyAppRule
Notification Throttle: 1000

InstanceName: MyAppInstance
ApplicationName: MyApp
Component: Generator
Thread: 4

I have been banging my head with this one. I tried creating the NS app from scracth. I managed to get it working again with <Action> element, using STMP notifications and XsltFormatter. After that I modified to solution, taking example from Shyams books userdefinedlogic sample. Got everything up and running, but when rule starts firing same thing happens again.

After that, I disabled the generator and did the debugging procedures. All went fine up to
NPPrepareRuleFiring. When I executed NSExecuteRuleFiring, bang! Fatal exception.. no additional information, sigh.

What I was wondering was that in the preparerulefiring resultset I got EventBatchId as null. Is this correct in this scenario?|||Hi,
have the same problem you have... did you find an answer?

Thanks

Ricardo Carvalho|||Have not had any luck with this. As a workaround I am using <action> element instead of <conditionaction>. I don't like it, but at the moment I have no other solution.

Fatal exception while firing a rule

Hi,

I am having a problem when moving our NS application from dev environment to testing environment. What happens, is that when the rule is fired, a fatal exception is generated.

Any hints how I can start hunting down what the source of the problem is. The thing is, this works in dev environment, but not in test. Further, if I try to execute the stored proc manually which fails (NS_MyAppApplication].[NSFire3]) I get the same error:A user request from the session with SPID 63 generated a fatal exception. SQL Server is terminating this session.

Both dev and test environments use same ADF and ICF files. The ADF file is pretty much like in the InventoryTracker sample, using ConditionAction element like this:

<ConditionAction>
<SqlLogin>NSRulesEvaluator</SqlLogin>
<SqlUser>NSRulesEvaluator</SqlUser>
<InputName>InventoryTrackerEvents</InputName>
<InputSchema>NS_InventoryTrackerApplication</InputSchema>
<SqlExpression>

INSERT INTO [NS_InventoryTrackerApplication].[InventoryTrackerNotifications]
(
[SubscriberId],
[DeviceName],
[SubscriberLocale],
[ProductId],
[ProductName],
[ProductNumber],
[Quantity],
[LocationName]
)

(
SELECT
r.[Subscription.SubscriberId],
r.[Subscription.DeviceName],
r.[Subscription.SubscriberLocale],
r.[Input.ProductId],
r.[Input.ProductName],
r.[Input.ProductNumber],
r.[Input.Quantity],
r.[Input.LocationName]

FROM [NS_InventoryTrackerApplication].InventoryTrackerRule AS r
)
</SqlExpression>
</ConditionAction>

I tried changing ADF to little simple version, using action element instead of conditionaction. This time I got it working (and before that normal error messages and not just a stack dump).

Any hints how I can find out what is the problem here, or am I possibly missing something totally?

//sami

Both servers are as below:

Microsoft SQL Server Management Studio 9.00.2047.00
Microsoft Analysis Services Client Tools 2005.090.2047.00
Microsoft Data Access Components (MDAC) 2000.086.1830.00 (srv03_sp1_rtm.050324-1447)
Microsoft MSXML 2.6 3.0 6.0
Microsoft Internet Explorer 6.0.3790.1830
Microsoft .NET Framework 2.0.50727.42
Operating System 5.2.3790

These are entries from application log (in reverse order):

--

Description: The running of the rule failed. Please check the rule.
EventParameters:
Application Name: MyApp
Quantum ID: 4513
Rule Firing ID: 17
Rule Name: MyAppRule
Notification Throttle: 1000
Event Class ID: 1
Subscription Class ID: 1
Rule ID: 3
Rule Action: INSERT INTO [NS_MyAppApplication].[MyAppNotifications]
(
[SubscriberId],
[DeviceName],
[SubscriberLocale],
[SomeData]
)

(
SELECT
r.[Subscription.SubscriberId],
r.[Subscription.DeviceName],
r.[Subscription.SubscriberLocale],
r.[Input.SomeData]
FROM [NS_MyAppApplication].MyAppRule AS r

)
Stored Procedure Name: [NS_MyAppApplication].[NSFire3]

SqlServerError:
Error Number: 0
Source: .Net SqlClient Data Provider
Number: 0
State: 0
Class: 11
Message: A severe error occurred on the current command. The results, if any, should be discarded.
Procedure:
Line Number: 0

Error Number: 1
Source: .Net SqlClient Data Provider
Number: 0
State: 0
Class: 20
Message: A severe error occurred on the current command. The results, if any, should be discarded.
Procedure:
Line Number: 0

Description: A severe error occurred on the current command. The results, if any, should be discarded.
A severe error occurred on the current command. The results, if any, should be discarded.
InstanceName: MyAppInstance
ApplicationName: MyApp
Component: Generator
Thread: 4

--

Notification Services performed a quantum status update.
EventParameters:
Application Name: MyApp
Quantum ID: 4513
Status Code: 128
Quantum Status Code: 135

InstanceName: MyAppInstance
ApplicationName: MyApp
Component: Generator
Thread: 4

--

A user request from the session with SPID 57 generated a fatal exception. SQL Server is terminating this session.

--

The generator has started firing a rule.
EventParameters:
Application Name: MyApp
Quantum ID: 4513
Rule Firing ID: 17
Rule Name: MyAppRule
Notification Throttle: 1000

InstanceName: MyAppInstance
ApplicationName: MyApp
Component: Generator
Thread: 4

I have been banging my head with this one. I tried creating the NS app from scracth. I managed to get it working again with <Action> element, using STMP notifications and XsltFormatter. After that I modified to solution, taking example from Shyams books userdefinedlogic sample. Got everything up and running, but when rule starts firing same thing happens again.

After that, I disabled the generator and did the debugging procedures. All went fine up to
NPPrepareRuleFiring. When I executed NSExecuteRuleFiring, bang! Fatal exception.. no additional information, sigh.

What I was wondering was that in the preparerulefiring resultset I got EventBatchId as null. Is this correct in this scenario?|||Hi,
have the same problem you have... did you find an answer?

Thanks

Ricardo Carvalho
|||Have not had any luck with this. As a workaround I am using <action> element instead of <conditionaction>. I don't like it, but at the moment I have no other solution.

Fatal exception while firing a rule

Hi,

I am having a problem when moving our NS application from dev environment to testing environment. What happens, is that when the rule is fired, a fatal exception is generated.

Any hints how I can start hunting down what the source of the problem is. The thing is, this works in dev environment, but not in test. Further, if I try to execute the stored proc manually which fails (NS_MyAppApplication].[NSFire3]) I get the same error: A user request from the session with SPID 63 generated a fatal exception. SQL Server is terminating this session.

Both dev and test environments use same ADF and ICF files. The ADF file is pretty much like in the InventoryTracker sample, using ConditionAction element like this:

<ConditionAction>
<SqlLogin>NSRulesEvaluator</SqlLogin>
<SqlUser>NSRulesEvaluator</SqlUser>
<InputName>InventoryTrackerEvents</InputName>
<InputSchema>NS_InventoryTrackerApplication</InputSchema>
<SqlExpression>

INSERT INTO [NS_InventoryTrackerApplication].[InventoryTrackerNotifications]
(
[SubscriberId],
[DeviceName],
[SubscriberLocale],
[ProductId],
[ProductName],
[ProductNumber],
[Quantity],
[LocationName]
)

(
SELECT
r.[Subscription.SubscriberId],
r.[Subscription.DeviceName],
r.[Subscription.SubscriberLocale],
r.[Input.ProductId],
r.[Input.ProductName],
r.[Input.ProductNumber],
r.[Input.Quantity],
r.[Input.LocationName]

FROM [NS_InventoryTrackerApplication].InventoryTrackerRule AS r
)
</SqlExpression>
</ConditionAction>

I tried changing ADF to little simple version, using action element instead of conditionaction. This time I got it working (and before that normal error messages and not just a stack dump).

Any hints how I can find out what is the problem here, or am I possibly missing something totally?

//sami

Both servers are as below:

Microsoft SQL Server Management Studio 9.00.2047.00
Microsoft Analysis Services Client Tools 2005.090.2047.00
Microsoft Data Access Components (MDAC) 2000.086.1830.00 (srv03_sp1_rtm.050324-1447)
Microsoft MSXML 2.6 3.0 6.0
Microsoft Internet Explorer 6.0.3790.1830
Microsoft .NET Framework 2.0.50727.42
Operating System 5.2.3790

These are entries from application log (in reverse order):

--

Description: The running of the rule failed. Please check the rule.
EventParameters:
Application Name: MyApp
Quantum ID: 4513
Rule Firing ID: 17
Rule Name: MyAppRule
Notification Throttle: 1000
Event Class ID: 1
Subscription Class ID: 1
Rule ID: 3
Rule Action: INSERT INTO [NS_MyAppApplication].[MyAppNotifications]
(
[SubscriberId],
[DeviceName],
[SubscriberLocale],
[SomeData]
)

(
SELECT
r.[Subscription.SubscriberId],
r.[Subscription.DeviceName],
r.[Subscription.SubscriberLocale],
r.[Input.SomeData]
FROM [NS_MyAppApplication].MyAppRule AS r

)
Stored Procedure Name: [NS_MyAppApplication].[NSFire3]

SqlServerError:
Error Number: 0
Source: .Net SqlClient Data Provider
Number: 0
State: 0
Class: 11
Message: A severe error occurred on the current command. The results, if any, should be discarded.
Procedure:
Line Number: 0

Error Number: 1
Source: .Net SqlClient Data Provider
Number: 0
State: 0
Class: 20
Message: A severe error occurred on the current command. The results, if any, should be discarded.
Procedure:
Line Number: 0

Description: A severe error occurred on the current command. The results, if any, should be discarded.
A severe error occurred on the current command. The results, if any, should be discarded.
InstanceName: MyAppInstance
ApplicationName: MyApp
Component: Generator
Thread: 4

--

Notification Services performed a quantum status update.
EventParameters:
Application Name: MyApp
Quantum ID: 4513
Status Code: 128
Quantum Status Code: 135

InstanceName: MyAppInstance
ApplicationName: MyApp
Component: Generator
Thread: 4

--

A user request from the session with SPID 57 generated a fatal exception. SQL Server is terminating this session.

--

The generator has started firing a rule.
EventParameters:
Application Name: MyApp
Quantum ID: 4513
Rule Firing ID: 17
Rule Name: MyAppRule
Notification Throttle: 1000

InstanceName: MyAppInstance
ApplicationName: MyApp
Component: Generator
Thread: 4

I have been banging my head with this one. I tried creating the NS app from scracth. I managed to get it working again with <Action> element, using STMP notifications and XsltFormatter. After that I modified to solution, taking example from Shyams books userdefinedlogic sample. Got everything up and running, but when rule starts firing same thing happens again.

After that, I disabled the generator and did the debugging procedures. All went fine up to
NPPrepareRuleFiring. When I executed NSExecuteRuleFiring, bang! Fatal exception.. no additional information, sigh.

What I was wondering was that in the preparerulefiring resultset I got EventBatchId as null. Is this correct in this scenario?|||Hi,
have the same problem you have... did you find an answer?

Thanks

Ricardo Carvalho|||Have not had any luck with this. As a workaround I am using <action> element instead of <conditionaction>. I don't like it, but at the moment I have no other solution.

Fatal Exception in SQL Server

Hello,
We got a SQL Server (no SP) running on Win 2k SP4. Recently been getting
this error message in event viewer and at the same time the program that
access SQL Server crashes.
Error: 0, Severity: 19, State: 0
SqlDumpExceptionHandler: Process 64 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
Does anyone have any idea what it is please. Thanks
Andrew
> We got a SQL Server (no SP) running on Win 2k SP4.
If this is SQL2000, apply SQL2000 sevice pack 4 + AWE memory hotfix first.
If this SQL2005, open a support case with Microsoft. But I'd strongly
suggest that you run SQL2005 on Windows 2003 SP1.
Linchi
"Huy (Andrew) V Nguyen" <andrew.nv@.gmail.com> wrote in message
news:%234ZSg%23cLGHA.3756@.TK2MSFTNGP10.phx.gbl...
> Hello,
> We got a SQL Server (no SP) running on Win 2k SP4. Recently been getting
> this error message in event viewer and at the same time the program that
> access SQL Server crashes.
> Error: 0, Severity: 19, State: 0
> SqlDumpExceptionHandler: Process 64 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> Does anyone have any idea what it is please. Thanks
> Andrew
|||Thank you for your reply. I already applied SP4 still the same message.
Where can I obtain AWE hotfix please.
Andrew
Linchi Shea wrote:
> If this is SQL2000, apply SQL2000 sevice pack 4 + AWE memory hotfix first.
> If this SQL2005, open a support case with Microsoft. But I'd strongly
> suggest that you run SQL2005 on Windows 2003 SP1.
> Linchi
> "Huy (Andrew) V Nguyen" <andrew.nv@.gmail.com> wrote in message
> news:%234ZSg%23cLGHA.3756@.TK2MSFTNGP10.phx.gbl...
>
|||You can get the AWE fix here :
http://www.microsoft.com/downloads/d...displaylang=en
But you will need to log a case with Microsoft CSS , because the error you
posted is not sufficient enough , we need at least the stack output from the
AV , and if there was any mini dump created in the log folder during this
time...
So as linchi said please log a case with Microsoft CSS for speedy resolution
HTH
"Huy (Andrew) V Nguyen" <andrew.nv@.gmail.com> wrote in message
news:uVHDk9cMGHA.3264@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> Thank you for your reply. I already applied SP4 still the same message.
> Where can I obtain AWE hotfix please.
> Andrew
> Linchi Shea wrote:

Fatal Exception in SQL Server

Hello,
We got a SQL Server (no SP) running on Win 2k SP4. Recently been getting
this error message in event viewer and at the same time the program that
access SQL Server crashes.
Error: 0, Severity: 19, State: 0
SqlDumpExceptionHandler: Process 64 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
Does anyone have any idea what it is please. Thanks
Andrew> We got a SQL Server (no SP) running on Win 2k SP4.
If this is SQL2000, apply SQL2000 sevice pack 4 + AWE memory hotfix first.
If this SQL2005, open a support case with Microsoft. But I'd strongly
suggest that you run SQL2005 on Windows 2003 SP1.
Linchi
"Huy (Andrew) V Nguyen" <andrew.nv@.gmail.com> wrote in message
news:%234ZSg%23cLGHA.3756@.TK2MSFTNGP10.phx.gbl...
> Hello,
> We got a SQL Server (no SP) running on Win 2k SP4. Recently been getting
> this error message in event viewer and at the same time the program that
> access SQL Server crashes.
> Error: 0, Severity: 19, State: 0
> SqlDumpExceptionHandler: Process 64 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> Does anyone have any idea what it is please. Thanks
> Andrew|||Thank you for your reply. I already applied SP4 still the same message.
Where can I obtain AWE hotfix please.
Andrew
Linchi Shea wrote:
> If this is SQL2000, apply SQL2000 sevice pack 4 + AWE memory hotfix first.
> If this SQL2005, open a support case with Microsoft. But I'd strongly
> suggest that you run SQL2005 on Windows 2003 SP1.
> Linchi
> "Huy (Andrew) V Nguyen" <andrew.nv@.gmail.com> wrote in message
> news:%234ZSg%23cLGHA.3756@.TK2MSFTNGP10.phx.gbl...
>|||You can get the AWE fix here :
http://www.microsoft.com/downloads/...&displaylang=en
But you will need to log a case with Microsoft CSS , because the error you
posted is not sufficient enough , we need at least the stack output from the
AV , and if there was any mini dump created in the log folder during this
time...
So as linchi said please log a case with Microsoft CSS for speedy resolution
HTH
"Huy (Andrew) V Nguyen" <andrew.nv@.gmail.com> wrote in message
news:uVHDk9cMGHA.3264@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> Thank you for your reply. I already applied SP4 still the same message.
> Where can I obtain AWE hotfix please.
> Andrew
> Linchi Shea wrote:

Fatal Exception in SQL Server

Hello,
We got a SQL Server (no SP) running on Win 2k SP4. Recently been getting
this error message in event viewer and at the same time the program that
access SQL Server crashes.
Error: 0, Severity: 19, State: 0
SqlDumpExceptionHandler: Process 64 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
Does anyone have any idea what it is please. Thanks
Andrew> We got a SQL Server (no SP) running on Win 2k SP4.
If this is SQL2000, apply SQL2000 sevice pack 4 + AWE memory hotfix first.
If this SQL2005, open a support case with Microsoft. But I'd strongly
suggest that you run SQL2005 on Windows 2003 SP1.
Linchi
"Huy (Andrew) V Nguyen" <andrew.nv@.gmail.com> wrote in message
news:%234ZSg%23cLGHA.3756@.TK2MSFTNGP10.phx.gbl...
> Hello,
> We got a SQL Server (no SP) running on Win 2k SP4. Recently been getting
> this error message in event viewer and at the same time the program that
> access SQL Server crashes.
> Error: 0, Severity: 19, State: 0
> SqlDumpExceptionHandler: Process 64 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> Does anyone have any idea what it is please. Thanks
> Andrew|||Thank you for your reply. I already applied SP4 still the same message.
Where can I obtain AWE hotfix please.
Andrew
Linchi Shea wrote:
>> We got a SQL Server (no SP) running on Win 2k SP4.
> If this is SQL2000, apply SQL2000 sevice pack 4 + AWE memory hotfix first.
> If this SQL2005, open a support case with Microsoft. But I'd strongly
> suggest that you run SQL2005 on Windows 2003 SP1.
> Linchi
> "Huy (Andrew) V Nguyen" <andrew.nv@.gmail.com> wrote in message
> news:%234ZSg%23cLGHA.3756@.TK2MSFTNGP10.phx.gbl...
>> Hello,
>> We got a SQL Server (no SP) running on Win 2k SP4. Recently been getting
>> this error message in event viewer and at the same time the program that
>> access SQL Server crashes.
>> Error: 0, Severity: 19, State: 0
>> SqlDumpExceptionHandler: Process 64 generated fatal exception c0000005
>> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
>> Does anyone have any idea what it is please. Thanks
>> Andrew
>|||You can get the AWE fix here :
http://www.microsoft.com/downloads/details.aspx?FamilyId=7C407047-3F1F-48B8-9E4C-DC32875E1961&displaylang=en
But you will need to log a case with Microsoft CSS , because the error you
posted is not sufficient enough , we need at least the stack output from the
AV , and if there was any mini dump created in the log folder during this
time...
So as linchi said please log a case with Microsoft CSS for speedy resolution
HTH
"Huy (Andrew) V Nguyen" <andrew.nv@.gmail.com> wrote in message
news:uVHDk9cMGHA.3264@.TK2MSFTNGP11.phx.gbl...
> Thank you for your reply. I already applied SP4 still the same message.
> Where can I obtain AWE hotfix please.
> Andrew
> Linchi Shea wrote:
>> We got a SQL Server (no SP) running on Win 2k SP4.
>> If this is SQL2000, apply SQL2000 sevice pack 4 + AWE memory hotfix
>> first. If this SQL2005, open a support case with Microsoft. But I'd
>> strongly suggest that you run SQL2005 on Windows 2003 SP1.
>> Linchi
>> "Huy (Andrew) V Nguyen" <andrew.nv@.gmail.com> wrote in message
>> news:%234ZSg%23cLGHA.3756@.TK2MSFTNGP10.phx.gbl...
>> Hello,
>> We got a SQL Server (no SP) running on Win 2k SP4. Recently been getting
>> this error message in event viewer and at the same time the program that
>> access SQL Server crashes.
>> Error: 0, Severity: 19, State: 0
>> SqlDumpExceptionHandler: Process 64 generated fatal exception c0000005
>> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
>> Does anyone have any idea what it is please. Thanks
>> Andrew

Fatal exception error in MSSQL2005 SP1

The SQL server was terminated by exception acess violation at 10pm but before
that, I got some dump logs between 8pm to 10pm. Any idea? Thanks in advance
****************SQLDUMP.LOG**************
Memory
MemoryLoad = 90%
Total Physical = 2047 MB
Available Physical = 202 MB
Total Page File = 3947 MB
Available Page File = 2046 MB
Total Virtual = 2047 MB
Available Virtual = 93 MB
***Stack Dump being sent to C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\SQLDump0002.txt
SqlDumpExceptionHandler: Process 70 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is
terminating this process.
*
*******************************************************************************
*
* BEGIN STACK DUMP:
* 07/20/06 20:26:18 spid 70
*
*
* Exception Address = 7C8224B2 Module(ntdll+000224B2)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address 00000003
* Input Buffer 510 bytes -
* select a.currencycode, a.glmasterno, a.loanrefno, a.customerid, a.contra
* cttype, a.NewLoanBaln, a.TtlAccrueInt, substring(b.duedate,5,2) + '/' +
* substring(b.duedate,3,2) + '/' + substring(b.duedate,1,2) as DueDate_Fox
* Pro, b.* from eximbills_drawfm00 a right join (select I.*, P.schedulep
* rincipal as MerchedPrincipal, P.penaltotalinterest as Ppenality from (se
* lect * from (Select *, case when left(duedate,2) > '78' then '19' + d
* uedate else '20' + duedate end as modi_duedate from eximbills_drawfpsf w
* here right(kpsfkey,1) = 'I') z where modi_duedate between '20060603' a
* nd '20060803' and payoutflag <> 'Y') I join (select scheduleprincipal
* , kpsfkey, penaltotalinterest from (Select *, case when left(duedate,
* 2) > '78' then '19' + duedate else '20' + duedate end as modi_duedate fr
* om eximbills_drawfpsf where right(kpsfkey,1) = 'P') x where modi_dueda
* te between '20060603' and '20060803' and payoutflag <> 'Y') P on le
* ft(I.kpsfkey,25) = left(P.kpsfkey,25)) b on rtrim(ltrim(a.loanrefno)) =
* substring(b.kpsfkey,1,12) where rtrim(ltrim(a.recordtype)) <> '009' or
* der by loanrefno, kpsfkey
****************SQLDUMPER_ERRORLOG**************
07/20/06 20:24:58, ERROR , SQLDUMPER_UNKNOWN_APP.EXE, AdjustTokenPrivileges
() failed (00000514)
07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4
supplied
07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 1744
07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags = 0x0
07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x02A03570
07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr
= 0x00000000
07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x00000000
07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName = <NULL>
07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Dump is associated
with file C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\SQLDump0001.txt
07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not
used
07/20/06 20:25:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
07/20/06 20:25:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0001.mdmp
07/20/06 20:25:03, ACTION, sqlservr.exe, Watson Invoke: NoHi stephanie
Have you run this query successfully from query analyser? Have you run DBCC
CHECKDB and made sure that there are no hardware errors or other errors
reported in the event log?
You may want to look at re-writing the query. It is best not not use SELECT
* in production code as you will be selecting more than you are using. Post
DDL and sample data with the expected output from that data if you need help
re-writing this see http://www.aspfaq.com/etiquette.asp?id=5006
John
"stephanie" wrote:
> The SQL server was terminated by exception acess violation at 10pm but before
> that, I got some dump logs between 8pm to 10pm. Any idea? Thanks in advance
> ****************SQLDUMP.LOG**************
> Memory
> MemoryLoad = 90%
> Total Physical = 2047 MB
> Available Physical = 202 MB
> Total Page File = 3947 MB
> Available Page File = 2046 MB
> Total Virtual = 2047 MB
> Available Virtual = 93 MB
> ***Stack Dump being sent to C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\LOG\SQLDump0002.txt
> SqlDumpExceptionHandler: Process 70 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is
> terminating this process.
> *
> *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 07/20/06 20:26:18 spid 70
> *
> *
> * Exception Address = 7C8224B2 Module(ntdll+000224B2)
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred reading address 00000003
> * Input Buffer 510 bytes -
> * select a.currencycode, a.glmasterno, a.loanrefno, a.customerid, a.contra
> * cttype, a.NewLoanBaln, a.TtlAccrueInt, substring(b.duedate,5,2) + '/' +
> * substring(b.duedate,3,2) + '/' + substring(b.duedate,1,2) as DueDate_Fox
> * Pro, b.* from eximbills_drawfm00 a right join (select I.*, P.schedulep
> * rincipal as MerchedPrincipal, P.penaltotalinterest as Ppenality from (se
> * lect * from (Select *, case when left(duedate,2) > '78' then '19' + d
> * uedate else '20' + duedate end as modi_duedate from eximbills_drawfpsf w
> * here right(kpsfkey,1) = 'I') z where modi_duedate between '20060603' a
> * nd '20060803' and payoutflag <> 'Y') I join (select scheduleprincipal
> * , kpsfkey, penaltotalinterest from (Select *, case when left(duedate,
> * 2) > '78' then '19' + duedate else '20' + duedate end as modi_duedate fr
> * om eximbills_drawfpsf where right(kpsfkey,1) = 'P') x where modi_dueda
> * te between '20060603' and '20060803' and payoutflag <> 'Y') P on le
> * ft(I.kpsfkey,25) = left(P.kpsfkey,25)) b on rtrim(ltrim(a.loanrefno)) => * substring(b.kpsfkey,1,12) where rtrim(ltrim(a.recordtype)) <> '009' or
> * der by loanrefno, kpsfkey
>
> ****************SQLDUMPER_ERRORLOG**************
> 07/20/06 20:24:58, ERROR , SQLDUMPER_UNKNOWN_APP.EXE, AdjustTokenPrivileges
> () failed (00000514)
> 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4
> supplied
> 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 1744
> 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
> 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
> 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags = 0x0
> 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr => 0x02A03570
> 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
> 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr
> = 0x00000000
> 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr => 0x00000000
> 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
> 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName => <NULL>
> 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
> 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Dump is associated
> with file C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\LOG\SQLDump0001.txt
> 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not
> used
> 07/20/06 20:25:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
> 07/20/06 20:25:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed:
> C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0001.mdmp
> 07/20/06 20:25:03, ACTION, sqlservr.exe, Watson Invoke: No|||The query is working fine with running in query analyzer and there is no
error in dbcc checkdb. I found that there was an error in event viewer about
fatal exception with win32 or c++ when the MSSQL2005 stopped unexpectedly.
SQL Server is terminating because of fatal exception c0000005. This error
may be caused by an unhandled Win32 or C++ exception, or by an access
violation encountered during exception handling. Check the SQL error log for
any related stack dumps or messages. This exception forces SQL Server to
shutdown. To recover from this error, restart the server (unless SQLAgent is
configured to auto restart).
Thanks in advance!
"John Bell" wrote:
> Hi stephanie
> Have you run this query successfully from query analyser? Have you run DBCC
> CHECKDB and made sure that there are no hardware errors or other errors
> reported in the event log?
> You may want to look at re-writing the query. It is best not not use SELECT
> * in production code as you will be selecting more than you are using. Post
> DDL and sample data with the expected output from that data if you need help
> re-writing this see http://www.aspfaq.com/etiquette.asp?id=5006
> John
> "stephanie" wrote:
> > The SQL server was terminated by exception acess violation at 10pm but before
> > that, I got some dump logs between 8pm to 10pm. Any idea? Thanks in advance
> > ****************SQLDUMP.LOG**************
> > Memory
> > MemoryLoad = 90%
> > Total Physical = 2047 MB
> > Available Physical = 202 MB
> > Total Page File = 3947 MB
> > Available Page File = 2046 MB
> > Total Virtual = 2047 MB
> > Available Virtual = 93 MB
> > ***Stack Dump being sent to C:\Program Files\Microsoft SQL
> > Server\MSSQL.1\MSSQL\LOG\SQLDump0002.txt
> > SqlDumpExceptionHandler: Process 70 generated fatal exception c0000005
> > EXCEPTION_ACCESS_VIOLATION. SQL Server is
> > terminating this process.
> >
> > *
> > *******************************************************************************
> > *
> >
> > * BEGIN STACK DUMP:
> >
> > * 07/20/06 20:26:18 spid 70
> >
> > *
> >
> > *
> >
> > * Exception Address = 7C8224B2 Module(ntdll+000224B2)
> >
> > * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> >
> > * Access Violation occurred reading address 00000003
> >
> > * Input Buffer 510 bytes -
> >
> > * select a.currencycode, a.glmasterno, a.loanrefno, a.customerid, a.contra
> >
> > * cttype, a.NewLoanBaln, a.TtlAccrueInt, substring(b.duedate,5,2) + '/' +
> >
> > * substring(b.duedate,3,2) + '/' + substring(b.duedate,1,2) as DueDate_Fox
> >
> > * Pro, b.* from eximbills_drawfm00 a right join (select I.*, P.schedulep
> >
> > * rincipal as MerchedPrincipal, P.penaltotalinterest as Ppenality from (se
> >
> > * lect * from (Select *, case when left(duedate,2) > '78' then '19' + d
> >
> > * uedate else '20' + duedate end as modi_duedate from eximbills_drawfpsf w
> >
> > * here right(kpsfkey,1) = 'I') z where modi_duedate between '20060603' a
> >
> > * nd '20060803' and payoutflag <> 'Y') I join (select scheduleprincipal
> >
> > * , kpsfkey, penaltotalinterest from (Select *, case when left(duedate,
> >
> > * 2) > '78' then '19' + duedate else '20' + duedate end as modi_duedate fr
> >
> > * om eximbills_drawfpsf where right(kpsfkey,1) = 'P') x where modi_dueda
> >
> > * te between '20060603' and '20060803' and payoutflag <> 'Y') P on le
> >
> > * ft(I.kpsfkey,25) = left(P.kpsfkey,25)) b on rtrim(ltrim(a.loanrefno)) => >
> > * substring(b.kpsfkey,1,12) where rtrim(ltrim(a.recordtype)) <> '009' or
> >
> > * der by loanrefno, kpsfkey
> >
> >
> > ****************SQLDUMPER_ERRORLOG**************
> > 07/20/06 20:24:58, ERROR , SQLDUMPER_UNKNOWN_APP.EXE, AdjustTokenPrivileges
> > () failed (00000514)
> > 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4
> > supplied
> > 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 1744
> > 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
> > 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
> > 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags = 0x0
> > 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr => > 0x02A03570
> > 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
> > 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr
> > = 0x00000000
> > 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr => > 0x00000000
> > 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
> > 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName => > <NULL>
> > 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
> > 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Dump is associated
> > with file C:\Program Files\Microsoft SQL
> > Server\MSSQL.1\MSSQL\LOG\SQLDump0001.txt
> > 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not
> > used
> > 07/20/06 20:25:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
> > 07/20/06 20:25:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed:
> > C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0001.mdmp
> > 07/20/06 20:25:03, ACTION, sqlservr.exe, Watson Invoke: No|||Hi Stephanie
There are a couple of issues logged at:
https://connect.microsoft.com/SQLServer/feedback/SearchResults.aspx?SearchQuery=c0000005
they mainly seem to be the 64 bit version. You could try the post SP1 hotfix
on a test server http://support.microsoft.com/Kb/918222 is publically
available and there are others available from PSS see
http://www.sqlsecurity.com/FAQs/SQLServerVersionDatabase/tabid/63/Default.aspx
I think the issue may be related to the complexity of the query, so you may
want to try and re-write it or reduce it to find the point when it fails.
You may also want to raise a call with PSS and pass on any dump files that
you have.
John
"stephanie" wrote:
> The query is working fine with running in query analyzer and there is no
> error in dbcc checkdb. I found that there was an error in event viewer about
> fatal exception with win32 or c++ when the MSSQL2005 stopped unexpectedly.
> SQL Server is terminating because of fatal exception c0000005. This error
> may be caused by an unhandled Win32 or C++ exception, or by an access
> violation encountered during exception handling. Check the SQL error log for
> any related stack dumps or messages. This exception forces SQL Server to
> shutdown. To recover from this error, restart the server (unless SQLAgent is
> configured to auto restart).
>
> Thanks in advance!
> "John Bell" wrote:
> > Hi stephanie
> >
> > Have you run this query successfully from query analyser? Have you run DBCC
> > CHECKDB and made sure that there are no hardware errors or other errors
> > reported in the event log?
> >
> > You may want to look at re-writing the query. It is best not not use SELECT
> > * in production code as you will be selecting more than you are using. Post
> > DDL and sample data with the expected output from that data if you need help
> > re-writing this see http://www.aspfaq.com/etiquette.asp?id=5006
> >
> > John
> >
> > "stephanie" wrote:
> >
> > > The SQL server was terminated by exception acess violation at 10pm but before
> > > that, I got some dump logs between 8pm to 10pm. Any idea? Thanks in advance
> > > ****************SQLDUMP.LOG**************
> > > Memory
> > > MemoryLoad = 90%
> > > Total Physical = 2047 MB
> > > Available Physical = 202 MB
> > > Total Page File = 3947 MB
> > > Available Page File = 2046 MB
> > > Total Virtual = 2047 MB
> > > Available Virtual = 93 MB
> > > ***Stack Dump being sent to C:\Program Files\Microsoft SQL
> > > Server\MSSQL.1\MSSQL\LOG\SQLDump0002.txt
> > > SqlDumpExceptionHandler: Process 70 generated fatal exception c0000005
> > > EXCEPTION_ACCESS_VIOLATION. SQL Server is
> > > terminating this process.
> > >
> > > *
> > > *******************************************************************************
> > > *
> > >
> > > * BEGIN STACK DUMP:
> > >
> > > * 07/20/06 20:26:18 spid 70
> > >
> > > *
> > >
> > > *
> > >
> > > * Exception Address = 7C8224B2 Module(ntdll+000224B2)
> > >
> > > * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> > >
> > > * Access Violation occurred reading address 00000003
> > >
> > > * Input Buffer 510 bytes -
> > >
> > > * select a.currencycode, a.glmasterno, a.loanrefno, a.customerid, a.contra
> > >
> > > * cttype, a.NewLoanBaln, a.TtlAccrueInt, substring(b.duedate,5,2) + '/' +
> > >
> > > * substring(b.duedate,3,2) + '/' + substring(b.duedate,1,2) as DueDate_Fox
> > >
> > > * Pro, b.* from eximbills_drawfm00 a right join (select I.*, P.schedulep
> > >
> > > * rincipal as MerchedPrincipal, P.penaltotalinterest as Ppenality from (se
> > >
> > > * lect * from (Select *, case when left(duedate,2) > '78' then '19' + d
> > >
> > > * uedate else '20' + duedate end as modi_duedate from eximbills_drawfpsf w
> > >
> > > * here right(kpsfkey,1) = 'I') z where modi_duedate between '20060603' a
> > >
> > > * nd '20060803' and payoutflag <> 'Y') I join (select scheduleprincipal
> > >
> > > * , kpsfkey, penaltotalinterest from (Select *, case when left(duedate,
> > >
> > > * 2) > '78' then '19' + duedate else '20' + duedate end as modi_duedate fr
> > >
> > > * om eximbills_drawfpsf where right(kpsfkey,1) = 'P') x where modi_dueda
> > >
> > > * te between '20060603' and '20060803' and payoutflag <> 'Y') P on le
> > >
> > > * ft(I.kpsfkey,25) = left(P.kpsfkey,25)) b on rtrim(ltrim(a.loanrefno)) => > >
> > > * substring(b.kpsfkey,1,12) where rtrim(ltrim(a.recordtype)) <> '009' or
> > >
> > > * der by loanrefno, kpsfkey
> > >
> > >
> > > ****************SQLDUMPER_ERRORLOG**************
> > > 07/20/06 20:24:58, ERROR , SQLDUMPER_UNKNOWN_APP.EXE, AdjustTokenPrivileges
> > > () failed (00000514)
> > > 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4
> > > supplied
> > > 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 1744
> > > 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
> > > 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
> > > 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags = 0x0
> > > 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr => > > 0x02A03570
> > > 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
> > > 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr
> > > = 0x00000000
> > > 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr => > > 0x00000000
> > > 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
> > > 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName => > > <NULL>
> > > 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
> > > 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Dump is associated
> > > with file C:\Program Files\Microsoft SQL
> > > Server\MSSQL.1\MSSQL\LOG\SQLDump0001.txt
> > > 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not
> > > used
> > > 07/20/06 20:25:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
> > > 07/20/06 20:25:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed:
> > > C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0001.mdmp
> > > 07/20/06 20:25:03, ACTION, sqlservr.exe, Watson Invoke: Nosql

Fatal exception error in MSSQL2005 SP1

The SQL server was terminated by exception acess violation at 10pm but befor
e
that, I got some dump logs between 8pm to 10pm. Any idea? Thanks in advanc
e
****************SQLDUMP.LOG**************
Memory
MemoryLoad = 90%
Total Physical = 2047 MB
Available Physical = 202 MB
Total Page File = 3947 MB
Available Page File = 2046 MB
Total Virtual = 2047 MB
Available Virtual = 93 MB
***Stack Dump being sent to C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\SQLDump0002.txt
SqlDumpExceptionHandler: Process 70 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is
terminating this process.
*
****************************************
************************************
***
*
* BEGIN STACK DUMP:
* 07/20/06 20:26:18 spid 70
*
*
* Exception Address = 7C8224B2 Module(ntdll+000224B2)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address 00000003
* Input Buffer 510 bytes -
* select a.currencycode, a.glmasterno, a.loanrefno, a.customerid, a.contra
* cttype, a.NewLoanBaln, a.TtlAccrueInt, substring(b.duedate,5,2) + '/' +
* substring(b.duedate,3,2) + '/' + substring(b.duedate,1,2) as DueDate_Fox
* Pro, b.* from eximbills_drawfm00 a right join (select I.*, P.schedulep
* rincipal as MerchedPrincipal, P.penaltotalinterest as Ppenality from (se
* lect * from (Select *, case when left(duedate,2) > '78' then '19' + d
* uedate else '20' + duedate end as modi_duedate from eximbills_drawfpsf w
* here right(kpsfkey,1) = 'I') z where modi_duedate between '20060603' a
* nd '20060803' and payoutflag <> 'Y') I join (select scheduleprincipal
* , kpsfkey, penaltotalinterest from (Select *, case when left(duedate,
* 2) > '78' then '19' + duedate else '20' + duedate end as modi_duedate fr
* om eximbills_drawfpsf where right(kpsfkey,1) = 'P') x where modi_dueda
* te between '20060603' and '20060803' and payoutflag <> 'Y') P on le
* ft(I.kpsfkey,25) = left(P.kpsfkey,25)) b on rtrim(ltrim(a.loanrefno)) =
* substring(b.kpsfkey,1,12) where rtrim(ltrim(a.recordtype)) <> '009' or
* der by loanrefno, kpsfkey
****************SQLDUMPER_ERRORLOG******
********
07/20/06 20:24:58, ERROR , SQLDUMPER_UNKNOWN_APP.EXE, AdjustTokenPrivileges
() failed (00000514)
07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4
supplied
07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 1744
07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags = 0x
0
07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr =
0x02A03570
07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr
= 0x00000000
07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr =
0x00000000
07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName =
<NULL>
07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NUL
L>
07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Dump is associated
with file C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\SQLDump0001.txt
07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not
used
07/20/06 20:25:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not us
ed
07/20/06 20:25:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0001.mdmp
07/20/06 20:25:03, ACTION, sqlservr.exe, Watson Invoke: NoHi stephanie
Have you run this query successfully from query analyser? Have you run DBCC
CHECKDB and made sure that there are no hardware errors or other errors
reported in the event log?
You may want to look at re-writing the query. It is best not not use SELECT
* in production code as you will be selecting more than you are using. Post
DDL and sample data with the expected output from that data if you need help
re-writing this see http://www.aspfaq.com/etiquette.asp?id=5006
John
"stephanie" wrote:

> The SQL server was terminated by exception acess violation at 10pm but bef
ore
> that, I got some dump logs between 8pm to 10pm. Any idea? Thanks in adva
nce
> ****************SQLDUMP.LOG**************
> Memory
> MemoryLoad = 90%
> Total Physical = 2047 MB
> Available Physical = 202 MB
> Total Page File = 3947 MB
> Available Page File = 2046 MB
> Total Virtual = 2047 MB
> Available Virtual = 93 MB
> ***Stack Dump being sent to C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\LOG\SQLDump0002.txt
> SqlDumpExceptionHandler: Process 70 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is
> terminating this process.
> *
> ****************************************
**********************************
*****
> *
> * BEGIN STACK DUMP:
> * 07/20/06 20:26:18 spid 70
> *
> *
> * Exception Address = 7C8224B2 Module(ntdll+000224B2)
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred reading address 00000003
> * Input Buffer 510 bytes -
> * select a.currencycode, a.glmasterno, a.loanrefno, a.customerid, a.contr
a
> * cttype, a.NewLoanBaln, a.TtlAccrueInt, substring(b.duedate,5,2) + '/' +
> * substring(b.duedate,3,2) + '/' + substring(b.duedate,1,2) as DueDate_Fo
x
> * Pro, b.* from eximbills_drawfm00 a right join (select I.*, P.schedule
p
> * rincipal as MerchedPrincipal, P.penaltotalinterest as Ppenality from (s
e
> * lect * from (Select *, case when left(duedate,2) > '78' then '19' +
d
> * uedate else '20' + duedate end as modi_duedate from eximbills_drawfpsf
w
> * here right(kpsfkey,1) = 'I') z where modi_duedate between '20060603'
a
> * nd '20060803' and payoutflag <> 'Y') I join (select scheduleprincipa
l
> * , kpsfkey, penaltotalinterest from (Select *, case when left(duedate
,
> * 2) > '78' then '19' + duedate else '20' + duedate end as modi_duedate f
r
> * om eximbills_drawfpsf where right(kpsfkey,1) = 'P') x where modi_dued
a
> * te between '20060603' and '20060803' and payoutflag <> 'Y') P on l
e
> * ft(I.kpsfkey,25) = left(P.kpsfkey,25)) b on rtrim(ltrim(a.loanrefno)) =
> * substring(b.kpsfkey,1,12) where rtrim(ltrim(a.recordtype)) <> '009' o
r
> * der by loanrefno, kpsfkey
>
> ****************SQLDUMPER_ERRORLOG******
********
> 07/20/06 20:24:58, ERROR , SQLDUMPER_UNKNOWN_APP.EXE, AdjustTokenPrivilege
s
> () failed (00000514)
> 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4
> supplied
> 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 1744
> 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
> 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
> 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags =
0x0
> 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr =
> 0x02A03570
> 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
> 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordP
tr
> = 0x00000000
> 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr =
> 0x00000000
> 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NUL
L>
> 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName =
> <NULL>
> 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <N
ULL>
> 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Dump is associated
> with file C:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\LOG\SQLDump0001.txt
> 07/20/06 20:24:58, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not
> used
> 07/20/06 20:25:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not
used
> 07/20/06 20:25:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed:
> C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0001.mdmp
> 07/20/06 20:25:03, ACTION, sqlservr.exe, Watson Invoke: No|||The query is working fine with running in query analyzer and there is no
error in dbcc checkdb. I found that there was an error in event viewer about
fatal exception with win32 or c++ when the MSSQL2005 stopped unexpectedly.
SQL Server is terminating because of fatal exception c0000005. This error
may be caused by an unhandled Win32 or C++ exception, or by an access
violation encountered during exception handling. Check the SQL error log for
any related stack dumps or messages. This exception forces SQL Server to
shutdown. To recover from this error, restart the server (unless SQLAgent is
configured to auto restart).
Thanks in advance!
"John Bell" wrote:
[vbcol=seagreen]
> Hi stephanie
> Have you run this query successfully from query analyser? Have you run DBC
C
> CHECKDB and made sure that there are no hardware errors or other errors
> reported in the event log?
> You may want to look at re-writing the query. It is best not not use SELEC
T
> * in production code as you will be selecting more than you are using. Pos
t
> DDL and sample data with the expected output from that data if you need he
lp
> re-writing this see http://www.aspfaq.com/etiquette.asp?id=5006
> John
> "stephanie" wrote:
>|||Hi Stephanie
There are a couple of issues logged at:
https://connect.microsoft.com/SQLSe...0
000005
they mainly seem to be the 64 bit version. You could try the post SP1 hotfix
on a test server http://support.microsoft.com/Kb/918222 is publically
available and there are others available from PSS see
[url]http://www.sqlsecurity.com/FAQs/SQLServerVersionDatabase/tabid/63/Default.aspx[/ur
l]
I think the issue may be related to the complexity of the query, so you may
want to try and re-write it or reduce it to find the point when it fails.
You may also want to raise a call with PSS and pass on any dump files that
you have.
John
"stephanie" wrote:
[vbcol=seagreen]
> The query is working fine with running in query analyzer and there is no
> error in dbcc checkdb. I found that there was an error in event viewer abo
ut
> fatal exception with win32 or c++ when the MSSQL2005 stopped unexpectedly.
> SQL Server is terminating because of fatal exception c0000005. This error
> may be caused by an unhandled Win32 or C++ exception, or by an access
> violation encountered during exception handling. Check the SQL error log f
or
> any related stack dumps or messages. This exception forces SQL Server to
> shutdown. To recover from this error, restart the server (unless SQLAgent
is
> configured to auto restart).
>
> Thanks in advance!
> "John Bell" wrote:
>

Fatal exception error in mSSQL 2000 sp4

Hi all,

We have intermittent fatal exception error since MSSQL 2000 sp3. We have applied sp4 but the problem still can't be solved. Below is part the the SQLdump. Any advise on it? Thanks in advance!

BEGIN STACK DUMP:
* 05/13/06 11:26:08 spid 0
*
* Exception Address = 05EB8187 (vsnupr + 00021F7C Line 0+00000000)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address 000001F0
*
* MODULE BASE END SIZE
* sqlservr 00400000 00CBAFFF 008bb000
* Invalid Address 77F80000 77FFCFFF 0007d000
* ADVAPI32 7C2D0000 7C331FFF 00062000
* KERNEL32 7C570000 7C622FFF 000b3000
* RPCRT4 77D30000 77DA0FFF 00071000
* MSVCP71 7C080000 7C0FBFFF 0007c000
* MSVCR71 7D000000 7D057FFF 00058000
* opends60 41060000 41065FFF 00006000
* SHELL32 782F0000 78534FFF 00245000
* GDI32 77F40000 77F7AFFF 0003b000
* USER32 77E10000 77E6EFFF 0005f000
* SHLWAPI 63180000 631E8FFF 00069000
* msvcrt 78000000 78044FFF 00045000
* COMCTL32 71710000 71793FFF 00084000
* sqlsort 42AE0000 42B6FFFF 00090000
* ums 41070000 4107DFFF 0000e000
* IMM32 75E60000 75E79FFF 0001a000
* sqlevn70 41080000 4108AFFF 0000b000
* NETAPI32 02BF0000 02C3EFFF 0004f000
* Secur32 02C40000 02C4EFFF 0000f000
* NTDSAPI 02C50000 02C60FFF 00011000
* DNSAPI 02C70000 02C93FFF 00024000
* WSOCK32 02CA0000 02CA7FFF 00008000
* WS2_32 02CB0000 02CC3FFF 00014000
* WS2HELP 02CD0000 02CD7FFF 00008000
* WLDAP32 02CE0000 02D09FFF 0002a000
* NETRAP 02D10000 02D15FFF 00006000
* SAMLIB 02D20000 02D2EFFF 0000f000
* AUTHZ 02D80000 02D8FFFF 00010000
* ole32 02FA0000 0308EFFF 000ef000
* XOLEHLP 03090000 03097FFF 00008000
* MSDTCPRX 030A0000 03156FFF 000b7000
* MTXCLU 03160000 0316FFFF 00010000
* VERSION 03170000 03176FFF 00007000
* LZ32 03180000 03185FFF 00006000
* CLUSAPI 03190000 0319FFFF 00010000
* RESUTILS 031A0000 031ACFFF 0000d000
* USERENV 031B0000 03210FFF 00061000
* rnr20 03220000 0322BFFF 0000c000
* iphlpapi 03270000 03282FFF 00013000
* ICMP 03290000 03294FFF 00005000
* MPRAPI 032A0000 032B6FFF 00017000
* OLEAUT32 032C0000 0335AFFF 0009b000
* ACTIVEDS 03360000 0338EFFF 0002f000
* ADSLDPC 03390000 033B2FFF 00023000
* RTUTILS 033C0000 033CDFFF 0000e000
* SETUPAPI 033D0000 0345DFFF 0008e000
* RASAPI32 03460000 03492FFF 00033000
* RASMAN 034A0000 034B0FFF 00011000
* TAPI32 034C0000 034E1FFF 00022000
* DHCPCSVC 034F0000 03508FFF 00019000
* winrnr 039B0000 039B7FFF 00008000
* rasadhlp 039C0000 039C4FFF 00005000
* SSNETLIB 04090000 040A5FFF 00016000
* NTMARTA 040E0000 040FCFFF 0001d000
* WINSPOOL 04110000 0412DFFF 0001e000
* MPR 04170000 0417FFFF 00010000
* security 04430000 04433FFF 00004000
* msafd 04770000 0478DFFF 0001e000
* wshtcpip 047D0000 047D6FFF 00007000
* SSmsLPCn 048F0000 048F7FFF 00008000
* SSnmPN70 04930000 04936FFF 00007000
* mswsock 049D0000 049E1FFF 00012000
* kerberos 04A40000 04A75FFF 00036000
* CRYPTDLL 04A80000 04A8DFFF 0000e000
* MSASN1 04A90000 04A9FFFF 00010000
* rsabase 04DA0000 04DC2FFF 00023000
* CRYPT32 04DD0000 04E56FFF 00087000
* SQLFTQRY 05050000 05075FFF 00026000
* CLBCATQ 05080000 0510FFFF 00090000
* sqloledb 05220000 0529CFFF 0007d000
* MSDART 052C0000 052E3FFF 00024000
* comdlg32 052F0000 0532DFFF 0003e000
* MSDATL3 05330000 05344FFF 00015000
* msv1_0 055D0000 055F0FFF 00021000
* oledb32 05700000 0576FFFF 00070000
* OLEDB32R 05770000 05780FFF 00011000
* xpsqlbot 05790000 05795FFF 00006000
* xpstar 05B00000 05B4CFFF 0004d000
* SQLRESLD 05B50000 05B5BFFF 0000c000
* SQLSVC 05B60000 05B7AFFF 0001b000
* ODBC32 05B80000 05BB9FFF 0003a000
* odbcbcp 05BC0000 05BC5FFF 00006000
* W95SCM 05BD0000 05BDCFFF 0000d000
* SQLUNIRL 05BE0000 05C0CFFF 0002d000
* SHFOLDER 05C10000 05C17FFF 00008000
* odbcint 05D60000 05D76FFF 00017000
* NDDEAPI 05D80000 05D86FFF 00007000
* SQLSVC 05D90000 05D95FFF 00006000
* xpstar 05DA0000 05DA8FFF 00009000
* xplog70 05DC0000 05DCEFFF 0000f000
* xplog70 05DD0000 05DD4FFF 00005000
* msdaora 05DF0000 05E26FFF 00037000
* MSDAORAR 05E30000 05E33FFF 00004000
* ociw32 10000000 1000DFFF 0000e000
* ORA73 05E80000 05ED8FFF 00059000
* CORE35 05EE0000 05F0BFFF 0002c000
* NLSRTL32 05F10000 05F57FFF 00048000
* MSVCRT40 05F60000 05F74FFF 00015000
* MSVCIRT 05F80000 05F91FFF 00012000
* CORE35O 05FA0000 05FC5FFF 00026000
* SQLLib18 05FF0000 06007FFF 00018000
* KG73 06010000 0605AFFF 0004b000
* comsvcs 06060000 061CEFFF 0016f000
* TxfAux 061D0000 06233FFF 00064000
* NLNT 06400000 06419FFF 0001a000
* WINMM 06420000 0644FFFF 00030000
* nttnt 06540000 0654BFFF 0000c000
* msdasql 06730000 06779FFF 0004a000
* MSDASQLR 06780000 06783FFF 00004000
* vfpodbc 06790000 06883FFF 000f4000
* odbccp32 076D0000 076E9FFF 0001a000
* cwbodbc 07C70000 07CE5FFF 00076000
* CWBNL 07CF0000 07D09FFF 0001a000
* cwbrw 07D10000 07D42FFF 00033000
* CwbAb1 07D50000 07D56FFF 00007000
* CWBSV 07D60000 07D7EFFF 0001f000
* CwbCf 07D80000 07D9DFFF 0001e000
* CwbAdNrt 07DA0000 07DB3FFF 00014000
* CwbBb1 07DC0000 07DC8FFF 00009000
* CWBCFTFT 07DD0000 07DD7FFF 00008000
* CWBNL1 07DE0000 07DECFFF 0000d000
* CwbAb 07DF0000 07DFEFFF 0000f000
* CWBCF1 07E00000 07E06FFF 00007000
* CWBNLTRN 07E10000 07E16FFF 00007000
* CwbCo 07E20000 07E57FFF 00038000
* CwbAd 07E60000 07E6CFFF 0000d000
* CwbMsgbx 07E70000 07E7AFFF 0000b000
* CWBNLDLG 07E80000 07E86FFF 00007000
* cwbuireg 07E90000 07E97FFF 00008000
* CwbAd1 07EA0000 07EA7FFF 00008000
* CWBUNPLA 07EB0000 07EE1FFF 00032000
* cwbsof 07EF0000 07F25FFF 00036000
* CwbSy 07F30000 07F39FFF 0000a000
* CWBRC 07F40000 07F51FFF 00012000
* CwbBb 07F60000 07F68FFF 00009000
* CWBUNSSL 07F70000 07F7FFFF 00010000
* MFC42 07F80000 0807AFFF 000fb000
* cwbstp 08080000 08096FFF 00017000
* CWBMSGB 084C0000 084C3FFF 00004000
* cwbcomsg 084D0000 084D4FFF 00005000
* CWBSOMRI 084E0000 084EDFFF 0000e000
* CWBODDLG 084F0000 084F6FFF 00007000
* CWBODMSG 08500000 08505FFF 00006000
* SQLTNSNT 08750000 0877FFFF 00030000
* NSNT 08780000 0879FFFF 00020000
* nasnsnt 087A0000 087C3FFF 00024000
* ntnt 087D0000 087D9FFF 0000a000
* NCRNT 087E0000 08828FFF 00049000
* msadce 08840000 0888CFFF 0004d000
* msadcer 08890000 08894FFF 00005000
* odsole70 09110000 09120FFF 00011000
* MQOA 09270000 092A9FFF 0003a000
* MQRT 092B0000 092CDFFF 0001e000
* MQSec 092D0000 092E3FFF 00014000
* MQUtil 092F0000 0930EFFF 0001f000
* MQDSCli 09310000 09326FFF 00017000
* SQLSRV32 095C0000 09626FFF 00067000
* sqlsrv32 09630000 09645FFF 00016000
* Cwbnetnt 09660000 09666FFF 00007000
* sqlvdi 0A260000 0A26CFFF 0000d000
* adsldp 04720000 04741FFF 00022000
* adsmsext 09EC0000 09ED1FFF 00012000
* sqlmap70 05000000 0502CFFF 0002d000
* MAPI32 05E40000 05E60FFF 00021000
* MSMAPI32 0A320000 0A3E7FFF 000c8000
* GAPI32 0A3F0000 0A407FFF 00018000
* dbghelp 0B540000 0B63FFFF 00100000
*
* Edi: 00000000:
* Esi: 0536AB20: 05DF2B28 00000007 00000001 00001000 05381978 0B1DB
F08
* Eax: 000001F0:
* Ebx: 77E1A7BD: 53EC8B55 A1645756 00000018 F08BC933 0F0C4D39 00008
B85
* Ecx: 00003931:
* Edx: 0B503032: 00000000 00000000 00000000 00000000 00000000 00000
000
* Eip: 05EB8187:
* Ebp: 0B50F98C: 0B50F9B8 05EAFCE3 00000002 00000000 0536AB20 77E1A
7BD
* SegCs: 0000001B:
* EFlags: 00010206: 0057005C 004E0049 0054004E 0073005C 00730079 00650
074
* Esp: 0B50F97C: 00000000 0536AB20 77E1A7BD 000001F0 0B50F9B8 05EAF
CE3
* SegSs: 00000023:
* *****************************************************************************
**
* --
--
* Short Stack Dump
* 05EB8187 Module(ORA73+00038187) (vsnupr+00021F7C)
* 05EAFCE3 Module(ORA73+0002FCE3) (vsnupr+00019AD8)
* 05EC4499 Module(ORA73+00044499) (vsnupr+0002E28E)
* 05EAFB95 Module(ORA73+0002FB95) (vsnupr+0001998A)
* 05EA1959 Module(ORA73+00021959) (vsnupr+0000B74E)
* 05E920A9 Module(ORA73+000120A9) (upiosd+00000063)
* 05E8BA77 Module(ORA73+0000BA77) (oparse+0000007C)
* 10001D88 Module(ociw32+00001D88) (oparse+00000028)
* 05E0EC77 Module(msdaora+0001EC77) (DllRegisterServer+000017B5)
* 780085BC Module(msvcrt+000085BC) (endthreadex+000000BC)
* 7C57B388 Module(KERNEL32+0000B388) (lstrcmpiW+000000B7)
-
* Location : 05EB8187 Module(ORA73+00038187) (vsnupr+00021F7C)
* Return Addr: 05EAFCE3 Module(ORA73+0002FCE3) (vsnupr+00019AD8)
Frame : 0B50F98C
Parameters:
[1] 00000002:
[2] 00000000:
[3] 0536AB20: 05DF2B28 00000007 00000001 00001000 05381978 0B1DBF08
[4] 77E1A7BD: 53EC8B55 A1645756 00000018 F08BC933 0F0C4D39 00008B85
160 bytes of stack data from 0B50F8EC to 0B50F98C
0B50F8EC: 000B0CE8 0A9E7C98 00000104 08A60048 [.....|......H...]
0B50F8FC: 05490178 08A60048 05490178 08A60040 [x.I.H...x.I.@....]
0B50F90C: 000001B7 00000001 00000000 00000000 [................]
0B50F91C: 00000000 00000000 00000000 00000000 [................]
:::: 2 Duplicate lines detected
0B50F94C: 00000000 0A9E7854 0000001C 77F82A8C [....Tx.......*.w]
0B50F95C: 0A9E7860 00000005 77F82A8C 000B0000 [`x.......*.w....]
0B50F96C: 000B0778 00000005 001761A8 0A9E7838 [x........a..8x..]
0B50F97C: 00000000 0536AB20 77E1A7BD 000001F0 [.... .6....w....]

Hi Stephanie,

What OS are you running on (e.g. Windows Server 2003)?

Is the SQL Server configured for AWE and are you using the /PAE switch?
|||OS is Win2000 SP4 and awe is not enabled. Any advise? Thanks|||Hi Stephanie,

I once had a Win 2K SP4 server that spit out errors like the one you are seeing occasionally.

This server had multiple processors on it but the error seemed to go away after I turned down the degree of parallelism so that it was less than the # of processors on the server.

If you've got multiple processors on the server, you might want to consider doing the same thing (turning down the degree of parallelism) and see if that helps any.
|||

Hi Nate,

Thanks for your advise. we have already turn off the parallelism and use 1 processor only (there are 2 processors in the machine). And I just found that the /PAE is turned on in boot.ini. Probably, it is root cause... Many Thanks for your advise.

|||Ah OK....I've read before that /PAE can cause problems so hopefully turning it off would make things better.

Glad I could be of a little help

Fatal exception error in mSSQL 2000 sp3 and sp4

Hi all,
We have intermittent fatal exception error since MSSQL 2000 sp3a. We have
applied sp4 but the problem still can't be solved. Below is part the the
SQLdump. Any advise on it? Thanks in advance!
BEGIN STACK DUMP:
* 05/13/06 11:26:08 spid 0
*
* Exception Address = 05EB8187 (vsnupr + 00021F7C Line 0+00000000)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address 000001F0
*
* MODULE BASE END SIZE
* sqlservr 00400000 00CBAFFF 008bb000
* Invalid Address 77F80000 77FFCFFF 0007d000
* ADVAPI32 7C2D0000 7C331FFF 00062000
* KERNEL32 7C570000 7C622FFF 000b3000
* RPCRT4 77D30000 77DA0FFF 00071000
* MSVCP71 7C080000 7C0FBFFF 0007c000
* MSVCR71 7D000000 7D057FFF 00058000
* opends60 41060000 41065FFF 00006000
* SHELL32 782F0000 78534FFF 00245000
* GDI32 77F40000 77F7AFFF 0003b000
* USER32 77E10000 77E6EFFF 0005f000
* SHLWAPI 63180000 631E8FFF 00069000
* msvcrt 78000000 78044FFF 00045000
* COMCTL32 71710000 71793FFF 00084000
* sqlsort 42AE0000 42B6FFFF 00090000
* ums 41070000 4107DFFF 0000e000
* IMM32 75E60000 75E79FFF 0001a000
* sqlevn70 41080000 4108AFFF 0000b000
* NETAPI32 02BF0000 02C3EFFF 0004f000
* Secur32 02C40000 02C4EFFF 0000f000
* NTDSAPI 02C50000 02C60FFF 00011000
* DNSAPI 02C70000 02C93FFF 00024000
* WSOCK32 02CA0000 02CA7FFF 00008000
* WS2_32 02CB0000 02CC3FFF 00014000
* WS2HELP 02CD0000 02CD7FFF 00008000
* WLDAP32 02CE0000 02D09FFF 0002a000
* NETRAP 02D10000 02D15FFF 00006000
* SAMLIB 02D20000 02D2EFFF 0000f000
* AUTHZ 02D80000 02D8FFFF 00010000
* ole32 02FA0000 0308EFFF 000ef000
* XOLEHLP 03090000 03097FFF 00008000
* MSDTCPRX 030A0000 03156FFF 000b7000
* MTXCLU 03160000 0316FFFF 00010000
* VERSION 03170000 03176FFF 00007000
* LZ32 03180000 03185FFF 00006000
* CLUSAPI 03190000 0319FFFF 00010000
* RESUTILS 031A0000 031ACFFF 0000d000
* USERENV 031B0000 03210FFF 00061000
* rnr20 03220000 0322BFFF 0000c000
* iphlpapi 03270000 03282FFF 00013000
* ICMP 03290000 03294FFF 00005000
* MPRAPI 032A0000 032B6FFF 00017000
* OLEAUT32 032C0000 0335AFFF 0009b000
* ACTIVEDS 03360000 0338EFFF 0002f000
* ADSLDPC 03390000 033B2FFF 00023000
* RTUTILS 033C0000 033CDFFF 0000e000
* SETUPAPI 033D0000 0345DFFF 0008e000
* RASAPI32 03460000 03492FFF 00033000
* RASMAN 034A0000 034B0FFF 00011000
* TAPI32 034C0000 034E1FFF 00022000
* DHCPCSVC 034F0000 03508FFF 00019000
* winrnr 039B0000 039B7FFF 00008000
* rasadhlp 039C0000 039C4FFF 00005000
* SSNETLIB 04090000 040A5FFF 00016000
* NTMARTA 040E0000 040FCFFF 0001d000
* WINSPOOL 04110000 0412DFFF 0001e000
* MPR 04170000 0417FFFF 00010000
* security 04430000 04433FFF 00004000
* msafd 04770000 0478DFFF 0001e000
* wshtcpip 047D0000 047D6FFF 00007000
* SSmsLPCn 048F0000 048F7FFF 00008000
* SSnmPN70 04930000 04936FFF 00007000
* mswsock 049D0000 049E1FFF 00012000
* kerberos 04A40000 04A75FFF 00036000
* CRYPTDLL 04A80000 04A8DFFF 0000e000
* MSASN1 04A90000 04A9FFFF 00010000
* rsabase 04DA0000 04DC2FFF 00023000
* CRYPT32 04DD0000 04E56FFF 00087000
* SQLFTQRY 05050000 05075FFF 00026000
* CLBCATQ 05080000 0510FFFF 00090000
* sqloledb 05220000 0529CFFF 0007d000
* MSDART 052C0000 052E3FFF 00024000
* comdlg32 052F0000 0532DFFF 0003e000
* MSDATL3 05330000 05344FFF 00015000
* msv1_0 055D0000 055F0FFF 00021000
* oledb32 05700000 0576FFFF 00070000
* OLEDB32R 05770000 05780FFF 00011000
* xpsqlbot 05790000 05795FFF 00006000
* xpstar 05B00000 05B4CFFF 0004d000
* SQLRESLD 05B50000 05B5BFFF 0000c000
* SQLSVC 05B60000 05B7AFFF 0001b000
* ODBC32 05B80000 05BB9FFF 0003a000
* odbcbcp 05BC0000 05BC5FFF 00006000
* W95SCM 05BD0000 05BDCFFF 0000d000
* SQLUNIRL 05BE0000 05C0CFFF 0002d000
* SHFOLDER 05C10000 05C17FFF 00008000
* odbcint 05D60000 05D76FFF 00017000
* NDDEAPI 05D80000 05D86FFF 00007000
* SQLSVC 05D90000 05D95FFF 00006000
* xpstar 05DA0000 05DA8FFF 00009000
* xplog70 05DC0000 05DCEFFF 0000f000
* xplog70 05DD0000 05DD4FFF 00005000
* msdaora 05DF0000 05E26FFF 00037000
* MSDAORAR 05E30000 05E33FFF 00004000
* ociw32 10000000 1000DFFF 0000e000
* ORA73 05E80000 05ED8FFF 00059000
* CORE35 05EE0000 05F0BFFF 0002c000
* NLSRTL32 05F10000 05F57FFF 00048000
* MSVCRT40 05F60000 05F74FFF 00015000
* MSVCIRT 05F80000 05F91FFF 00012000
* CORE35O 05FA0000 05FC5FFF 00026000
* SQLLib18 05FF0000 06007FFF 00018000
* KG73 06010000 0605AFFF 0004b000
* comsvcs 06060000 061CEFFF 0016f000
* TxfAux 061D0000 06233FFF 00064000
* NLNT 06400000 06419FFF 0001a000
* WINMM 06420000 0644FFFF 00030000
* nttnt 06540000 0654BFFF 0000c000
* msdasql 06730000 06779FFF 0004a000
* MSDASQLR 06780000 06783FFF 00004000
* vfpodbc 06790000 06883FFF 000f4000
* odbccp32 076D0000 076E9FFF 0001a000
* cwbodbc 07C70000 07CE5FFF 00076000
* CWBNL 07CF0000 07D09FFF 0001a000
* cwbrw 07D10000 07D42FFF 00033000
* CwbAb1 07D50000 07D56FFF 00007000
* CWBSV 07D60000 07D7EFFF 0001f000
* CwbCf 07D80000 07D9DFFF 0001e000
* CwbAdNrt 07DA0000 07DB3FFF 00014000
* CwbBb1 07DC0000 07DC8FFF 00009000
* CWBCFTFT 07DD0000 07DD7FFF 00008000
* CWBNL1 07DE0000 07DECFFF 0000d000
* CwbAb 07DF0000 07DFEFFF 0000f000
* CWBCF1 07E00000 07E06FFF 00007000
* CWBNLTRN 07E10000 07E16FFF 00007000
* CwbCo 07E20000 07E57FFF 00038000
* CwbAd 07E60000 07E6CFFF 0000d000
* CwbMsgbx 07E70000 07E7AFFF 0000b000
* CWBNLDLG 07E80000 07E86FFF 00007000
* cwbuireg 07E90000 07E97FFF 00008000
* CwbAd1 07EA0000 07EA7FFF 00008000
* CWBUNPLA 07EB0000 07EE1FFF 00032000
* cwbsof 07EF0000 07F25FFF 00036000
* CwbSy 07F30000 07F39FFF 0000a000
* CWBRC 07F40000 07F51FFF 00012000
* CwbBb 07F60000 07F68FFF 00009000
* CWBUNSSL 07F70000 07F7FFFF 00010000
* MFC42 07F80000 0807AFFF 000fb000
* cwbstp 08080000 08096FFF 00017000
* CWBMSGB 084C0000 084C3FFF 00004000
* cwbcomsg 084D0000 084D4FFF 00005000
* CWBSOMRI 084E0000 084EDFFF 0000e000
* CWBODDLG 084F0000 084F6FFF 00007000
* CWBODMSG 08500000 08505FFF 00006000
* SQLTNSNT 08750000 0877FFFF 00030000
* NSNT 08780000 0879FFFF 00020000
* nasnsnt 087A0000 087C3FFF 00024000
* ntnt 087D0000 087D9FFF 0000a000
* NCRNT 087E0000 08828FFF 00049000
* msadce 08840000 0888CFFF 0004d000
* msadcer 08890000 08894FFF 00005000
* odsole70 09110000 09120FFF 00011000
* MQOA 09270000 092A9FFF 0003a000
* MQRT 092B0000 092CDFFF 0001e000
* MQSec 092D0000 092E3FFF 00014000
* MQUtil 092F0000 0930EFFF 0001f000
* MQDSCli 09310000 09326FFF 00017000
* SQLSRV32 095C0000 09626FFF 00067000
* sqlsrv32 09630000 09645FFF 00016000
* Cwbnetnt 09660000 09666FFF 00007000
* sqlvdi 0A260000 0A26CFFF 0000d000
* adsldp 04720000 04741FFF 00022000
* adsmsext 09EC0000 09ED1FFF 00012000
* sqlmap70 05000000 0502CFFF 0002d000
* MAPI32 05E40000 05E60FFF 00021000
* MSMAPI32 0A320000 0A3E7FFF 000c8000
* GAPI32 0A3F0000 0A407FFF 00018000
* dbghelp 0B540000 0B63FFFF 00100000
*
* Edi: 00000000:
* Esi: 0536AB20: 05DF2B28 00000007 00000001 00001000 05381978
0B1DB
F08
* Eax: 000001F0:
* Ebx: 77E1A7BD: 53EC8B55 A1645756 00000018 F08BC933 0F0C4D39
00008
B85
* Ecx: 00003931:
* Edx: 0B503032: 00000000 00000000 00000000 00000000 00000000
00000
000
* Eip: 05EB8187:
* Ebp: 0B50F98C: 0B50F9B8 05EAFCE3 00000002 00000000 0536AB20
77E1A
7BD
* SegCs: 0000001B:
* EFlags: 00010206: 0057005C 004E0049 0054004E 0073005C 00730079
00650
074
* Esp: 0B50F97C: 00000000 0536AB20 77E1A7BD 000001F0 0B50F9B8
05EAF
CE3
* SegSs: 00000023:
*
*****************************************************************************
**
*
----
--
* Short Stack Dump
* 05EB8187 Module(ORA73+00038187) (vsnupr+00021F7C)
* 05EAFCE3 Module(ORA73+0002FCE3) (vsnupr+00019AD8)
* 05EC4499 Module(ORA73+00044499) (vsnupr+0002E28E)
* 05EAFB95 Module(ORA73+0002FB95) (vsnupr+0001998A)
* 05EA1959 Module(ORA73+00021959) (vsnupr+0000B74E)
* 05E920A9 Module(ORA73+000120A9) (upiosd+00000063)
* 05E8BA77 Module(ORA73+0000BA77) (oparse+0000007C)
* 10001D88 Module(ociw32+00001D88) (oparse+00000028)
* 05E0EC77 Module(msdaora+0001EC77) (DllRegisterServer+000017B5)
* 780085BC Module(msvcrt+000085BC) (endthreadex+000000BC)
* 7C57B388 Module(KERNEL32+0000B388) (lstrcmpiW+000000B7)
----
* Location : 05EB8187 Module(ORA73+00038187) (vsnupr+00021F7C)
* Return Addr: 05EAFCE3 Module(ORA73+0002FCE3) (vsnupr+00019AD8)
Frame : 0B50F98C
Parameters:
[1] 00000002:
[2] 00000000:
[3] 0536AB20: 05DF2B28 00000007 00000001 00001000 05381978 0B1DBF08
[4] 77E1A7BD: 53EC8B55 A1645756 00000018 F08BC933 0F0C4D39 00008B85
160 bytes of stack data from 0B50F8EC to 0B50F98C
0B50F8EC: 000B0CE8 0A9E7C98 00000104 08A60048 [....|.....H...]
0B50F8FC: 05490178 08A60048 05490178 08A60040 [x.I.H...x.I.@....]
0B50F90C: 000001B7 00000001 00000000 00000000 [............]
0B50F91C: 00000000 00000000 00000000 00000000 [............]
:::: 2 Duplicate lines detected
0B50F94C: 00000000 0A9E7854 0000001C 77F82A8C [...Tx......*.w]
0B50F95C: 0A9E7860 00000005 77F82A8C 000B0000 [`x......*.w...]
0B50F96C: 000B0778 00000005 001761A8 0A9E7838 [x......a..8x..]
0B50F97C: 00000000 0536AB20 77E1A7BD 000001F0 [... .6...w...]Hi Stephanie,
Is the machine you are running on a multiprocessor machine? What sort
of storage system are you using (e.g. RAID, SAN)?
If you have a contract with MS Support (I'm under the impression you
need a contract now to get phone or email support for SQL Server 2000,
could be wrong though) you might consider forwarding them the SQL Dump
and also your mini-dump file (you should've got 2 files out of the
exception, a .txt file and another file which would be your mini-dump
file).
Sorry I can't be of more help.