Excel Import: running

Showing posts with label running. Show all posts

Thursday, March 29, 2012

ExecContextHit through SQL Profiler

Hello,
Hopefully someone can answer this question. I am running a procedure which uses Dynamic SQL ie: Scroll Cursor, User Functions, and sp_executesql to update a table. When I run this sp in a query window it runs much faster then when it is called from a Jo
b. I ran Profiler traces with both methods and noticed that there were SP:ExecContectHit entries in the Traces. Does this mean that at the point that I see these statements that there is an sp_recompile occurring within the sp? There is definitely a sligh
t delay in the job sp after each of the SP:ContectHit statements. If it is recompiling is there anyway to prohibit that?
Thanks !!
ExecContextHit means that an execution context version (has
session specific info) was found in cache.
Monitor SP:Recompile for recompiles. If you are experiencing
recompiles, you can reference the following:
INF: Troubleshooting Stored Procedure Recompilation
http://support.microsoft.com/?id=243586
You should also make sure the job has set nocount on in the
beginning of the stored procedure and T-SQL batches.
Depending on your version of SQL Server, you can also hit
issues with delays in Agent jobs if you aren't on the latest
service pack. I think it was SQL 7, SP4 that addressed
issues related to this.
-Sue
On Mon, 28 Jun 2004 13:43:01 -0700, "nupee"
<nupee@.discussions.microsoft.com> wrote:

>Hello,
>Hopefully someone can answer this question. I am running a procedure which uses Dynamic SQL ie: Scroll Cursor, User Functions, and sp_executesql to update a table. When I run this sp in a query window it runs much faster then when it is called from a J
ob. I ran Profiler traces with both methods and noticed that there were SP:ExecContectHit entries in the Traces. Does this mean that at the point that I see these statements that there is an sp_recompile occurring within the sp? There is definitely a slig
ht delay in the job sp after each of the SP:ContectHit statements. If it is recompiling is there anyway to prohibit that?
>Thanks !!
|||ExecContextHit means that an execution context version (has
session specific info) was found in cache.
Monitor SP:Recompile for recompiles. If you are experiencing
recompiles, you can reference the following:
INF: Troubleshooting Stored Procedure Recompilation
http://support.microsoft.com/?id=243586
You should also make sure the job has set nocount on in the
beginning of the stored procedure and T-SQL batches.
Depending on your version of SQL Server, you can also hit
issues with delays in Agent jobs if you aren't on the latest
service pack. I think it was SQL 7, SP4 that addressed
issues related to this.
-Sue
On Mon, 28 Jun 2004 13:43:01 -0700, "nupee"
<nupee@.discussions.microsoft.com> wrote:

>Hello,
>Hopefully someone can answer this question. I am running a procedure which uses Dynamic SQL ie: Scroll Cursor, User Functions, and sp_executesql to update a table. When I run this sp in a query window it runs much faster then when it is called from a J
ob. I ran Profiler traces with both methods and noticed that there were SP:ExecContectHit entries in the Traces. Does this mean that at the point that I see these statements that there is an sp_recompile occurring within the sp? There is definitely a slig
ht delay in the job sp after each of the SP:ContectHit statements. If it is recompiling is there anyway to prohibit that?
>Thanks !!
|||The set nocount on worked. Thank You !
"Sue Hoegemeier" wrote:
[vbcol=seagreen]
> ExecContextHit means that an execution context version (has
> session specific info) was found in cache.
> Monitor SP:Recompile for recompiles. If you are experiencing
> recompiles, you can reference the following:
> INF: Troubleshooting Stored Procedure Recompilation
> http://support.microsoft.com/?id=243586
> You should also make sure the job has set nocount on in the
> beginning of the stored procedure and T-SQL batches.
> Depending on your version of SQL Server, you can also hit
> issues with delays in Agent jobs if you aren't on the latest
> service pack. I think it was SQL 7, SP4 that addressed
> issues related to this.
> -Sue
> On Mon, 28 Jun 2004 13:43:01 -0700, "nupee"
> <nupee@.discussions.microsoft.com> wrote:
Job. I ran Profiler traces with both methods and noticed that there were SP:ExecContectHit entries in the Traces. Does this mean that at the point that I see these statements that there is an sp_recompile occurring within the sp? There is definitely a sl
ight delay in the job sp after each of the SP:ContectHit statements. If it is recompiling is there anyway to prohibit that?
>
|||Your welcome - thanks for posting back that it fixed the
issue.
-Sue
On Tue, 29 Jun 2004 12:48:01 -0700, "nupee"
<nupee@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>The set nocount on worked. Thank You !
>"Sue Hoegemeier" wrote:
a Job. I ran Profiler traces with both methods and noticed that there were SP:ExecContectHit entries in the Traces. Does this mean that at the point that I see these statements that there is an sp_recompile occurring within the sp? There is definitely a s
light delay in the job sp after each of the SP:ContectHit statements. If it is recompiling is there anyway to prohibit that?[vbcol=seagreen]
|||The set nocount on worked. Thank You !
"Sue Hoegemeier" wrote:
[vbcol=seagreen]
> ExecContextHit means that an execution context version (has
> session specific info) was found in cache.
> Monitor SP:Recompile for recompiles. If you are experiencing
> recompiles, you can reference the following:
> INF: Troubleshooting Stored Procedure Recompilation
> http://support.microsoft.com/?id=243586
> You should also make sure the job has set nocount on in the
> beginning of the stored procedure and T-SQL batches.
> Depending on your version of SQL Server, you can also hit
> issues with delays in Agent jobs if you aren't on the latest
> service pack. I think it was SQL 7, SP4 that addressed
> issues related to this.
> -Sue
> On Mon, 28 Jun 2004 13:43:01 -0700, "nupee"
> <nupee@.discussions.microsoft.com> wrote:
Job. I ran Profiler traces with both methods and noticed that there were SP:ExecContectHit entries in the Traces. Does this mean that at the point that I see these statements that there is an sp_recompile occurring within the sp? There is definitely a sl
ight delay in the job sp after each of the SP:ContectHit statements. If it is recompiling is there anyway to prohibit that?
>
|||Your welcome - thanks for posting back that it fixed the
issue.
-Sue
On Tue, 29 Jun 2004 12:48:01 -0700, "nupee"
<nupee@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>The set nocount on worked. Thank You !
>"Sue Hoegemeier" wrote:
a Job. I ran Profiler traces with both methods and noticed that there were SP:ExecContectHit entries in the Traces. Does this mean that at the point that I see these statements that there is an sp_recompile occurring within the sp? There is definitely a s
light delay in the job sp after each of the SP:ContectHit statements. If it is recompiling is there anyway to prohibit that?[vbcol=seagreen]

Tuesday, March 27, 2012

EXEC sp_serveroption

Does the sql server require a re-start after running EXEC sp_serveroption
command?Hi,
I have tried most of the parameters in sp_severoptions procedure and those
do not require any restart of sql server service.
Thanks
Hari
SQL Server MVP
"Arul" wrote:
> Does the sql server require a re-start after running EXEC sp_serveroption
> command?
>

EXEC sp_serveroption

Does the sql server require a re-start after running EXEC sp_serveroption
command?Hi,
I have tried most of the parameters in sp_severoptions procedure and those
do not require any restart of sql server service.
Thanks
Hari
SQL Server MVP
"Arul" wrote:

> Does the sql server require a re-start after running EXEC sp_serveroption
> command?
>

EXEC sp_serveroption

Does the sql server require a re-start after running EXEC sp_serveroption
command?
Hi,
I have tried most of the parameters in sp_severoptions procedure and those
do not require any restart of sql server service.
Thanks
Hari
SQL Server MVP
"Arul" wrote:

> Does the sql server require a re-start after running EXEC sp_serveroption
> command?
>

EXEC Query Performance

I am running into a situation where a program runs a stored procedure, withi
n that stored procedure a SQL statement is built and then executed using the
EXEC command. It looks like that when the generated statement exceeds a ce
rtain time threshold, the s
tored procedure exits without any warning.
I know there is no warning because I have run profiler and I get a statement
start time but no end time. I have also logged every step in the stored pr
ocedure and it just bails on me. Any ideas?Funny you mention that Peter, I run the stored procedure in QA and it runs f
ine. The funny thing is that when the stored proc fails, the rest of the pro
cess completes. I have not been able to get access to the .Net code to view
how it is executed yet.
"Dan" wrote:

> I am running into a situation where a program runs a stored procedure, within that
stored procedure a SQL statement is built and then executed using the EXEC command.
It looks like that when the generated statement exceeds a certain time threshold,
the
stored procedure exits without any warning.
> I know there is no warning because I have run profiler and I get a statement start
time but no end time. I have also logged every step in the stored procedure and it
just bails on me. Any ideas?|||Your connection timeout setting is probably too low. Try adjusting it.
Andrew J. Kelly SQL MVP
"Dan" <Dan@.discussions.microsoft.com> wrote in message
news:DDE31E4A-8E88-4F76-90EE-6D04541D13C5@.microsoft.com...
> I am running into a situation where a program runs a stored procedure,
within that stored procedure a SQL statement is built and then executed
using the EXEC command. It looks like that when the generated statement
exceeds a certain time threshold, the stored procedure exits without any
warning.
> I know there is no warning because I have run profiler and I get a
statement start time but no end time. I have also logged every step in the
stored procedure and it just bails on me. Any ideas?|||Andrew, that is what I am thinking too. I have finally gotten a hold of the
code the developer uses to call this. Can any of you see anything wrong wi
th this code?
Dim cnTemp As Connection
Dim rsTemp As Recordset '--ADODB.Recordset
Dim strSQL As String
Set cnTemp = New ADODB.Connection
Set rsTemp = New ADODB.Recordset
cnTemp.ConnectionString = "Provider=SQLOLEDB;Data Source=PowerWare2000;Initi
al Catalog=PWProd; User ID=*******;Password=********;"
cnTemp.Open
strSQL = "Exec " & SP_CreatePrintJob & " " & JobTicketNr
rsTemp.CursorLocation = adUseClient
rsTemp.CursorType = adOpenStatic
rsTemp.LockType = adLockOptimistic
rsTemp.Open strSQL, cnTemp, , , adCmdText
"Andrew J. Kelly" wrote:

> Your connection timeout setting is probably too low. Try adjusting it.
> --
> Andrew J. Kelly SQL MVP
>
> "Dan" <Dan@.discussions.microsoft.com> wrote in message
> news:DDE31E4A-8E88-4F76-90EE-6D04541D13C5@.microsoft.com...
> within that stored procedure a SQL statement is built and then executed
> using the EXEC command. It looks like that when the generated statement
> exceeds a certain time threshold, the stored procedure exits without any
> warning.
> statement start time but no end time. I have also logged every step in th
e
> stored procedure and it just bails on me. Any ideas?
>
>|||You don't actually set the timeout and by default I believe it is set to 30
seconds. This should help with that:
http://www.aspfaq.com/show.asp?id=2066
But you also want to optimize these queries so they don't take so long to
begin with. Using stored procedures with parameters instead of adhoc sql is
a good start.
Andrew J. Kelly SQL MVP
"Daniel Avsec" <DanielAvsec@.discussions.microsoft.com> wrote in message
news:9F7A3F1B-3868-4B19-9A5F-63462C3D48A4@.microsoft.com...
> Andrew, that is what I am thinking too. I have finally gotten a hold of
the code the developer uses to call this. Can any of you see anything wrong
with this code?
> Dim cnTemp As Connection
> Dim rsTemp As Recordset '--ADODB.Recordset
> Dim strSQL As String
> Set cnTemp = New ADODB.Connection
> Set rsTemp = New ADODB.Recordset
> cnTemp.ConnectionString = "Provider=SQLOLEDB;Data
Source=PowerWare2000;Initial Catalog=PWProd; User
ID=*******;Password=********;"[vbcol=seagreen]
> cnTemp.Open
> strSQL = "Exec " & SP_CreatePrintJob & " " & JobTicketNr
> rsTemp.CursorLocation = adUseClient
> rsTemp.CursorType = adOpenStatic
> rsTemp.LockType = adLockOptimistic
> rsTemp.Open strSQL, cnTemp, , , adCmdText
> "Andrew J. Kelly" wrote:
>
the[vbcol=seagreen]sql

EXEC Query Performance

