I've got a report that runs from Crystal 10 just fine and the field shows up, but the field is missing when the report is run from Crystal Enterprise. All other fields show up just fine.
Information that may be important or not: I'm retrieving data from a SQL Server 2000 database Previously, I was getting a "failed to create rowset" error and the report wouldn't run at all. I narrowed the problem to the "Solution" field. Once I changed the driver* in the database connection, the report ran but the Solution field didn't show up. It's the longest field in the report and the only field in the report over 255 characters, if that means anything.
*I think I changed it from OLE DB to ODBC, but it could have been the other way around or totally different. Someone who's been here more than 3 weeks talked me through it.
Edit: I've tried Cstr({Solution}) and even Left(Cstr({Solution}), 20)Strangely, removing the Select Distinct Records option fixed it. To solve the resulting duplicate records problem, suppressed every result where the "ticket number" equaled the previous number. I think the report takes longer to run now.
Showing posts with label enterprise. Show all posts
Showing posts with label enterprise. Show all posts
Thursday, March 29, 2012
Friday, March 23, 2012
Feature Request: 2005 Beta 2
Greetings,
I have a feature request for the Enterprise Studio.
We have about 500+ stored procedures in our CRM application and opening up
Enterprise Manager (in 2000) or Enterprise Studio (2005) I have to look at a
huge list of stored procedures and find the one I'm specifically looking
for. Granted, in 2005 there is a "filter" it is rather unintuitive.
I'd like to request the abililty to add my own "folder" to the list where I
can create categories to group my stored procedures. for example, I can
create a "Invoices" group where all my invoice related SP's go, and a
"Policies" group where all my policies related SP's will go. In addition to
this, we have more tables than SPs, so we should be able to group any
object, Table, SP, View, etc.
Not sure if you've considered this already but the filtering isn't as
intuitive. It requires me to have to constantly enter in new filters to
filter the list before I can browse around. I'd like to browse directly to
what I'm looking for.
Thanks,
Shawn
Hi Shawn,
Have you considered using Schemas for this? (Introduced in SQL Server 2005
also).
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Shawn B." <leabre@.html.com> wrote in message
news:OLcOBc6zEHA.1564@.TK2MSFTNGP09.phx.gbl...
> Greetings,
> I have a feature request for the Enterprise Studio.
> We have about 500+ stored procedures in our CRM application and opening up
> Enterprise Manager (in 2000) or Enterprise Studio (2005) I have to look at
> a
> huge list of stored procedures and find the one I'm specifically looking
> for. Granted, in 2005 there is a "filter" it is rather unintuitive.
> I'd like to request the abililty to add my own "folder" to the list where
> I
> can create categories to group my stored procedures. for example, I can
> create a "Invoices" group where all my invoice related SP's go, and a
> "Policies" group where all my policies related SP's will go. In addition
> to
> this, we have more tables than SPs, so we should be able to group any
> object, Table, SP, View, etc.
> Not sure if you've considered this already but the filtering isn't as
> intuitive. It requires me to have to constantly enter in new filters to
> filter the list before I can browse around. I'd like to browse directly
> to
> what I'm looking for.
>
> Thanks,
> Shawn
>
|||What are schemas in this context? after a cursory google and help topics
lookup, I have no clue what they can do for me.
Thanks,
Shawn
"Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
news:e8NiNJ8zEHA.2528@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Hi Shawn,
> Have you considered using Schemas for this? (Introduced in SQL Server 2005
> also).
> HTH,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "Shawn B." <leabre@.html.com> wrote in message
> news:OLcOBc6zEHA.1564@.TK2MSFTNGP09.phx.gbl...
up[vbcol=seagreen]
at[vbcol=seagreen]
where[vbcol=seagreen]
addition
>
|||I believe this has been suggested before but to make sure please send the
details of your request to sqlwish@.microsoft.com
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Shawn B." <leabre@.html.com> wrote in message
news:OLcOBc6zEHA.1564@.TK2MSFTNGP09.phx.gbl...
> Greetings,
> I have a feature request for the Enterprise Studio.
> We have about 500+ stored procedures in our CRM application and opening up
> Enterprise Manager (in 2000) or Enterprise Studio (2005) I have to look at
> a
> huge list of stored procedures and find the one I'm specifically looking
> for. Granted, in 2005 there is a "filter" it is rather unintuitive.
> I'd like to request the abililty to add my own "folder" to the list where
> I
> can create categories to group my stored procedures. for example, I can
> create a "Invoices" group where all my invoice related SP's go, and a
> "Policies" group where all my policies related SP's will go. In addition
> to
> this, we have more tables than SPs, so we should be able to group any
> object, Table, SP, View, etc.
> Not sure if you've considered this already but the filtering isn't as
> intuitive. It requires me to have to constantly enter in new filters to
> filter the list before I can browse around. I'd like to browse directly
> to
> what I'm looking for.
>
> Thanks,
> Shawn
>
|||Hi Shawn,
Take a look at the Northwind sample database in SQL Server 2005 Beta if you
have access to it from the MSDN site. Whereas Northwind's tables, procs,
etc. before were just one big list, now there are separate schemas for
HumanResources, etc. with only those objects relevant to that part of the
app in them.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Shawn B." <leabre@.html.com> wrote in message
news:OWVSG5A0EHA.1192@.tk2msftngp13.phx.gbl...
> What are schemas in this context? after a cursory google and help topics
> lookup, I have no clue what they can do for me.
>
> Thanks,
> Shawn
>
> "Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
> news:e8NiNJ8zEHA.2528@.TK2MSFTNGP10.phx.gbl...
> up
> at
> where
> addition
>
|||Sorry, brain explosion - meant to point you to the Adventureworks sample,
not Northwind.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
news:OLy2UoU0EHA.3244@.TK2MSFTNGP10.phx.gbl...
> Hi Shawn,
> Take a look at the Northwind sample database in SQL Server 2005 Beta if
> you have access to it from the MSDN site. Whereas Northwind's tables,
> procs, etc. before were just one big list, now there are separate schemas
> for HumanResources, etc. with only those objects relevant to that part of
> the app in them.
> HTH,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "Shawn B." <leabre@.html.com> wrote in message
> news:OWVSG5A0EHA.1192@.tk2msftngp13.phx.gbl...
>
I have a feature request for the Enterprise Studio.
We have about 500+ stored procedures in our CRM application and opening up
Enterprise Manager (in 2000) or Enterprise Studio (2005) I have to look at a
huge list of stored procedures and find the one I'm specifically looking
for. Granted, in 2005 there is a "filter" it is rather unintuitive.
I'd like to request the abililty to add my own "folder" to the list where I
can create categories to group my stored procedures. for example, I can
create a "Invoices" group where all my invoice related SP's go, and a
"Policies" group where all my policies related SP's will go. In addition to
this, we have more tables than SPs, so we should be able to group any
object, Table, SP, View, etc.
Not sure if you've considered this already but the filtering isn't as
intuitive. It requires me to have to constantly enter in new filters to
filter the list before I can browse around. I'd like to browse directly to
what I'm looking for.
Thanks,
Shawn
Hi Shawn,
Have you considered using Schemas for this? (Introduced in SQL Server 2005
also).
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Shawn B." <leabre@.html.com> wrote in message
news:OLcOBc6zEHA.1564@.TK2MSFTNGP09.phx.gbl...
> Greetings,
> I have a feature request for the Enterprise Studio.
> We have about 500+ stored procedures in our CRM application and opening up
> Enterprise Manager (in 2000) or Enterprise Studio (2005) I have to look at
> a
> huge list of stored procedures and find the one I'm specifically looking
> for. Granted, in 2005 there is a "filter" it is rather unintuitive.
> I'd like to request the abililty to add my own "folder" to the list where
> I
> can create categories to group my stored procedures. for example, I can
> create a "Invoices" group where all my invoice related SP's go, and a
> "Policies" group where all my policies related SP's will go. In addition
> to
> this, we have more tables than SPs, so we should be able to group any
> object, Table, SP, View, etc.
> Not sure if you've considered this already but the filtering isn't as
> intuitive. It requires me to have to constantly enter in new filters to
> filter the list before I can browse around. I'd like to browse directly
> to
> what I'm looking for.
>
> Thanks,
> Shawn
>
|||What are schemas in this context? after a cursory google and help topics
lookup, I have no clue what they can do for me.
Thanks,
Shawn
"Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
news:e8NiNJ8zEHA.2528@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Hi Shawn,
> Have you considered using Schemas for this? (Introduced in SQL Server 2005
> also).
> HTH,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "Shawn B." <leabre@.html.com> wrote in message
> news:OLcOBc6zEHA.1564@.TK2MSFTNGP09.phx.gbl...
up[vbcol=seagreen]
at[vbcol=seagreen]
where[vbcol=seagreen]
addition
>
|||I believe this has been suggested before but to make sure please send the
details of your request to sqlwish@.microsoft.com
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Shawn B." <leabre@.html.com> wrote in message
news:OLcOBc6zEHA.1564@.TK2MSFTNGP09.phx.gbl...
> Greetings,
> I have a feature request for the Enterprise Studio.
> We have about 500+ stored procedures in our CRM application and opening up
> Enterprise Manager (in 2000) or Enterprise Studio (2005) I have to look at
> a
> huge list of stored procedures and find the one I'm specifically looking
> for. Granted, in 2005 there is a "filter" it is rather unintuitive.
> I'd like to request the abililty to add my own "folder" to the list where
> I
> can create categories to group my stored procedures. for example, I can
> create a "Invoices" group where all my invoice related SP's go, and a
> "Policies" group where all my policies related SP's will go. In addition
> to
> this, we have more tables than SPs, so we should be able to group any
> object, Table, SP, View, etc.
> Not sure if you've considered this already but the filtering isn't as
> intuitive. It requires me to have to constantly enter in new filters to
> filter the list before I can browse around. I'd like to browse directly
> to
> what I'm looking for.
>
> Thanks,
> Shawn
>
|||Hi Shawn,
Take a look at the Northwind sample database in SQL Server 2005 Beta if you
have access to it from the MSDN site. Whereas Northwind's tables, procs,
etc. before were just one big list, now there are separate schemas for
HumanResources, etc. with only those objects relevant to that part of the
app in them.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Shawn B." <leabre@.html.com> wrote in message
news:OWVSG5A0EHA.1192@.tk2msftngp13.phx.gbl...
> What are schemas in this context? after a cursory google and help topics
> lookup, I have no clue what they can do for me.
>
> Thanks,
> Shawn
>
> "Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
> news:e8NiNJ8zEHA.2528@.TK2MSFTNGP10.phx.gbl...
> up
> at
> where
> addition
>
|||Sorry, brain explosion - meant to point you to the Adventureworks sample,
not Northwind.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
news:OLy2UoU0EHA.3244@.TK2MSFTNGP10.phx.gbl...
> Hi Shawn,
> Take a look at the Northwind sample database in SQL Server 2005 Beta if
> you have access to it from the MSDN site. Whereas Northwind's tables,
> procs, etc. before were just one big list, now there are separate schemas
> for HumanResources, etc. with only those objects relevant to that part of
> the app in them.
> HTH,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "Shawn B." <leabre@.html.com> wrote in message
> news:OWVSG5A0EHA.1192@.tk2msftngp13.phx.gbl...
>
Monday, March 19, 2012
Fatal exception caught and SQL abort
We're running Microsoft SQL Server 2000 - 8.00.818 (Intel IA-64)
Jun 1 2003 15:32:45
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: ).
The SQL Server was fatally aborted with the following error. Can anyone help?
SqlDumpExceptionHandler: Process 222 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process..
*
*******************************************************************************
*
* BEGIN STACK DUMP:
* 02/21/05 21:30:03 spid 222
*
* Exception Address = 0000000000489D00 (SendOdsDone + 0000000000000070
Line 0+0000000000000000)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address 000000000000029C
* Input Buffer 164 bytes -
* EXECUTE msdb.dbo.sp_sqlagent_has_server_access @.login_name = N'hxdom0\ms
* sql_admin'
*
*
* MODULE BASE END SIZE
* sqlservr 0000000000400000 0000000001BA5FFF 017a6000
* ntdll 0000000077E70000 0000000077FF3FFF 00184000
* kernel32 0000000077C90000 0000000077E5FFFF 001d0000
* ADVAPI32 000006FB7FE80000 000006FB7FFDFFFF 00160000
* RPCRT4 000006FB7FC60000 000006FB7FE75FFF 00216000
* USER32 0000000077B30000 0000000077C89FFF 0015a000
* GDI32 000006FB7FB90000 000006FB7FC5DFFF 000ce000
* ole32 000006FB7E7B0000 000006FB7EB23FFF 00374000
* msvcrt 000006FB7FAA0000 000006FB7FB85FFF 000e6000
* OLEAUT32 000006FB7E410000 000006FB7E7A9FFF 0039a000
* VERSION 000006FB7FA80000 000006FB7FA97FFF 00018000
* opends60 0000000004D00000 0000000004D15FFF 00016000
* sqlsort 0000000004000000 00000000040A3FFF 000a4000
* MSVCIRT 000006FB5BDC0000 000006FB5BDF3FFF 00034000
* IMM32 000006FB7C5F0000 000006FB7C647FFF 00058000
* LPK 000006FB608C0000 000006FB608DBFFF 0001c000
* USP10 000006FB76450000 000006FB7650FFFF 000c0000
* sqlevn70 0000000010000000 0000000010007FFF 00008000
* Secur32 000006FB7E170000 000006FB7E1A5FFF 00036000
* NETAPI32 000006FB73BF0000 000006FB73CC9FFF 000da000
* COMRES 000006FB7E340000 000006FB7E40BFFF 000cc000
* XOLEHLP 000006FBEF110000 000006FBEF11FFFF 00010000
* MSDTCPRX 000006FB5D910000 000006FB5DA5BFFF 0014c000
* MSVCP60 00000000780C0000 00000000781B7FFF 000f8000
* MTXCLU 000006FB79BF0000 000006FB79C2DFFF 0003e000
* WSOCK32 000006FB73AC0000 000006FB73ACFFFF 00010000
* WS2_32 000006FB73B60000 000006FB73BA3FFF 00044000
* WS2HELP 000006FB73B40000 000006FB73B59FFF 0001a000
* CLUSAPI 000006FB79950000 000006FB79985FFF 00036000
* RESUTILS 000006FB79B50000 000006FB79B81FFF 00032000
* USERENV 000006FB7B3F0000 000006FB7B56FFFF 00180000
* MFC42u 000006FB75490000 000006FB757F5FFF 00366000
* mswsock 000006FB73970000 000006FB73A21FFF 000b2000
* DNSAPI 000006FB7E050000 000006FB7E0BFFFF 00070000
* winrnr 000006FB7E1B0000 000006FB7E1C5FFF 00016000
* WLDAP32 000006FB7E0F0000 000006FB7E165FFF 00076000
* rasadhlp 000006FB7E1D0000 000006FB7E1E1FFF 00012000
* NTMARTA 000006FB7DA80000 000006FB7DAE1FFF 00062000
* SAMLIB 000006FBFF470000 000006FBFF497FFF 00028000
* SSNETLIB 000006FBFF3F0000 000006FBFF43BFFF 0004c000
* security 000006FB740D0000 000006FB740DBFFF 0000c000
* wshtcpip 000006FB73900000 000006FB73915FFF 00016000
* SSmsLPCn 000006FBFF0B0000 000006FBFF0CBFFF 0001c000
* SSnmPN70 000006FBE8CC0000 000006FBE8CD3FFF 00014000
* ntdsapi 000006FB7CF00000 000006FB7CF39FFF 0003a000
* kerberos 000006FB73CD0000 000006FB73DB1FFF 000e2000
* cryptdll 000006FB7CEE0000 000006FB7CEFBFFF 0001c000
* MSASN1 000006FB7C3C0000 000006FB7C3F1FFF 00032000
* SQLFTQRY 0000000041020000 0000000041093FFF 00074000
* CLBCatQ 000006FB7E1F0000 000006FB7E337FFF 00148000
* sqloledb 000006FBE9F70000 000006FBEA0D1FFF 00162000
* MSDART 000006FB79070000 000006FB790DFFFF 00070000
* COMCTL32 000006FB725B0000 000006FB72745FFF 00196000
* comdlg32 000006FB7C650000 000006FB7C70BFFF 000bc000
* SHLWAPI 000006FB7EB30000 000006FB7EBEBFFF 000bc000
* SHELL32 000006FB7ED90000 000006FB7FA09FFF 00c7a000
* MSDATL3 000006FB5DAB0000 000006FB5DAEFFFF 00040000
* comctl32 000006FB72370000 000006FB725A7FFF 00238000
* oledb32 000006FBE8F90000 000006FBE90E5FFF 00156000
* OLEDB32R 000006FBFECA0000 000006FBFECB3FFF 00014000
* xpstar 000006FBE9A90000 000006FBE9B65FFF 000d6000
* SQLRESLD 000000001C000000 000000001C015FFF 00016000
* SQLSVC 000006FBE9A30000 000006FBE9A8BFFF 0005c000
* ODBC32 000006FBE9980000 000006FBE9A21FFF 000a2000
* odbcbcp 000006FBE9960000 000006FBE9973FFF 00014000
* W95SCM 000000001C500000 000000001C52FFFF 00030000
* SHFOLDER 000006FB7CEC0000 000006FB7CED5FFF 00016000
* odbcint 000006FBE97C0000 000006FBE97D7FFF 00018000
* SQLSVC 000006FBFED50000 000006FBFED53FFF 00004000
* xpstar 000006FBE97B0000 000006FBE97B9FFF 0000a000
* msv1_0 000006FB7DAF0000 000006FB7DB4DFFF 0005e000
* rsaenh 000000000FF90000 000000000FFF5FFF 00066000
* PSAPI 000006FB7D8B0000 000006FB7D8CDFFF 0001e000
* xpsqlbot 000006FBE4C30000 000006FBE4C41FFF 00012000
* xplog70 000006FBE43C0000 000006FBE43FBFFF 0003c000
* xplog70 000006FBE43B0000 000006FBE43B5FFF 00006000
* sqlvdi 000006FBE1E10000 000006FBE1E39FFF 0002a000
* sqlmap70 000006FBEF290000 000006FBEF2A1FFF 00012000
* NETRAP 000006FBEBCA0000 000006FBEBCB5FFF 00016000
* dbghelp 000006FB6C510000 000006FB6C737FFF 00228000
*
* DbI0: 0000000000000000:
* DbI1: 0000000000000000:
* DbI2: 0000000483048F01:
* DbI3: E00000008345B0D0:
* DbI4: 000006FB0008000B: 0820000000000000 081F58000006FB00
000001000006FB00 CCE0000000000000 66E000000006FB57 080178000006F965
* DbI5: 000006FB29552208: 0000000001637B90 00000009FFFFFFE0
00000000000A0000 0000000000000000 0000000001637B90 0000000AFFFFFFE0
* DbI6: 000006FB29552160: 0000000000000000 000000000162C790
00000004FFFFFFE0 0000000000000000 0000000000000000 000000000162C790
* DbI7: 000006FB29552608: 000000000162CFE8 0000000100000020
0000000000000052 0000000000000000 000000000162C960 00000021FFFFFFE0
* DbD0: 000006FB29552758: 0000000000000000 0000000000000000
000000000162C730 00000026FFFFFFE0 0000000000000000 0000000000000000
* DbD1: 000006FB295526B0: 0000000000000020 0000000000000000
0000000000000000 000000000162C960 00000023FFFFFFE0 0000000000000000
* DbD2: 000006FB29552410: 00000016FFFFFFE0 0000000000000000
0000000000000000 0000000001635510 0000000000000020 0000000000130001
* DbD3: 000006FB29552560: 0000000000000000 000000000162C820
0000000600000000 000000000000002E 0000000000000000 000000000162C970
* DbD4: 000006FB295524B8: 0000000000000000 0000000000000000
000000000162C960 0000001BFFFFFFE0 0000000000000000 0000000000000000
* DbD5: 000006FB29552A08: 000000000162C730 0000002FFFFFFFE0
0000000000000000 0000000000000000 000000000162CFF8 0000000000000000
* DbD6: 000006FB29552B58: 0000000000000000 0000000000000000
0000000001637B90 00000038FFFFFFE0 0000000000160000 0000000000000000
* DbD7: 000006FB29552AB0: 00000032FFFFFFE0 0000000000140000
0000000000000000 0000000001637B90 00000033FFFFFFE0 0000000000150000
* StFPSR: 000998489E744232:
* IntGp: 0000000001CE2000:
* IntT0: 000006FBD9CC2070: 000006FBEE9FD520 000006FBD9CBA37C
0000000000400000 0000000001822298 000006FBD9CBBB28 000006FBD9CBA300
* IntT1: FFFFFFFFFFFFFFFE:
* IntS0: 0000000077CB1130: 0000000077CB8960 0000000077FE2000
0000000077CB89C0 0000000077FE2000 0000000077CB8A60 0000000077FE2000
* IntS1: 000000000168FED0: 00000000007E4850 0000000001CE2000
00000000009246D0 0000000001CE2000 000000000064AE90 0000000001CE2000
* IntS2: 000006FBEE9E1170: 000006FBEE9F9DD0 000006FBEE9F3530
2E522E412E532067 000000003035392E 011801A30010000D 0000000000000000
* IntS3: 0000000000000000:
* IntV0: 0000000000000000:
* IntT2: 0000000000000040:
* IntT3: 0000000000000202:
* IntT4: 0000000000000000:
* IntSp: 000006FBD9CBF5E0: FFFFFFFFFFFFFFFE 0000000000000000
0000000000000000 0000000000788B60 0000000200000002 000006F9F50992C8
* IntTeb: 000006FBFF9EE000: 0000000000000000 000006FBCE810000
000006FBCE808000 0000000000000000 000006FBD7992010 0000000000000000
* IntT5: 0000000000000000:
* IntT6: 0000000000000000:
* IntT7: 0000000000000048:
* IntT8: 0000000000000001:
* IntT9: 0000000000000000:
* IntT10: 0000000000000000:
* IntT11: 0000000000000000:
* IntT12: 0000000000000000:
* IntT13: 0000000000000000:
* IntT14: 0000000000000000:
* IntT15: 0000000000000000:
* IntT16: 000006FBFFFDE000: 0000000000000000 FFFFFFFFFFFFFFFF
0000000000400000 0000000077FBC360 000006FBFFF80000 0000000000000000
* IntT17: 0000000000000000:
* IntT18: 000006FBD9CBF9D0: 000006F9FCEFC0E8 000006F965100C40
000006F965100C40 0000000100000001 000006FBEEA12CB0 000006F9FCEFC568
* IntT19: 000006FBD9CBF618: 000006FA00000001 000006F9F50996C8
00000000016280E0 0000000000000000 0000000000000000 000006FB12000000
* IntT20: 0000000000000000:
* IntT21: 0000000000000288:
* IntT22: 000006FBFFB03D68: 0000000000000000 000006FBEE9CF7B0
000006FBFB2B6AC0 0010016D00040004 0000002000000001 0000000000000000
* IntNats: 0000000000000000:
* Preds: 00000000000085C1:
* BrRp: 00000000004DD3D0: 000021061921E011 454E9D0007F11EAC
0000101878012819 2000000000000200 43A021001B61C801 8400648700480000
* BrS0: 0000000000000000:
* BrS1: 0000000000000000:
* BrS2: 0000000000000000:
* BrS3: 0000000000000000:
* BrS4: 0000000000000000:
* BrT0: 000006FBFFB5CFA0: 0010014F00020015 0000000100000000
000006FBFFAE1530 0010000099DEAD99 1E80C4E500000001 0000000000000000
* BrT1: 0000000000000001:
* ApUNAT: 0000000000000000:
* ApLC: 0000000000000000:
* ApEC: 0000000000000000:
* ApCCV: 00000000FFFFFFFF:
* ApDCR: 0000000000007E05:
* RsPFS: C000000000000B9D:
* RsBSP: 000006FBD9CC0250: FFFFFFFFFFFFFFFD 0000000000000001
0000000000000001 0000000001AF9CD8 0000000000000000 0000000000000000
* RsBSPSTORE: 000006FBD9CC0250: FFFFFFFFFFFFFFFD 0000000000000001
0000000000000001 0000000001AF9CD8 0000000000000000 0000000000000000
* RsRSC: 000000000000000F:
* RsRNAT: 0000000000000000:
* StIPSR: 00001013082A6018:
* StIIP: 0000000000489D00: 01C010105400E808 84152144C02020A4
01B02105484D380A 537CF9D34020E0B0 019010183C01180A 8038E1A5002060AC
* StIFS: 8000000000000B1A:
* StFCR: 0000000000000040:
* Eflag: 0000000000000202:
* SegCSD: 0000000000000000:
* SegSSD: CF3FFFFF00000000:
* Cflag: 0000060100000111:
* StFSR: 0000000000000000:
* StFIR: 0000000000000000:
* StFDR: 0000000000000000:
*
*******************************************************************************
*
----
* Short Stack Dump
* 0000000000489D00 Module(sqlservr+0000000000089D00)
(SendOdsDone+0000000000000070)
* 00000000004DD3D0 Module(sqlservr+00000000000DD3D0)
(language_exec+0000000000000B20)
* 00000000004DD690 Module(sqlservr+00000000000DD690)
(process_commands+00000000000003A0)
* 00000000004058B0 Module(sqlservr+00000000000058B0)
(ProcessWorkRequests+0000000000000A00)
* 00000000007E4960 Module(sqlservr+00000000003E4960)
(FiberStartRoutine+0000000000000110)
* 0000000077D24400 Module(kernel32+0000000000094400)
(GetDateFormatW+0000000000070070)
* 0000000077CB8990 Module(kernel32+0000000000028990)
(GetDateFormatW+0000000000004600)
* 0000000077CB8950 Module(kernel32+0000000000028950)
(GetDateFormatW+00000000000045C0)
*
----Please contact Microsoft Product Support Services
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright © SQLDev.Net 1991-2005 All rights reserved.
"wc chan" <wcchan@.discussions.microsoft.com> wrote in message
news:1626D38A-2AFB-4099-8999-13F76C324438@.microsoft.com...
> We're running Microsoft SQL Server 2000 - 8.00.818 (Intel IA-64)
> Jun 1 2003 15:32:45
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: ).
> The SQL Server was fatally aborted with the following error. Can anyone
> help?
> SqlDumpExceptionHandler: Process 222 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process..
> *
> *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 02/21/05 21:30:03 spid 222
> *
> * Exception Address = 0000000000489D00 (SendOdsDone + 0000000000000070
> Line 0+0000000000000000)
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred reading address 000000000000029C
> * Input Buffer 164 bytes -
> * EXECUTE msdb.dbo.sp_sqlagent_has_server_access @.login_name => N'hxdom0\ms
> * sql_admin'
> *
> *
> * MODULE BASE END SIZE
> * sqlservr 0000000000400000 0000000001BA5FFF
> 017a6000
> * ntdll 0000000077E70000 0000000077FF3FFF
> 00184000
> * kernel32 0000000077C90000 0000000077E5FFFF
> 001d0000
> * ADVAPI32 000006FB7FE80000 000006FB7FFDFFFF
> 00160000
> * RPCRT4 000006FB7FC60000 000006FB7FE75FFF
> 00216000
> * USER32 0000000077B30000 0000000077C89FFF
> 0015a000
> * GDI32 000006FB7FB90000 000006FB7FC5DFFF
> 000ce000
> * ole32 000006FB7E7B0000 000006FB7EB23FFF
> 00374000
> * msvcrt 000006FB7FAA0000 000006FB7FB85FFF
> 000e6000
> * OLEAUT32 000006FB7E410000 000006FB7E7A9FFF
> 0039a000
> * VERSION 000006FB7FA80000 000006FB7FA97FFF
> 00018000
> * opends60 0000000004D00000 0000000004D15FFF
> 00016000
> * sqlsort 0000000004000000 00000000040A3FFF
> 000a4000
> * MSVCIRT 000006FB5BDC0000 000006FB5BDF3FFF
> 00034000
> * IMM32 000006FB7C5F0000 000006FB7C647FFF
> 00058000
> * LPK 000006FB608C0000 000006FB608DBFFF
> 0001c000
> * USP10 000006FB76450000 000006FB7650FFFF
> 000c0000
> * sqlevn70 0000000010000000 0000000010007FFF
> 00008000
> * Secur32 000006FB7E170000 000006FB7E1A5FFF
> 00036000
> * NETAPI32 000006FB73BF0000 000006FB73CC9FFF
> 000da000
> * COMRES 000006FB7E340000 000006FB7E40BFFF
> 000cc000
> * XOLEHLP 000006FBEF110000 000006FBEF11FFFF
> 00010000
> * MSDTCPRX 000006FB5D910000 000006FB5DA5BFFF
> 0014c000
> * MSVCP60 00000000780C0000 00000000781B7FFF
> 000f8000
> * MTXCLU 000006FB79BF0000 000006FB79C2DFFF
> 0003e000
> * WSOCK32 000006FB73AC0000 000006FB73ACFFFF
> 00010000
> * WS2_32 000006FB73B60000 000006FB73BA3FFF
> 00044000
> * WS2HELP 000006FB73B40000 000006FB73B59FFF
> 0001a000
> * CLUSAPI 000006FB79950000 000006FB79985FFF
> 00036000
> * RESUTILS 000006FB79B50000 000006FB79B81FFF
> 00032000
> * USERENV 000006FB7B3F0000 000006FB7B56FFFF
> 00180000
> * MFC42u 000006FB75490000 000006FB757F5FFF
> 00366000
> * mswsock 000006FB73970000 000006FB73A21FFF
> 000b2000
> * DNSAPI 000006FB7E050000 000006FB7E0BFFFF
> 00070000
> * winrnr 000006FB7E1B0000 000006FB7E1C5FFF
> 00016000
> * WLDAP32 000006FB7E0F0000 000006FB7E165FFF
> 00076000
> * rasadhlp 000006FB7E1D0000 000006FB7E1E1FFF
> 00012000
> * NTMARTA 000006FB7DA80000 000006FB7DAE1FFF
> 00062000
> * SAMLIB 000006FBFF470000 000006FBFF497FFF
> 00028000
> * SSNETLIB 000006FBFF3F0000 000006FBFF43BFFF
> 0004c000
> * security 000006FB740D0000 000006FB740DBFFF
> 0000c000
> * wshtcpip 000006FB73900000 000006FB73915FFF
> 00016000
> * SSmsLPCn 000006FBFF0B0000 000006FBFF0CBFFF
> 0001c000
> * SSnmPN70 000006FBE8CC0000 000006FBE8CD3FFF
> 00014000
> * ntdsapi 000006FB7CF00000 000006FB7CF39FFF
> 0003a000
> * kerberos 000006FB73CD0000 000006FB73DB1FFF
> 000e2000
> * cryptdll 000006FB7CEE0000 000006FB7CEFBFFF
> 0001c000
> * MSASN1 000006FB7C3C0000 000006FB7C3F1FFF
> 00032000
> * SQLFTQRY 0000000041020000 0000000041093FFF
> 00074000
> * CLBCatQ 000006FB7E1F0000 000006FB7E337FFF
> 00148000
> * sqloledb 000006FBE9F70000 000006FBEA0D1FFF
> 00162000
> * MSDART 000006FB79070000 000006FB790DFFFF
> 00070000
> * COMCTL32 000006FB725B0000 000006FB72745FFF
> 00196000
> * comdlg32 000006FB7C650000 000006FB7C70BFFF
> 000bc000
> * SHLWAPI 000006FB7EB30000 000006FB7EBEBFFF
> 000bc000
> * SHELL32 000006FB7ED90000 000006FB7FA09FFF
> 00c7a000
> * MSDATL3 000006FB5DAB0000 000006FB5DAEFFFF
> 00040000
> * comctl32 000006FB72370000 000006FB725A7FFF
> 00238000
> * oledb32 000006FBE8F90000 000006FBE90E5FFF
> 00156000
> * OLEDB32R 000006FBFECA0000 000006FBFECB3FFF
> 00014000
> * xpstar 000006FBE9A90000 000006FBE9B65FFF
> 000d6000
> * SQLRESLD 000000001C000000 000000001C015FFF
> 00016000
> * SQLSVC 000006FBE9A30000 000006FBE9A8BFFF
> 0005c000
> * ODBC32 000006FBE9980000 000006FBE9A21FFF
> 000a2000
> * odbcbcp 000006FBE9960000 000006FBE9973FFF
> 00014000
> * W95SCM 000000001C500000 000000001C52FFFF
> 00030000
> * SHFOLDER 000006FB7CEC0000 000006FB7CED5FFF
> 00016000
> * odbcint 000006FBE97C0000 000006FBE97D7FFF
> 00018000
> * SQLSVC 000006FBFED50000 000006FBFED53FFF
> 00004000
> * xpstar 000006FBE97B0000 000006FBE97B9FFF
> 0000a000
> * msv1_0 000006FB7DAF0000 000006FB7DB4DFFF
> 0005e000
> * rsaenh 000000000FF90000 000000000FFF5FFF
> 00066000
> * PSAPI 000006FB7D8B0000 000006FB7D8CDFFF
> 0001e000
> * xpsqlbot 000006FBE4C30000 000006FBE4C41FFF
> 00012000
> * xplog70 000006FBE43C0000 000006FBE43FBFFF
> 0003c000
> * xplog70 000006FBE43B0000 000006FBE43B5FFF
> 00006000
> * sqlvdi 000006FBE1E10000 000006FBE1E39FFF
> 0002a000
> * sqlmap70 000006FBEF290000 000006FBEF2A1FFF
> 00012000
> * NETRAP 000006FBEBCA0000 000006FBEBCB5FFF
> 00016000
> * dbghelp 000006FB6C510000 000006FB6C737FFF
> 00228000
> *
> * DbI0: 0000000000000000:
> * DbI1: 0000000000000000:
> * DbI2: 0000000483048F01:
> * DbI3: E00000008345B0D0:
> * DbI4: 000006FB0008000B: 0820000000000000 081F58000006FB00
> 000001000006FB00 CCE0000000000000 66E000000006FB57 080178000006F965
> * DbI5: 000006FB29552208: 0000000001637B90 00000009FFFFFFE0
> 00000000000A0000 0000000000000000 0000000001637B90 0000000AFFFFFFE0
> * DbI6: 000006FB29552160: 0000000000000000 000000000162C790
> 00000004FFFFFFE0 0000000000000000 0000000000000000 000000000162C790
> * DbI7: 000006FB29552608: 000000000162CFE8 0000000100000020
> 0000000000000052 0000000000000000 000000000162C960 00000021FFFFFFE0
> * DbD0: 000006FB29552758: 0000000000000000 0000000000000000
> 000000000162C730 00000026FFFFFFE0 0000000000000000 0000000000000000
> * DbD1: 000006FB295526B0: 0000000000000020 0000000000000000
> 0000000000000000 000000000162C960 00000023FFFFFFE0 0000000000000000
> * DbD2: 000006FB29552410: 00000016FFFFFFE0 0000000000000000
> 0000000000000000 0000000001635510 0000000000000020 0000000000130001
> * DbD3: 000006FB29552560: 0000000000000000 000000000162C820
> 0000000600000000 000000000000002E 0000000000000000 000000000162C970
> * DbD4: 000006FB295524B8: 0000000000000000 0000000000000000
> 000000000162C960 0000001BFFFFFFE0 0000000000000000 0000000000000000
> * DbD5: 000006FB29552A08: 000000000162C730 0000002FFFFFFFE0
> 0000000000000000 0000000000000000 000000000162CFF8 0000000000000000
> * DbD6: 000006FB29552B58: 0000000000000000 0000000000000000
> 0000000001637B90 00000038FFFFFFE0 0000000000160000 0000000000000000
> * DbD7: 000006FB29552AB0: 00000032FFFFFFE0 0000000000140000
> 0000000000000000 0000000001637B90 00000033FFFFFFE0 0000000000150000
> * StFPSR: 000998489E744232:
> * IntGp: 0000000001CE2000:
> * IntT0: 000006FBD9CC2070: 000006FBEE9FD520 000006FBD9CBA37C
> 0000000000400000 0000000001822298 000006FBD9CBBB28 000006FBD9CBA300
> * IntT1: FFFFFFFFFFFFFFFE:
> * IntS0: 0000000077CB1130: 0000000077CB8960 0000000077FE2000
> 0000000077CB89C0 0000000077FE2000 0000000077CB8A60 0000000077FE2000
> * IntS1: 000000000168FED0: 00000000007E4850 0000000001CE2000
> 00000000009246D0 0000000001CE2000 000000000064AE90 0000000001CE2000
> * IntS2: 000006FBEE9E1170: 000006FBEE9F9DD0 000006FBEE9F3530
> 2E522E412E532067 000000003035392E 011801A30010000D 0000000000000000
> * IntS3: 0000000000000000:
> * IntV0: 0000000000000000:
> * IntT2: 0000000000000040:
> * IntT3: 0000000000000202:
> * IntT4: 0000000000000000:
> * IntSp: 000006FBD9CBF5E0: FFFFFFFFFFFFFFFE 0000000000000000
> 0000000000000000 0000000000788B60 0000000200000002 000006F9F50992C8
> * IntTeb: 000006FBFF9EE000: 0000000000000000 000006FBCE810000
> 000006FBCE808000 0000000000000000 000006FBD7992010 0000000000000000
> * IntT5: 0000000000000000:
> * IntT6: 0000000000000000:
> * IntT7: 0000000000000048:
> * IntT8: 0000000000000001:
> * IntT9: 0000000000000000:
> * IntT10: 0000000000000000:
> * IntT11: 0000000000000000:
> * IntT12: 0000000000000000:
> * IntT13: 0000000000000000:
> * IntT14: 0000000000000000:
> * IntT15: 0000000000000000:
> * IntT16: 000006FBFFFDE000: 0000000000000000 FFFFFFFFFFFFFFFF
> 0000000000400000 0000000077FBC360 000006FBFFF80000 0000000000000000
> * IntT17: 0000000000000000:
> * IntT18: 000006FBD9CBF9D0: 000006F9FCEFC0E8 000006F965100C40
> 000006F965100C40 0000000100000001 000006FBEEA12CB0 000006F9FCEFC568
> * IntT19: 000006FBD9CBF618: 000006FA00000001 000006F9F50996C8
> 00000000016280E0 0000000000000000 0000000000000000 000006FB12000000
> * IntT20: 0000000000000000:
> * IntT21: 0000000000000288:
> * IntT22: 000006FBFFB03D68: 0000000000000000 000006FBEE9CF7B0
> 000006FBFB2B6AC0 0010016D00040004 0000002000000001 0000000000000000
> * IntNats: 0000000000000000:
> * Preds: 00000000000085C1:
> * BrRp: 00000000004DD3D0: 000021061921E011 454E9D0007F11EAC
> 0000101878012819 2000000000000200 43A021001B61C801 8400648700480000
> * BrS0: 0000000000000000:
> * BrS1: 0000000000000000:
> * BrS2: 0000000000000000:
> * BrS3: 0000000000000000:
> * BrS4: 0000000000000000:
> * BrT0: 000006FBFFB5CFA0: 0010014F00020015 0000000100000000
> 000006FBFFAE1530 0010000099DEAD99 1E80C4E500000001 0000000000000000
> * BrT1: 0000000000000001:
> * ApUNAT: 0000000000000000:
> * ApLC: 0000000000000000:
> * ApEC: 0000000000000000:
> * ApCCV: 00000000FFFFFFFF:
> * ApDCR: 0000000000007E05:
> * RsPFS: C000000000000B9D:
> * RsBSP: 000006FBD9CC0250: FFFFFFFFFFFFFFFD 0000000000000001
> 0000000000000001 0000000001AF9CD8 0000000000000000 0000000000000000
> * RsBSPSTORE: 000006FBD9CC0250: FFFFFFFFFFFFFFFD 0000000000000001
> 0000000000000001 0000000001AF9CD8 0000000000000000 0000000000000000
> * RsRSC: 000000000000000F:
> * RsRNAT: 0000000000000000:
> * StIPSR: 00001013082A6018:
> * StIIP: 0000000000489D00: 01C010105400E808 84152144C02020A4
> 01B02105484D380A 537CF9D34020E0B0 019010183C01180A 8038E1A5002060AC
> * StIFS: 8000000000000B1A:
> * StFCR: 0000000000000040:
> * Eflag: 0000000000000202:
> * SegCSD: 0000000000000000:
> * SegSSD: CF3FFFFF00000000:
> * Cflag: 0000060100000111:
> * StFSR: 0000000000000000:
> * StFIR: 0000000000000000:
> * StFDR: 0000000000000000:
> *
> *******************************************************************************
> *
> ----
> * Short Stack Dump
> * 0000000000489D00 Module(sqlservr+0000000000089D00)
> (SendOdsDone+0000000000000070)
> * 00000000004DD3D0 Module(sqlservr+00000000000DD3D0)
> (language_exec+0000000000000B20)
> * 00000000004DD690 Module(sqlservr+00000000000DD690)
> (process_commands+00000000000003A0)
> * 00000000004058B0 Module(sqlservr+00000000000058B0)
> (ProcessWorkRequests+0000000000000A00)
> * 00000000007E4960 Module(sqlservr+00000000003E4960)
> (FiberStartRoutine+0000000000000110)
> * 0000000077D24400 Module(kernel32+0000000000094400)
> (GetDateFormatW+0000000000070070)
> * 0000000077CB8990 Module(kernel32+0000000000028990)
> (GetDateFormatW+0000000000004600)
> * 0000000077CB8950 Module(kernel32+0000000000028950)
> (GetDateFormatW+00000000000045C0)
> *
> ----
Jun 1 2003 15:32:45
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: ).
The SQL Server was fatally aborted with the following error. Can anyone help?
SqlDumpExceptionHandler: Process 222 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process..
*
*******************************************************************************
*
* BEGIN STACK DUMP:
* 02/21/05 21:30:03 spid 222
*
* Exception Address = 0000000000489D00 (SendOdsDone + 0000000000000070
Line 0+0000000000000000)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address 000000000000029C
* Input Buffer 164 bytes -
* EXECUTE msdb.dbo.sp_sqlagent_has_server_access @.login_name = N'hxdom0\ms
* sql_admin'
*
*
* MODULE BASE END SIZE
* sqlservr 0000000000400000 0000000001BA5FFF 017a6000
* ntdll 0000000077E70000 0000000077FF3FFF 00184000
* kernel32 0000000077C90000 0000000077E5FFFF 001d0000
* ADVAPI32 000006FB7FE80000 000006FB7FFDFFFF 00160000
* RPCRT4 000006FB7FC60000 000006FB7FE75FFF 00216000
* USER32 0000000077B30000 0000000077C89FFF 0015a000
* GDI32 000006FB7FB90000 000006FB7FC5DFFF 000ce000
* ole32 000006FB7E7B0000 000006FB7EB23FFF 00374000
* msvcrt 000006FB7FAA0000 000006FB7FB85FFF 000e6000
* OLEAUT32 000006FB7E410000 000006FB7E7A9FFF 0039a000
* VERSION 000006FB7FA80000 000006FB7FA97FFF 00018000
* opends60 0000000004D00000 0000000004D15FFF 00016000
* sqlsort 0000000004000000 00000000040A3FFF 000a4000
* MSVCIRT 000006FB5BDC0000 000006FB5BDF3FFF 00034000
* IMM32 000006FB7C5F0000 000006FB7C647FFF 00058000
* LPK 000006FB608C0000 000006FB608DBFFF 0001c000
* USP10 000006FB76450000 000006FB7650FFFF 000c0000
* sqlevn70 0000000010000000 0000000010007FFF 00008000
* Secur32 000006FB7E170000 000006FB7E1A5FFF 00036000
* NETAPI32 000006FB73BF0000 000006FB73CC9FFF 000da000
* COMRES 000006FB7E340000 000006FB7E40BFFF 000cc000
* XOLEHLP 000006FBEF110000 000006FBEF11FFFF 00010000
* MSDTCPRX 000006FB5D910000 000006FB5DA5BFFF 0014c000
* MSVCP60 00000000780C0000 00000000781B7FFF 000f8000
* MTXCLU 000006FB79BF0000 000006FB79C2DFFF 0003e000
* WSOCK32 000006FB73AC0000 000006FB73ACFFFF 00010000
* WS2_32 000006FB73B60000 000006FB73BA3FFF 00044000
* WS2HELP 000006FB73B40000 000006FB73B59FFF 0001a000
* CLUSAPI 000006FB79950000 000006FB79985FFF 00036000
* RESUTILS 000006FB79B50000 000006FB79B81FFF 00032000
* USERENV 000006FB7B3F0000 000006FB7B56FFFF 00180000
* MFC42u 000006FB75490000 000006FB757F5FFF 00366000
* mswsock 000006FB73970000 000006FB73A21FFF 000b2000
* DNSAPI 000006FB7E050000 000006FB7E0BFFFF 00070000
* winrnr 000006FB7E1B0000 000006FB7E1C5FFF 00016000
* WLDAP32 000006FB7E0F0000 000006FB7E165FFF 00076000
* rasadhlp 000006FB7E1D0000 000006FB7E1E1FFF 00012000
* NTMARTA 000006FB7DA80000 000006FB7DAE1FFF 00062000
* SAMLIB 000006FBFF470000 000006FBFF497FFF 00028000
* SSNETLIB 000006FBFF3F0000 000006FBFF43BFFF 0004c000
* security 000006FB740D0000 000006FB740DBFFF 0000c000
* wshtcpip 000006FB73900000 000006FB73915FFF 00016000
* SSmsLPCn 000006FBFF0B0000 000006FBFF0CBFFF 0001c000
* SSnmPN70 000006FBE8CC0000 000006FBE8CD3FFF 00014000
* ntdsapi 000006FB7CF00000 000006FB7CF39FFF 0003a000
* kerberos 000006FB73CD0000 000006FB73DB1FFF 000e2000
* cryptdll 000006FB7CEE0000 000006FB7CEFBFFF 0001c000
* MSASN1 000006FB7C3C0000 000006FB7C3F1FFF 00032000
* SQLFTQRY 0000000041020000 0000000041093FFF 00074000
* CLBCatQ 000006FB7E1F0000 000006FB7E337FFF 00148000
* sqloledb 000006FBE9F70000 000006FBEA0D1FFF 00162000
* MSDART 000006FB79070000 000006FB790DFFFF 00070000
* COMCTL32 000006FB725B0000 000006FB72745FFF 00196000
* comdlg32 000006FB7C650000 000006FB7C70BFFF 000bc000
* SHLWAPI 000006FB7EB30000 000006FB7EBEBFFF 000bc000
* SHELL32 000006FB7ED90000 000006FB7FA09FFF 00c7a000
* MSDATL3 000006FB5DAB0000 000006FB5DAEFFFF 00040000
* comctl32 000006FB72370000 000006FB725A7FFF 00238000
* oledb32 000006FBE8F90000 000006FBE90E5FFF 00156000
* OLEDB32R 000006FBFECA0000 000006FBFECB3FFF 00014000
* xpstar 000006FBE9A90000 000006FBE9B65FFF 000d6000
* SQLRESLD 000000001C000000 000000001C015FFF 00016000
* SQLSVC 000006FBE9A30000 000006FBE9A8BFFF 0005c000
* ODBC32 000006FBE9980000 000006FBE9A21FFF 000a2000
* odbcbcp 000006FBE9960000 000006FBE9973FFF 00014000
* W95SCM 000000001C500000 000000001C52FFFF 00030000
* SHFOLDER 000006FB7CEC0000 000006FB7CED5FFF 00016000
* odbcint 000006FBE97C0000 000006FBE97D7FFF 00018000
* SQLSVC 000006FBFED50000 000006FBFED53FFF 00004000
* xpstar 000006FBE97B0000 000006FBE97B9FFF 0000a000
* msv1_0 000006FB7DAF0000 000006FB7DB4DFFF 0005e000
* rsaenh 000000000FF90000 000000000FFF5FFF 00066000
* PSAPI 000006FB7D8B0000 000006FB7D8CDFFF 0001e000
* xpsqlbot 000006FBE4C30000 000006FBE4C41FFF 00012000
* xplog70 000006FBE43C0000 000006FBE43FBFFF 0003c000
* xplog70 000006FBE43B0000 000006FBE43B5FFF 00006000
* sqlvdi 000006FBE1E10000 000006FBE1E39FFF 0002a000
* sqlmap70 000006FBEF290000 000006FBEF2A1FFF 00012000
* NETRAP 000006FBEBCA0000 000006FBEBCB5FFF 00016000
* dbghelp 000006FB6C510000 000006FB6C737FFF 00228000
*
* DbI0: 0000000000000000:
* DbI1: 0000000000000000:
* DbI2: 0000000483048F01:
* DbI3: E00000008345B0D0:
* DbI4: 000006FB0008000B: 0820000000000000 081F58000006FB00
000001000006FB00 CCE0000000000000 66E000000006FB57 080178000006F965
* DbI5: 000006FB29552208: 0000000001637B90 00000009FFFFFFE0
00000000000A0000 0000000000000000 0000000001637B90 0000000AFFFFFFE0
* DbI6: 000006FB29552160: 0000000000000000 000000000162C790
00000004FFFFFFE0 0000000000000000 0000000000000000 000000000162C790
* DbI7: 000006FB29552608: 000000000162CFE8 0000000100000020
0000000000000052 0000000000000000 000000000162C960 00000021FFFFFFE0
* DbD0: 000006FB29552758: 0000000000000000 0000000000000000
000000000162C730 00000026FFFFFFE0 0000000000000000 0000000000000000
* DbD1: 000006FB295526B0: 0000000000000020 0000000000000000
0000000000000000 000000000162C960 00000023FFFFFFE0 0000000000000000
* DbD2: 000006FB29552410: 00000016FFFFFFE0 0000000000000000
0000000000000000 0000000001635510 0000000000000020 0000000000130001
* DbD3: 000006FB29552560: 0000000000000000 000000000162C820
0000000600000000 000000000000002E 0000000000000000 000000000162C970
* DbD4: 000006FB295524B8: 0000000000000000 0000000000000000
000000000162C960 0000001BFFFFFFE0 0000000000000000 0000000000000000
* DbD5: 000006FB29552A08: 000000000162C730 0000002FFFFFFFE0
0000000000000000 0000000000000000 000000000162CFF8 0000000000000000
* DbD6: 000006FB29552B58: 0000000000000000 0000000000000000
0000000001637B90 00000038FFFFFFE0 0000000000160000 0000000000000000
* DbD7: 000006FB29552AB0: 00000032FFFFFFE0 0000000000140000
0000000000000000 0000000001637B90 00000033FFFFFFE0 0000000000150000
* StFPSR: 000998489E744232:
* IntGp: 0000000001CE2000:
* IntT0: 000006FBD9CC2070: 000006FBEE9FD520 000006FBD9CBA37C
0000000000400000 0000000001822298 000006FBD9CBBB28 000006FBD9CBA300
* IntT1: FFFFFFFFFFFFFFFE:
* IntS0: 0000000077CB1130: 0000000077CB8960 0000000077FE2000
0000000077CB89C0 0000000077FE2000 0000000077CB8A60 0000000077FE2000
* IntS1: 000000000168FED0: 00000000007E4850 0000000001CE2000
00000000009246D0 0000000001CE2000 000000000064AE90 0000000001CE2000
* IntS2: 000006FBEE9E1170: 000006FBEE9F9DD0 000006FBEE9F3530
2E522E412E532067 000000003035392E 011801A30010000D 0000000000000000
* IntS3: 0000000000000000:
* IntV0: 0000000000000000:
* IntT2: 0000000000000040:
* IntT3: 0000000000000202:
* IntT4: 0000000000000000:
* IntSp: 000006FBD9CBF5E0: FFFFFFFFFFFFFFFE 0000000000000000
0000000000000000 0000000000788B60 0000000200000002 000006F9F50992C8
* IntTeb: 000006FBFF9EE000: 0000000000000000 000006FBCE810000
000006FBCE808000 0000000000000000 000006FBD7992010 0000000000000000
* IntT5: 0000000000000000:
* IntT6: 0000000000000000:
* IntT7: 0000000000000048:
* IntT8: 0000000000000001:
* IntT9: 0000000000000000:
* IntT10: 0000000000000000:
* IntT11: 0000000000000000:
* IntT12: 0000000000000000:
* IntT13: 0000000000000000:
* IntT14: 0000000000000000:
* IntT15: 0000000000000000:
* IntT16: 000006FBFFFDE000: 0000000000000000 FFFFFFFFFFFFFFFF
0000000000400000 0000000077FBC360 000006FBFFF80000 0000000000000000
* IntT17: 0000000000000000:
* IntT18: 000006FBD9CBF9D0: 000006F9FCEFC0E8 000006F965100C40
000006F965100C40 0000000100000001 000006FBEEA12CB0 000006F9FCEFC568
* IntT19: 000006FBD9CBF618: 000006FA00000001 000006F9F50996C8
00000000016280E0 0000000000000000 0000000000000000 000006FB12000000
* IntT20: 0000000000000000:
* IntT21: 0000000000000288:
* IntT22: 000006FBFFB03D68: 0000000000000000 000006FBEE9CF7B0
000006FBFB2B6AC0 0010016D00040004 0000002000000001 0000000000000000
* IntNats: 0000000000000000:
* Preds: 00000000000085C1:
* BrRp: 00000000004DD3D0: 000021061921E011 454E9D0007F11EAC
0000101878012819 2000000000000200 43A021001B61C801 8400648700480000
* BrS0: 0000000000000000:
* BrS1: 0000000000000000:
* BrS2: 0000000000000000:
* BrS3: 0000000000000000:
* BrS4: 0000000000000000:
* BrT0: 000006FBFFB5CFA0: 0010014F00020015 0000000100000000
000006FBFFAE1530 0010000099DEAD99 1E80C4E500000001 0000000000000000
* BrT1: 0000000000000001:
* ApUNAT: 0000000000000000:
* ApLC: 0000000000000000:
* ApEC: 0000000000000000:
* ApCCV: 00000000FFFFFFFF:
* ApDCR: 0000000000007E05:
* RsPFS: C000000000000B9D:
* RsBSP: 000006FBD9CC0250: FFFFFFFFFFFFFFFD 0000000000000001
0000000000000001 0000000001AF9CD8 0000000000000000 0000000000000000
* RsBSPSTORE: 000006FBD9CC0250: FFFFFFFFFFFFFFFD 0000000000000001
0000000000000001 0000000001AF9CD8 0000000000000000 0000000000000000
* RsRSC: 000000000000000F:
* RsRNAT: 0000000000000000:
* StIPSR: 00001013082A6018:
* StIIP: 0000000000489D00: 01C010105400E808 84152144C02020A4
01B02105484D380A 537CF9D34020E0B0 019010183C01180A 8038E1A5002060AC
* StIFS: 8000000000000B1A:
* StFCR: 0000000000000040:
* Eflag: 0000000000000202:
* SegCSD: 0000000000000000:
* SegSSD: CF3FFFFF00000000:
* Cflag: 0000060100000111:
* StFSR: 0000000000000000:
* StFIR: 0000000000000000:
* StFDR: 0000000000000000:
*
*******************************************************************************
*
----
* Short Stack Dump
* 0000000000489D00 Module(sqlservr+0000000000089D00)
(SendOdsDone+0000000000000070)
* 00000000004DD3D0 Module(sqlservr+00000000000DD3D0)
(language_exec+0000000000000B20)
* 00000000004DD690 Module(sqlservr+00000000000DD690)
(process_commands+00000000000003A0)
* 00000000004058B0 Module(sqlservr+00000000000058B0)
(ProcessWorkRequests+0000000000000A00)
* 00000000007E4960 Module(sqlservr+00000000003E4960)
(FiberStartRoutine+0000000000000110)
* 0000000077D24400 Module(kernel32+0000000000094400)
(GetDateFormatW+0000000000070070)
* 0000000077CB8990 Module(kernel32+0000000000028990)
(GetDateFormatW+0000000000004600)
* 0000000077CB8950 Module(kernel32+0000000000028950)
(GetDateFormatW+00000000000045C0)
*
----Please contact Microsoft Product Support Services
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright © SQLDev.Net 1991-2005 All rights reserved.
"wc chan" <wcchan@.discussions.microsoft.com> wrote in message
news:1626D38A-2AFB-4099-8999-13F76C324438@.microsoft.com...
> We're running Microsoft SQL Server 2000 - 8.00.818 (Intel IA-64)
> Jun 1 2003 15:32:45
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: ).
> The SQL Server was fatally aborted with the following error. Can anyone
> help?
> SqlDumpExceptionHandler: Process 222 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process..
> *
> *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 02/21/05 21:30:03 spid 222
> *
> * Exception Address = 0000000000489D00 (SendOdsDone + 0000000000000070
> Line 0+0000000000000000)
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred reading address 000000000000029C
> * Input Buffer 164 bytes -
> * EXECUTE msdb.dbo.sp_sqlagent_has_server_access @.login_name => N'hxdom0\ms
> * sql_admin'
> *
> *
> * MODULE BASE END SIZE
> * sqlservr 0000000000400000 0000000001BA5FFF
> 017a6000
> * ntdll 0000000077E70000 0000000077FF3FFF
> 00184000
> * kernel32 0000000077C90000 0000000077E5FFFF
> 001d0000
> * ADVAPI32 000006FB7FE80000 000006FB7FFDFFFF
> 00160000
> * RPCRT4 000006FB7FC60000 000006FB7FE75FFF
> 00216000
> * USER32 0000000077B30000 0000000077C89FFF
> 0015a000
> * GDI32 000006FB7FB90000 000006FB7FC5DFFF
> 000ce000
> * ole32 000006FB7E7B0000 000006FB7EB23FFF
> 00374000
> * msvcrt 000006FB7FAA0000 000006FB7FB85FFF
> 000e6000
> * OLEAUT32 000006FB7E410000 000006FB7E7A9FFF
> 0039a000
> * VERSION 000006FB7FA80000 000006FB7FA97FFF
> 00018000
> * opends60 0000000004D00000 0000000004D15FFF
> 00016000
> * sqlsort 0000000004000000 00000000040A3FFF
> 000a4000
> * MSVCIRT 000006FB5BDC0000 000006FB5BDF3FFF
> 00034000
> * IMM32 000006FB7C5F0000 000006FB7C647FFF
> 00058000
> * LPK 000006FB608C0000 000006FB608DBFFF
> 0001c000
> * USP10 000006FB76450000 000006FB7650FFFF
> 000c0000
> * sqlevn70 0000000010000000 0000000010007FFF
> 00008000
> * Secur32 000006FB7E170000 000006FB7E1A5FFF
> 00036000
> * NETAPI32 000006FB73BF0000 000006FB73CC9FFF
> 000da000
> * COMRES 000006FB7E340000 000006FB7E40BFFF
> 000cc000
> * XOLEHLP 000006FBEF110000 000006FBEF11FFFF
> 00010000
> * MSDTCPRX 000006FB5D910000 000006FB5DA5BFFF
> 0014c000
> * MSVCP60 00000000780C0000 00000000781B7FFF
> 000f8000
> * MTXCLU 000006FB79BF0000 000006FB79C2DFFF
> 0003e000
> * WSOCK32 000006FB73AC0000 000006FB73ACFFFF
> 00010000
> * WS2_32 000006FB73B60000 000006FB73BA3FFF
> 00044000
> * WS2HELP 000006FB73B40000 000006FB73B59FFF
> 0001a000
> * CLUSAPI 000006FB79950000 000006FB79985FFF
> 00036000
> * RESUTILS 000006FB79B50000 000006FB79B81FFF
> 00032000
> * USERENV 000006FB7B3F0000 000006FB7B56FFFF
> 00180000
> * MFC42u 000006FB75490000 000006FB757F5FFF
> 00366000
> * mswsock 000006FB73970000 000006FB73A21FFF
> 000b2000
> * DNSAPI 000006FB7E050000 000006FB7E0BFFFF
> 00070000
> * winrnr 000006FB7E1B0000 000006FB7E1C5FFF
> 00016000
> * WLDAP32 000006FB7E0F0000 000006FB7E165FFF
> 00076000
> * rasadhlp 000006FB7E1D0000 000006FB7E1E1FFF
> 00012000
> * NTMARTA 000006FB7DA80000 000006FB7DAE1FFF
> 00062000
> * SAMLIB 000006FBFF470000 000006FBFF497FFF
> 00028000
> * SSNETLIB 000006FBFF3F0000 000006FBFF43BFFF
> 0004c000
> * security 000006FB740D0000 000006FB740DBFFF
> 0000c000
> * wshtcpip 000006FB73900000 000006FB73915FFF
> 00016000
> * SSmsLPCn 000006FBFF0B0000 000006FBFF0CBFFF
> 0001c000
> * SSnmPN70 000006FBE8CC0000 000006FBE8CD3FFF
> 00014000
> * ntdsapi 000006FB7CF00000 000006FB7CF39FFF
> 0003a000
> * kerberos 000006FB73CD0000 000006FB73DB1FFF
> 000e2000
> * cryptdll 000006FB7CEE0000 000006FB7CEFBFFF
> 0001c000
> * MSASN1 000006FB7C3C0000 000006FB7C3F1FFF
> 00032000
> * SQLFTQRY 0000000041020000 0000000041093FFF
> 00074000
> * CLBCatQ 000006FB7E1F0000 000006FB7E337FFF
> 00148000
> * sqloledb 000006FBE9F70000 000006FBEA0D1FFF
> 00162000
> * MSDART 000006FB79070000 000006FB790DFFFF
> 00070000
> * COMCTL32 000006FB725B0000 000006FB72745FFF
> 00196000
> * comdlg32 000006FB7C650000 000006FB7C70BFFF
> 000bc000
> * SHLWAPI 000006FB7EB30000 000006FB7EBEBFFF
> 000bc000
> * SHELL32 000006FB7ED90000 000006FB7FA09FFF
> 00c7a000
> * MSDATL3 000006FB5DAB0000 000006FB5DAEFFFF
> 00040000
> * comctl32 000006FB72370000 000006FB725A7FFF
> 00238000
> * oledb32 000006FBE8F90000 000006FBE90E5FFF
> 00156000
> * OLEDB32R 000006FBFECA0000 000006FBFECB3FFF
> 00014000
> * xpstar 000006FBE9A90000 000006FBE9B65FFF
> 000d6000
> * SQLRESLD 000000001C000000 000000001C015FFF
> 00016000
> * SQLSVC 000006FBE9A30000 000006FBE9A8BFFF
> 0005c000
> * ODBC32 000006FBE9980000 000006FBE9A21FFF
> 000a2000
> * odbcbcp 000006FBE9960000 000006FBE9973FFF
> 00014000
> * W95SCM 000000001C500000 000000001C52FFFF
> 00030000
> * SHFOLDER 000006FB7CEC0000 000006FB7CED5FFF
> 00016000
> * odbcint 000006FBE97C0000 000006FBE97D7FFF
> 00018000
> * SQLSVC 000006FBFED50000 000006FBFED53FFF
> 00004000
> * xpstar 000006FBE97B0000 000006FBE97B9FFF
> 0000a000
> * msv1_0 000006FB7DAF0000 000006FB7DB4DFFF
> 0005e000
> * rsaenh 000000000FF90000 000000000FFF5FFF
> 00066000
> * PSAPI 000006FB7D8B0000 000006FB7D8CDFFF
> 0001e000
> * xpsqlbot 000006FBE4C30000 000006FBE4C41FFF
> 00012000
> * xplog70 000006FBE43C0000 000006FBE43FBFFF
> 0003c000
> * xplog70 000006FBE43B0000 000006FBE43B5FFF
> 00006000
> * sqlvdi 000006FBE1E10000 000006FBE1E39FFF
> 0002a000
> * sqlmap70 000006FBEF290000 000006FBEF2A1FFF
> 00012000
> * NETRAP 000006FBEBCA0000 000006FBEBCB5FFF
> 00016000
> * dbghelp 000006FB6C510000 000006FB6C737FFF
> 00228000
> *
> * DbI0: 0000000000000000:
> * DbI1: 0000000000000000:
> * DbI2: 0000000483048F01:
> * DbI3: E00000008345B0D0:
> * DbI4: 000006FB0008000B: 0820000000000000 081F58000006FB00
> 000001000006FB00 CCE0000000000000 66E000000006FB57 080178000006F965
> * DbI5: 000006FB29552208: 0000000001637B90 00000009FFFFFFE0
> 00000000000A0000 0000000000000000 0000000001637B90 0000000AFFFFFFE0
> * DbI6: 000006FB29552160: 0000000000000000 000000000162C790
> 00000004FFFFFFE0 0000000000000000 0000000000000000 000000000162C790
> * DbI7: 000006FB29552608: 000000000162CFE8 0000000100000020
> 0000000000000052 0000000000000000 000000000162C960 00000021FFFFFFE0
> * DbD0: 000006FB29552758: 0000000000000000 0000000000000000
> 000000000162C730 00000026FFFFFFE0 0000000000000000 0000000000000000
> * DbD1: 000006FB295526B0: 0000000000000020 0000000000000000
> 0000000000000000 000000000162C960 00000023FFFFFFE0 0000000000000000
> * DbD2: 000006FB29552410: 00000016FFFFFFE0 0000000000000000
> 0000000000000000 0000000001635510 0000000000000020 0000000000130001
> * DbD3: 000006FB29552560: 0000000000000000 000000000162C820
> 0000000600000000 000000000000002E 0000000000000000 000000000162C970
> * DbD4: 000006FB295524B8: 0000000000000000 0000000000000000
> 000000000162C960 0000001BFFFFFFE0 0000000000000000 0000000000000000
> * DbD5: 000006FB29552A08: 000000000162C730 0000002FFFFFFFE0
> 0000000000000000 0000000000000000 000000000162CFF8 0000000000000000
> * DbD6: 000006FB29552B58: 0000000000000000 0000000000000000
> 0000000001637B90 00000038FFFFFFE0 0000000000160000 0000000000000000
> * DbD7: 000006FB29552AB0: 00000032FFFFFFE0 0000000000140000
> 0000000000000000 0000000001637B90 00000033FFFFFFE0 0000000000150000
> * StFPSR: 000998489E744232:
> * IntGp: 0000000001CE2000:
> * IntT0: 000006FBD9CC2070: 000006FBEE9FD520 000006FBD9CBA37C
> 0000000000400000 0000000001822298 000006FBD9CBBB28 000006FBD9CBA300
> * IntT1: FFFFFFFFFFFFFFFE:
> * IntS0: 0000000077CB1130: 0000000077CB8960 0000000077FE2000
> 0000000077CB89C0 0000000077FE2000 0000000077CB8A60 0000000077FE2000
> * IntS1: 000000000168FED0: 00000000007E4850 0000000001CE2000
> 00000000009246D0 0000000001CE2000 000000000064AE90 0000000001CE2000
> * IntS2: 000006FBEE9E1170: 000006FBEE9F9DD0 000006FBEE9F3530
> 2E522E412E532067 000000003035392E 011801A30010000D 0000000000000000
> * IntS3: 0000000000000000:
> * IntV0: 0000000000000000:
> * IntT2: 0000000000000040:
> * IntT3: 0000000000000202:
> * IntT4: 0000000000000000:
> * IntSp: 000006FBD9CBF5E0: FFFFFFFFFFFFFFFE 0000000000000000
> 0000000000000000 0000000000788B60 0000000200000002 000006F9F50992C8
> * IntTeb: 000006FBFF9EE000: 0000000000000000 000006FBCE810000
> 000006FBCE808000 0000000000000000 000006FBD7992010 0000000000000000
> * IntT5: 0000000000000000:
> * IntT6: 0000000000000000:
> * IntT7: 0000000000000048:
> * IntT8: 0000000000000001:
> * IntT9: 0000000000000000:
> * IntT10: 0000000000000000:
> * IntT11: 0000000000000000:
> * IntT12: 0000000000000000:
> * IntT13: 0000000000000000:
> * IntT14: 0000000000000000:
> * IntT15: 0000000000000000:
> * IntT16: 000006FBFFFDE000: 0000000000000000 FFFFFFFFFFFFFFFF
> 0000000000400000 0000000077FBC360 000006FBFFF80000 0000000000000000
> * IntT17: 0000000000000000:
> * IntT18: 000006FBD9CBF9D0: 000006F9FCEFC0E8 000006F965100C40
> 000006F965100C40 0000000100000001 000006FBEEA12CB0 000006F9FCEFC568
> * IntT19: 000006FBD9CBF618: 000006FA00000001 000006F9F50996C8
> 00000000016280E0 0000000000000000 0000000000000000 000006FB12000000
> * IntT20: 0000000000000000:
> * IntT21: 0000000000000288:
> * IntT22: 000006FBFFB03D68: 0000000000000000 000006FBEE9CF7B0
> 000006FBFB2B6AC0 0010016D00040004 0000002000000001 0000000000000000
> * IntNats: 0000000000000000:
> * Preds: 00000000000085C1:
> * BrRp: 00000000004DD3D0: 000021061921E011 454E9D0007F11EAC
> 0000101878012819 2000000000000200 43A021001B61C801 8400648700480000
> * BrS0: 0000000000000000:
> * BrS1: 0000000000000000:
> * BrS2: 0000000000000000:
> * BrS3: 0000000000000000:
> * BrS4: 0000000000000000:
> * BrT0: 000006FBFFB5CFA0: 0010014F00020015 0000000100000000
> 000006FBFFAE1530 0010000099DEAD99 1E80C4E500000001 0000000000000000
> * BrT1: 0000000000000001:
> * ApUNAT: 0000000000000000:
> * ApLC: 0000000000000000:
> * ApEC: 0000000000000000:
> * ApCCV: 00000000FFFFFFFF:
> * ApDCR: 0000000000007E05:
> * RsPFS: C000000000000B9D:
> * RsBSP: 000006FBD9CC0250: FFFFFFFFFFFFFFFD 0000000000000001
> 0000000000000001 0000000001AF9CD8 0000000000000000 0000000000000000
> * RsBSPSTORE: 000006FBD9CC0250: FFFFFFFFFFFFFFFD 0000000000000001
> 0000000000000001 0000000001AF9CD8 0000000000000000 0000000000000000
> * RsRSC: 000000000000000F:
> * RsRNAT: 0000000000000000:
> * StIPSR: 00001013082A6018:
> * StIIP: 0000000000489D00: 01C010105400E808 84152144C02020A4
> 01B02105484D380A 537CF9D34020E0B0 019010183C01180A 8038E1A5002060AC
> * StIFS: 8000000000000B1A:
> * StFCR: 0000000000000040:
> * Eflag: 0000000000000202:
> * SegCSD: 0000000000000000:
> * SegSSD: CF3FFFFF00000000:
> * Cflag: 0000060100000111:
> * StFSR: 0000000000000000:
> * StFIR: 0000000000000000:
> * StFDR: 0000000000000000:
> *
> *******************************************************************************
> *
> ----
> * Short Stack Dump
> * 0000000000489D00 Module(sqlservr+0000000000089D00)
> (SendOdsDone+0000000000000070)
> * 00000000004DD3D0 Module(sqlservr+00000000000DD3D0)
> (language_exec+0000000000000B20)
> * 00000000004DD690 Module(sqlservr+00000000000DD690)
> (process_commands+00000000000003A0)
> * 00000000004058B0 Module(sqlservr+00000000000058B0)
> (ProcessWorkRequests+0000000000000A00)
> * 00000000007E4960 Module(sqlservr+00000000003E4960)
> (FiberStartRoutine+0000000000000110)
> * 0000000077D24400 Module(kernel32+0000000000094400)
> (GetDateFormatW+0000000000070070)
> * 0000000077CB8990 Module(kernel32+0000000000028990)
> (GetDateFormatW+0000000000004600)
> * 0000000077CB8950 Module(kernel32+0000000000028950)
> (GetDateFormatW+00000000000045C0)
> *
> ----
Fatal Error 7105 ... text, ntext, or image node does not exist
I'm getting the following in error in Enterprise Manager:
Fatal Error 7105 ... text, ntext, or image node does not exist
It seems that a row in a table has become corrupt or something because when
I try to query for that row or scroll down in the table to view the row (the
preceding rows display fine), that is when I get this error. Can a row that
causes this error be salvaged or deleted or something? It seems it is this
one row that is causing the problem. Is that right?
I found this KB article that suggests applying a hotfix.
http://support.microsoft.com/kb/890755
The hotfix seems to have come out between SP 3a & SP 4. I already have
Service Pack 4 installed, so I'm wondering if this proposed hotfix is already
part of SP 4 or if I should try to apply the hotfix?
I don't want to mess up my box, but I need this error resolved.
If anyone can offer furter advice, I would appreciated (and then I can get a
broken app back up and running).
Thanks
I have a correction to my post.
I'm getting the following error in Enterprise Manager:
[Microsoft][ODBC SQL Server Driver][SQL Server]Page (1:6890), slot 35 for
text, ntext, or image node does not exist.
In my web app, the error is:
Fatal Error 7105 ... text, ntext, or image node does not exist
Fatal Error 7105 ... text, ntext, or image node does not exist
It seems that a row in a table has become corrupt or something because when
I try to query for that row or scroll down in the table to view the row (the
preceding rows display fine), that is when I get this error. Can a row that
causes this error be salvaged or deleted or something? It seems it is this
one row that is causing the problem. Is that right?
I found this KB article that suggests applying a hotfix.
http://support.microsoft.com/kb/890755
The hotfix seems to have come out between SP 3a & SP 4. I already have
Service Pack 4 installed, so I'm wondering if this proposed hotfix is already
part of SP 4 or if I should try to apply the hotfix?
I don't want to mess up my box, but I need this error resolved.
If anyone can offer furter advice, I would appreciated (and then I can get a
broken app back up and running).
Thanks
I have a correction to my post.
I'm getting the following error in Enterprise Manager:
[Microsoft][ODBC SQL Server Driver][SQL Server]Page (1:6890), slot 35 for
text, ntext, or image node does not exist.
In my web app, the error is:
Fatal Error 7105 ... text, ntext, or image node does not exist
Fatal Error 7105 ... text, ntext, or image node does not exist
I'm getting the following in error in Enterprise Manager:
Fatal Error 7105 ... text, ntext, or image node does not exist
It seems that a row in a table has become corrupt or something because when
I try to query for that row or scroll down in the table to view the row (the
preceding rows display fine), that is when I get this error. Can a row that
causes this error be salvaged or deleted or something? It seems it is this
one row that is causing the problem. Is that right?
I found this KB article that suggests applying a hotfix.
http://support.microsoft.com/kb/890755
The hotfix seems to have come out between SP 3a & SP 4. I already have
Service Pack 4 installed, so I'm wondering if this proposed hotfix is alread
y
part of SP 4 or if I should try to apply the hotfix?
I don't want to mess up my box, but I need this error resolved.
If anyone can offer furter advice, I would appreciated (and then I can get a
broken app back up and running).
ThanksI have a correction to my post.
I'm getting the following error in Enterprise Manager:
[Microsoft][ODBC SQL Server Driver][SQL Server]Page (1:6890), sl
ot 35 for
text, ntext, or image node does not exist.
In my web app, the error is:
Fatal Error 7105 ... text, ntext, or image node does not exist
Fatal Error 7105 ... text, ntext, or image node does not exist
It seems that a row in a table has become corrupt or something because when
I try to query for that row or scroll down in the table to view the row (the
preceding rows display fine), that is when I get this error. Can a row that
causes this error be salvaged or deleted or something? It seems it is this
one row that is causing the problem. Is that right?
I found this KB article that suggests applying a hotfix.
http://support.microsoft.com/kb/890755
The hotfix seems to have come out between SP 3a & SP 4. I already have
Service Pack 4 installed, so I'm wondering if this proposed hotfix is alread
y
part of SP 4 or if I should try to apply the hotfix?
I don't want to mess up my box, but I need this error resolved.
If anyone can offer furter advice, I would appreciated (and then I can get a
broken app back up and running).
ThanksI have a correction to my post.
I'm getting the following error in Enterprise Manager:
[Microsoft][ODBC SQL Server Driver][SQL Server]Page (1:6890), sl
ot 35 for
text, ntext, or image node does not exist.
In my web app, the error is:
Fatal Error 7105 ... text, ntext, or image node does not exist
Fatal Error 7105 ... text, ntext, or image node does not exist
I'm getting the following in error in Enterprise Manager:
Fatal Error 7105 ... text, ntext, or image node does not exist
It seems that a row in a table has become corrupt or something because when
I try to query for that row or scroll down in the table to view the row (the
preceding rows display fine), that is when I get this error. Can a row that
causes this error be salvaged or deleted or something? It seems it is this
one row that is causing the problem. Is that right?
I found this KB article that suggests applying a hotfix.
http://support.microsoft.com/kb/890755
The hotfix seems to have come out between SP 3a & SP 4. I already have
Service Pack 4 installed, so I'm wondering if this proposed hotfix is already
part of SP 4 or if I should try to apply the hotfix?
I don't want to mess up my box, but I need this error resolved.
If anyone can offer furter advice, I would appreciated (and then I can get a
broken app back up and running).
ThanksI have a correction to my post.
I'm getting the following error in Enterprise Manager:
[Microsoft][ODBC SQL Server Driver][SQL Server]Page (1:6890), slot 35 for
text, ntext, or image node does not exist.
In my web app, the error is:
Fatal Error 7105 ... text, ntext, or image node does not exist
Fatal Error 7105 ... text, ntext, or image node does not exist
It seems that a row in a table has become corrupt or something because when
I try to query for that row or scroll down in the table to view the row (the
preceding rows display fine), that is when I get this error. Can a row that
causes this error be salvaged or deleted or something? It seems it is this
one row that is causing the problem. Is that right?
I found this KB article that suggests applying a hotfix.
http://support.microsoft.com/kb/890755
The hotfix seems to have come out between SP 3a & SP 4. I already have
Service Pack 4 installed, so I'm wondering if this proposed hotfix is already
part of SP 4 or if I should try to apply the hotfix?
I don't want to mess up my box, but I need this error resolved.
If anyone can offer furter advice, I would appreciated (and then I can get a
broken app back up and running).
ThanksI have a correction to my post.
I'm getting the following error in Enterprise Manager:
[Microsoft][ODBC SQL Server Driver][SQL Server]Page (1:6890), slot 35 for
text, ntext, or image node does not exist.
In my web app, the error is:
Fatal Error 7105 ... text, ntext, or image node does not exist
Monday, March 12, 2012
Fastest way to alter table structure
I'm writing a database table designer (works like the Enterprise Manager one, but with restricted datatypes and some checks), and I have a bit of a question:
To alter the structure of a table, I'm currently using the same method as Enterprise Manager (create a temporary table with the new schema, copy the data across, drop the original table, rename the temporary table).
When altering the structure of a table with a large number of rows, but not changing the order of columns or adding columns in the middle of the table:
Would it be faster to execute multiple ALTER TABLE statements? If so, at what point would it become slower? (Say, changing lots of column data types, etc).Thanks
Probably always faster using ALTER TABLE.
I really doubt that ALTER TABLE statements would be noticably slower.
|||Thanks.I was worried that if there were a lot of column data type changes there could be a lot of conversions, and a lot of overhead from going through the entire table multiple times.
|||I guess that could happen -depends upon the quantity and type of changes.
Friday, February 24, 2012
Failure to start up SQL Server
SQL fails to start up - no error message is given- in SQL Server Service
Manager or in Enterprise Manager
The problem first occurred when starting up my computer and SQL failed to
start automatically (Auto start service when OS starts check box is ticked)
Leonard wrote:
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is ticked)
and the error message is:??
|||Have alook in the event log of WIndows to see where the problem is.
Jens Suessmeyer,
"Leonard" <Leonard@.discussions.microsoft.com> schrieb im Newsbeitrag
news:8664BBA4-F8CC-417C-B732-B4E9DEE008C9@.microsoft.com...
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is
> ticked)
|||Check SQL errorlogs as well.
Adrian
"Leonard" <Leonard@.discussions.microsoft.com> wrote in message
news:8664BBA4-F8CC-417C-B732-B4E9DEE008C9@.microsoft.com...
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is
> ticked)
|||I too have this problem. There is no error message. After installing sp4,
the system reboots and starts the Service Manager but it doesn't
automatically load my server\instance name. I have to do that manually.
Event viewer logs do not show any errors.
Have you found a solution yet?
Manager or in Enterprise Manager
The problem first occurred when starting up my computer and SQL failed to
start automatically (Auto start service when OS starts check box is ticked)
Leonard wrote:
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is ticked)
and the error message is:??
|||Have alook in the event log of WIndows to see where the problem is.
Jens Suessmeyer,
"Leonard" <Leonard@.discussions.microsoft.com> schrieb im Newsbeitrag
news:8664BBA4-F8CC-417C-B732-B4E9DEE008C9@.microsoft.com...
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is
> ticked)
|||Check SQL errorlogs as well.
Adrian
"Leonard" <Leonard@.discussions.microsoft.com> wrote in message
news:8664BBA4-F8CC-417C-B732-B4E9DEE008C9@.microsoft.com...
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is
> ticked)
|||I too have this problem. There is no error message. After installing sp4,
the system reboots and starts the Service Manager but it doesn't
automatically load my server\instance name. I have to do that manually.
Event viewer logs do not show any errors.
Have you found a solution yet?
Failure to start up SQL Server
SQL fails to start up - no error message is given- in SQL Server Service
Manager or in Enterprise Manager
The problem first occurred when starting up my computer and SQL failed to
start automatically (Auto start service when OS starts check box is ticked)Leonard wrote:[vbcol=seagreen]
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is ticked)[/vbcol
]
and the error message is:'?|||Have alook in the event log of WIndows to see where the problem is.
Jens Suessmeyer,
"Leonard" <Leonard@.discussions.microsoft.com> schrieb im Newsbeitrag
news:8664BBA4-F8CC-417C-B732-B4E9DEE008C9@.microsoft.com...
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is
> ticked)|||Check SQL errorlogs as well.
Adrian
"Leonard" <Leonard@.discussions.microsoft.com> wrote in message
news:8664BBA4-F8CC-417C-B732-B4E9DEE008C9@.microsoft.com...
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is
> ticked)|||I too have this problem. There is no error message. After installing sp4,
the system reboots and starts the Service Manager but it doesn't
automatically load my server\instance name. I have to do that manually.
Event viewer logs do not show any errors.
Have you found a solution yet?
Manager or in Enterprise Manager
The problem first occurred when starting up my computer and SQL failed to
start automatically (Auto start service when OS starts check box is ticked)Leonard wrote:[vbcol=seagreen]
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is ticked)[/vbcol
]
and the error message is:'?|||Have alook in the event log of WIndows to see where the problem is.
Jens Suessmeyer,
"Leonard" <Leonard@.discussions.microsoft.com> schrieb im Newsbeitrag
news:8664BBA4-F8CC-417C-B732-B4E9DEE008C9@.microsoft.com...
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is
> ticked)|||Check SQL errorlogs as well.
Adrian
"Leonard" <Leonard@.discussions.microsoft.com> wrote in message
news:8664BBA4-F8CC-417C-B732-B4E9DEE008C9@.microsoft.com...
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is
> ticked)|||I too have this problem. There is no error message. After installing sp4,
the system reboots and starts the Service Manager but it doesn't
automatically load my server\instance name. I have to do that manually.
Event viewer logs do not show any errors.
Have you found a solution yet?
Failure to start up SQL Server
SQL fails to start up - no error message is given- in SQL Server Service
Manager or in Enterprise Manager
The problem first occurred when starting up my computer and SQL failed to
start automatically (Auto start service when OS starts check box is ticked)Leonard wrote:
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is ticked)
and the error message is:'?|||Have alook in the event log of WIndows to see where the problem is.
Jens Suessmeyer,
"Leonard" <Leonard@.discussions.microsoft.com> schrieb im Newsbeitrag
news:8664BBA4-F8CC-417C-B732-B4E9DEE008C9@.microsoft.com...
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is
> ticked)|||Check SQL errorlogs as well.
Adrian
"Leonard" <Leonard@.discussions.microsoft.com> wrote in message
news:8664BBA4-F8CC-417C-B732-B4E9DEE008C9@.microsoft.com...
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is
> ticked)|||I too have this problem. There is no error message. After installing sp4,
the system reboots and starts the Service Manager but it doesn't
automatically load my server\instance name. I have to do that manually.
Event viewer logs do not show any errors.
Have you found a solution yet?
Manager or in Enterprise Manager
The problem first occurred when starting up my computer and SQL failed to
start automatically (Auto start service when OS starts check box is ticked)Leonard wrote:
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is ticked)
and the error message is:'?|||Have alook in the event log of WIndows to see where the problem is.
Jens Suessmeyer,
"Leonard" <Leonard@.discussions.microsoft.com> schrieb im Newsbeitrag
news:8664BBA4-F8CC-417C-B732-B4E9DEE008C9@.microsoft.com...
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is
> ticked)|||Check SQL errorlogs as well.
Adrian
"Leonard" <Leonard@.discussions.microsoft.com> wrote in message
news:8664BBA4-F8CC-417C-B732-B4E9DEE008C9@.microsoft.com...
> SQL fails to start up - no error message is given- in SQL Server Service
> Manager or in Enterprise Manager
> The problem first occurred when starting up my computer and SQL failed to
> start automatically (Auto start service when OS starts check box is
> ticked)|||I too have this problem. There is no error message. After installing sp4,
the system reboots and starts the Service Manager but it doesn't
automatically load my server\instance name. I have to do that manually.
Event viewer logs do not show any errors.
Have you found a solution yet?
Sunday, February 19, 2012
failure installing SQL Server 2005
I am trying to install SQL Server Sept 2005 on Windows Server Enterprise Ed. 2003 which was just freshly installed on a new partition. I downloaded files from a DVD and when I click on install.exe it checks the system configuration: everything is OK (all checks passed) but then I get a window/message:
"The installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows installation package."
It is a DVD I got as a part of my MSDN Pro subscription from MS. What else can I do about it?
Thanks.Hi,
did you try to copy the installation files to hdd and install from there? You also may ask the msdn support:
http://msdn.microsoft.com/subscriptions/support/default.aspx|||Are you installing on a virtual machine by any chance? Andrew Watt MVP - InfoPath wrote in message news:2a922efb-0221-4c8d-9771-2ebb57bfaa3b@.discussions.microsoft.com... >I am trying to install SQL Server Sept 2005 on Windows Server Enterprise
> Ed. 2003 which was just freshly installed on a new partition. I
> downloaded files from a DVD and when I click on install.exe it checks
> the system configuration: everything is OK (all checks passed) but then
> I get a window/message: >
> "The installation package could not be opened. Verify that the package
> exists and that you can access it, or contact the application vendor to
> verify that this is a valid Windows installation package." >
> It is a DVD I got as a part of my MSDN Pro subscription from MS. What
> else can I do about it? >
> Thanks. >
>|||Thanks,
The installation files are on HDD as of now. I am clicking on install.exe which is on the partition. I do not quite remember how they ended up there when I first used a DVD to install it and something went wrong, I aborted the attempt then but it gave me no other choice. Perhaps I felt that some other issues could have been responsible. I just installed the Win Server 2003 and some drivers were still missing, so I spent the next two days hunting for them.
Going to msdn support is the last resort. I will do it when all other avenues are exhausted.
Thanks again.|||No, it is a physical partition. I have already installed the SQL Server 2005 yesterday after I posted my last message. I do not know what the problem was initially, most likely the fact that the WINSer2003 did not have all set of drivers and therefore the download could not even access the Internet.
Anyway, I am using this to ask another question. My work now is hampered by the fact that I could not find a driver for my Dell 2001FP monitor to exercise the full resolution of 1600x1200. The driver I found provides only 1280x1024 as the highest.
I contacted Dell and they said that neither Dell nor Microsoft have drivers for Windows 2003 Server.
I am thinking about writing a driver myself but with no experience in drivers and total lack of concept do not know where to start. Anybody could offer any pointers?
Thanks.
Subscribe to:
Posts (Atom)