Hello
We have made a database installed it on MS SQL server version 8.0.0.760 (SP3) running on Win NT 4.0 (SP6a) danish. The database is accessed from a program made with delphi 6, and it uses BDE.
The problem is when we start the program, it says :
Field 'V=E6rdi' not found.
This field is accessed by a view called Xsystem:
which contain: select * from Xtable.
This problem is not found on another PC runnig Windows 2000 (sp3). On this PC it work fine.
Any Help pleaseHi,
TRY FOR TEST
CREATE VIEW TESTVIEW AS
SELECT "Værdi" AS Vaerdi from Xtable
>We have made a database installed it on MS SQL server
>version 8.0.0.760 (SP3) running on Win NT 4.0 (SP6a)
>danish. The database is accessed from a program made with
>delphi 6, and it uses BDE.
Check version of Middlewares
MDAC
BDE
--
SHINICHI YONEDA MXL04371@.nifty.ne.jp
Microsoft Most Valuable Professional
MVP for SQL Server 2002-2003|||Thank you Mr. SHINICHI YONEDA for your reply.
I will try this.
>--Original Message--
>Hi,
> TRY FOR TEST
>CREATE VIEW TESTVIEW AS
>SELECT "V=E6rdi" AS Vaerdi from Xtable
>>We have made a database installed it on MS SQL server
>>version 8.0.0.760 (SP3) running on Win NT 4.0 (SP6a)
>>danish. The database is accessed from a program made with
>>delphi 6, and it uses BDE.
> Check version of Middlewares
>MDAC
>BDE
>--
>SHINICHI YONEDA MXL04371@.nifty.ne.jp
>Microsoft Most Valuable Professional
>MVP for SQL Server 2002-2003
>.
>
Showing posts with label running. Show all posts
Showing posts with label running. Show all posts
Thursday, March 29, 2012
'field name' is not a recognized OPTIMIZER LOCK HINTS option
I get 'field name' is not a recognized OPTIMIZER LOCK HINTS option
when running the following query:
select
(SELECT
listdate FROM DateList2(ejDateBeg, epDateBeg, eeDateBeg,
euDateMod, HRTimeStamp) AS ChangeDate
FROM tablea Emp INNER JOIN Tableb HR
ON Emp.col1= HR.col1)
The function DateList2 is defined as so:
create FUNCTION [dbo].[DateList]
(
@.date1 smalldatetime,
@.date2 smalldatetime,
@.date3 smalldatetime,
@.date4 smalldatetime,
@.date5 smalldatetime
)
RETURNS TABLE
AS
RETURN
(
-- Add the SELECT statement with parameter references here
SELECT @.date1 as ListDate UNION
SELECT @.date2 as ListDate UNION
SELECT @.date3 as ListDate UNION
SELECT @.date4 as ListDate UNION
SELECT @.date5 as ListDate
)
The intent is to grab the highest date form a set of 5 dates that come from
either tablea or tableb and pass it as ChangeDate.
Any assistance would be appreciated.
Thanks,
DaveHi Dave
My guess is that the parser thinks DateList2 is a table, not a function, so
the parens following the name are thought to be a hint.
User defined functions must be qualified with their owner name to help the
parser distinguish them from tables. For example, if the owner of the
function is dbo, you can do this:
select
( SELECT
listdate FROM dbo.DateList2(ejDateBeg, epDateBeg, eeDateBeg,
euDateMod, HRTimeStamp) AS ChangeDate
...
HTH
Kalen Delaney, SQL Server MVP
"Dave Sundell" <DaveSundell@.discussions.microsoft.com> wrote in message
news:FE9D8229-391D-4823-8079-D7CDD8155A5C@.microsoft.com...
>I get 'field name' is not a recognized OPTIMIZER LOCK HINTS option
> when running the following query:
> select
> (SELECT
> listdate FROM DateList2(ejDateBeg, epDateBeg, eeDateBeg,
> euDateMod, HRTimeStamp) AS ChangeDate
> FROM tablea Emp INNER JOIN Tableb HR
> ON Emp.col1= HR.col1)
> The function DateList2 is defined as so:
> create FUNCTION [dbo].[DateList]
> (
> @.date1 smalldatetime,
> @.date2 smalldatetime,
> @.date3 smalldatetime,
> @.date4 smalldatetime,
> @.date5 smalldatetime
> )
> RETURNS TABLE
> AS
> RETURN
> (
> -- Add the SELECT statement with parameter references here
> SELECT @.date1 as ListDate UNION
> SELECT @.date2 as ListDate UNION
> SELECT @.date3 as ListDate UNION
> SELECT @.date4 as ListDate UNION
> SELECT @.date5 as ListDate
> )
> The intent is to grab the highest date form a set of 5 dates that come
> from
> either tablea or tableb and pass it as ChangeDate.
> Any assistance would be appreciated.
> Thanks,
> Dave|||karen,
Thanks for responding. I did put dbo. and it still didn't work. It is like
the compiler is getting lost.
Dave
"Kalen Delaney" wrote:
> Hi Dave
> My guess is that the parser thinks DateList2 is a table, not a function, s
o
> the parens following the name are thought to be a hint.
> User defined functions must be qualified with their owner name to help th
e
> parser distinguish them from tables. For example, if the owner of the
> function is dbo, you can do this:
> select
> ( SELECT
> listdate FROM dbo.DateList2(ejDateBeg, epDateBeg, eeDateBeg,
> euDateMod, HRTimeStamp) AS ChangeDate
> ....
>
> --
> HTH
> Kalen Delaney, SQL Server MVP
>
> "Dave Sundell" <DaveSundell@.discussions.microsoft.com> wrote in message
> news:FE9D8229-391D-4823-8079-D7CDD8155A5C@.microsoft.com...
>
>|||One more thing. I even hardcoded dates, '1/1/2006' or passed null and it wor
ks.
"Dave Sundell" wrote:
> karen,
> Thanks for responding. I did put dbo. and it still didn't work. It is like
> the compiler is getting lost.
> Dave
> "Kalen Delaney" wrote:
>|||Dave,
In SQL Server 2000, you cannot pass a column to a table-valued
function. SQL Server 2000 can't handle a correlated table source,
but SQL Server 2005 can, if you use the APPLY operator.
It doesn't look to me as though what you are doing will work
anyway, since dbo.DateList may contain as many as 5 rows, and
if it does contain more than one, the sub-SELECT will raise an
error.
Try something like this if you are using 2000.
select
thisCol, thatCol,
(
select top 1 listdate from (
(select ejDateBeg as listdate union all
select epDateBeg union all select eeDateBeg
union all select euDateMod union all select HRTimeStamp
) as T
order by listdate desc
) as ChangeDate
from tablea as Emp ...
If this doesn't work (and I vaguely recall some quirks in
SQL Server 2000 when things are nested this deeply), please
post the CREATE TABLE statements and sample data sufficient
to reproduce the scenario (http://www.aspfaq.com/etiquette.asp?id=5006)
Steve Kass
Drew University
Dave Sundell wrote:
>I get 'field name' is not a recognized OPTIMIZER LOCK HINTS option
>when running the following query:
>select
>(SELECT
> listdate FROM DateList2(ejDateBeg, epDateBeg, eeDateBeg,
>euDateMod, HRTimeStamp) AS ChangeDate
>FROM tablea Emp INNER JOIN Tableb HR
> ON Emp.col1= HR.col1)
>The function DateList2 is defined as so:
>create FUNCTION [dbo].[DateList]
>(
> @.date1 smalldatetime,
> @.date2 smalldatetime,
> @.date3 smalldatetime,
> @.date4 smalldatetime,
> @.date5 smalldatetime
> )
>RETURNS TABLE
>AS
>RETURN
>(
> -- Add the SELECT statement with parameter references here
> SELECT @.date1 as ListDate UNION
> SELECT @.date2 as ListDate UNION
> SELECT @.date3 as ListDate UNION
> SELECT @.date4 as ListDate UNION
> SELECT @.date5 as ListDate
> )
>The intent is to grab the highest date form a set of 5 dates that come from
>either tablea or tableb and pass it as ChangeDate.
>Any assistance would be appreciated.
>Thanks,
>Dave
>|||You cannot pass columns as params for a Table valued UDF.
For fixing it, since you need only one value from that function, you can use
a scalar valued function.
Your query (as you have provided) will however work is SQL Server 2005 as
long as the UDF returns only one row.
Maybe you would want to go through this discussion :)
http://groups.google.co.in/group/mi...4b44dbec88e80d6
Hope this helps.
--
-Omnibuzz (The SQL GC)
http://omnibuzz-sql.blogspot.com/|||Thanks to all (Karen, Steve, OmniBuzz) that responded. You were all a big he
lp.
Dave
"Omnibuzz" wrote:
> You cannot pass columns as params for a Table valued UDF.
> For fixing it, since you need only one value from that function, you can u
se
> a scalar valued function.
> Your query (as you have provided) will however work is SQL Server 2005 as
> long as the UDF returns only one row.
> Maybe you would want to go through this discussion :)
> http://groups.google.co.in/group/mi...4b44dbec88e80d6
> Hope this helps.
> --
> -Omnibuzz (The SQL GC)
> http://omnibuzz-sql.blogspot.com/
>
when running the following query:
select
(SELECT
listdate FROM DateList2(ejDateBeg, epDateBeg, eeDateBeg,
euDateMod, HRTimeStamp) AS ChangeDate
FROM tablea Emp INNER JOIN Tableb HR
ON Emp.col1= HR.col1)
The function DateList2 is defined as so:
create FUNCTION [dbo].[DateList]
(
@.date1 smalldatetime,
@.date2 smalldatetime,
@.date3 smalldatetime,
@.date4 smalldatetime,
@.date5 smalldatetime
)
RETURNS TABLE
AS
RETURN
(
-- Add the SELECT statement with parameter references here
SELECT @.date1 as ListDate UNION
SELECT @.date2 as ListDate UNION
SELECT @.date3 as ListDate UNION
SELECT @.date4 as ListDate UNION
SELECT @.date5 as ListDate
)
The intent is to grab the highest date form a set of 5 dates that come from
either tablea or tableb and pass it as ChangeDate.
Any assistance would be appreciated.
Thanks,
DaveHi Dave
My guess is that the parser thinks DateList2 is a table, not a function, so
the parens following the name are thought to be a hint.
User defined functions must be qualified with their owner name to help the
parser distinguish them from tables. For example, if the owner of the
function is dbo, you can do this:
select
( SELECT
listdate FROM dbo.DateList2(ejDateBeg, epDateBeg, eeDateBeg,
euDateMod, HRTimeStamp) AS ChangeDate
...
HTH
Kalen Delaney, SQL Server MVP
"Dave Sundell" <DaveSundell@.discussions.microsoft.com> wrote in message
news:FE9D8229-391D-4823-8079-D7CDD8155A5C@.microsoft.com...
>I get 'field name' is not a recognized OPTIMIZER LOCK HINTS option
> when running the following query:
> select
> (SELECT
> listdate FROM DateList2(ejDateBeg, epDateBeg, eeDateBeg,
> euDateMod, HRTimeStamp) AS ChangeDate
> FROM tablea Emp INNER JOIN Tableb HR
> ON Emp.col1= HR.col1)
> The function DateList2 is defined as so:
> create FUNCTION [dbo].[DateList]
> (
> @.date1 smalldatetime,
> @.date2 smalldatetime,
> @.date3 smalldatetime,
> @.date4 smalldatetime,
> @.date5 smalldatetime
> )
> RETURNS TABLE
> AS
> RETURN
> (
> -- Add the SELECT statement with parameter references here
> SELECT @.date1 as ListDate UNION
> SELECT @.date2 as ListDate UNION
> SELECT @.date3 as ListDate UNION
> SELECT @.date4 as ListDate UNION
> SELECT @.date5 as ListDate
> )
> The intent is to grab the highest date form a set of 5 dates that come
> from
> either tablea or tableb and pass it as ChangeDate.
> Any assistance would be appreciated.
> Thanks,
> Dave|||karen,
Thanks for responding. I did put dbo. and it still didn't work. It is like
the compiler is getting lost.
Dave
"Kalen Delaney" wrote:
> Hi Dave
> My guess is that the parser thinks DateList2 is a table, not a function, s
o
> the parens following the name are thought to be a hint.
> User defined functions must be qualified with their owner name to help th
e
> parser distinguish them from tables. For example, if the owner of the
> function is dbo, you can do this:
> select
> ( SELECT
> listdate FROM dbo.DateList2(ejDateBeg, epDateBeg, eeDateBeg,
> euDateMod, HRTimeStamp) AS ChangeDate
> ....
>
> --
> HTH
> Kalen Delaney, SQL Server MVP
>
> "Dave Sundell" <DaveSundell@.discussions.microsoft.com> wrote in message
> news:FE9D8229-391D-4823-8079-D7CDD8155A5C@.microsoft.com...
>
>|||One more thing. I even hardcoded dates, '1/1/2006' or passed null and it wor
ks.
"Dave Sundell" wrote:
> karen,
> Thanks for responding. I did put dbo. and it still didn't work. It is like
> the compiler is getting lost.
> Dave
> "Kalen Delaney" wrote:
>|||Dave,
In SQL Server 2000, you cannot pass a column to a table-valued
function. SQL Server 2000 can't handle a correlated table source,
but SQL Server 2005 can, if you use the APPLY operator.
It doesn't look to me as though what you are doing will work
anyway, since dbo.DateList may contain as many as 5 rows, and
if it does contain more than one, the sub-SELECT will raise an
error.
Try something like this if you are using 2000.
select
thisCol, thatCol,
(
select top 1 listdate from (
(select ejDateBeg as listdate union all
select epDateBeg union all select eeDateBeg
union all select euDateMod union all select HRTimeStamp
) as T
order by listdate desc
) as ChangeDate
from tablea as Emp ...
If this doesn't work (and I vaguely recall some quirks in
SQL Server 2000 when things are nested this deeply), please
post the CREATE TABLE statements and sample data sufficient
to reproduce the scenario (http://www.aspfaq.com/etiquette.asp?id=5006)
Steve Kass
Drew University
Dave Sundell wrote:
>I get 'field name' is not a recognized OPTIMIZER LOCK HINTS option
>when running the following query:
>select
>(SELECT
> listdate FROM DateList2(ejDateBeg, epDateBeg, eeDateBeg,
>euDateMod, HRTimeStamp) AS ChangeDate
>FROM tablea Emp INNER JOIN Tableb HR
> ON Emp.col1= HR.col1)
>The function DateList2 is defined as so:
>create FUNCTION [dbo].[DateList]
>(
> @.date1 smalldatetime,
> @.date2 smalldatetime,
> @.date3 smalldatetime,
> @.date4 smalldatetime,
> @.date5 smalldatetime
> )
>RETURNS TABLE
>AS
>RETURN
>(
> -- Add the SELECT statement with parameter references here
> SELECT @.date1 as ListDate UNION
> SELECT @.date2 as ListDate UNION
> SELECT @.date3 as ListDate UNION
> SELECT @.date4 as ListDate UNION
> SELECT @.date5 as ListDate
> )
>The intent is to grab the highest date form a set of 5 dates that come from
>either tablea or tableb and pass it as ChangeDate.
>Any assistance would be appreciated.
>Thanks,
>Dave
>|||You cannot pass columns as params for a Table valued UDF.
For fixing it, since you need only one value from that function, you can use
a scalar valued function.
Your query (as you have provided) will however work is SQL Server 2005 as
long as the UDF returns only one row.
Maybe you would want to go through this discussion :)
http://groups.google.co.in/group/mi...4b44dbec88e80d6
Hope this helps.
--
-Omnibuzz (The SQL GC)
http://omnibuzz-sql.blogspot.com/|||Thanks to all (Karen, Steve, OmniBuzz) that responded. You were all a big he
lp.
Dave
"Omnibuzz" wrote:
> You cannot pass columns as params for a Table valued UDF.
> For fixing it, since you need only one value from that function, you can u
se
> a scalar valued function.
> Your query (as you have provided) will however work is SQL Server 2005 as
> long as the UDF returns only one row.
> Maybe you would want to go through this discussion :)
> http://groups.google.co.in/group/mi...4b44dbec88e80d6
> Hope this helps.
> --
> -Omnibuzz (The SQL GC)
> http://omnibuzz-sql.blogspot.com/
>
Tuesday, March 27, 2012
Fiber Mode
Hi...can someone explain to me what fiber mode is, and how can I tell if my
instance of SQL Server is running in fiber mode
Thanks.An instance of the database engine is in fiber mode if the option
lightweight pooling is set to 1. You can see the setting of that option
using sp_configure or Enterprise Manager. It is an advanced option, so you
have to have the sp_configure show advanced options setting turned on.
There are a set of topics in the SQL Server 2000 Books Online that discuss
how the database engine uses Windows threads and fibers under this node:
http://msdn.microsoft.com/library/d...asp?frame=true
Fiber mode is specifically discussed in this topic:
http://msdn.microsoft.com/library/d...asp?frame=true
Most instances of the database engine are not run in fiber mode, most of the
time the instance runs fine without using fibers.
Alan Brewer [MSFT]
Lead programming Writer
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
instance of SQL Server is running in fiber mode
Thanks.An instance of the database engine is in fiber mode if the option
lightweight pooling is set to 1. You can see the setting of that option
using sp_configure or Enterprise Manager. It is an advanced option, so you
have to have the sp_configure show advanced options setting turned on.
There are a set of topics in the SQL Server 2000 Books Online that discuss
how the database engine uses Windows threads and fibers under this node:
http://msdn.microsoft.com/library/d...asp?frame=true
Fiber mode is specifically discussed in this topic:
http://msdn.microsoft.com/library/d...asp?frame=true
Most instances of the database engine are not run in fiber mode, most of the
time the instance runs fine without using fibers.
Alan Brewer [MSFT]
Lead programming Writer
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
Fiber Mode
Hi...can someone explain to me what fiber mode is, and how can I tell if my
instance of SQL Server is running in fiber mode
Thanks.An instance of the database engine is in fiber mode if the option
lightweight pooling is set to 1. You can see the setting of that option
using sp_configure or Enterprise Manager. It is an advanced option, so you
have to have the sp_configure show advanced options setting turned on.
There are a set of topics in the SQL Server 2000 Books Online that discuss
how the database engine uses Windows threads and fibers under this node:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_sa_0w6d.asp?frame=true
Fiber mode is specifically discussed in this topic:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_sa_9m9f.asp?frame=true
Most instances of the database engine are not run in fiber mode, most of the
time the instance runs fine without using fibers.
--
Alan Brewer [MSFT]
Lead Programming Writer
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
instance of SQL Server is running in fiber mode
Thanks.An instance of the database engine is in fiber mode if the option
lightweight pooling is set to 1. You can see the setting of that option
using sp_configure or Enterprise Manager. It is an advanced option, so you
have to have the sp_configure show advanced options setting turned on.
There are a set of topics in the SQL Server 2000 Books Online that discuss
how the database engine uses Windows threads and fibers under this node:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_sa_0w6d.asp?frame=true
Fiber mode is specifically discussed in this topic:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_sa_9m9f.asp?frame=true
Most instances of the database engine are not run in fiber mode, most of the
time the instance runs fine without using fibers.
--
Alan Brewer [MSFT]
Lead Programming Writer
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
Friday, March 23, 2012
Feedback on use of multiple instances
I am currently looking into the high-availability and
consolidations features in SQL Server 2000. MS implies
that running multiple instances of sql server on the same
server will result in a degregation of performance. I am
looking to install a solution that uses Quad 2.5 GB
processor, 4 GB ram server and possibly a cluster. I was
wonder if performance would be an issue for running 10 -
16 instances of sql on that.
Does anyone have a similar setup? If so, how many
instances do you use?
Is this something is widely used among corporations?
Thanks in advance,
SarahSarah,
It's not that simple. If you are talking about consolidating 10 to 16
individual servers into 1 quad processor server then that may be a bit much.
Not because SQL Server can't handle 16 instances but it may simply be a
matter or resources. Of coarse this all depends on what your doing with the
16 instances. Why that many instances vs just a few? You don't need a
separate instance for each db or application. What kind of apps / db's are
you planning on having in this server. You can't take 10 servers that had
anywhere from 10 - say 20 processors, each with say 1GB of ram and simply
through them all onto 1 quad proc server with 4GB and expect to have similar
performance. Unless of coarse they were all well under utilized to begin
with. The bottom line is that there is nothing inherently wrong with
upsizing and consolidating but you need to make sure you have all your ducks
in a row before deciding what type os server to use and how to allocate the
resources.
--
Andrew J. Kelly
SQL Server MVP
"Sarah" <anonymous@.discussions.microsoft.com> wrote in message
news:0c3401c3a476$d0af6e40$a401280a@.phx.gbl...
> I am currently looking into the high-availability and
> consolidations features in SQL Server 2000. MS implies
> that running multiple instances of sql server on the same
> server will result in a degregation of performance. I am
> looking to install a solution that uses Quad 2.5 GB
> processor, 4 GB ram server and possibly a cluster. I was
> wonder if performance would be an issue for running 10 -
> 16 instances of sql on that.
> Does anyone have a similar setup? If so, how many
> instances do you use?
> Is this something is widely used among corporations?
> Thanks in advance,
> Sarah|||Thank you for your response.
So then, what are the peformance differences if say you
had 10 databases on one instances of sql on a single
machine verses 10 instances of sql w/ one database each.
What I am looking to do is basically keep the
databases/application isolated from one another from a
performance and security standpoint. All of these are for
the most part low usage.
The current directive is to place all or most db's on the
same server & same instance. I'm trying to decide if
going w/ separate instances would be a better option.
Thanks again,
Sarah
>--Original Message--
>Sarah,
>It's not that simple. If you are talking about
consolidating 10 to 16
>individual servers into 1 quad processor server then that
may be a bit much.
>Not because SQL Server can't handle 16 instances but it
may simply be a
>matter or resources. Of coarse this all depends on what
your doing with the
>16 instances. Why that many instances vs just a few?
You don't need a
>separate instance for each db or application. What kind
of apps / db's are
>you planning on having in this server. You can't take 10
servers that had
>anywhere from 10 - say 20 processors, each with say 1GB
of ram and simply
>through them all onto 1 quad proc server with 4GB and
expect to have similar
>performance. Unless of coarse they were all well under
utilized to begin
>with. The bottom line is that there is nothing
inherently wrong with
>upsizing and consolidating but you need to make sure you
have all your ducks
>in a row before deciding what type os server to use and
how to allocate the
>resources.
>--
>Andrew J. Kelly
>SQL Server MVP
>
>"Sarah" <anonymous@.discussions.microsoft.com> wrote in
message
>news:0c3401c3a476$d0af6e40$a401280a@.phx.gbl...
>> I am currently looking into the high-availability and
>> consolidations features in SQL Server 2000. MS implies
>> that running multiple instances of sql server on the
same
>> server will result in a degregation of performance. I
am
>> looking to install a solution that uses Quad 2.5 GB
>> processor, 4 GB ram server and possibly a cluster. I
was
>> wonder if performance would be an issue for running 10 -
>> 16 instances of sql on that.
>> Does anyone have a similar setup? If so, how many
>> instances do you use?
>> Is this something is widely used among corporations?
>> Thanks in advance,
>> Sarah
>
>.
>|||"Sarah" <anonymous@.discussions.microsoft.com> wrote in message
news:01e301c3a488$72b6b570$a101280a@.phx.gbl...
> Thank you for your response.
> So then, what are the peformance differences if say you
> had 10 databases on one instances of sql on a single
> machine verses 10 instances of sql w/ one database each.
> What I am looking to do is basically keep the
> databases/application isolated from one another from a
> performance and security standpoint. All of these are for
> the most part low usage.
Performance will most likely be worse. Each instance has its own overhead
in processor time and memory usage. So if each database is using only 1% of
the available processor time and memory in a single instance, you would
probably see zero change in performance if you ran 10 instances each with
its own database. But if each database were using 10% of the available
resources in one instance, splitting these into 10 instances your available
resources will no longer be the same and each database's chunk of available
memory and/or processor time will be lower, thereby resulting in worse
performance.
Plus there's the management issue. Managing 10 instances is going to be
quite a bit more work than managing a single instance. From a security
standpoint, databases can be isolated very easily by simply managing logins
to the server. What benefit are you hoping to get, security-wise, from
multiple instances?|||if all the db's are single company internal users, i would
try to run as many db apps within a single instance as
practical
i would recommend multi-instance for ISP environments
where each instance belongs to a completely different
company/customer and security/isolation is required.
>--Original Message--
>Sarah,
>It's not that simple. If you are talking about
consolidating 10 to 16
>individual servers into 1 quad processor server then that
may be a bit much.
>Not because SQL Server can't handle 16 instances but it
may simply be a
>matter or resources. Of coarse this all depends on what
your doing with the
>16 instances. Why that many instances vs just a few?
You don't need a
>separate instance for each db or application. What kind
of apps / db's are
>you planning on having in this server. You can't take 10
servers that had
>anywhere from 10 - say 20 processors, each with say 1GB
of ram and simply
>through them all onto 1 quad proc server with 4GB and
expect to have similar
>performance. Unless of coarse they were all well under
utilized to begin
>with. The bottom line is that there is nothing
inherently wrong with
>upsizing and consolidating but you need to make sure you
have all your ducks
>in a row before deciding what type os server to use and
how to allocate the
>resources.
>--
>Andrew J. Kelly
>SQL Server MVP
>
>"Sarah" <anonymous@.discussions.microsoft.com> wrote in
message
>news:0c3401c3a476$d0af6e40$a401280a@.phx.gbl...
>> I am currently looking into the high-availability and
>> consolidations features in SQL Server 2000. MS implies
>> that running multiple instances of sql server on the
same
>> server will result in a degregation of performance. I
am
>> looking to install a solution that uses Quad 2.5 GB
>> processor, 4 GB ram server and possibly a cluster. I
was
>> wonder if performance would be an issue for running 10 -
>> 16 instances of sql on that.
>> Does anyone have a similar setup? If so, how many
>> instances do you use?
>> Is this something is widely used among corporations?
>> Thanks in advance,
>> Sarah
>
>.
>|||Sarah,
I pretty much agree with Adam. With proper security you can still isolate
the db's from each others users without going to the trouble of putting them
in their own instance. Again as Adam points out performance would most
likely be better for those reasons and sql server will not have to
dynamically adjust memory between the 10 instances. From the little info we
know of your situation it does not sound like it is worth the trouble of
having a separate instance for each db.
--
Andrew J. Kelly
SQL Server MVP
"Adam Machanic" <amachanic@.air-worldwide.nospamallowed.com> wrote in message
news:u2HcEnIpDHA.2776@.tk2msftngp13.phx.gbl...
> "Sarah" <anonymous@.discussions.microsoft.com> wrote in message
> news:01e301c3a488$72b6b570$a101280a@.phx.gbl...
> > Thank you for your response.
> > So then, what are the peformance differences if say you
> > had 10 databases on one instances of sql on a single
> > machine verses 10 instances of sql w/ one database each.
> > What I am looking to do is basically keep the
> > databases/application isolated from one another from a
> > performance and security standpoint. All of these are for
> > the most part low usage.
> Performance will most likely be worse. Each instance has its own
overhead
> in processor time and memory usage. So if each database is using only 1%
of
> the available processor time and memory in a single instance, you would
> probably see zero change in performance if you ran 10 instances each with
> its own database. But if each database were using 10% of the available
> resources in one instance, splitting these into 10 instances your
available
> resources will no longer be the same and each database's chunk of
available
> memory and/or processor time will be lower, thereby resulting in worse
> performance.
> Plus there's the management issue. Managing 10 instances is going to be
> quite a bit more work than managing a single instance. From a security
> standpoint, databases can be isolated very easily by simply managing
logins
> to the server. What benefit are you hoping to get, security-wise, from
> multiple instances?
>|||Here's where I'm coming from...
I am used to envrinoment where every application got it's
own sql db on it's own sql server. Now I am in an
environment where they all have to be placed on the same
server. How can I guarantee up time to my users when
mutliple applications have access to the same sql server.
If I have to stop one, they all get stopped... serivce
packs/ upgrades, errors, runaway transactions... etc.
I was thinking that by using a resource manager and
separate instances, I could limit a lot of the interaction.
But then I was unsure if other people actually did that
and if it would work properly.
As you can tell... I'm not really a dba, just a windows
admin that has to work w/ sql server...
>--Original Message--
>"Sarah" <anonymous@.discussions.microsoft.com> wrote in
message
>news:01e301c3a488$72b6b570$a101280a@.phx.gbl...
>> Thank you for your response.
>> So then, what are the peformance differences if say you
>> had 10 databases on one instances of sql on a single
>> machine verses 10 instances of sql w/ one database each.
>> What I am looking to do is basically keep the
>> databases/application isolated from one another from a
>> performance and security standpoint. All of these are
for
>> the most part low usage.
> Performance will most likely be worse. Each instance
has its own overhead
>in processor time and memory usage. So if each database
is using only 1% of
>the available processor time and memory in a single
instance, you would
>probably see zero change in performance if you ran 10
instances each with
>its own database. But if each database were using 10% of
the available
>resources in one instance, splitting these into 10
instances your available
>resources will no longer be the same and each database's
chunk of available
>memory and/or processor time will be lower, thereby
resulting in worse
>performance.
> Plus there's the management issue. Managing 10
instances is going to be
>quite a bit more work than managing a single instance.
From a security
>standpoint, databases can be isolated very easily by
simply managing logins
>to the server. What benefit are you hoping to get,
security-wise, from
>multiple instances?
>
>.
>|||"Sarah" <anonymous@.discussions.microsoft.com> wrote in message
news:02fc01c3a494$656e5330$a101280a@.phx.gbl...
> Here's where I'm coming from...
> I am used to envrinoment where every application got it's
> own sql db on it's own sql server. Now I am in an
> environment where they all have to be placed on the same
> server. How can I guarantee up time to my users when
> mutliple applications have access to the same sql server.
> If I have to stop one, they all get stopped... serivce
> packs/ upgrades, errors, runaway transactions... etc.
> I was thinking that by using a resource manager and
> separate instances, I could limit a lot of the interaction.
> But then I was unsure if other people actually did that
> and if it would work properly.
> As you can tell... I'm not really a dba, just a windows
> admin that has to work w/ sql server...
You shouldn't have to stop and restart the server very often (almost
never, unless something is very wrong). Just like normal Windows
administration, you'll install service packs and upgrades during planned
downtime or off hours... And now that you're administrating SQL Server I'd
like to welcome you to the world of being a DBA :)sql
consolidations features in SQL Server 2000. MS implies
that running multiple instances of sql server on the same
server will result in a degregation of performance. I am
looking to install a solution that uses Quad 2.5 GB
processor, 4 GB ram server and possibly a cluster. I was
wonder if performance would be an issue for running 10 -
16 instances of sql on that.
Does anyone have a similar setup? If so, how many
instances do you use?
Is this something is widely used among corporations?
Thanks in advance,
SarahSarah,
It's not that simple. If you are talking about consolidating 10 to 16
individual servers into 1 quad processor server then that may be a bit much.
Not because SQL Server can't handle 16 instances but it may simply be a
matter or resources. Of coarse this all depends on what your doing with the
16 instances. Why that many instances vs just a few? You don't need a
separate instance for each db or application. What kind of apps / db's are
you planning on having in this server. You can't take 10 servers that had
anywhere from 10 - say 20 processors, each with say 1GB of ram and simply
through them all onto 1 quad proc server with 4GB and expect to have similar
performance. Unless of coarse they were all well under utilized to begin
with. The bottom line is that there is nothing inherently wrong with
upsizing and consolidating but you need to make sure you have all your ducks
in a row before deciding what type os server to use and how to allocate the
resources.
--
Andrew J. Kelly
SQL Server MVP
"Sarah" <anonymous@.discussions.microsoft.com> wrote in message
news:0c3401c3a476$d0af6e40$a401280a@.phx.gbl...
> I am currently looking into the high-availability and
> consolidations features in SQL Server 2000. MS implies
> that running multiple instances of sql server on the same
> server will result in a degregation of performance. I am
> looking to install a solution that uses Quad 2.5 GB
> processor, 4 GB ram server and possibly a cluster. I was
> wonder if performance would be an issue for running 10 -
> 16 instances of sql on that.
> Does anyone have a similar setup? If so, how many
> instances do you use?
> Is this something is widely used among corporations?
> Thanks in advance,
> Sarah|||Thank you for your response.
So then, what are the peformance differences if say you
had 10 databases on one instances of sql on a single
machine verses 10 instances of sql w/ one database each.
What I am looking to do is basically keep the
databases/application isolated from one another from a
performance and security standpoint. All of these are for
the most part low usage.
The current directive is to place all or most db's on the
same server & same instance. I'm trying to decide if
going w/ separate instances would be a better option.
Thanks again,
Sarah
>--Original Message--
>Sarah,
>It's not that simple. If you are talking about
consolidating 10 to 16
>individual servers into 1 quad processor server then that
may be a bit much.
>Not because SQL Server can't handle 16 instances but it
may simply be a
>matter or resources. Of coarse this all depends on what
your doing with the
>16 instances. Why that many instances vs just a few?
You don't need a
>separate instance for each db or application. What kind
of apps / db's are
>you planning on having in this server. You can't take 10
servers that had
>anywhere from 10 - say 20 processors, each with say 1GB
of ram and simply
>through them all onto 1 quad proc server with 4GB and
expect to have similar
>performance. Unless of coarse they were all well under
utilized to begin
>with. The bottom line is that there is nothing
inherently wrong with
>upsizing and consolidating but you need to make sure you
have all your ducks
>in a row before deciding what type os server to use and
how to allocate the
>resources.
>--
>Andrew J. Kelly
>SQL Server MVP
>
>"Sarah" <anonymous@.discussions.microsoft.com> wrote in
message
>news:0c3401c3a476$d0af6e40$a401280a@.phx.gbl...
>> I am currently looking into the high-availability and
>> consolidations features in SQL Server 2000. MS implies
>> that running multiple instances of sql server on the
same
>> server will result in a degregation of performance. I
am
>> looking to install a solution that uses Quad 2.5 GB
>> processor, 4 GB ram server and possibly a cluster. I
was
>> wonder if performance would be an issue for running 10 -
>> 16 instances of sql on that.
>> Does anyone have a similar setup? If so, how many
>> instances do you use?
>> Is this something is widely used among corporations?
>> Thanks in advance,
>> Sarah
>
>.
>|||"Sarah" <anonymous@.discussions.microsoft.com> wrote in message
news:01e301c3a488$72b6b570$a101280a@.phx.gbl...
> Thank you for your response.
> So then, what are the peformance differences if say you
> had 10 databases on one instances of sql on a single
> machine verses 10 instances of sql w/ one database each.
> What I am looking to do is basically keep the
> databases/application isolated from one another from a
> performance and security standpoint. All of these are for
> the most part low usage.
Performance will most likely be worse. Each instance has its own overhead
in processor time and memory usage. So if each database is using only 1% of
the available processor time and memory in a single instance, you would
probably see zero change in performance if you ran 10 instances each with
its own database. But if each database were using 10% of the available
resources in one instance, splitting these into 10 instances your available
resources will no longer be the same and each database's chunk of available
memory and/or processor time will be lower, thereby resulting in worse
performance.
Plus there's the management issue. Managing 10 instances is going to be
quite a bit more work than managing a single instance. From a security
standpoint, databases can be isolated very easily by simply managing logins
to the server. What benefit are you hoping to get, security-wise, from
multiple instances?|||if all the db's are single company internal users, i would
try to run as many db apps within a single instance as
practical
i would recommend multi-instance for ISP environments
where each instance belongs to a completely different
company/customer and security/isolation is required.
>--Original Message--
>Sarah,
>It's not that simple. If you are talking about
consolidating 10 to 16
>individual servers into 1 quad processor server then that
may be a bit much.
>Not because SQL Server can't handle 16 instances but it
may simply be a
>matter or resources. Of coarse this all depends on what
your doing with the
>16 instances. Why that many instances vs just a few?
You don't need a
>separate instance for each db or application. What kind
of apps / db's are
>you planning on having in this server. You can't take 10
servers that had
>anywhere from 10 - say 20 processors, each with say 1GB
of ram and simply
>through them all onto 1 quad proc server with 4GB and
expect to have similar
>performance. Unless of coarse they were all well under
utilized to begin
>with. The bottom line is that there is nothing
inherently wrong with
>upsizing and consolidating but you need to make sure you
have all your ducks
>in a row before deciding what type os server to use and
how to allocate the
>resources.
>--
>Andrew J. Kelly
>SQL Server MVP
>
>"Sarah" <anonymous@.discussions.microsoft.com> wrote in
message
>news:0c3401c3a476$d0af6e40$a401280a@.phx.gbl...
>> I am currently looking into the high-availability and
>> consolidations features in SQL Server 2000. MS implies
>> that running multiple instances of sql server on the
same
>> server will result in a degregation of performance. I
am
>> looking to install a solution that uses Quad 2.5 GB
>> processor, 4 GB ram server and possibly a cluster. I
was
>> wonder if performance would be an issue for running 10 -
>> 16 instances of sql on that.
>> Does anyone have a similar setup? If so, how many
>> instances do you use?
>> Is this something is widely used among corporations?
>> Thanks in advance,
>> Sarah
>
>.
>|||Sarah,
I pretty much agree with Adam. With proper security you can still isolate
the db's from each others users without going to the trouble of putting them
in their own instance. Again as Adam points out performance would most
likely be better for those reasons and sql server will not have to
dynamically adjust memory between the 10 instances. From the little info we
know of your situation it does not sound like it is worth the trouble of
having a separate instance for each db.
--
Andrew J. Kelly
SQL Server MVP
"Adam Machanic" <amachanic@.air-worldwide.nospamallowed.com> wrote in message
news:u2HcEnIpDHA.2776@.tk2msftngp13.phx.gbl...
> "Sarah" <anonymous@.discussions.microsoft.com> wrote in message
> news:01e301c3a488$72b6b570$a101280a@.phx.gbl...
> > Thank you for your response.
> > So then, what are the peformance differences if say you
> > had 10 databases on one instances of sql on a single
> > machine verses 10 instances of sql w/ one database each.
> > What I am looking to do is basically keep the
> > databases/application isolated from one another from a
> > performance and security standpoint. All of these are for
> > the most part low usage.
> Performance will most likely be worse. Each instance has its own
overhead
> in processor time and memory usage. So if each database is using only 1%
of
> the available processor time and memory in a single instance, you would
> probably see zero change in performance if you ran 10 instances each with
> its own database. But if each database were using 10% of the available
> resources in one instance, splitting these into 10 instances your
available
> resources will no longer be the same and each database's chunk of
available
> memory and/or processor time will be lower, thereby resulting in worse
> performance.
> Plus there's the management issue. Managing 10 instances is going to be
> quite a bit more work than managing a single instance. From a security
> standpoint, databases can be isolated very easily by simply managing
logins
> to the server. What benefit are you hoping to get, security-wise, from
> multiple instances?
>|||Here's where I'm coming from...
I am used to envrinoment where every application got it's
own sql db on it's own sql server. Now I am in an
environment where they all have to be placed on the same
server. How can I guarantee up time to my users when
mutliple applications have access to the same sql server.
If I have to stop one, they all get stopped... serivce
packs/ upgrades, errors, runaway transactions... etc.
I was thinking that by using a resource manager and
separate instances, I could limit a lot of the interaction.
But then I was unsure if other people actually did that
and if it would work properly.
As you can tell... I'm not really a dba, just a windows
admin that has to work w/ sql server...
>--Original Message--
>"Sarah" <anonymous@.discussions.microsoft.com> wrote in
message
>news:01e301c3a488$72b6b570$a101280a@.phx.gbl...
>> Thank you for your response.
>> So then, what are the peformance differences if say you
>> had 10 databases on one instances of sql on a single
>> machine verses 10 instances of sql w/ one database each.
>> What I am looking to do is basically keep the
>> databases/application isolated from one another from a
>> performance and security standpoint. All of these are
for
>> the most part low usage.
> Performance will most likely be worse. Each instance
has its own overhead
>in processor time and memory usage. So if each database
is using only 1% of
>the available processor time and memory in a single
instance, you would
>probably see zero change in performance if you ran 10
instances each with
>its own database. But if each database were using 10% of
the available
>resources in one instance, splitting these into 10
instances your available
>resources will no longer be the same and each database's
chunk of available
>memory and/or processor time will be lower, thereby
resulting in worse
>performance.
> Plus there's the management issue. Managing 10
instances is going to be
>quite a bit more work than managing a single instance.
From a security
>standpoint, databases can be isolated very easily by
simply managing logins
>to the server. What benefit are you hoping to get,
security-wise, from
>multiple instances?
>
>.
>|||"Sarah" <anonymous@.discussions.microsoft.com> wrote in message
news:02fc01c3a494$656e5330$a101280a@.phx.gbl...
> Here's where I'm coming from...
> I am used to envrinoment where every application got it's
> own sql db on it's own sql server. Now I am in an
> environment where they all have to be placed on the same
> server. How can I guarantee up time to my users when
> mutliple applications have access to the same sql server.
> If I have to stop one, they all get stopped... serivce
> packs/ upgrades, errors, runaway transactions... etc.
> I was thinking that by using a resource manager and
> separate instances, I could limit a lot of the interaction.
> But then I was unsure if other people actually did that
> and if it would work properly.
> As you can tell... I'm not really a dba, just a windows
> admin that has to work w/ sql server...
You shouldn't have to stop and restart the server very often (almost
never, unless something is very wrong). Just like normal Windows
administration, you'll install service packs and upgrades during planned
downtime or off hours... And now that you're administrating SQL Server I'd
like to welcome you to the world of being a DBA :)sql
Feedback from Tape Backups
Hi Folks,
I'm trying to find a way to get access to the STATS output from the BACKUP
command during automated backups.
When running the BACKUP command in QA it shows the output, line by line, as
the backup progresses. Is there any way I can get this information when the
BACKUP statement is run from a job? I thought the console tool might have
been the answer, but it doesn't show any progress messages.
Is the only option to use the Job/Step/Adv/Output to file option, and "tail"
the file?
TIA
J.
In this case, the client application is SQL Server Agent, more specific, the sub-component in Agent
that executes your TSQL job steps. And Agent isn't written to output this information "as it goes".
It might update the output file as information comes in (I haven't tested this), so I think that
this is probably your best bet. Another option is of course to schedule an EXE file that you wrote
and you have in your EXE file code to output the information to where ever you want it to go.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"J Hunter" <ms-nntp-nospam@.jshunter.co.uk> wrote in message
news:eL976GjHFHA.1860@.TK2MSFTNGP15.phx.gbl...
> Hi Folks,
> I'm trying to find a way to get access to the STATS output from the BACKUP
> command during automated backups.
> When running the BACKUP command in QA it shows the output, line by line, as
> the backup progresses. Is there any way I can get this information when the
> BACKUP statement is run from a job? I thought the console tool might have
> been the answer, but it doesn't show any progress messages.
> Is the only option to use the Job/Step/Adv/Output to file option, and "tail"
> the file?
> TIA
> J.
>
>
|||Thanks Tibor
With regard to your comments on creating my own EXE, how would I go about
getting access to the messages - given that they are not returned as part of
a result set?
Cheers
J.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OU%23Lr5lHFHA.4060@.TK2MSFTNGP14.phx.gbl...
> In this case, the client application is SQL Server Agent, more specific,
the sub-component in Agent
> that executes your TSQL job steps. And Agent isn't written to output this
information "as it goes".
> It might update the output file as information comes in (I haven't tested
this), so I think that
> this is probably your best bet. Another option is of course to schedule an
EXE file that you wrote
> and you have in your EXE file code to output the information to where ever
you want it to go.[vbcol=seagreen]
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "J Hunter" <ms-nntp-nospam@.jshunter.co.uk> wrote in message
> news:eL976GjHFHA.1860@.TK2MSFTNGP15.phx.gbl...
BACKUP[vbcol=seagreen]
as[vbcol=seagreen]
the[vbcol=seagreen]
have[vbcol=seagreen]
"tail"
>
|||First I believe that you have to program asynchronously. Otherwise the command will be blocked until
it has finished. These are returned as messages, technically same way as PRINT and errors. I'm no
API expert, so you might want to investigate this further and possibly asking in a newsgroup
dedicated to the API you are using (ADO, ADO.NET etc).
The bigger problem is how your EXE will output to the screen. Remember that agent is a service (in
"NT") and a service has no Window context...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"J Hunter" <ms-nntp-nospam@.jshunter.co.uk> wrote in message
news:ePdMhboHFHA.236@.TK2MSFTNGP14.phx.gbl...
> Thanks Tibor
> With regard to your comments on creating my own EXE, how would I go about
> getting access to the messages - given that they are not returned as part of
> a result set?
> Cheers
> J.
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:OU%23Lr5lHFHA.4060@.TK2MSFTNGP14.phx.gbl...
> the sub-component in Agent
> information "as it goes".
> this), so I think that
> EXE file that you wrote
> you want it to go.
> BACKUP
> as
> the
> have
> "tail"
>
sql
I'm trying to find a way to get access to the STATS output from the BACKUP
command during automated backups.
When running the BACKUP command in QA it shows the output, line by line, as
the backup progresses. Is there any way I can get this information when the
BACKUP statement is run from a job? I thought the console tool might have
been the answer, but it doesn't show any progress messages.
Is the only option to use the Job/Step/Adv/Output to file option, and "tail"
the file?
TIA
J.
In this case, the client application is SQL Server Agent, more specific, the sub-component in Agent
that executes your TSQL job steps. And Agent isn't written to output this information "as it goes".
It might update the output file as information comes in (I haven't tested this), so I think that
this is probably your best bet. Another option is of course to schedule an EXE file that you wrote
and you have in your EXE file code to output the information to where ever you want it to go.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"J Hunter" <ms-nntp-nospam@.jshunter.co.uk> wrote in message
news:eL976GjHFHA.1860@.TK2MSFTNGP15.phx.gbl...
> Hi Folks,
> I'm trying to find a way to get access to the STATS output from the BACKUP
> command during automated backups.
> When running the BACKUP command in QA it shows the output, line by line, as
> the backup progresses. Is there any way I can get this information when the
> BACKUP statement is run from a job? I thought the console tool might have
> been the answer, but it doesn't show any progress messages.
> Is the only option to use the Job/Step/Adv/Output to file option, and "tail"
> the file?
> TIA
> J.
>
>
|||Thanks Tibor
With regard to your comments on creating my own EXE, how would I go about
getting access to the messages - given that they are not returned as part of
a result set?
Cheers
J.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OU%23Lr5lHFHA.4060@.TK2MSFTNGP14.phx.gbl...
> In this case, the client application is SQL Server Agent, more specific,
the sub-component in Agent
> that executes your TSQL job steps. And Agent isn't written to output this
information "as it goes".
> It might update the output file as information comes in (I haven't tested
this), so I think that
> this is probably your best bet. Another option is of course to schedule an
EXE file that you wrote
> and you have in your EXE file code to output the information to where ever
you want it to go.[vbcol=seagreen]
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "J Hunter" <ms-nntp-nospam@.jshunter.co.uk> wrote in message
> news:eL976GjHFHA.1860@.TK2MSFTNGP15.phx.gbl...
BACKUP[vbcol=seagreen]
as[vbcol=seagreen]
the[vbcol=seagreen]
have[vbcol=seagreen]
"tail"
>
|||First I believe that you have to program asynchronously. Otherwise the command will be blocked until
it has finished. These are returned as messages, technically same way as PRINT and errors. I'm no
API expert, so you might want to investigate this further and possibly asking in a newsgroup
dedicated to the API you are using (ADO, ADO.NET etc).
The bigger problem is how your EXE will output to the screen. Remember that agent is a service (in
"NT") and a service has no Window context...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"J Hunter" <ms-nntp-nospam@.jshunter.co.uk> wrote in message
news:ePdMhboHFHA.236@.TK2MSFTNGP14.phx.gbl...
> Thanks Tibor
> With regard to your comments on creating my own EXE, how would I go about
> getting access to the messages - given that they are not returned as part of
> a result set?
> Cheers
> J.
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:OU%23Lr5lHFHA.4060@.TK2MSFTNGP14.phx.gbl...
> the sub-component in Agent
> information "as it goes".
> this), so I think that
> EXE file that you wrote
> you want it to go.
> BACKUP
> as
> the
> have
> "tail"
>
sql
Federation/replication - DB2 & Microsoft SQL Server 2000
Hi all,
I'm new to this forum, though not new to sql server am new to DB2.
We are running Microsoft SQL Server 2000 but we have recently acquired similar business in another country which runs IBM DB2 database system. We are interested in incorporating the data from DB2 in our system. The tables are slightly different in DB2.
Q. what is the best way to integrate the two systems? Should we take the route of a federated system or replication of data?
We are interested in knowing what is happening in the other business (DB2) but we what the two systems to operate in parallel for about a year, before we come up with the best solution.
The company is after a short term and long term solution.
Can any one please help or point me to the right place?
Regards,
Chloe.What you are describing is a consulting engagement. I would STRONGLY suggest that you consider paying someone with an appropriate level of expertise to come examine your systems and give you a professional opinion. While you can get good ideas from the internet, you really need something more solid than a good idea, and you really need someone with the experience to know what questions you didn't ask and the time and energy to both ask and answer them for you. I'm not trying to sell you anything, and I'm not volunteering for the engagement, I'm just trying to keep you from hurting yourself!
With that said, I'd suggest you consider using sp_addlinkedserver (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_sp_adda_8gqa.asp). It will allow your SQL Server to "see" the AS400 data, and that will be a stepping stone to allowing you to build reports, etc from the merged companies combined perspective.
Don't give up on using the Internet to get good ideas, it is great for that. As your business grows, don't "bet the farm" on what you get from the Internet until you get to the point that you can critically examine the information and know at least enough to know if you've asked all of the relevant questions.
As a side note, you might consider one of the firms that helps firms like yours grow. There are several of them, and while they aren't cheap they can easily save 100 times what they cost. I work for one of those firms (I don't do client engagements, just IT), and I see examples of mergers that went well (and poorly) every day.
Find the appropriate expertise, even if it is expensive. As the old saying goes: If you think education is expensive, you should consider the cost of ignorance!
-PatP|||Hi Pat,
Thanks a lot for your advice. What you said is right we should get a professional to do the job for us and as you rightly pointed out it will probably be expensive.
I want to point out that our business is very small and we can't afford to pay a professional, however, I and my business pattern studied IT and designed the current system we are using. But that was a long time ago and we don't have much experience in integrating data from different databases plus new technologies come up every day. And its for that reason/s, that I asked the question/s on this forum to find out what is out there that we can use. Or probably some body has integrated data from the two systems mentioned and would like to give us some advice.
Thanks again for sharing your wisdom.
Any more advice on the mentioned issue will be highly appreciated.
Best regards,
Chloe
I'm new to this forum, though not new to sql server am new to DB2.
We are running Microsoft SQL Server 2000 but we have recently acquired similar business in another country which runs IBM DB2 database system. We are interested in incorporating the data from DB2 in our system. The tables are slightly different in DB2.
Q. what is the best way to integrate the two systems? Should we take the route of a federated system or replication of data?
We are interested in knowing what is happening in the other business (DB2) but we what the two systems to operate in parallel for about a year, before we come up with the best solution.
The company is after a short term and long term solution.
Can any one please help or point me to the right place?
Regards,
Chloe.What you are describing is a consulting engagement. I would STRONGLY suggest that you consider paying someone with an appropriate level of expertise to come examine your systems and give you a professional opinion. While you can get good ideas from the internet, you really need something more solid than a good idea, and you really need someone with the experience to know what questions you didn't ask and the time and energy to both ask and answer them for you. I'm not trying to sell you anything, and I'm not volunteering for the engagement, I'm just trying to keep you from hurting yourself!
With that said, I'd suggest you consider using sp_addlinkedserver (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_sp_adda_8gqa.asp). It will allow your SQL Server to "see" the AS400 data, and that will be a stepping stone to allowing you to build reports, etc from the merged companies combined perspective.
Don't give up on using the Internet to get good ideas, it is great for that. As your business grows, don't "bet the farm" on what you get from the Internet until you get to the point that you can critically examine the information and know at least enough to know if you've asked all of the relevant questions.
As a side note, you might consider one of the firms that helps firms like yours grow. There are several of them, and while they aren't cheap they can easily save 100 times what they cost. I work for one of those firms (I don't do client engagements, just IT), and I see examples of mergers that went well (and poorly) every day.
Find the appropriate expertise, even if it is expensive. As the old saying goes: If you think education is expensive, you should consider the cost of ignorance!
-PatP|||Hi Pat,
Thanks a lot for your advice. What you said is right we should get a professional to do the job for us and as you rightly pointed out it will probably be expensive.
I want to point out that our business is very small and we can't afford to pay a professional, however, I and my business pattern studied IT and designed the current system we are using. But that was a long time ago and we don't have much experience in integrating data from different databases plus new technologies come up every day. And its for that reason/s, that I asked the question/s on this forum to find out what is out there that we can use. Or probably some body has integrated data from the two systems mentioned and would like to give us some advice.
Thanks again for sharing your wisdom.
Any more advice on the mentioned issue will be highly appreciated.
Best regards,
Chloe
Feature request
Some of our users who may be running packages are not so adept at editing XML configuration files. It'd be nice if we could instead either:
1. Have an interface to modify the XML dtsConfig files
or 2. Have another option that would prompt via dialog box for the configuration options when the DTS package is run.
On #1, anyone know of any existing programs that would be useful (something that would ignore the markup and just edit the variables)?
Thanks for the request, Jonathan. It's on our list of things to consider for the next version, we just didn't have the time to get it into SQL Server 2005.
1. Have an interface to modify the XML dtsConfig files
or 2. Have another option that would prompt via dialog box for the configuration options when the DTS package is run.
On #1, anyone know of any existing programs that would be useful (something that would ignore the markup and just edit the variables)?
Thanks for the request, Jonathan. It's on our list of things to consider for the next version, we just didn't have the time to get it into SQL Server 2005.
regards,
ash
Wednesday, March 21, 2012
fcb::ZeroFile(): GetOverLappedResult() failed with error 27.
Hi,
I have a server that is running MSSQL2000 SP4 + 2159 hotfix. Whever I try to
expand a data file by 4 GB - it does not report any error. The windows
explorer shows the new size. But the enterpise manager and sp_helpdb show the
old size and there is an entry in the SQL error log that says..
fcb::ZeroFile(): GetOverLappedResult() failed with error 27.
Has any one come across this before? What is the solution?
Sounds like you have some serious issues with your disk. 27 is an OS error, "Cannot find requested
sector". Is the file compressed? If so, this isn't supported, and things like these are expected
(although I'm not sure whether this particular error message is expected). If not, I'd run a
comprehensive check at the file system/disk level.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:0AD05B12-0C6F-4A1E-9B73-C39BB1BDD360@.microsoft.com...
> Hi,
> I have a server that is running MSSQL2000 SP4 + 2159 hotfix. Whever I try to
> expand a data file by 4 GB - it does not report any error. The windows
> explorer shows the new size. But the enterpise manager and sp_helpdb show the
> old size and there is an entry in the SQL error log that says..
> fcb::ZeroFile(): GetOverLappedResult() failed with error 27.
> Has any one come across this before? What is the solution?
I have a server that is running MSSQL2000 SP4 + 2159 hotfix. Whever I try to
expand a data file by 4 GB - it does not report any error. The windows
explorer shows the new size. But the enterpise manager and sp_helpdb show the
old size and there is an entry in the SQL error log that says..
fcb::ZeroFile(): GetOverLappedResult() failed with error 27.
Has any one come across this before? What is the solution?
Sounds like you have some serious issues with your disk. 27 is an OS error, "Cannot find requested
sector". Is the file compressed? If so, this isn't supported, and things like these are expected
(although I'm not sure whether this particular error message is expected). If not, I'd run a
comprehensive check at the file system/disk level.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:0AD05B12-0C6F-4A1E-9B73-C39BB1BDD360@.microsoft.com...
> Hi,
> I have a server that is running MSSQL2000 SP4 + 2159 hotfix. Whever I try to
> expand a data file by 4 GB - it does not report any error. The windows
> explorer shows the new size. But the enterpise manager and sp_helpdb show the
> old size and there is an entry in the SQL error log that says..
> fcb::ZeroFile(): GetOverLappedResult() failed with error 27.
> Has any one come across this before? What is the solution?
fcb::ZeroFile(): GetOverLappedResult() failed with error 27.
Hi,
I have a server that is running MSSQL2000 SP4 + 2159 hotfix. Whever I try to
expand a data file by 4 GB - it does not report any error. The windows
explorer shows the new size. But the enterpise manager and sp_helpdb show th
e
old size and there is an entry in the SQL error log that says..
fcb::ZeroFile(): GetOverLappedResult() failed with error 27.
Has any one come across this before? What is the solution?Sounds like you have some serious issues with your disk. 27 is an OS error,
"Cannot find requested
sector". Is the file compressed? If so, this isn't supported, and things lik
e these are expected
(although I'm not sure whether this particular error message is expected). I
f not, I'd run a
comprehensive check at the file system/disk level.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:0AD05B12-0C6F-4A1E-9B73-C39BB1BDD360@.microsoft.com...
> Hi,
> I have a server that is running MSSQL2000 SP4 + 2159 hotfix. Whever I try
to
> expand a data file by 4 GB - it does not report any error. The windows
> explorer shows the new size. But the enterpise manager and sp_helpdb show
the
> old size and there is an entry in the SQL error log that says..
> fcb::ZeroFile(): GetOverLappedResult() failed with error 27.
> Has any one come across this before? What is the solution?sql
I have a server that is running MSSQL2000 SP4 + 2159 hotfix. Whever I try to
expand a data file by 4 GB - it does not report any error. The windows
explorer shows the new size. But the enterpise manager and sp_helpdb show th
e
old size and there is an entry in the SQL error log that says..
fcb::ZeroFile(): GetOverLappedResult() failed with error 27.
Has any one come across this before? What is the solution?Sounds like you have some serious issues with your disk. 27 is an OS error,
"Cannot find requested
sector". Is the file compressed? If so, this isn't supported, and things lik
e these are expected
(although I'm not sure whether this particular error message is expected). I
f not, I'd run a
comprehensive check at the file system/disk level.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:0AD05B12-0C6F-4A1E-9B73-C39BB1BDD360@.microsoft.com...
> Hi,
> I have a server that is running MSSQL2000 SP4 + 2159 hotfix. Whever I try
to
> expand a data file by 4 GB - it does not report any error. The windows
> explorer shows the new size. But the enterpise manager and sp_helpdb show
the
> old size and there is an entry in the SQL error log that says..
> fcb::ZeroFile(): GetOverLappedResult() failed with error 27.
> Has any one come across this before? What is the solution?sql
fcb::ZeroFile(): GetOverLappedResult() failed with error 27.
Hi,
I have a server that is running MSSQL2000 SP4 + 2159 hotfix. Whever I try to
expand a data file by 4 GB - it does not report any error. The windows
explorer shows the new size. But the enterpise manager and sp_helpdb show the
old size and there is an entry in the SQL error log that says..
fcb::ZeroFile(): GetOverLappedResult() failed with error 27.
Has any one come across this before? What is the solution?Sounds like you have some serious issues with your disk. 27 is an OS error, "Cannot find requested
sector". Is the file compressed? If so, this isn't supported, and things like these are expected
(although I'm not sure whether this particular error message is expected). If not, I'd run a
comprehensive check at the file system/disk level.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:0AD05B12-0C6F-4A1E-9B73-C39BB1BDD360@.microsoft.com...
> Hi,
> I have a server that is running MSSQL2000 SP4 + 2159 hotfix. Whever I try to
> expand a data file by 4 GB - it does not report any error. The windows
> explorer shows the new size. But the enterpise manager and sp_helpdb show the
> old size and there is an entry in the SQL error log that says..
> fcb::ZeroFile(): GetOverLappedResult() failed with error 27.
> Has any one come across this before? What is the solution?
I have a server that is running MSSQL2000 SP4 + 2159 hotfix. Whever I try to
expand a data file by 4 GB - it does not report any error. The windows
explorer shows the new size. But the enterpise manager and sp_helpdb show the
old size and there is an entry in the SQL error log that says..
fcb::ZeroFile(): GetOverLappedResult() failed with error 27.
Has any one come across this before? What is the solution?Sounds like you have some serious issues with your disk. 27 is an OS error, "Cannot find requested
sector". Is the file compressed? If so, this isn't supported, and things like these are expected
(although I'm not sure whether this particular error message is expected). If not, I'd run a
comprehensive check at the file system/disk level.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Bharath" <Bharath@.discussions.microsoft.com> wrote in message
news:0AD05B12-0C6F-4A1E-9B73-C39BB1BDD360@.microsoft.com...
> Hi,
> I have a server that is running MSSQL2000 SP4 + 2159 hotfix. Whever I try to
> expand a data file by 4 GB - it does not report any error. The windows
> explorer shows the new size. But the enterpise manager and sp_helpdb show the
> old size and there is an entry in the SQL error log that says..
> fcb::ZeroFile(): GetOverLappedResult() failed with error 27.
> Has any one come across this before? What is the solution?
Faulty Restore
Until recently we received backups of a clients database
and restored it with no problems. They are running SQL
2000 on NT 4.0. About a month ago we noticed some problem
with the backups, DBCC CHECKDB revealed consistency
errors in the databases after restore. We are running SQL
2000 SP3a on XP Pro. They can restore there backup
locally but when ever we restore them we get errors.
Any help would be very much appreciated.
If there are consistency errors with the restored db it is most likely they
exist in the original one. They need to fix the errors in the original db
before you can get good backups.
Andrew J. Kelly SQL MVP
"Geoff Aukett" <anonymous@.discussions.microsoft.com> wrote in message
news:1c6c901c4222c$4b313d00$a301280a@.phx.gbl...
> Until recently we received backups of a clients database
> and restored it with no problems. They are running SQL
> 2000 on NT 4.0. About a month ago we noticed some problem
> with the backups, DBCC CHECKDB revealed consistency
> errors in the databases after restore. We are running SQL
> 2000 SP3a on XP Pro. They can restore there backup
> locally but when ever we restore them we get errors.
> Any help would be very much appreciated.
|||Thats what is so odd, their DBA assures us that they
restore and checkout ok at their end?
>--Original Message--
>If there are consistency errors with the restored db it
is most likely they
>exist in the original one. They need to fix the errors
in the original db
>before you can get good backups.
>--
>Andrew J. Kelly SQL MVP
>
>"Geoff Aukett" <anonymous@.discussions.microsoft.com>
wrote in message[vbcol=seagreen]
>news:1c6c901c4222c$4b313d00$a301280a@.phx.gbl...
database[vbcol=seagreen]
problem[vbcol=seagreen]
SQL
>
>.
>
|||It's possible the backup file itself can get corrupted but in my experience
when this happens you get file errors in most cases. Have they actually run
a full DBCC CHECKDB abd DBCC CHECKCATALOG lately?
Andrew J. Kelly SQL MVP
<anonymous@.discussions.microsoft.com> wrote in message
news:1cd0401c422b6$a765dec0$a401280a@.phx.gbl...[vbcol=seagreen]
> Thats what is so odd, their DBA assures us that they
> restore and checkout ok at their end?
> is most likely they
> in the original db
> wrote in message
> database
> problem
> SQL
and restored it with no problems. They are running SQL
2000 on NT 4.0. About a month ago we noticed some problem
with the backups, DBCC CHECKDB revealed consistency
errors in the databases after restore. We are running SQL
2000 SP3a on XP Pro. They can restore there backup
locally but when ever we restore them we get errors.
Any help would be very much appreciated.
If there are consistency errors with the restored db it is most likely they
exist in the original one. They need to fix the errors in the original db
before you can get good backups.
Andrew J. Kelly SQL MVP
"Geoff Aukett" <anonymous@.discussions.microsoft.com> wrote in message
news:1c6c901c4222c$4b313d00$a301280a@.phx.gbl...
> Until recently we received backups of a clients database
> and restored it with no problems. They are running SQL
> 2000 on NT 4.0. About a month ago we noticed some problem
> with the backups, DBCC CHECKDB revealed consistency
> errors in the databases after restore. We are running SQL
> 2000 SP3a on XP Pro. They can restore there backup
> locally but when ever we restore them we get errors.
> Any help would be very much appreciated.
|||Thats what is so odd, their DBA assures us that they
restore and checkout ok at their end?
>--Original Message--
>If there are consistency errors with the restored db it
is most likely they
>exist in the original one. They need to fix the errors
in the original db
>before you can get good backups.
>--
>Andrew J. Kelly SQL MVP
>
>"Geoff Aukett" <anonymous@.discussions.microsoft.com>
wrote in message[vbcol=seagreen]
>news:1c6c901c4222c$4b313d00$a301280a@.phx.gbl...
database[vbcol=seagreen]
problem[vbcol=seagreen]
SQL
>
>.
>
|||It's possible the backup file itself can get corrupted but in my experience
when this happens you get file errors in most cases. Have they actually run
a full DBCC CHECKDB abd DBCC CHECKCATALOG lately?
Andrew J. Kelly SQL MVP
<anonymous@.discussions.microsoft.com> wrote in message
news:1cd0401c422b6$a765dec0$a401280a@.phx.gbl...[vbcol=seagreen]
> Thats what is so odd, their DBA assures us that they
> restore and checkout ok at their end?
> is most likely they
> in the original db
> wrote in message
> database
> problem
> SQL
Faulty Restore
Until recently we received backups of a clients database
and restored it with no problems. They are running SQL
2000 on NT 4.0. About a month ago we noticed some problem
with the backups, DBCC CHECKDB revealed consistency
errors in the databases after restore. We are running SQL
2000 SP3a on XP Pro. They can restore there backup
locally but when ever we restore them we get errors.
Any help would be very much appreciated.If there are consistency errors with the restored db it is most likely they
exist in the original one. They need to fix the errors in the original db
before you can get good backups.
--
Andrew J. Kelly SQL MVP
"Geoff Aukett" <anonymous@.discussions.microsoft.com> wrote in message
news:1c6c901c4222c$4b313d00$a301280a@.phx.gbl...
> Until recently we received backups of a clients database
> and restored it with no problems. They are running SQL
> 2000 on NT 4.0. About a month ago we noticed some problem
> with the backups, DBCC CHECKDB revealed consistency
> errors in the databases after restore. We are running SQL
> 2000 SP3a on XP Pro. They can restore there backup
> locally but when ever we restore them we get errors.
> Any help would be very much appreciated.|||Thats what is so odd, their DBA assures us that they
restore and checkout ok at their end?
>--Original Message--
>If there are consistency errors with the restored db it
is most likely they
>exist in the original one. They need to fix the errors
in the original db
>before you can get good backups.
>--
>Andrew J. Kelly SQL MVP
>
>"Geoff Aukett" <anonymous@.discussions.microsoft.com>
wrote in message
>news:1c6c901c4222c$4b313d00$a301280a@.phx.gbl...
>> Until recently we received backups of a clients
database
>> and restored it with no problems. They are running SQL
>> 2000 on NT 4.0. About a month ago we noticed some
problem
>> with the backups, DBCC CHECKDB revealed consistency
>> errors in the databases after restore. We are running
SQL
>> 2000 SP3a on XP Pro. They can restore there backup
>> locally but when ever we restore them we get errors.
>> Any help would be very much appreciated.
>
>.
>|||It's possible the backup file itself can get corrupted but in my experience
when this happens you get file errors in most cases. Have they actually run
a full DBCC CHECKDB abd DBCC CHECKCATALOG lately?
--
Andrew J. Kelly SQL MVP
<anonymous@.discussions.microsoft.com> wrote in message
news:1cd0401c422b6$a765dec0$a401280a@.phx.gbl...
> Thats what is so odd, their DBA assures us that they
> restore and checkout ok at their end?
> >--Original Message--
> >If there are consistency errors with the restored db it
> is most likely they
> >exist in the original one. They need to fix the errors
> in the original db
> >before you can get good backups.
> >
> >--
> >Andrew J. Kelly SQL MVP
> >
> >
> >"Geoff Aukett" <anonymous@.discussions.microsoft.com>
> wrote in message
> >news:1c6c901c4222c$4b313d00$a301280a@.phx.gbl...
> >> Until recently we received backups of a clients
> database
> >> and restored it with no problems. They are running SQL
> >> 2000 on NT 4.0. About a month ago we noticed some
> problem
> >> with the backups, DBCC CHECKDB revealed consistency
> >> errors in the databases after restore. We are running
> SQL
> >> 2000 SP3a on XP Pro. They can restore there backup
> >> locally but when ever we restore them we get errors.
> >>
> >> Any help would be very much appreciated.
> >
> >
> >.
> >
and restored it with no problems. They are running SQL
2000 on NT 4.0. About a month ago we noticed some problem
with the backups, DBCC CHECKDB revealed consistency
errors in the databases after restore. We are running SQL
2000 SP3a on XP Pro. They can restore there backup
locally but when ever we restore them we get errors.
Any help would be very much appreciated.If there are consistency errors with the restored db it is most likely they
exist in the original one. They need to fix the errors in the original db
before you can get good backups.
--
Andrew J. Kelly SQL MVP
"Geoff Aukett" <anonymous@.discussions.microsoft.com> wrote in message
news:1c6c901c4222c$4b313d00$a301280a@.phx.gbl...
> Until recently we received backups of a clients database
> and restored it with no problems. They are running SQL
> 2000 on NT 4.0. About a month ago we noticed some problem
> with the backups, DBCC CHECKDB revealed consistency
> errors in the databases after restore. We are running SQL
> 2000 SP3a on XP Pro. They can restore there backup
> locally but when ever we restore them we get errors.
> Any help would be very much appreciated.|||Thats what is so odd, their DBA assures us that they
restore and checkout ok at their end?
>--Original Message--
>If there are consistency errors with the restored db it
is most likely they
>exist in the original one. They need to fix the errors
in the original db
>before you can get good backups.
>--
>Andrew J. Kelly SQL MVP
>
>"Geoff Aukett" <anonymous@.discussions.microsoft.com>
wrote in message
>news:1c6c901c4222c$4b313d00$a301280a@.phx.gbl...
>> Until recently we received backups of a clients
database
>> and restored it with no problems. They are running SQL
>> 2000 on NT 4.0. About a month ago we noticed some
problem
>> with the backups, DBCC CHECKDB revealed consistency
>> errors in the databases after restore. We are running
SQL
>> 2000 SP3a on XP Pro. They can restore there backup
>> locally but when ever we restore them we get errors.
>> Any help would be very much appreciated.
>
>.
>|||It's possible the backup file itself can get corrupted but in my experience
when this happens you get file errors in most cases. Have they actually run
a full DBCC CHECKDB abd DBCC CHECKCATALOG lately?
--
Andrew J. Kelly SQL MVP
<anonymous@.discussions.microsoft.com> wrote in message
news:1cd0401c422b6$a765dec0$a401280a@.phx.gbl...
> Thats what is so odd, their DBA assures us that they
> restore and checkout ok at their end?
> >--Original Message--
> >If there are consistency errors with the restored db it
> is most likely they
> >exist in the original one. They need to fix the errors
> in the original db
> >before you can get good backups.
> >
> >--
> >Andrew J. Kelly SQL MVP
> >
> >
> >"Geoff Aukett" <anonymous@.discussions.microsoft.com>
> wrote in message
> >news:1c6c901c4222c$4b313d00$a301280a@.phx.gbl...
> >> Until recently we received backups of a clients
> database
> >> and restored it with no problems. They are running SQL
> >> 2000 on NT 4.0. About a month ago we noticed some
> problem
> >> with the backups, DBCC CHECKDB revealed consistency
> >> errors in the databases after restore. We are running
> SQL
> >> 2000 SP3a on XP Pro. They can restore there backup
> >> locally but when ever we restore them we get errors.
> >>
> >> Any help would be very much appreciated.
> >
> >
> >.
> >
Faulty Restore
Until recently we received backups of a clients database
and restored it with no problems. They are running SQL
2000 on NT 4.0. About a month ago we noticed some problem
with the backups, DBCC CHECKDB revealed consistency
errors in the databases after restore. We are running SQL
2000 SP3a on XP Pro. They can restore there backup
locally but when ever we restore them we get errors.
Any help would be very much appreciated.If there are consistency errors with the restored db it is most likely they
exist in the original one. They need to fix the errors in the original db
before you can get good backups.
Andrew J. Kelly SQL MVP
"Geoff Aukett" <anonymous@.discussions.microsoft.com> wrote in message
news:1c6c901c4222c$4b313d00$a301280a@.phx
.gbl...
> Until recently we received backups of a clients database
> and restored it with no problems. They are running SQL
> 2000 on NT 4.0. About a month ago we noticed some problem
> with the backups, DBCC CHECKDB revealed consistency
> errors in the databases after restore. We are running SQL
> 2000 SP3a on XP Pro. They can restore there backup
> locally but when ever we restore them we get errors.
> Any help would be very much appreciated.|||Thats what is so odd, their DBA assures us that they
restore and checkout ok at their end?
>--Original Message--
>If there are consistency errors with the restored db it
is most likely they
>exist in the original one. They need to fix the errors
in the original db
>before you can get good backups.
>--
>Andrew J. Kelly SQL MVP
>
>"Geoff Aukett" <anonymous@.discussions.microsoft.com>
wrote in message
> news:1c6c901c4222c$4b313d00$a301280a@.phx
.gbl...
database[vbcol=seagreen]
problem[vbcol=seagreen]
SQL[vbcol=seagreen]
>
>.
>|||It's possible the backup file itself can get corrupted but in my experience
when this happens you get file errors in most cases. Have they actually run
a full DBCC CHECKDB abd DBCC CHECKCATALOG lately?
Andrew J. Kelly SQL MVP
<anonymous@.discussions.microsoft.com> wrote in message
news:1cd0401c422b6$a765dec0$a401280a@.phx
.gbl...[vbcol=seagreen]
> Thats what is so odd, their DBA assures us that they
> restore and checkout ok at their end?
>
> is most likely they
> in the original db
> wrote in message
> database
> problem
> SQL
and restored it with no problems. They are running SQL
2000 on NT 4.0. About a month ago we noticed some problem
with the backups, DBCC CHECKDB revealed consistency
errors in the databases after restore. We are running SQL
2000 SP3a on XP Pro. They can restore there backup
locally but when ever we restore them we get errors.
Any help would be very much appreciated.If there are consistency errors with the restored db it is most likely they
exist in the original one. They need to fix the errors in the original db
before you can get good backups.
Andrew J. Kelly SQL MVP
"Geoff Aukett" <anonymous@.discussions.microsoft.com> wrote in message
news:1c6c901c4222c$4b313d00$a301280a@.phx
.gbl...
> Until recently we received backups of a clients database
> and restored it with no problems. They are running SQL
> 2000 on NT 4.0. About a month ago we noticed some problem
> with the backups, DBCC CHECKDB revealed consistency
> errors in the databases after restore. We are running SQL
> 2000 SP3a on XP Pro. They can restore there backup
> locally but when ever we restore them we get errors.
> Any help would be very much appreciated.|||Thats what is so odd, their DBA assures us that they
restore and checkout ok at their end?
>--Original Message--
>If there are consistency errors with the restored db it
is most likely they
>exist in the original one. They need to fix the errors
in the original db
>before you can get good backups.
>--
>Andrew J. Kelly SQL MVP
>
>"Geoff Aukett" <anonymous@.discussions.microsoft.com>
wrote in message
> news:1c6c901c4222c$4b313d00$a301280a@.phx
.gbl...
database[vbcol=seagreen]
problem[vbcol=seagreen]
SQL[vbcol=seagreen]
>
>.
>|||It's possible the backup file itself can get corrupted but in my experience
when this happens you get file errors in most cases. Have they actually run
a full DBCC CHECKDB abd DBCC CHECKCATALOG lately?
Andrew J. Kelly SQL MVP
<anonymous@.discussions.microsoft.com> wrote in message
news:1cd0401c422b6$a765dec0$a401280a@.phx
.gbl...[vbcol=seagreen]
> Thats what is so odd, their DBA assures us that they
> restore and checkout ok at their end?
>
> is most likely they
> in the original db
> wrote in message
> database
> problem
> SQL
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:
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:
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
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
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 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)
> *
> ----
Subscribe to:
Posts (Atom)