I am running into a situation where a program runs a stored procedure, within that stored procedure a SQL statement is built and then executed using the EXEC command. It looks like that when the generated statement exceeds a certain time threshold, the stored procedure exits without any warning.
I know there is no warning because I have run profiler and I get a statement start time but no end time. I have also logged every step in the stored procedure and it just bails on me. Any ideas?How are you executing the original SP, and have you tried
it in QA ?
>--Original Message--
>I am running into a situation where a program runs a
stored procedure, within that stored procedure a SQL
statement is built and then executed using the EXEC
command. It looks like that when the generated statement
exceeds a certain time threshold, the stored procedure
exits without any warning.
>I know there is no warning because I have run profiler
and I get a statement start time but no end time. I have
also logged every step in the stored procedure and it just
bails on me. Any ideas?
>.
>|||Your connection timeout setting is probably too low. Try adjusting it.
--
Andrew J. Kelly SQL MVP
"Dan" <Dan@.discussions.microsoft.com> wrote in message
news:DDE31E4A-8E88-4F76-90EE-6D04541D13C5@.microsoft.com...
> I am running into a situation where a program runs a stored procedure,
within that stored procedure a SQL statement is built and then executed
using the EXEC command. It looks like that when the generated statement
exceeds a certain time threshold, the stored procedure exits without any
warning.
> I know there is no warning because I have run profiler and I get a
statement start time but no end time. I have also logged every step in the
stored procedure and it just bails on me. Any ideas?|||You don't actually set the timeout and by default I believe it is set to 30
seconds. This should help with that:
http://www.aspfaq.com/show.asp?id=2066
But you also want to optimize these queries so they don't take so long to
begin with. Using stored procedures with parameters instead of adhoc sql is
a good start.
--
Andrew J. Kelly SQL MVP
"Daniel Avsec" <DanielAvsec@.discussions.microsoft.com> wrote in message
news:9F7A3F1B-3868-4B19-9A5F-63462C3D48A4@.microsoft.com...
> Andrew, that is what I am thinking too. I have finally gotten a hold of
the code the developer uses to call this. Can any of you see anything wrong
with this code?
> Dim cnTemp As Connection
> Dim rsTemp As Recordset '--ADODB.Recordset
> Dim strSQL As String
> Set cnTemp = New ADODB.Connection
> Set rsTemp = New ADODB.Recordset
> cnTemp.ConnectionString = "Provider=SQLOLEDB;Data
Source=PowerWare2000;Initial Catalog=PWProd; User
ID=*******;Password=********;"
> cnTemp.Open
> strSQL = "Exec " & SP_CreatePrintJob & " " & JobTicketNr
> rsTemp.CursorLocation = adUseClient
> rsTemp.CursorType = adOpenStatic
> rsTemp.LockType = adLockOptimistic
> rsTemp.Open strSQL, cnTemp, , , adCmdText
> "Andrew J. Kelly" wrote:
> > Your connection timeout setting is probably too low. Try adjusting it.
> >
> > --
> > Andrew J. Kelly SQL MVP
> >
> >
> > "Dan" <Dan@.discussions.microsoft.com> wrote in message
> > news:DDE31E4A-8E88-4F76-90EE-6D04541D13C5@.microsoft.com...
> > > I am running into a situation where a program runs a stored procedure,
> > within that stored procedure a SQL statement is built and then executed
> > using the EXEC command. It looks like that when the generated statement
> > exceeds a certain time threshold, the stored procedure exits without any
> > warning.
> > >
> > > I know there is no warning because I have run profiler and I get a
> > statement start time but no end time. I have also logged every step in
the
> > stored procedure and it just bails on me. Any ideas?
> >
> >
> >

Monday, March 26, 2012

EXEC Query Performance

I am running into a situation where a program runs a stored procedure, within that stored procedure a SQL statement is built and then executed using the EXEC command. It looks like that when the generated statement exceeds a certain time threshold, the s
tored procedure exits without any warning.
I know there is no warning because I have run profiler and I get a statement start time but no end time. I have also logged every step in the stored procedure and it just bails on me. Any ideas?
Funny you mention that Peter, I run the stored procedure in QA and it runs fine. The funny thing is that when the stored proc fails, the rest of the process completes. I have not been able to get access to the .Net code to view how it is executed yet.
"Dan" wrote:

> I am running into a situation where a program runs a stored procedure, within that stored procedure a SQL statement is built and then executed using the EXEC command. It looks like that when the generated statement exceeds a certain time threshold, the
stored procedure exits without any warning.
> I know there is no warning because I have run profiler and I get a statement start time but no end time. I have also logged every step in the stored procedure and it just bails on me. Any ideas?
|||Your connection timeout setting is probably too low. Try adjusting it.
Andrew J. Kelly SQL MVP
"Dan" <Dan@.discussions.microsoft.com> wrote in message
news:DDE31E4A-8E88-4F76-90EE-6D04541D13C5@.microsoft.com...
> I am running into a situation where a program runs a stored procedure,
within that stored procedure a SQL statement is built and then executed
using the EXEC command. It looks like that when the generated statement
exceeds a certain time threshold, the stored procedure exits without any
warning.
> I know there is no warning because I have run profiler and I get a
statement start time but no end time. I have also logged every step in the
stored procedure and it just bails on me. Any ideas?
|||Andrew, that is what I am thinking too. I have finally gotten a hold of the code the developer uses to call this. Can any of you see anything wrong with this code?
Dim cnTemp As Connection
Dim rsTemp As Recordset '--ADODB.Recordset
Dim strSQL As String
Set cnTemp = New ADODB.Connection
Set rsTemp = New ADODB.Recordset
cnTemp.ConnectionString = "Provider=SQLOLEDB;Data Source=PowerWare2000;Initial Catalog=PWProd; User ID=*******;Password=********;"
cnTemp.Open
strSQL = "Exec " & SP_CreatePrintJob & " " & JobTicketNr
rsTemp.CursorLocation = adUseClient
rsTemp.CursorType = adOpenStatic
rsTemp.LockType = adLockOptimistic
rsTemp.Open strSQL, cnTemp, , , adCmdText
"Andrew J. Kelly" wrote:

> Your connection timeout setting is probably too low. Try adjusting it.
> --
> Andrew J. Kelly SQL MVP
>
> "Dan" <Dan@.discussions.microsoft.com> wrote in message
> news:DDE31E4A-8E88-4F76-90EE-6D04541D13C5@.microsoft.com...
> within that stored procedure a SQL statement is built and then executed
> using the EXEC command. It looks like that when the generated statement
> exceeds a certain time threshold, the stored procedure exits without any
> warning.
> statement start time but no end time. I have also logged every step in the
> stored procedure and it just bails on me. Any ideas?
>
>
|||You don't actually set the timeout and by default I believe it is set to 30
seconds. This should help with that:
http://www.aspfaq.com/show.asp?id=2066
But you also want to optimize these queries so they don't take so long to
begin with. Using stored procedures with parameters instead of adhoc sql is
a good start.
Andrew J. Kelly SQL MVP
"Daniel Avsec" <DanielAvsec@.discussions.microsoft.com> wrote in message
news:9F7A3F1B-3868-4B19-9A5F-63462C3D48A4@.microsoft.com...
> Andrew, that is what I am thinking too. I have finally gotten a hold of
the code the developer uses to call this. Can any of you see anything wrong
with this code?
> Dim cnTemp As Connection
> Dim rsTemp As Recordset '--ADODB.Recordset
> Dim strSQL As String
> Set cnTemp = New ADODB.Connection
> Set rsTemp = New ADODB.Recordset
> cnTemp.ConnectionString = "Provider=SQLOLEDB;Data
Source=PowerWare2000;Initial Catalog=PWProd; User
ID=*******;Password=********;"[vbcol=seagreen]
> cnTemp.Open
> strSQL = "Exec " & SP_CreatePrintJob & " " & JobTicketNr
> rsTemp.CursorLocation = adUseClient
> rsTemp.CursorType = adOpenStatic
> rsTemp.LockType = adLockOptimistic
> rsTemp.Open strSQL, cnTemp, , , adCmdText
> "Andrew J. Kelly" wrote:
the[vbcol=seagreen]

Monday, March 12, 2012

Exchange 5.5 email problem

I have an Active Directory network with an Exchange 5.5 server running on a
Windows NT box.
I am hosting 3 email domains on that box. For example lets call them
mydomain1.com, mydomain2.com and mydomain3.com.
All external emails come in and work just fine except for the mydomain3.com
emails. My internal Active Dirctory domain is mydomain3.com.
Currently my Exchange server on the NT box is pointing at the internal DNS
server that forwards requests to the outside. I was thinking my problem is
that and that I might need to have the NT box with Exchange on it use our
ISP DNS servers instead.
Any ideas? I read something about Active Directory Connector, but didn't
know if I need to look at that or how the DNS settings are set up on the
Exchange server.
Thanks...if anyone wants to email me directly...feel free!!
"CJ" <chrisj@.illicom.net> wrote:

>I have an Active Directory network with an Exchange 5.5 server running on a
>Windows NT box.
>I am hosting 3 email domains on that box. For example lets call them
>mydomain1.com, mydomain2.com and mydomain3.com.
>All external emails come in and work just fine except for the mydomain3.com
>emails. My internal Active Dirctory domain is mydomain3.com.
>Currently my Exchange server on the NT box is pointing at the internal DNS
>server that forwards requests to the outside. I was thinking my problem is
>that and that I might need to have the NT box with Exchange on it use our
>ISP DNS servers instead.
>Any ideas? I read something about Active Directory Connector, but didn't
>know if I need to look at that or how the DNS settings are set up on the
>Exchange server.
>Thanks...if anyone wants to email me directly...feel free!!
>
If your Exchange server is running without ADC then it's not AD aware
(but you'd worked that out)
The Internet Mail Service should receive mail for all three domains
and route them to wherever you need.
Can you confirm that all three domains are set to "Route Inbound"? Or
alternatively two of the domains are routed to a third domain (be it
1, 2 or 3)
Then you need to make sure that you are receiving the mails for
domain3.com in the first place. Is it a registered domain? Does it
have MX records that point to a valid A record in the ISP DNS?
If domain3 isn't valid then you're not going to get mail into it.
Check by doing an nslookup against all three domains and make sure
that they point to the same A record and that the A record matches the
IP address you want the mail delivered to.#
Mark Arnold MCSA MCSE+M MVP,
FAQ: http://www.swinc.com/resource/exchange.htm
Blog: http://www.msexchange.me.uk
|||Figured it out.. the problem ended up being i simply needed my Exchange
server to have the DNS settings for my ISP, not my internal DNS servers
"Mark Arnold [MVP]" <mark@.mvps.org> wrote in message
news:9gaif051c15fpakgru8be75a35dgaefh9p@.4ax.com... [vbcol=seagreen]
> "CJ" <chrisj@.illicom.net> wrote:
a[vbcol=seagreen]
mydomain3.com[vbcol=seagreen]
DNS[vbcol=seagreen]
is
> If your Exchange server is running without ADC then it's not AD aware
> (but you'd worked that out)
> The Internet Mail Service should receive mail for all three domains
> and route them to wherever you need.
> Can you confirm that all three domains are set to "Route Inbound"? Or
> alternatively two of the domains are routed to a third domain (be it
> 1, 2 or 3)
> Then you need to make sure that you are receiving the mails for
> domain3.com in the first place. Is it a registered domain? Does it
> have MX records that point to a valid A record in the ISP DNS?
> If domain3 isn't valid then you're not going to get mail into it.
> Check by doing an nslookup against all three domains and make sure
> that they point to the same A record and that the A record matches the
> IP address you want the mail delivered to.#
>
> Mark Arnold MCSA MCSE+M MVP,
> FAQ: http://www.swinc.com/resource/exchange.htm
> Blog: http://www.msexchange.me.uk

Excessive Logon Audit Events

I have a stand alone Windows 2000 server sp4 running SQL 2000 sp3. I need t
o be able to audit successful and failed Logon events and I have the group p
olicy set to do this. The box is in an offsite facility connected by at T1
over a VPN connection. My
SQL developers have the remote server registered in their Enterprise Manager
along with the local SQL servers. When they have Enterprise Manager open,
the following event is logged on the remote SQL server every 10 seconds. It
is filling my log and maki
ng it difficult to read. Why is this happening and can I make it stop?
Event Type: Success Audit
Event Source: Security
Event Category: Account Logon
Event ID: 680
Date: 6/28/2004
Time: 9:01:29 AM
User: NT AUTHORITY\SYSTEM
Computer: CONDOR
Description:
Account Used for Logon by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
Account Name:
SomeUser
Workstation:
UserWorkstationIn Enterprise Manager (the devs need to do this on their PC's) goto
Tools>Options and uncheck the Poll Server checkbox. As you will see the
default interval for this polling is 10 seconds.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Chris Wilkins" <Chris Wilkins@.discussions.microsoft.com> wrote in message
news:2D79110F-901D-43F2-9DA6-1AD0A97CC90F@.microsoft.com...
> I have a stand alone Windows 2000 server sp4 running SQL 2000 sp3. I need
to be able to audit successful and failed Logon events and I have the group
policy set to do this. The box is in an offsite facility connected by at T1
over a VPN connection. My SQL developers have the remote server registered
in their Enterprise Manager along with the local SQL servers. When they
have Enterprise Manager open, the following event is logged on the remote
SQL server every 10 seconds. It is filling my log and making it difficult
to read. Why is this happening and can I make it stop?
> Event Type: Success Audit
> Event Source: Security
> Event Category: Account Logon
> Event ID: 680
> Date: 6/28/2004
> Time: 9:01:29 AM
> User: NT AUTHORITY\SYSTEM
> Computer: CONDOR
> Description:
> Account Used for Logon by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
> Account Name:
> SomeUser
> Workstation:
> UserWorkstation
>

Friday, March 9, 2012

EXCEPTION_ACCESS_VIOLATION within SQL Server when running SSIS package

Hi, I'm not sure if this is the right forum, so please point me in the right direction if it isn't.

I'm getting an EXCEPTION_ACCESS_VIOLATION and a minidump in the SQL server logs when using the OLE DB Provider for SQL Server.

The error occurs when I run an SSIS package non-interactively (using Package.Execute). The odd thing is that the package works fine when I run it from within Visual Studio. Also, this same bit of code was working fine a couple of weeks ago (it's part of my unit tests, it just started failing when I added a new, unrelated SSIS package to the project). The error occurs during the validation phase.

Here's the first part of the stack dump, which just shows that the provider is executing a very simple statement (SELECT * FROM [table-name]):

Code Snippet

* BEGIN STACK DUMP:
* 05/14/07 10:42:34 spid 56
*
*
* Exception Address = 01CBBF90 Module(sqlservr+00CBBF90)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred writing address 0000001C
* Input Buffer 108 bytes -
* ?? & ?> ff ff 02 00 00 00 00 01 26 04 00 00 00 e7 3e 00 09 04
* 2> s e l e c t 00 01 32 3e 00 73 00 65 00 6c 00 65 00 63 00 74 00 20
* * f r o m [ d 00 2a 00 20 00 66 00 72 00 6f 00 6d 00 20 00 5b 00 64
* b o ] . [ P x p T 00 62 00 6f 00 5d 00 2e 00 5b 00 50 00 78 00 70 00 54
* a r g e t ] & 00 61 00 72 00 67 00 65 00 74 00 5d 00 00 01 26 04 04
* & & 02 80 03 00 00 01 26 04 04 04 80 04 00 00 01 26 04 00
*

I presume this is something for the SQL Server team; how should I go about getting this resolved?

Cheers Rich

To report this you need to open a ticket with Microsoft PSS. Your support options can be found here https://support.microsoft.com/common/international.aspx?rdpath=1&gprid=2855.

EXCEPTION_ACCESS_VIOLATION in RangeGenerator::GetNextRange

Hi,
I'm getting errors from SQL Server 2000 SP3 running under Windows Server
2003. Rebooting the server doesn't help and running DBCC CHECKDB doesn't
give any errors. I've looked in the Knowledge Base for articles dealing
with EXCEPTION_ACCESS_VIOLATION errors, but none of them seen to apply to
me.
Here is part of what is showing up in the log:
SqlDumpExceptionHandler: Process 1780 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process. *
************************************************** *****************************
*
* BEGIN STACK DUMP:
* 06/25/04 14:49:33 spid 55
*
* Exception Address = 007F8A40 (RangeGenerator::GetNextRange + 000003D0
Line 0+00000000) * Exception Code = c0000005
EXCEPTION_ACCESS_VIOLATION * Access Violation occurred reading address
E89C400A * Input Buffer 2342 bytes -
* select distinct rb.brand_cd,rb.report_item_cd into #temp4rb from
REPORT_ * LIST rl,REPORT_BRANDS rb where service_cd=1 and report_cd=35
and report_ * table_cd=4 and rl.report_item_cd=rb.report_item_cd select
market_cd,sto * re_cd,ad_dt_yyyymm,report_item_cd,ad_quality_cd,su m(
ad_cnt) ad_cnt into * #temp4ac from FEAT_SUM_QUAL_REBATE f,#temp4rb rb
where f.brand_cd=rb.br * and_cd and market_cd in
(1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17 *
,18,19,20,21,22,23,24,25,27,28,29,31,32,34,35,36,3 7,38,40,44,46,49,50,52 *
,53,57,77,78,85,86,87) and ad_dt_yyyymm in ( 200405,200404,200403,
* 200402,200401,200312,200311,200310,200309,200308,2 00307,200306) group
by * market_cd,store_cd,ad_dt_yyyymm,report_item_cd,ad_ quality_cd *
* MODULE BASE END SIZE * sqlservr
00400000 00B2CFFF 0072d000 * ntdll
77F40000 77FF9FFF 000ba000 * kernel32
77E40000 77F33FFF 000f4000 * ADVAPI32 77DA0000
77E2FFFF 00090000 * RPCRT4 77C50000 77CF3FFF
000a4000 * USER32 77D00000 77D8EFFF 0008f000 *
GDI32 77C00000 77C43FFF 00044000 * OPENDS60
41060000 41065FFF 00006000 * MSVCRT
77BA0000 77BF3FFF 00054000 * UMS
41070000 4107CFFF 0000d000 * SQLSORT 42AE0000
42B6FFFF 00090000 * MSVCIRT 60020000 6002FFFF
00010000 * sqlevn70 41080000 41086FFF 00007000 *
NETAPI32 02C60000 02CB2FFF 00053000 * ole32
030D0000 031F3FFF 00124000 * XOLEHLP
03200000 03205FFF 00006000 * MSDTCPRX
03210000 03280FFF 00071000 * OLEAUT32 03290000
0330CFFF 0007d000 * MSVCP60 03310000 03370FFF
00061000 * MTXCLU 03380000 03397FFF 00018000 *
VERSION 033A0000 033A7FFF 00008000 * WSOCK32
033B0000 033B8FFF 00009000 * WS2_32
033C0000 033D7FFF 00018000 * WS2HELP
033E0000 033E7FFF 00008000 * CLUSAPI 03430000
03440FFF 00011000 * RESUTILS 03450000 03461FFF
00012000 * USERENV 03470000 03529FFF 000ba000 *
MFC42u 03530000 03623FFF 000f4000 * secur32
036B0000 036C2FFF 00013000 * mswsock
036E0000 03722FFF 00043000 * DNSAPI
03730000 03756FFF 00027000 * winrnr 037A0000
037A6FFF 00007000 * WLDAP32 037B0000 037DEFFF
0002f000 * rasadhlp 03800000 03804FFF 00005000 *
SSNMPN70 00C70000 00C75FFF 00006000 * SSNETLIB
00C80000 00C94FFF 00015000 * security
044B0000 044B3FFF 00004000 * wshtcpip
04500000 04507FFF 00008000 * SSmsLPCn 04510000
04516FFF 00007000 * ntdsapi 04530000 04545FFF
00016000 * SQLFTQRY 04420000 04451FFF 00032000 *
CLBCatQ 04A60000 04ADDFFF 0007e000 * COMRes
04AE0000 04BA5FFF 000c6000 * sqloledb
04BB0000 04C35FFF 00086000 * MSDART
04480000 044A8FFF 00029000 * COMCTL32 04C40000
04CCFFFF 00090000 * comdlg32 04CD0000 04D16FFF
00047000 * SHLWAPI 04D20000 04D68FFF 00049000 *
SHELL32 04D70000 0554CFFF 007dd000 * MSDATL3
045B0000 045C7FFF 00018000 * comctl32
05550000 05635FFF 000e6000 * oledb32
059E0000 05A5CFFF 0007d000 * OLEDB32R 05A60000
05A70FFF 00011000 * rsaenh 0FFD0000 0FFFCFFF
0002d000 * PSAPI 05B00000 05B0AFFF 0000b000 *
xpstar 03050000 03096FFF 00047000 * SQLRESLD
030A0000 030A6FFF 00007000 * SQLSVC
030B0000 030C6FFF 00017000 * ODBC32
05C10000 05C49FFF 0003a000 * odbcbcp 05C50000
05C55FFF 00006000 * W95SCM 05C60000 05C6BFFF
0000c000 * SQLUNIRL 05C70000 05C9CFFF 0002d000 *
WINSPOOL 05CA0000 05CC5FFF 00026000 * SHFOLDER
05CD0000 05CD8FFF 00009000 * odbcint
05EB0000 05EC6FFF 00017000 * NDDEAPI
05FE0000 05FE6FFF 00007000 * SQLSVC 05FF0000
05FF5FFF 00006000 * xpstar 06000000 06008FFF
00009000 * dbghelp 06840000 068F4FFF 000b5000 *
* Edi: 067BFCD8: 3AE52EB8 067BFD10 A7FFFFFA 389C2000 067BFDB4
0097C46F * Esi: 389C2000: 01000201 00018000 00000000 00150000
00000000 00330000 * Eax: 58001005: 00000000 03000000 00000B00
8C000000 88000002 88000002 * Ebx: 389E8708: 3868DCE4 000004F7
00000004 000004F4 00000004 00000000 * Ecx: 00000033:
* Edx: 00000002:
* Eip: 007F8A40: 4604B70F 8D4C4303 8BFA3074 8BA50C45 A5663448
C150418B * Ebp: 067BFCF4: 067BFD10 00801CB1 3AE52D68 3AE225E8
00000000 3AE52998 * SegCs: 0000001B:
* EFlags: 00010207: 43003B00 5C003A00 49005700 44004E00 57004F00
3B005300 * Esp: 067BFC6C: 00000001 3AE52B44 00000000 00000000
00000000 00C567A0 * SegSs: 00000023:
*
************************************************** *****************************
*
* Short Stack Dump
* 007F8A40 Module(sqlservr+003F8A40)
(RangeGenerator::GetNextRange+000003D0) * 00801CB1
Module(sqlservr+00401CB1) (RowsetSS::FetchNextRow+00000153) * 0042A4F6
Module(sqlservr+0002A4F6) (CQScanRowset::GetRowWithPrefetch+00000040) *
0042C21B Module(sqlservr+0002C21B) (CQScanRange::GetRow+000000EF) *
004314C9 Module(sqlservr+000314C9) (CQScanHashMatch::Iterate+00000BAF) *
00431B41 Module(sqlservr+00031B41) (CQScanHashMatch::GetRow+0000009F) *
006FCBF7 Module(sqlservr+002FCBF7) (CQScanXProducer::Open+0000039B) *
006FC656 Module(sqlservr+002FC656) (FnProducerThread+0000020E) * 0051274C
Module(sqlservr+0011274C) (subproc_main+000000C2) * 41075002
Module(UMS+00005002) (ProcessWorkRequests+00000272) * 41074698
Module(UMS+00004698) (ThreadStartRoutine+00000098) * 77BC90A2
Module(MSVCRT+000290A2) (endthread+000000A6) * 77E4A990
Module(kernel32+0000A990) (FlsSetValue+00000779)
If you don't find anything on KB, are up on sp and CHECKDB comes out clean, it is time for a case
with MS Support...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Glen K" <blah@.blah.com> wrote in message news:pan.2004.06.25.19.18.22.966869@.blah.com...
> Hi,
> I'm getting errors from SQL Server 2000 SP3 running under Windows Server
> 2003. Rebooting the server doesn't help and running DBCC CHECKDB doesn't
> give any errors. I've looked in the Knowledge Base for articles dealing
> with EXCEPTION_ACCESS_VIOLATION errors, but none of them seen to apply to
> me.
> Here is part of what is showing up in the log:
>
> SqlDumpExceptionHandler: Process 1780 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process. *
> ************************************************** *****************************
> *
> * BEGIN STACK DUMP:
> * 06/25/04 14:49:33 spid 55
> *
> * Exception Address = 007F8A40 (RangeGenerator::GetNextRange + 000003D0
> Line 0+00000000) * Exception Code = c0000005
> EXCEPTION_ACCESS_VIOLATION * Access Violation occurred reading address
> E89C400A * Input Buffer 2342 bytes -
> * select distinct rb.brand_cd,rb.report_item_cd into #temp4rb from
> REPORT_ * LIST rl,REPORT_BRANDS rb where service_cd=1 and report_cd=35
> and report_ * table_cd=4 and rl.report_item_cd=rb.report_item_cd select
> market_cd,sto * re_cd,ad_dt_yyyymm,report_item_cd,ad_quality_cd,su m(
> ad_cnt) ad_cnt into * #temp4ac from FEAT_SUM_QUAL_REBATE f,#temp4rb rb
> where f.brand_cd=rb.br * and_cd and market_cd in
> (1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17 *
> ,18,19,20,21,22,23,24,25,27,28,29,31,32,34,35,36,3 7,38,40,44,46,49,50,52 *
> ,53,57,77,78,85,86,87) and ad_dt_yyyymm in ( 200405,200404,200403,
> * 200402,200401,200312,200311,200310,200309,200308,2 00307,200306) group
> by * market_cd,store_cd,ad_dt_yyyymm,report_item_cd,ad_ quality_cd *
> * MODULE BASE END SIZE * sqlservr
> 00400000 00B2CFFF 0072d000 * ntdll
> 77F40000 77FF9FFF 000ba000 * kernel32
> 77E40000 77F33FFF 000f4000 * ADVAPI32 77DA0000
> 77E2FFFF 00090000 * RPCRT4 77C50000 77CF3FFF
> 000a4000 * USER32 77D00000 77D8EFFF 0008f000 *
> GDI32 77C00000 77C43FFF 00044000 * OPENDS60
> 41060000 41065FFF 00006000 * MSVCRT
> 77BA0000 77BF3FFF 00054000 * UMS
> 41070000 4107CFFF 0000d000 * SQLSORT 42AE0000
> 42B6FFFF 00090000 * MSVCIRT 60020000 6002FFFF
> 00010000 * sqlevn70 41080000 41086FFF 00007000 *
> NETAPI32 02C60000 02CB2FFF 00053000 * ole32
> 030D0000 031F3FFF 00124000 * XOLEHLP
> 03200000 03205FFF 00006000 * MSDTCPRX
> 03210000 03280FFF 00071000 * OLEAUT32 03290000
> 0330CFFF 0007d000 * MSVCP60 03310000 03370FFF
> 00061000 * MTXCLU 03380000 03397FFF 00018000 *
> VERSION 033A0000 033A7FFF 00008000 * WSOCK32
> 033B0000 033B8FFF 00009000 * WS2_32
> 033C0000 033D7FFF 00018000 * WS2HELP
> 033E0000 033E7FFF 00008000 * CLUSAPI 03430000
> 03440FFF 00011000 * RESUTILS 03450000 03461FFF
> 00012000 * USERENV 03470000 03529FFF 000ba000 *
> MFC42u 03530000 03623FFF 000f4000 * secur32
> 036B0000 036C2FFF 00013000 * mswsock
> 036E0000 03722FFF 00043000 * DNSAPI
> 03730000 03756FFF 00027000 * winrnr 037A0000
> 037A6FFF 00007000 * WLDAP32 037B0000 037DEFFF
> 0002f000 * rasadhlp 03800000 03804FFF 00005000 *
> SSNMPN70 00C70000 00C75FFF 00006000 * SSNETLIB
> 00C80000 00C94FFF 00015000 * security
> 044B0000 044B3FFF 00004000 * wshtcpip
> 04500000 04507FFF 00008000 * SSmsLPCn 04510000
> 04516FFF 00007000 * ntdsapi 04530000 04545FFF
> 00016000 * SQLFTQRY 04420000 04451FFF 00032000 *
> CLBCatQ 04A60000 04ADDFFF 0007e000 * COMRes
> 04AE0000 04BA5FFF 000c6000 * sqloledb
> 04BB0000 04C35FFF 00086000 * MSDART
> 04480000 044A8FFF 00029000 * COMCTL32 04C40000
> 04CCFFFF 00090000 * comdlg32 04CD0000 04D16FFF
> 00047000 * SHLWAPI 04D20000 04D68FFF 00049000 *
> SHELL32 04D70000 0554CFFF 007dd000 * MSDATL3
> 045B0000 045C7FFF 00018000 * comctl32
> 05550000 05635FFF 000e6000 * oledb32
> 059E0000 05A5CFFF 0007d000 * OLEDB32R 05A60000
> 05A70FFF 00011000 * rsaenh 0FFD0000 0FFFCFFF
> 0002d000 * PSAPI 05B00000 05B0AFFF 0000b000 *
> xpstar 03050000 03096FFF 00047000 * SQLRESLD
> 030A0000 030A6FFF 00007000 * SQLSVC
> 030B0000 030C6FFF 00017000 * ODBC32
> 05C10000 05C49FFF 0003a000 * odbcbcp 05C50000
> 05C55FFF 00006000 * W95SCM 05C60000 05C6BFFF
> 0000c000 * SQLUNIRL 05C70000 05C9CFFF 0002d000 *
> WINSPOOL 05CA0000 05CC5FFF 00026000 * SHFOLDER
> 05CD0000 05CD8FFF 00009000 * odbcint
> 05EB0000 05EC6FFF 00017000 * NDDEAPI
> 05FE0000 05FE6FFF 00007000 * SQLSVC 05FF0000
> 05FF5FFF 00006000 * xpstar 06000000 06008FFF
> 00009000 * dbghelp 06840000 068F4FFF 000b5000 *
> * Edi: 067BFCD8: 3AE52EB8 067BFD10 A7FFFFFA 389C2000 067BFDB4
> 0097C46F * Esi: 389C2000: 01000201 00018000 00000000 00150000
> 00000000 00330000 * Eax: 58001005: 00000000 03000000 00000B00
> 8C000000 88000002 88000002 * Ebx: 389E8708: 3868DCE4 000004F7
> 00000004 000004F4 00000004 00000000 * Ecx: 00000033:
> * Edx: 00000002:
> * Eip: 007F8A40: 4604B70F 8D4C4303 8BFA3074 8BA50C45 A5663448
> C150418B * Ebp: 067BFCF4: 067BFD10 00801CB1 3AE52D68 3AE225E8
> 00000000 3AE52998 * SegCs: 0000001B:
> * EFlags: 00010207: 43003B00 5C003A00 49005700 44004E00 57004F00
> 3B005300 * Esp: 067BFC6C: 00000001 3AE52B44 00000000 00000000
> 00000000 00C567A0 * SegSs: 00000023:
> *
> ************************************************** *****************************
> *
> ----
> * Short Stack Dump
> * 007F8A40 Module(sqlservr+003F8A40)
> (RangeGenerator::GetNextRange+000003D0) * 00801CB1
> Module(sqlservr+00401CB1) (RowsetSS::FetchNextRow+00000153) * 0042A4F6
> Module(sqlservr+0002A4F6) (CQScanRowset::GetRowWithPrefetch+00000040) *
> 0042C21B Module(sqlservr+0002C21B) (CQScanRange::GetRow+000000EF) *
> 004314C9 Module(sqlservr+000314C9) (CQScanHashMatch::Iterate+00000BAF) *
> 00431B41 Module(sqlservr+00031B41) (CQScanHashMatch::GetRow+0000009F) *
> 006FCBF7 Module(sqlservr+002FCBF7) (CQScanXProducer::Open+0000039B) *
> 006FC656 Module(sqlservr+002FC656) (FnProducerThread+0000020E) * 0051274C
> Module(sqlservr+0011274C) (subproc_main+000000C2) * 41075002
> Module(UMS+00005002) (ProcessWorkRequests+00000272) * 41074698
> Module(UMS+00004698) (ThreadStartRoutine+00000098) * 77BC90A2
> Module(MSVCRT+000290A2) (endthread+000000A6) * 77E4A990
> Module(kernel32+0000A990) (FlsSetValue+00000779)
|||Hi Glen,
Thanks for Tibor's suggestion. Looking at the nature of this issue, it
would require intensive troubleshooting which would be done quickly and
effectively with direct assistance from a Microsoft Support Professional
through Microsoft Product Support Services. You can contact Microsoft
Product Support directly by choosing one of the options listed at
http://support.microsoft.com/default...=sz;en-us;top.
If this is not an urgent issue and you would like us to create an incident
for you and have Microsoft Customer Service Representative contact you
directly, please send email to (remove "online." from this no Spam email
address) mailto:dscommhf@.online.microsoft.com with the following
information,
*Include "Followup: <Tomcat IssueID>" in the email Subject.
*Location of the post
*First Name, Last Name
*MSDN Subscriber ID
*Company name (if any)
*Phone number
*e-mail address
Sincerely yours,
Bill Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
| From: Glen K <blah@.blah.com>
| Subject: EXCEPTION_ACCESS_VIOLATION in RangeGenerator::GetNextRange
| User-Agent: Pan/0.14.2 (This is not a psychotic episode. It's a cleansing
moment of clarity.)
| Message-ID: <pan.2004.06.25.19.18.22.966869@.blah.com>
| Newsgroups: microsoft.public.sqlserver.server
| MIME-Version: 1.0
| Content-Type: text/plain; charset=ISO-2022-jp
| Content-Transfer-Encoding: 8bit
| Lines: 124
| Date: Fri, 25 Jun 2004 19:18:22 GMT
| NNTP-Posting-Host: 67.86.129.2
| X-Complaints-To: abuse@.cv.net
| X-Trace: news4.srv.hcvlny.cv.net 1088191102 67.86.129.2 (Fri, 25 Jun 2004
15:18:22 EDT)
| NNTP-Posting-Date: Fri, 25 Jun 2004 15:18:22 EDT
| Organization: Optimum Online
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.phx.gbl!newsfeed00.s
ul.t-online.de!t-online.de!border2.nntp.dca.giganews.com!nntp.gigan ews.com!f
eed5.newsreader.com!newsreader.com!news3.optonline .net!news4.srv.hcvlny.cv.n
et.POSTED!not-for-mail
| Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.server:347783
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Hi,
| I'm getting errors from SQL Server 2000 SP3 running under Windows Server
| 2003. Rebooting the server doesn't help and running DBCC CHECKDB doesn't
| give any errors. I've looked in the Knowledge Base for articles dealing
| with EXCEPTION_ACCESS_VIOLATION errors, but none of them seen to apply to
| me.
|
| Here is part of what is showing up in the log:
|
|
|
| SqlDumpExceptionHandler: Process 1780 generated fatal exception c0000005
| EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process. *
|
************************************************** **************************
***
| *
| * BEGIN STACK DUMP:
| * 06/25/04 14:49:33 spid 55
| *
| * Exception Address = 007F8A40 (RangeGenerator::GetNextRange + 000003D0
| Line 0+00000000) * Exception Code = c0000005
| EXCEPTION_ACCESS_VIOLATION * Access Violation occurred reading address
| E89C400A * Input Buffer 2342 bytes -
| * select distinct rb.brand_cd,rb.report_item_cd into #temp4rb from
| REPORT_ * LIST rl,REPORT_BRANDS rb where service_cd=1 and report_cd=35
| and report_ * table_cd=4 and rl.report_item_cd=rb.report_item_cd select
| market_cd,sto * re_cd,ad_dt_yyyymm,report_item_cd,ad_quality_cd,su m(
| ad_cnt) ad_cnt into * #temp4ac from FEAT_SUM_QUAL_REBATE f,#temp4rb rb
| where f.brand_cd=rb.br * and_cd and market_cd in
| (1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17 *
| ,18,19,20,21,22,23,24,25,27,28,29,31,32,34,35,36,3 7,38,40,44,46,49,50,52 *
| ,53,57,77,78,85,86,87) and ad_dt_yyyymm in ( 200405,200404,200403,
| * 200402,200401,200312,200311,200310,200309,200308,2 00307,200306) group
| by * market_cd,store_cd,ad_dt_yyyymm,report_item_cd,ad_ quality_cd *
| * MODULE BASE END SIZE * sqlservr
| 00400000 00B2CFFF 0072d000 * ntdll
| 77F40000 77FF9FFF 000ba000 * kernel32
| 77E40000 77F33FFF 000f4000 * ADVAPI32 77DA0000
| 77E2FFFF 00090000 * RPCRT4 77C50000 77CF3FFF
| 000a4000 * USER32 77D00000 77D8EFFF 0008f000 *
| GDI32 77C00000 77C43FFF 00044000 * OPENDS60
| 41060000 41065FFF 00006000 * MSVCRT
| 77BA0000 77BF3FFF 00054000 * UMS
| 41070000 4107CFFF 0000d000 * SQLSORT 42AE0000
| 42B6FFFF 00090000 * MSVCIRT 60020000 6002FFFF
| 00010000 * sqlevn70 41080000 41086FFF 00007000 *
| NETAPI32 02C60000 02CB2FFF 00053000 * ole32
| 030D0000 031F3FFF 00124000 * XOLEHLP
| 03200000 03205FFF 00006000 * MSDTCPRX
| 03210000 03280FFF 00071000 * OLEAUT32 03290000
| 0330CFFF 0007d000 * MSVCP60 03310000 03370FFF
| 00061000 * MTXCLU 03380000 03397FFF 00018000 *
| VERSION 033A0000 033A7FFF 00008000 * WSOCK32
| 033B0000 033B8FFF 00009000 * WS2_32
| 033C0000 033D7FFF 00018000 * WS2HELP
| 033E0000 033E7FFF 00008000 * CLUSAPI 03430000
| 03440FFF 00011000 * RESUTILS 03450000 03461FFF
| 00012000 * USERENV 03470000 03529FFF 000ba000 *
| MFC42u 03530000 03623FFF 000f4000 * secur32
| 036B0000 036C2FFF 00013000 * mswsock
| 036E0000 03722FFF 00043000 * DNSAPI
| 03730000 03756FFF 00027000 * winrnr 037A0000
| 037A6FFF 00007000 * WLDAP32 037B0000 037DEFFF
| 0002f000 * rasadhlp 03800000 03804FFF 00005000 *
| SSNMPN70 00C70000 00C75FFF 00006000 * SSNETLIB
| 00C80000 00C94FFF 00015000 * security
| 044B0000 044B3FFF 00004000 * wshtcpip
| 04500000 04507FFF 00008000 * SSmsLPCn 04510000
| 04516FFF 00007000 * ntdsapi 04530000 04545FFF
| 00016000 * SQLFTQRY 04420000 04451FFF 00032000 *
| CLBCatQ 04A60000 04ADDFFF 0007e000 * COMRes
| 04AE0000 04BA5FFF 000c6000 * sqloledb
| 04BB0000 04C35FFF 00086000 * MSDART
| 04480000 044A8FFF 00029000 * COMCTL32 04C40000
| 04CCFFFF 00090000 * comdlg32 04CD0000 04D16FFF
| 00047000 * SHLWAPI 04D20000 04D68FFF 00049000 *
| SHELL32 04D70000 0554CFFF 007dd000 * MSDATL3
| 045B0000 045C7FFF 00018000 * comctl32
| 05550000 05635FFF 000e6000 * oledb32
| 059E0000 05A5CFFF 0007d000 * OLEDB32R 05A60000
| 05A70FFF 00011000 * rsaenh 0FFD0000 0FFFCFFF
| 0002d000 * PSAPI 05B00000 05B0AFFF 0000b000 *
| xpstar 03050000 03096FFF 00047000 * SQLRESLD
| 030A0000 030A6FFF 00007000 * SQLSVC
| 030B0000 030C6FFF 00017000 * ODBC32
| 05C10000 05C49FFF 0003a000 * odbcbcp 05C50000
| 05C55FFF 00006000 * W95SCM 05C60000 05C6BFFF
| 0000c000 * SQLUNIRL 05C70000 05C9CFFF 0002d000 *
| WINSPOOL 05CA0000 05CC5FFF 00026000 * SHFOLDER
| 05CD0000 05CD8FFF 00009000 * odbcint
| 05EB0000 05EC6FFF 00017000 * NDDEAPI
| 05FE0000 05FE6FFF 00007000 * SQLSVC 05FF0000
| 05FF5FFF 00006000 * xpstar 06000000 06008FFF
| 00009000 * dbghelp 06840000 068F4FFF 000b5000 *
| * Edi: 067BFCD8: 3AE52EB8 067BFD10 A7FFFFFA 389C2000 067BFDB4
| 0097C46F * Esi: 389C2000: 01000201 00018000 00000000 00150000
| 00000000 00330000 * Eax: 58001005: 00000000 03000000 00000B00
| 8C000000 88000002 88000002 * Ebx: 389E8708: 3868DCE4 000004F7
| 00000004 000004F4 00000004 00000000 * Ecx: 00000033:
| * Edx: 00000002:
| * Eip: 007F8A40: 4604B70F 8D4C4303 8BFA3074 8BA50C45 A5663448
| C150418B * Ebp: 067BFCF4: 067BFD10 00801CB1 3AE52D68 3AE225E8
| 00000000 3AE52998 * SegCs: 0000001B:
| * EFlags: 00010207: 43003B00 5C003A00 49005700 44004E00 57004F00
| 3B005300 * Esp: 067BFC6C: 00000001 3AE52B44 00000000 00000000
| 00000000 00C567A0 * SegSs: 00000023:
| *
|
************************************************** **************************
***
| *
|
| * Short Stack Dump
| * 007F8A40 Module(sqlservr+003F8A40)
| (RangeGenerator::GetNextRange+000003D0) * 00801CB1
| Module(sqlservr+00401CB1) (RowsetSS::FetchNextRow+00000153) * 0042A4F6
| Module(sqlservr+0002A4F6) (CQScanRowset::GetRowWithPrefetch+00000040) *
| 0042C21B Module(sqlservr+0002C21B) (CQScanRange::GetRow+000000EF) *
| 004314C9 Module(sqlservr+000314C9) (CQScanHashMatch::Iterate+00000BAF) *
| 00431B41 Module(sqlservr+00031B41) (CQScanHashMatch::GetRow+0000009F) *
| 006FCBF7 Module(sqlservr+002FCBF7) (CQScanXProducer::Open+0000039B) *
| 006FC656 Module(sqlservr+002FC656) (FnProducerThread+0000020E) * 0051274C
| Module(sqlservr+0011274C) (subproc_main+000000C2) * 41075002
| Module(UMS+00005002) (ProcessWorkRequests+00000272) * 41074698
| Module(UMS+00004698) (ThreadStartRoutine+00000098) * 77BC90A2
| Module(MSVCRT+000290A2) (endthread+000000A6) * 77E4A990
| Module(kernel32+0000A990) (FlsSetValue+00000779)
|
|||Hi Glen,
Thanks for Tibor's suggestion. Looking at the nature of this issue, it
would require intensive troubleshooting which would be done quickly and
effectively with direct assistance from a Microsoft Support Professional
through Microsoft Product Support Services. You can contact Microsoft
Product Support directly by choosing one of the options listed at
http://support.microsoft.com/default...=sz;en-us;top.
If this is not an urgent issue and you would like us to create an incident
for you and have Microsoft Customer Service Representative contact you
directly, please send email to (remove "online." from this no Spam email
address) mailto:dscommhf@.online.microsoft.com with the following
information,
*Include "Followup: <Tomcat IssueID>" in the email Subject.
*Location of the post
*First Name, Last Name
*MSDN Subscriber ID
*Company name (if any)
*Phone number
*e-mail address
Sincerely yours,
Bill Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
| From: Glen K <blah@.blah.com>
| Subject: EXCEPTION_ACCESS_VIOLATION in RangeGenerator::GetNextRange
| User-Agent: Pan/0.14.2 (This is not a psychotic episode. It's a cleansing
moment of clarity.)
| Message-ID: <pan.2004.06.25.19.18.22.966869@.blah.com>
| Newsgroups: microsoft.public.sqlserver.server
| MIME-Version: 1.0
| Content-Type: text/plain; charset=ISO-2022-jp
| Content-Transfer-Encoding: 8bit
| Lines: 124
| Date: Fri, 25 Jun 2004 19:18:22 GMT
| NNTP-Posting-Host: 67.86.129.2
| X-Complaints-To: abuse@.cv.net
| X-Trace: news4.srv.hcvlny.cv.net 1088191102 67.86.129.2 (Fri, 25 Jun 2004
15:18:22 EDT)
| NNTP-Posting-Date: Fri, 25 Jun 2004 15:18:22 EDT
| Organization: Optimum Online
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.phx.gbl!newsfeed00.s
ul.t-online.de!t-online.de!border2.nntp.dca.giganews.com!nntp.gigan ews.com!f
eed5.newsreader.com!newsreader.com!news3.optonline .net!news4.srv.hcvlny.cv.n
et.POSTED!not-for-mail
| Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.server:347783
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Hi,
| I'm getting errors from SQL Server 2000 SP3 running under Windows Server
| 2003. Rebooting the server doesn't help and running DBCC CHECKDB doesn't
| give any errors. I've looked in the Knowledge Base for articles dealing
| with EXCEPTION_ACCESS_VIOLATION errors, but none of them seen to apply to
| me.
|
| Here is part of what is showing up in the log:
|
|
|
| SqlDumpExceptionHandler: Process 1780 generated fatal exception c0000005
| EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process. *
|
************************************************** **************************
***
| *
| * BEGIN STACK DUMP:
| * 06/25/04 14:49:33 spid 55
| *
| * Exception Address = 007F8A40 (RangeGenerator::GetNextRange + 000003D0
| Line 0+00000000) * Exception Code = c0000005
| EXCEPTION_ACCESS_VIOLATION * Access Violation occurred reading address
| E89C400A * Input Buffer 2342 bytes -
| * select distinct rb.brand_cd,rb.report_item_cd into #temp4rb from
| REPORT_ * LIST rl,REPORT_BRANDS rb where service_cd=1 and report_cd=35
| and report_ * table_cd=4 and rl.report_item_cd=rb.report_item_cd select
| market_cd,sto * re_cd,ad_dt_yyyymm,report_item_cd,ad_quality_cd,su m(
| ad_cnt) ad_cnt into * #temp4ac from FEAT_SUM_QUAL_REBATE f,#temp4rb rb
| where f.brand_cd=rb.br * and_cd and market_cd in
| (1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17 *
| ,18,19,20,21,22,23,24,25,27,28,29,31,32,34,35,36,3 7,38,40,44,46,49,50,52 *
| ,53,57,77,78,85,86,87) and ad_dt_yyyymm in ( 200405,200404,200403,
| * 200402,200401,200312,200311,200310,200309,200308,2 00307,200306) group
| by * market_cd,store_cd,ad_dt_yyyymm,report_item_cd,ad_ quality_cd *
| * MODULE BASE END SIZE * sqlservr
| 00400000 00B2CFFF 0072d000 * ntdll
| 77F40000 77FF9FFF 000ba000 * kernel32
| 77E40000 77F33FFF 000f4000 * ADVAPI32 77DA0000
| 77E2FFFF 00090000 * RPCRT4 77C50000 77CF3FFF
| 000a4000 * USER32 77D00000 77D8EFFF 0008f000 *
| GDI32 77C00000 77C43FFF 00044000 * OPENDS60
| 41060000 41065FFF 00006000 * MSVCRT
| 77BA0000 77BF3FFF 00054000 * UMS
| 41070000 4107CFFF 0000d000 * SQLSORT 42AE0000
| 42B6FFFF 00090000 * MSVCIRT 60020000 6002FFFF
| 00010000 * sqlevn70 41080000 41086FFF 00007000 *
| NETAPI32 02C60000 02CB2FFF 00053000 * ole32
| 030D0000 031F3FFF 00124000 * XOLEHLP
| 03200000 03205FFF 00006000 * MSDTCPRX
| 03210000 03280FFF 00071000 * OLEAUT32 03290000
| 0330CFFF 0007d000 * MSVCP60 03310000 03370FFF
| 00061000 * MTXCLU 03380000 03397FFF 00018000 *
| VERSION 033A0000 033A7FFF 00008000 * WSOCK32
| 033B0000 033B8FFF 00009000 * WS2_32
| 033C0000 033D7FFF 00018000 * WS2HELP
| 033E0000 033E7FFF 00008000 * CLUSAPI 03430000
| 03440FFF 00011000 * RESUTILS 03450000 03461FFF
| 00012000 * USERENV 03470000 03529FFF 000ba000 *
| MFC42u 03530000 03623FFF 000f4000 * secur32
| 036B0000 036C2FFF 00013000 * mswsock
| 036E0000 03722FFF 00043000 * DNSAPI
| 03730000 03756FFF 00027000 * winrnr 037A0000
| 037A6FFF 00007000 * WLDAP32 037B0000 037DEFFF
| 0002f000 * rasadhlp 03800000 03804FFF 00005000 *
| SSNMPN70 00C70000 00C75FFF 00006000 * SSNETLIB
| 00C80000 00C94FFF 00015000 * security
| 044B0000 044B3FFF 00004000 * wshtcpip
| 04500000 04507FFF 00008000 * SSmsLPCn 04510000
| 04516FFF 00007000 * ntdsapi 04530000 04545FFF
| 00016000 * SQLFTQRY 04420000 04451FFF 00032000 *
| CLBCatQ 04A60000 04ADDFFF 0007e000 * COMRes
| 04AE0000 04BA5FFF 000c6000 * sqloledb
| 04BB0000 04C35FFF 00086000 * MSDART
| 04480000 044A8FFF 00029000 * COMCTL32 04C40000
| 04CCFFFF 00090000 * comdlg32 04CD0000 04D16FFF
| 00047000 * SHLWAPI 04D20000 04D68FFF 00049000 *
| SHELL32 04D70000 0554CFFF 007dd000 * MSDATL3
| 045B0000 045C7FFF 00018000 * comctl32
| 05550000 05635FFF 000e6000 * oledb32
| 059E0000 05A5CFFF 0007d000 * OLEDB32R 05A60000
| 05A70FFF 00011000 * rsaenh 0FFD0000 0FFFCFFF
| 0002d000 * PSAPI 05B00000 05B0AFFF 0000b000 *
| xpstar 03050000 03096FFF 00047000 * SQLRESLD
| 030A0000 030A6FFF 00007000 * SQLSVC
| 030B0000 030C6FFF 00017000 * ODBC32
| 05C10000 05C49FFF 0003a000 * odbcbcp 05C50000
| 05C55FFF 00006000 * W95SCM 05C60000 05C6BFFF
| 0000c000 * SQLUNIRL 05C70000 05C9CFFF 0002d000 *
| WINSPOOL 05CA0000 05CC5FFF 00026000 * SHFOLDER
| 05CD0000 05CD8FFF 00009000 * odbcint
| 05EB0000 05EC6FFF 00017000 * NDDEAPI
| 05FE0000 05FE6FFF 00007000 * SQLSVC 05FF0000
| 05FF5FFF 00006000 * xpstar 06000000 06008FFF
| 00009000 * dbghelp 06840000 068F4FFF 000b5000 *
| * Edi: 067BFCD8: 3AE52EB8 067BFD10 A7FFFFFA 389C2000 067BFDB4
| 0097C46F * Esi: 389C2000: 01000201 00018000 00000000 00150000
| 00000000 00330000 * Eax: 58001005: 00000000 03000000 00000B00
| 8C000000 88000002 88000002 * Ebx: 389E8708: 3868DCE4 000004F7
| 00000004 000004F4 00000004 00000000 * Ecx: 00000033:
| * Edx: 00000002:
| * Eip: 007F8A40: 4604B70F 8D4C4303 8BFA3074 8BA50C45 A5663448
| C150418B * Ebp: 067BFCF4: 067BFD10 00801CB1 3AE52D68 3AE225E8
| 00000000 3AE52998 * SegCs: 0000001B:
| * EFlags: 00010207: 43003B00 5C003A00 49005700 44004E00 57004F00
| 3B005300 * Esp: 067BFC6C: 00000001 3AE52B44 00000000 00000000
| 00000000 00C567A0 * SegSs: 00000023:
| *
|
************************************************** **************************
***
| *
|
| * Short Stack Dump
| * 007F8A40 Module(sqlservr+003F8A40)
| (RangeGenerator::GetNextRange+000003D0) * 00801CB1
| Module(sqlservr+00401CB1) (RowsetSS::FetchNextRow+00000153) * 0042A4F6
| Module(sqlservr+0002A4F6) (CQScanRowset::GetRowWithPrefetch+00000040) *
| 0042C21B Module(sqlservr+0002C21B) (CQScanRange::GetRow+000000EF) *
| 004314C9 Module(sqlservr+000314C9) (CQScanHashMatch::Iterate+00000BAF) *
| 00431B41 Module(sqlservr+00031B41) (CQScanHashMatch::GetRow+0000009F) *
| 006FCBF7 Module(sqlservr+002FCBF7) (CQScanXProducer::Open+0000039B) *
| 006FC656 Module(sqlservr+002FC656) (FnProducerThread+0000020E) * 0051274C
| Module(sqlservr+0011274C) (subproc_main+000000C2) * 41075002
| Module(UMS+00005002) (ProcessWorkRequests+00000272) * 41074698
| Module(UMS+00004698) (ThreadStartRoutine+00000098) * 77BC90A2
| Module(MSVCRT+000290A2) (endthread+000000A6) * 77E4A990
| Module(kernel32+0000A990) (FlsSetValue+00000779)
|

EXCEPTION_ACCESS_VIOLATION in RangeGenerator::GetNextRange

Hi,
I'm getting errors from SQL Server 2000 SP3 running under Windows Server
2003. Rebooting the server doesn't help and running DBCC CHECKDB doesn't
give any errors. I've looked in the Knowledge Base for articles dealing
with EXCEPTION_ACCESS_VIOLATION errors, but none of them seen to apply to
me.
Here is part of what is showing up in the log:
SqlDumpExceptionHandler: Process 1780 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process. *
****************************************
************************************
***
*
* BEGIN STACK DUMP:
* 06/25/04 14:49:33 spid 55
*
* Exception Address = 007F8A40 (RangeGenerator::GetNextRange + 000003D0
Line 0+00000000) * Exception Code = c0000005
EXCEPTION_ACCESS_VIOLATION * Access Violation occurred reading address
E89C400A * Input Buffer 2342 bytes -
* select distinct rb.brand_cd,rb.report_item_cd into #temp4rb from
REPORT_ * LIST rl,REPORT_BRANDS rb where service_cd=1 and report_cd=35
and report_ * table_cd=4 and rl.report_item_cd=rb.report_item_cd select
market_cd,sto * re_cd,ad_dt_yyyymm,report_item_cd,ad_qua
lity_cd,sum(
ad_cnt) ad_cnt into * #temp4ac from FEAT_SUM_QUAL_REBATE f,#temp4rb rb
where f.brand_cd=rb.br * and_cd and market_cd in
(1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,
17 *
,18,19,20,21,22,23,24,25,27,28,29,31,32,
34,35,36,37,38,40,44,46,49,50,52 *
,53,57,77,78,85,86,87) and ad_dt_yyyymm in ( 200405,200404,200403,
* 200402,200401,200312,200311,200310,20030
9,200308,200307,200306) group
by * market_cd,store_cd,ad_dt_yyyymm,report_i
tem_cd,ad_quality_cd *
* MODULE BASE END SIZE * sqlservr
00400000 00B2CFFF 0072d000 * ntdll
77F40000 77FF9FFF 000ba000 * kernel32
77E40000 77F33FFF 000f4000 * ADVAPI32 77DA0000
77E2FFFF 00090000 * RPCRT4 77C50000 77CF3FFF
000a4000 * USER32 77D00000 77D8EFFF 0008f000 *
GDI32 77C00000 77C43FFF 00044000 * OPENDS60
41060000 41065FFF 00006000 * MSVCRT
77BA0000 77BF3FFF 00054000 * UMS
41070000 4107CFFF 0000d000 * SQLSORT 42AE0000
42B6FFFF 00090000 * MSVCIRT 60020000 6002FFFF
00010000 * sqlevn70 41080000 41086FFF 00007000 *
NETAPI32 02C60000 02CB2FFF 00053000 * ole32
030D0000 031F3FFF 00124000 * XOLEHLP
03200000 03205FFF 00006000 * MSDTCPRX
03210000 03280FFF 00071000 * OLEAUT32 03290000
0330CFFF 0007d000 * MSVCP60 03310000 03370FFF
00061000 * MTXCLU 03380000 03397FFF 00018000 *
VERSION 033A0000 033A7FFF 00008000 * WSOCK32
033B0000 033B8FFF 00009000 * WS2_32
033C0000 033D7FFF 00018000 * WS2HELP
033E0000 033E7FFF 00008000 * CLUSAPI 03430000
03440FFF 00011000 * RESUTILS 03450000 03461FFF
00012000 * USERENV 03470000 03529FFF 000ba000 *
MFC42u 03530000 03623FFF 000f4000 * secur32
036B0000 036C2FFF 00013000 * mswsock
036E0000 03722FFF 00043000 * DNSAPI
03730000 03756FFF 00027000 * winrnr 037A0000
037A6FFF 00007000 * WLDAP32 037B0000 037DEFFF
0002f000 * rasadhlp 03800000 03804FFF 00005000 *
SSNMPN70 00C70000 00C75FFF 00006000 * SSNETLIB
00C80000 00C94FFF 00015000 * security
044B0000 044B3FFF 00004000 * wshtcpip
04500000 04507FFF 00008000 * SSmsLPCn 04510000
04516FFF 00007000 * ntdsapi 04530000 04545FFF
00016000 * SQLFTQRY 04420000 04451FFF 00032000 *
CLBCatQ 04A60000 04ADDFFF 0007e000 * COMRes
04AE0000 04BA5FFF 000c6000 * sqloledb
04BB0000 04C35FFF 00086000 * MSDART
04480000 044A8FFF 00029000 * COMCTL32 04C40000
04CCFFFF 00090000 * comdlg32 04CD0000 04D16FFF
00047000 * SHLWAPI 04D20000 04D68FFF 00049000 *
SHELL32 04D70000 0554CFFF 007dd000 * MSDATL3
045B0000 045C7FFF 00018000 * comctl32
05550000 05635FFF 000e6000 * oledb32
059E0000 05A5CFFF 0007d000 * OLEDB32R 05A60000
05A70FFF 00011000 * rsaenh 0FFD0000 0FFFCFFF
0002d000 * PSAPI 05B00000 05B0AFFF 0000b000 *
xpstar 03050000 03096FFF 00047000 * SQLRESLD
030A0000 030A6FFF 00007000 * SQLSVC
030B0000 030C6FFF 00017000 * ODBC32
05C10000 05C49FFF 0003a000 * odbcbcp 05C50000
05C55FFF 00006000 * W95SCM 05C60000 05C6BFFF
0000c000 * SQLUNIRL 05C70000 05C9CFFF 0002d000 *
WINSPOOL 05CA0000 05CC5FFF 00026000 * SHFOLDER
05CD0000 05CD8FFF 00009000 * odbcint
05EB0000 05EC6FFF 00017000 * NDDEAPI
05FE0000 05FE6FFF 00007000 * SQLSVC 05FF0000
05FF5FFF 00006000 * xpstar 06000000 06008FFF
00009000 * dbghelp 06840000 068F4FFF 000b5000 *
* Edi: 067BFCD8: 3AE52EB8 067BFD10 A7FFFFFA 389C2000 067BFDB4
0097C46F * Esi: 389C2000: 01000201 00018000 00000000 00150000
00000000 00330000 * Eax: 58001005: 00000000 03000000 00000B00
8C000000 88000002 88000002 * Ebx: 389E8708: 3868DCE4 000004F7
00000004 000004F4 00000004 00000000 * Ecx: 00000033:
* Edx: 00000002:
* Eip: 007F8A40: 4604B70F 8D4C4303 8BFA3074 8BA50C45 A5663448
C150418B * Ebp: 067BFCF4: 067BFD10 00801CB1 3AE52D68 3AE225E8
00000000 3AE52998 * SegCs: 0000001B:
* EFlags: 00010207: 43003B00 5C003A00 49005700 44004E00 57004F00
3B005300 * Esp: 067BFC6C: 00000001 3AE52B44 00000000 00000000
00000000 00C567A0 * SegSs: 00000023:
*
****************************************
************************************
***
*
----
--
* Short Stack Dump
* 007F8A40 Module(sqlservr+003F8A40)
(RangeGenerator::GetNextRange+000003D0) * 00801CB1
Module(sqlservr+00401CB1) (RowsetSS::FetchNextRow+00000153) * 0042A4F6
Module(sqlservr+0002A4F6) (CQScanRowset::GetRowWithPrefetch+000000
40) *
0042C21B Module(sqlservr+0002C21B) (CQScanRange::GetRow+000000EF) *
004314C9 Module(sqlservr+000314C9) (CQScanHashMatch::Iterate+00000BAF) *
00431B41 Module(sqlservr+00031B41) (CQScanHashMatch::GetRow+0000009F) *
006FCBF7 Module(sqlservr+002FCBF7) (CQScanXProducer::Open+0000039B) *
006FC656 Module(sqlservr+002FC656) (FnProducerThread+0000020E) * 0051274C
Module(sqlservr+0011274C) (subproc_main+000000C2) * 41075002
Module(UMS+00005002) (ProcessWorkRequests+00000272) * 41074698
Module(UMS+00004698) (ThreadStartRoutine+00000098) * 77BC90A2
Module(MSVCRT+000290A2) (endthread+000000A6) * 77E4A990
Module(kernel32+0000A990) (FlsSetValue+00000779)If you don't find anything on KB, are up on sp and CHECKDB comes out clean,
it is time for a case
with MS Support...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Glen K" <blah@.blah.com> wrote in message news:pan.2004.06.25.19.18.22.966869@.blah.com...[vb
col=seagreen]
> Hi,
> I'm getting errors from SQL Server 2000 SP3 running under Windows Server
> 2003. Rebooting the server doesn't help and running DBCC CHECKDB doesn't
> give any errors. I've looked in the Knowledge Base for articles dealing
> with EXCEPTION_ACCESS_VIOLATION errors, but none of them seen to apply to
> me.
> Here is part of what is showing up in the log:
>
> SqlDumpExceptionHandler: Process 1780 generated fatal exception c0000005
> EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process. *
> ****************************************
**********************************
*****
> *
> * BEGIN STACK DUMP:
> * 06/25/04 14:49:33 spid 55
> *
> * Exception Address = 007F8A40 (RangeGenerator::GetNextRange + 000003D0
> Line 0+00000000) * Exception Code = c0000005
> EXCEPTION_ACCESS_VIOLATION * Access Violation occurred reading address
> E89C400A * Input Buffer 2342 bytes -
> * select distinct rb.brand_cd,rb.report_item_cd into #temp4rb from
> REPORT_ * LIST rl,REPORT_BRANDS rb where service_cd=1 and report_cd=35
> and report_ * table_cd=4 and rl.report_item_cd=rb.report_item_cd select
> market_cd,sto * re_cd,ad_dt_yyyymm,report_item_cd,ad_qua
lity_cd,sum(
> ad_cnt) ad_cnt into * #temp4ac from FEAT_SUM_QUAL_REBATE f,#temp4rb rb
> where f.brand_cd=rb.br * and_cd and market_cd in
> (1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,
17 *
> ,18,19,20,21,22,23,24,25,27,28,29,31,32,
34,35,36,37,38,40,44,46,49,50,52 *
> ,53,57,77,78,85,86,87) and ad_dt_yyyymm in ( 200405,200404,200403,
> * 200402,200401,200312,200311,200310,20030
9,200308,200307,200306) group
> by * market_cd,store_cd,ad_dt_yyyymm,report_i
tem_cd,ad_quality_cd *
> * MODULE BASE END SIZE * sqlservr
> 00400000 00B2CFFF 0072d000 * ntdll
> 77F40000 77FF9FFF 000ba000 * kernel32
> 77E40000 77F33FFF 000f4000 * ADVAPI32 77DA0000
> 77E2FFFF 00090000 * RPCRT4 77C50000 77CF3FFF
> 000a4000 * USER32 77D00000 77D8EFFF 0008f000 *
> GDI32 77C00000 77C43FFF 00044000 * OPENDS60
> 41060000 41065FFF 00006000 * MSVCRT
> 77BA0000 77BF3FFF 00054000 * UMS
> 41070000 4107CFFF 0000d000 * SQLSORT 42AE0000
> 42B6FFFF 00090000 * MSVCIRT 60020000 6002FFFF
> 00010000 * sqlevn70 41080000 41086FFF 00007000 *
> NETAPI32 02C60000 02CB2FFF 00053000 * ole32
> 030D0000 031F3FFF 00124000 * XOLEHLP
> 03200000 03205FFF 00006000 * MSDTCPRX
> 03210000 03280FFF 00071000 * OLEAUT32 03290000
> 0330CFFF 0007d000 * MSVCP60 03310000 03370FFF
> 00061000 * MTXCLU 03380000 03397FFF 00018000 *
> VERSION 033A0000 033A7FFF 00008000 * WSOCK32
> 033B0000 033B8FFF 00009000 * WS2_32
> 033C0000 033D7FFF 00018000 * WS2HELP
> 033E0000 033E7FFF 00008000 * CLUSAPI 03430000
> 03440FFF 00011000 * RESUTILS 03450000 03461FFF
> 00012000 * USERENV 03470000 03529FFF 000ba000 *
> MFC42u 03530000 03623FFF 000f4000 * secur32
> 036B0000 036C2FFF 00013000 * mswsock
> 036E0000 03722FFF 00043000 * DNSAPI
> 03730000 03756FFF 00027000 * winrnr 037A0000
> 037A6FFF 00007000 * WLDAP32 037B0000 037DEFFF
> 0002f000 * rasadhlp 03800000 03804FFF 00005000 *
> SSNMPN70 00C70000 00C75FFF 00006000 * SSNETLIB
> 00C80000 00C94FFF 00015000 * security
> 044B0000 044B3FFF 00004000 * wshtcpip
> 04500000 04507FFF 00008000 * SSmsLPCn 04510000
> 04516FFF 00007000 * ntdsapi 04530000 04545FFF
> 00016000 * SQLFTQRY 04420000 04451FFF 00032000 *
> CLBCatQ 04A60000 04ADDFFF 0007e000 * COMRes
> 04AE0000 04BA5FFF 000c6000 * sqloledb
> 04BB0000 04C35FFF 00086000 * MSDART
> 04480000 044A8FFF 00029000 * COMCTL32 04C40000
> 04CCFFFF 00090000 * comdlg32 04CD0000 04D16FFF
> 00047000 * SHLWAPI 04D20000 04D68FFF 00049000 *
> SHELL32 04D70000 0554CFFF 007dd000 * MSDATL3
> 045B0000 045C7FFF 00018000 * comctl32
> 05550000 05635FFF 000e6000 * oledb32
> 059E0000 05A5CFFF 0007d000 * OLEDB32R 05A60000
> 05A70FFF 00011000 * rsaenh 0FFD0000 0FFFCFFF
> 0002d000 * PSAPI 05B00000 05B0AFFF 0000b000 *
> xpstar 03050000 03096FFF 00047000 * SQLRESLD
> 030A0000 030A6FFF 00007000 * SQLSVC
> 030B0000 030C6FFF 00017000 * ODBC32
> 05C10000 05C49FFF 0003a000 * odbcbcp 05C50000
> 05C55FFF 00006000 * W95SCM 05C60000 05C6BFFF
> 0000c000 * SQLUNIRL 05C70000 05C9CFFF 0002d000 *
> WINSPOOL 05CA0000 05CC5FFF 00026000 * SHFOLDER
> 05CD0000 05CD8FFF 00009000 * odbcint
> 05EB0000 05EC6FFF 00017000 * NDDEAPI
> 05FE0000 05FE6FFF 00007000 * SQLSVC 05FF0000
> 05FF5FFF 00006000 * xpstar 06000000 06008FFF
> 00009000 * dbghelp 06840000 068F4FFF 000b5000 *
> * Edi: 067BFCD8: 3AE52EB8 067BFD10 A7FFFFFA 389C2000 067BFDB4
> 0097C46F * Esi: 389C2000: 01000201 00018000 00000000 00150000
> 00000000 00330000 * Eax: 58001005: 00000000 03000000 00000B00
> 8C000000 88000002 88000002 * Ebx: 389E8708: 3868DCE4 000004F7
> 00000004 000004F4 00000004 00000000 * Ecx: 00000033:
> * Edx: 00000002:
> * Eip: 007F8A40: 4604B70F 8D4C4303 8BFA3074 8BA50C45 A5663448
> C150418B * Ebp: 067BFCF4: 067BFD10 00801CB1 3AE52D68 3AE225E8
> 00000000 3AE52998 * SegCs: 0000001B:
> * EFlags: 00010207: 43003B00 5C003A00 49005700 44004E00 57004F00
> 3B005300 * Esp: 067BFC6C: 00000001 3AE52B44 00000000 00000000
> 00000000 00C567A0 * SegSs: 00000023:
> *
> ****************************************
**********************************
*****
> *
> ----
--
> * Short Stack Dump
> * 007F8A40 Module(sqlservr+003F8A40)
> (RangeGenerator::GetNextRange+000003D0) * 00801CB1
> Module(sqlservr+00401CB1) (RowsetSS::FetchNextRow+00000153) * 0042A4F6
> Module(sqlservr+0002A4F6) (CQScanRowset::GetRowWithPrefetch+000000
40) *
> 0042C21B Module(sqlservr+0002C21B) (CQScanRange::GetRow+000000EF) *
> 004314C9 Module(sqlservr+000314C9) (CQScanHashMatch::Iterate+00000BAF) *
> 00431B41 Module(sqlservr+00031B41) (CQScanHashMatch::GetRow+0000009F) *
> 006FCBF7 Module(sqlservr+002FCBF7) (CQScanXProducer::Open+0000039B) *
> 006FC656 Module(sqlservr+002FC656) (FnProducerThread+0000020E) * 0051274C
> Module(sqlservr+0011274C) (subproc_main+000000C2) * 41075002
> Module(UMS+00005002) (ProcessWorkRequests+00000272) * 41074698
> Module(UMS+00004698) (ThreadStartRoutine+00000098) * 77BC90A2
> Module(MSVCRT+000290A2) (endthread+000000A6) * 77E4A990
> Module(kernel32+0000A990) (FlsSetValue+00000779)[/vbcol]|||Hi Glen,
Thanks for Tibor's suggestion. Looking at the nature of this issue, it
would require intensive troubleshooting which would be done quickly and
effectively with direct assistance from a Microsoft Support Professional
through Microsoft Product Support Services. You can contact Microsoft
Product Support directly by choosing one of the options listed at
http://support.microsoft.com/defaul...d=sz;en-us;top.
If this is not an urgent issue and you would like us to create an incident
for you and have Microsoft Customer Service Representative contact you
directly, please send email to (remove "online." from this no Spam email
address) mailto:dscommhf@.online.microsoft.com with the following
information,
*Include "Followup: <Tomcat IssueID>" in the email Subject.
*Location of the post
*First Name, Last Name
*MSDN Subscriber ID
*Company name (if any)
*Phone number
*e-mail address
Sincerely yours,
Bill Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
--
| From: Glen K <blah@.blah.com>
| Subject: EXCEPTION_ACCESS_VIOLATION in RangeGenerator::GetNextRange
| User-Agent: Pan/0.14.2 (This is not a psychotic episode. It's a cleansing
moment of clarity.)
| Message-ID: <pan.2004.06.25.19.18.22.966869@.blah.com>
| Newsgroups: microsoft.public.sqlserver.server
| MIME-Version: 1.0
| Content-Type: text/plain; charset=ISO-2022-jp
| Content-Transfer-Encoding: 8bit
| Lines: 124
| Date: Fri, 25 Jun 2004 19:18:22 GMT
| NNTP-Posting-Host: 67.86.129.2
| X-Complaints-To: abuse@.cv.net
| X-Trace: news4.srv.hcvlny.cv.net 1088191102 67.86.129.2 (Fri, 25 Jun 2004
15:18:22 EDT)
| NNTP-Posting-Date: Fri, 25 Jun 2004 15:18:22 EDT
| Organization: Optimum Online
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.s
ul.t-online.de!t-online.de!border2.nntp.dca.giganews.com!nntp.giganews.com!f
eed5.newsreader.com!newsreader.com!news3.optonline.net!news4.srv.hcvlny.cv.n
et.POSTED!not-for-mail
| Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.server:347783
| X-Tomcat-NG: microsoft.public.sqlserver.server
|
| Hi,
| I'm getting errors from SQL Server 2000 SP3 running under Windows Server
| 2003. Rebooting the server doesn't help and running DBCC CHECKDB doesn't
| give any errors. I've looked in the Knowledge Base for articles dealing
| with EXCEPTION_ACCESS_VIOLATION errors, but none of them seen to apply to
| me.
|
| Here is part of what is showing up in the log:
|
|
|
| SqlDumpExceptionHandler: Process 1780 generated fatal exception c0000005
| EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process. *
|
****************************************
************************************
***
| *
| * BEGIN STACK DUMP:
| * 06/25/04 14:49:33 spid 55
| *
| * Exception Address = 007F8A40 (RangeGenerator::GetNextRange + 000003D0
| Line 0+00000000) * Exception Code = c0000005
| EXCEPTION_ACCESS_VIOLATION * Access Violation occurred reading address
| E89C400A * Input Buffer 2342 bytes -
| * select distinct rb.brand_cd,rb.report_item_cd into #temp4rb from
| REPORT_ * LIST rl,REPORT_BRANDS rb where service_cd=1 and report_cd=35
| and report_ * table_cd=4 and rl.report_item_cd=rb.report_item_cd select
| market_cd,sto * re_cd,ad_dt_yyyymm,report_item_cd,ad_qua
lity_cd,sum(
| ad_cnt) ad_cnt into * #temp4ac from FEAT_SUM_QUAL_REBATE f,#temp4rb rb
| where f.brand_cd=rb.br * and_cd and market_cd in
| (1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,
17 *
| ,18,19,20,21,22,23,24,25,27,28,29,31,32,
34,35,36,37,38,40,44,46,49,50,52 *
| ,53,57,77,78,85,86,87) and ad_dt_yyyymm in ( 200405,200404,200403,
| * 200402,200401,200312,200311,200310,20030
9,200308,200307,200306) group
| by * market_cd,store_cd,ad_dt_yyyymm,report_i
tem_cd,ad_quality_cd *
| * MODULE BASE END SIZE * sqlservr
| 00400000 00B2CFFF 0072d000 * ntdll
| 77F40000 77FF9FFF 000ba000 * kernel32
| 77E40000 77F33FFF 000f4000 * ADVAPI32 77DA0000
| 77E2FFFF 00090000 * RPCRT4 77C50000 77CF3FFF
| 000a4000 * USER32 77D00000 77D8EFFF 0008f000 *
| GDI32 77C00000 77C43FFF 00044000 * OPENDS60
| 41060000 41065FFF 00006000 * MSVCRT
| 77BA0000 77BF3FFF 00054000 * UMS
| 41070000 4107CFFF 0000d000 * SQLSORT 42AE0000
| 42B6FFFF 00090000 * MSVCIRT 60020000 6002FFFF
| 00010000 * sqlevn70 41080000 41086FFF 00007000 *
| NETAPI32 02C60000 02CB2FFF 00053000 * ole32
| 030D0000 031F3FFF 00124000 * XOLEHLP
| 03200000 03205FFF 00006000 * MSDTCPRX
| 03210000 03280FFF 00071000 * OLEAUT32 03290000
| 0330CFFF 0007d000 * MSVCP60 03310000 03370FFF
| 00061000 * MTXCLU 03380000 03397FFF 00018000 *
| VERSION 033A0000 033A7FFF 00008000 * WSOCK32
| 033B0000 033B8FFF 00009000 * WS2_32
| 033C0000 033D7FFF 00018000 * WS2HELP
| 033E0000 033E7FFF 00008000 * CLUSAPI 03430000
| 03440FFF 00011000 * RESUTILS 03450000 03461FFF
| 00012000 * USERENV 03470000 03529FFF 000ba000 *
| MFC42u 03530000 03623FFF 000f4000 * secur32
| 036B0000 036C2FFF 00013000 * mswsock
| 036E0000 03722FFF 00043000 * DNSAPI
| 03730000 03756FFF 00027000 * winrnr 037A0000
| 037A6FFF 00007000 * WLDAP32 037B0000 037DEFFF
| 0002f000 * rasadhlp 03800000 03804FFF 00005000 *
| SSNMPN70 00C70000 00C75FFF 00006000 * SSNETLIB
| 00C80000 00C94FFF 00015000 * security
| 044B0000 044B3FFF 00004000 * wshtcpip
| 04500000 04507FFF 00008000 * SSmsLPCn 04510000
| 04516FFF 00007000 * ntdsapi 04530000 04545FFF
| 00016000 * SQLFTQRY 04420000 04451FFF 00032000 *
| CLBCatQ 04A60000 04ADDFFF 0007e000 * COMRes
| 04AE0000 04BA5FFF 000c6000 * sqloledb
| 04BB0000 04C35FFF 00086000 * MSDART
| 04480000 044A8FFF 00029000 * COMCTL32 04C40000
| 04CCFFFF 00090000 * comdlg32 04CD0000 04D16FFF
| 00047000 * SHLWAPI 04D20000 04D68FFF 00049000 *
| SHELL32 04D70000 0554CFFF 007dd000 * MSDATL3
| 045B0000 045C7FFF 00018000 * comctl32
| 05550000 05635FFF 000e6000 * oledb32
| 059E0000 05A5CFFF 0007d000 * OLEDB32R 05A60000
| 05A70FFF 00011000 * rsaenh 0FFD0000 0FFFCFFF
| 0002d000 * PSAPI 05B00000 05B0AFFF 0000b000 *
| xpstar 03050000 03096FFF 00047000 * SQLRESLD
| 030A0000 030A6FFF 00007000 * SQLSVC
| 030B0000 030C6FFF 00017000 * ODBC32
| 05C10000 05C49FFF 0003a000 * odbcbcp 05C50000
| 05C55FFF 00006000 * W95SCM 05C60000 05C6BFFF
| 0000c000 * SQLUNIRL 05C70000 05C9CFFF 0002d000 *
| WINSPOOL 05CA0000 05CC5FFF 00026000 * SHFOLDER
| 05CD0000 05CD8FFF 00009000 * odbcint
| 05EB0000 05EC6FFF 00017000 * NDDEAPI
| 05FE0000 05FE6FFF 00007000 * SQLSVC 05FF0000
| 05FF5FFF 00006000 * xpstar 06000000 06008FFF
| 00009000 * dbghelp 06840000 068F4FFF 000b5000 *
| * Edi: 067BFCD8: 3AE52EB8 067BFD10 A7FFFFFA 389C2000 067BFDB4
| 0097C46F * Esi: 389C2000: 01000201 00018000 00000000 00150000
| 00000000 00330000 * Eax: 58001005: 00000000 03000000 00000B00
| 8C000000 88000002 88000002 * Ebx: 389E8708: 3868DCE4 000004F7
| 00000004 000004F4 00000004 00000000 * Ecx: 00000033:
| * Edx: 00000002:
| * Eip: 007F8A40: 4604B70F 8D4C4303 8BFA3074 8BA50C45 A5663448
| C150418B * Ebp: 067BFCF4: 067BFD10 00801CB1 3AE52D68 3AE225E8
| 00000000 3AE52998 * SegCs: 0000001B:
| * EFlags: 00010207: 43003B00 5C003A00 49005700 44004E00 57004F00
| 3B005300 * Esp: 067BFC6C: 00000001 3AE52B44 00000000 00000000
| 00000000 00C567A0 * SegSs: 00000023:
| *
|
****************************************
************************************
***
| *
|
----
--
| * Short Stack Dump
| * 007F8A40 Module(sqlservr+003F8A40)
| (RangeGenerator::GetNextRange+000003D0) * 00801CB1
| Module(sqlservr+00401CB1) (RowsetSS::FetchNextRow+00000153) * 0042A4F6
| Module(sqlservr+0002A4F6) (CQScanRowset::GetRowWithPrefetch+000000
40) *
| 0042C21B Module(sqlservr+0002C21B) (CQScanRange::GetRow+000000EF) *
| 004314C9 Module(sqlservr+000314C9) (CQScanHashMatch::Iterate+00000BAF) *
| 00431B41 Module(sqlservr+00031B41) (CQScanHashMatch::GetRow+0000009F) *
| 006FCBF7 Module(sqlservr+002FCBF7) (CQScanXProducer::Open+0000039B) *
| 006FC656 Module(sqlservr+002FC656) (FnProducerThread+0000020E) * 0051274C
| Module(sqlservr+0011274C) (subproc_main+000000C2) * 41075002
| Module(UMS+00005002) (ProcessWorkRequests+00000272) * 41074698
| Module(UMS+00004698) (ThreadStartRoutine+00000098) * 77BC90A2
| Module(MSVCRT+000290A2) (endthread+000000A6) * 77E4A990
| Module(kernel32+0000A990) (FlsSetValue+00000779)
|

EXCEPTION_ACCESS_VIOLATION and sp3

Hi.
I installed SQL Server 2000 (it's a DC running Win2K Server SP4,
Exchange 2000 built 6249:4 SP3, Etrust Inoculate it 7.0, Zetafax
7.5) but the service didn't start and in the event
viewer the following error occured:
Event ID: 17055
Source: MSSQLSERVER
DESC: 17310:
FRunCm: Process 4008 gen fatal except c0000005
EXCEPTION_ACCESS_VIOLATION.
SQL Server is terminating the process.
As per Microsoft I ran SP3a ( http://support.microsoft.com/?kbid=814572 ) :
the setup stops and I obtained an error in the script
"sp3_serv_uni.sql" .
I checked sp3_serv_uni.out : "..General network error..".
I tried using Named Pipes only in Network Utility and the same for Client
Network Utility on the Server : it doesn't work !!
From where i had to start to solve the problem?
Please Help ( no deep experience in SQL2k...) .Thanks
P.S.Analysis Services is not installed.have u installed the latest MDAC as well?
Try change the Port number or use TCP/IP
Regards
Z
"Corrado N." <coradon_987@.libero.it> wrote in message
news:bk7997$ppe7h$1@.ID-107005.news.uni-berlin.de...
> Hi.
> I installed SQL Server 2000 (it's a DC running Win2K Server SP4,
> Exchange 2000 built 6249:4 SP3, Etrust Inoculate it 7.0, Zetafax
> 7.5) but the service didn't start and in the event
> viewer the following error occured:
> Event ID: 17055
> Source: MSSQLSERVER
> DESC: 17310:
> FRunCm: Process 4008 gen fatal except c0000005
> EXCEPTION_ACCESS_VIOLATION.
> SQL Server is terminating the process.
>
> As per Microsoft I ran SP3a ( http://support.microsoft.com/?kbid=814572 )
:
> the setup stops and I obtained an error in the script
> "sp3_serv_uni.sql" .
> I checked sp3_serv_uni.out : "..General network error..".
> I tried using Named Pipes only in Network Utility and the same for
Client
> Network Utility on the Server : it doesn't work !!
> From where i had to start to solve the problem?
> Please Help ( no deep experience in SQL2k...) .Thanks
> P.S.Analysis Services is not installed.
>

Wednesday, March 7, 2012

Exception trying to import data from Excel .

Hello,
I am running SQL Management Studio and was trying to import excel data into
a table on my local 2005 database. When I choose the import task then choose
Excel as the data source I get this lovely message:
TITLE: SQL Server Import and Export Wizard
An error occurred which the SQL Server Integration Services Wizard was not
prepared to handle.
ADDITIONAL INFORMATION:
Exception has been thrown by the target of an invocation. (mscorlib)
The connection type "EXCEL" specified for connection manager
"{2D54D28C-42CF-4614-ADB6-371E9E4F927D}" is not recognized as a valid
connection manager type. This error is returned when an attempt is made to
create a connection manager for an unknown connection type. Check the
spelling in the connection type name.
({06C927B9-F2F2-429B-B488-591883AE4655})
The connection type "EXCEL" specified for connection manager
"{2D54D28C-42CF-4614-ADB6-371E9E4F927D}" is not recognized as a valid
connection manager type. This error is returned when an attempt is made to
create a connection manager for an unknown connection type. Check the
spelling in the connection type name.
({06C927B9-F2F2-429B-B488-591883AE4655})
I have searched the net (google and groups) and have come up with nothing.
Any ideas would be greatly appreciated.
Rich
Hello Rich,
It seems there is some issues in SSIS related components are not registered
properly. You may want to try the following:
Bring up a command prompt and
-- go to C:\Program Files\Microsoft SQL Server\90\DTS\Binn
-- type below to unregister:
regsvr32.exe -u dtsconn.dll
--Then type below to register:
regsvr32.exe dtsconn.dll
If the issue persists, please ensure the Users (machinename\Users) have
Full Control on the
HKEY_CLASSES_ROOT\CLSID\.
In fact, you should go to PERMISSION-->ADVANCE
Ensure machinename\Users have full control permission.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Exception trying to import data from Excel .
>thread-index: AcY9aoUve4FjMD2oRuCRoGREQJdwgw==
>X-WBNR-Posting-Host: 143.166.226.16
>From: "=?Utf-8?B?UmljaCBEZW5pcw==?=" <cojones@.community.nospam>
>Subject: Exception trying to import data from Excel .
>Date: Wed, 1 Mar 2006 11:58:33 -0800
>Lines: 39
>Message-ID: <61A56959-4BBB-4267-BDF9-D2CACA3AF52E@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.tools
>Path: TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.tools:29869
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.tools
>Hello,
>I am running SQL Management Studio and was trying to import excel data
into
>a table on my local 2005 database. When I choose the import task then
choose
>Excel as the data source I get this lovely message:
>TITLE: SQL Server Import and Export Wizard
>--
>An error occurred which the SQL Server Integration Services Wizard was not
>prepared to handle.
>--
>ADDITIONAL INFORMATION:
>Exception has been thrown by the target of an invocation. (mscorlib)
>--
>The connection type "EXCEL" specified for connection manager
>"{2D54D28C-42CF-4614-ADB6-371E9E4F927D}" is not recognized as a valid
>connection manager type. This error is returned when an attempt is made to
>create a connection manager for an unknown connection type. Check the
>spelling in the connection type name.
> ({06C927B9-F2F2-429B-B488-591883AE4655})
>--
>The connection type "EXCEL" specified for connection manager
>"{2D54D28C-42CF-4614-ADB6-371E9E4F927D}" is not recognized as a valid
>connection manager type. This error is returned when an attempt is made to
>create a connection manager for an unknown connection type. Check the
>spelling in the connection type name.
> ({06C927B9-F2F2-429B-B488-591883AE4655})
>I have searched the net (google and groups) and have come up with nothing.

>Any ideas would be greatly appreciated.
>--
>Rich
>
|||Peter,
Thanks for the quick response. I tried what you said (unregister and
re-register) and it yeilded no results. I then applied the registry
permisison (while SQL Management studio was open and the error was on the
screen) to the CLSID folder (giving Users full control). I then tried the
operation again and got a message saying something to the effect of Server
Name Unknown (sorry I didnt think to write it down). So I closed the SQL
Management studio and re-opened it. When I tried again, I got a similar
message to the first time I tried but it had different CLSID's. I have
attached the message below.
One other thing to note, I noticed that I also do not have the drivers to be
able to read in such things as flat files. On a co-workers computer it
appears between the first .net dirvers and the media catalog drivers. I am
not sure if te two are related but I thought I would bring it up.
Lastly before, you replied today, I uninstalled SQL Server and the tools and
then re-installed. Still nothing.
Message follows:
TITLE: SQL Server Import and Export Wizard
An error occurred which the SQL Server Integration Services Wizard was not
prepared to handle.
ADDITIONAL INFORMATION:
Exception has been thrown by the target of an invocation. (mscorlib)
The connection type "EXCEL" specified for connection manager
"{586BE7D4-F968-4585-9DE7-DAEDAD067CF3}" is not recognized as a valid
connection manager type. This error is returned when an attempt is made to
create a connection manager for an unknown connection type. Check the
spelling in the connection type name.
({38BF22B4-3036-4BAB-9177-4820DA4EE187})
The connection type "EXCEL" specified for connection manager
"{586BE7D4-F968-4585-9DE7-DAEDAD067CF3}" is not recognized as a valid
connection manager type. This error is returned when an attempt is made to
create a connection manager for an unknown connection type. Check the
spelling in the connection type name.
({38BF22B4-3036-4BAB-9177-4820DA4EE187})
BUTTONS:
OK
Rich
"Peter Yang [MSFT]" wrote:

> Hello Rich,
> It seems there is some issues in SSIS related components are not registered
> properly. You may want to try the following:
> Bring up a command prompt and
> -- go to C:\Program Files\Microsoft SQL Server\90\DTS\Binn
> -- type below to unregister:
> regsvr32.exe -u dtsconn.dll
> --Then type below to register:
> regsvr32.exe dtsconn.dll
> If the issue persists, please ensure the Users (machinename\Users) have
> Full Control on the
> HKEY_CLASSES_ROOT\CLSID\.
> In fact, you should go to PERMISSION-->ADVANCE
> Ensure machinename\Users have full control permission.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> --
> into
> choose
>
>
|||Hello Rich,
It seems that oledb related driver has issues on this server. I suggest
that you try the following steps:
1. Reinstall MDAC by right clicking %windir%\inf\mdac.inf->Install to
reinstall MDAC. You may prompt to insert Win2003 setup CD.
2. Reinstall Jet SP8 on your server:
239114: How To: Obtain the Latest Service Pack for the Microsoft Jet 4.0
http://support.microsoft.com/default...b;en-us;239114
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Exception trying to import data from Excel .
>thread-index: AcY9rUgr1ynjYsVLQnuskA4GOXAWCw==
>X-WBNR-Posting-Host: 70.123.136.122
>From: "=?Utf-8?B?UmljaCBEZW5pcw==?=" <cojones@.community.nospam>
>References: <61A56959-4BBB-4267-BDF9-D2CACA3AF52E@.microsoft.com>
<53c43gaPGHA.8000@.TK2MSFTNGXA03.phx.gbl>
>Subject: RE: Exception trying to import data from Excel .
>Date: Wed, 1 Mar 2006 19:56:27 -0800
>Lines: 167
>Message-ID: <ADECD008-AC46-4800-B932-121744E9B779@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.tools
>Path: TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.tools:29881
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.tools
>Peter,
>Thanks for the quick response. I tried what you said (unregister and
>re-register) and it yeilded no results. I then applied the registry
>permisison (while SQL Management studio was open and the error was on the
>screen) to the CLSID folder (giving Users full control). I then tried the
>operation again and got a message saying something to the effect of Server
>Name Unknown (sorry I didnt think to write it down). So I closed the SQL
>Management studio and re-opened it. When I tried again, I got a similar
>message to the first time I tried but it had different CLSID's. I have
>attached the message below.
>One other thing to note, I noticed that I also do not have the drivers to
be
>able to read in such things as flat files. On a co-workers computer it
>appears between the first .net dirvers and the media catalog drivers. I
am
>not sure if te two are related but I thought I would bring it up.
>Lastly before, you replied today, I uninstalled SQL Server and the tools
and[vbcol=seagreen]
>then re-installed. Still nothing.
>Message follows:
>TITLE: SQL Server Import and Export Wizard
>--
>An error occurred which the SQL Server Integration Services Wizard was not
>prepared to handle.
>--
>ADDITIONAL INFORMATION:
>Exception has been thrown by the target of an invocation. (mscorlib)
>--
>The connection type "EXCEL" specified for connection manager
>"{586BE7D4-F968-4585-9DE7-DAEDAD067CF3}" is not recognized as a valid
>connection manager type. This error is returned when an attempt is made to
>create a connection manager for an unknown connection type. Check the
>spelling in the connection type name.
> ({38BF22B4-3036-4BAB-9177-4820DA4EE187})
>--
>The connection type "EXCEL" specified for connection manager
>"{586BE7D4-F968-4585-9DE7-DAEDAD067CF3}" is not recognized as a valid
>connection manager type. This error is returned when an attempt is made to
>create a connection manager for an unknown connection type. Check the
>spelling in the connection type name.
> ({38BF22B4-3036-4BAB-9177-4820DA4EE187})
>--
>BUTTONS:
>OK
>--
>
>--
>Rich
>
>"Peter Yang [MSFT]" wrote:
registered[vbcol=seagreen]
rights.[vbcol=seagreen]
not[vbcol=seagreen]
to[vbcol=seagreen]
to[vbcol=seagreen]
nothing.
>
|||Peter,
You are a genius. Thanks a million. I re-installed the MDAC inf and
everything started working again. Thank you so much. I have a task where I
REALLY needed to be able to import some xls/csv spreadsheets and was not
looking forward to having to write the code to do it myself.
Thanks again.
Rich
"Peter Yang [MSFT]" wrote:

> Hello Rich,
> It seems that oledb related driver has issues on this server. I suggest
> that you try the following steps:
> 1. Reinstall MDAC by right clicking %windir%\inf\mdac.inf->Install to
> reinstall MDAC. You may prompt to insert Win2003 setup CD.
> 2. Reinstall Jet SP8 on your server:
> 239114: How To: Obtain the Latest Service Pack for the Microsoft Jet 4.0
> http://support.microsoft.com/default...b;en-us;239114
> Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> --
> <53c43gaPGHA.8000@.TK2MSFTNGXA03.phx.gbl>
> be
> am
> and
> registered
> rights.
> not
> to
> to
> nothing.
>
|||Hello Rich,
Welcome! Great to hear the issue is resolved. :-)
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: Exception trying to import data from Excel .
>thread-index: AcY+EDFvaKWB5xrzSHyd9a5fSbx9sA==
>X-WBNR-Posting-Host: 143.166.226.17
>From: "=?Utf-8?B?UmljaCBEZW5pcw==?=" <cojones@.community.nospam>
>References: <61A56959-4BBB-4267-BDF9-D2CACA3AF52E@.microsoft.com>
<53c43gaPGHA.8000@.TK2MSFTNGXA03.phx.gbl>
<ADECD008-AC46-4800-B932-121744E9B779@.microsoft.com>
<MZFTnFdPGHA.2528@.TK2MSFTNGXA03.phx.gbl>
>Subject: RE: Exception trying to import data from Excel .
>Date: Thu, 2 Mar 2006 07:44:29 -0800
>Lines: 247
>Message-ID: <FF059899-A260-49CC-85F8-134D3D7F75BA@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.tools
>Path: TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.tools:29886
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.tools
>Peter,
>You are a genius. Thanks a million. I re-installed the MDAC inf and
>everything started working again. Thank you so much. I have a task where
I[vbcol=seagreen]
>REALLY needed to be able to import some xls/csv spreadsheets and was not
>looking forward to having to write the code to do it myself.
>Thanks again.
>--
>Rich
>
>"Peter Yang [MSFT]" wrote:
4.0[vbcol=seagreen]
rights.[vbcol=seagreen]
the[vbcol=seagreen]
the[vbcol=seagreen]
Server[vbcol=seagreen]
SQL[vbcol=seagreen]
similar[vbcol=seagreen]
to[vbcol=seagreen]
I[vbcol=seagreen]
tools[vbcol=seagreen]
not[vbcol=seagreen]
to[vbcol=seagreen]
to[vbcol=seagreen]
have[vbcol=seagreen]
so[vbcol=seagreen]
data[vbcol=seagreen]
then[vbcol=seagreen]
was[vbcol=seagreen]
valid[vbcol=seagreen]
made[vbcol=seagreen]
the[vbcol=seagreen]
valid[vbcol=seagreen]
made[vbcol=seagreen]
the
>

Thursday, March 29, 2012

ExecContextHit through SQL Profiler

ExecContextHit through SQL Profiler

Tuesday, March 27, 2012

EXEC sp_serveroption

EXEC sp_serveroption

EXEC sp_serveroption

EXEC Query Performance

EXEC Query Performance

Monday, March 26, 2012

EXEC Query Performance

Monday, March 12, 2012

Exchange 5.5 email problem

Excessive Logon Audit Events

Friday, March 9, 2012

EXCEPTION_ACCESS_VIOLATION within SQL Server when running SSIS package

EXCEPTION_ACCESS_VIOLATION in RangeGenerator::GetNextRange

EXCEPTION_ACCESS_VIOLATION in RangeGenerator::GetNextRange

EXCEPTION_ACCESS_VIOLATION and sp3

Wednesday, March 7, 2012

Exception trying to import data from Excel .

Excel Import

Blog Archive

About Me