SQL Server >> 0x800703E6 Invalid access to memory location.

by zach.sherry » Fri, 06 Apr 2007 07:58:52 GMT

All,

I have been running into a strange issue when using the sp_OACreate
and sp_OAMethod ext. sprocs in SQL Server.

The following errors are returned in this order when running a sproc
that creates an instance of a DLL and executes a command against it:

1. sp_OAMethod - 0x80010105 The Server Threw an Exception

Seems to create the object correctly the first time execution takes
place after the DBCC FREEPROCCACHE and DBCC DROPCLEANBUFFERS commands
are executed.

2. sp_OACreate - 0x80004002 No such interface supported

Returns this error once.

3. sp_OACreate - 0x800703E6 Invalid access to memory location.

Then continues to return this error until the DBCC FREEPROCCACHE and
DBCC DROPCLEANBUFFERS commands are run.


The syntax of the commands is as follows:

EXEC @hr = sp_OACreate '<DLL CLASS>', @object OUT, 4

EXEC @hr = sp_OAMethod @object, '<COMMAND>', @Results OUTPUT,
@variable1, @variable2


I noticed the following new app log entry on the first day this
started occuring:

The application, C:\WINDOWS\system32\DllHost.exe, generated an
application error The error occurred on 04/05/2007 @ 12:56:55.647 The
exception generated was c0000005 at address 7C8224B2 (ntdll!
ExpInterlockedPopEntrySListFault)

This is a multi-threaded COM object generated in VB6 and will initiate
and accept commands without error when implemented with a stand alone
VB application on the same server. Further, creating instances of
other components with the sp_OAxxx ext. sprocs return no such errors.

Any help is appreciated.

Thanks,
Zach



Similar Threads

1. Error Importing DTS Package - Invalid access to memory location - SQL Server DTS

2. CImageHelper::Init () Failed load of dbghelp.dll - Invalid access to memory location

This is just a small snippet from the beginning of an error message 
generated this morning. I guess my boss restarted the box and it was fine 
after that.  All ideas are appreciated. SQL2k SP3A.

TIA, ChrisR



2005-04-08 04:15:00.36 server    CImageHelper::Init () Failed load of 
dbghelp.dll - Invalid access to memory location.

 2005-04-08 04:15:00.36 server    CImageHelper::Init () Failed load of 
dbghelp.dll - Invalid access to memory location.



***Symbol load failed - Proceed to dump without any symbols

*Stack Dump being sent to d:\databases\MSSQL\log\SQLDump0025.txt

2005-04-08 04:15:00.36 server    process_login: Process 988 generated fatal 
exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating 
this process.

* 
*******************************************************************************

*

* BEGIN STACK DUMP:

*   04/08/05 04:15:00 spid 0

*

*   Exception Address = 77FCCAAD

*   Exception Code    = c0000005 EXCEPTION_ACCESS_VIOLATION

*   Access Violation occurred writing address 00620061


3. SQL Agent Job fails with Error: Invalid access to memory location. - SQL Server DTS

4. Problems installing SP3 - Memory location

Hello!
I'm having problems installing ServicePack 3 on SQL server Developer
Edition!

I receive this error:
Setup initialization error.
Invalid access to memory location.
c:\--------\----\---\Temp\sqlsut.dll.

What is the problem here?

-- 


- Lars



5. i'm really desperate: invalid memory alloc request - PostgreSQL

6. ERROR: invalid memory alloc request size 0

Hello,

I'm getting the following error when I try to update or insert into a table.
This just started happening today.  The table has been working fine up to
now.  The table has 27,000 rows and 24 columns.

ERROR:  invalid memory alloc request size 0

Why does this happen?  And how can I work around it?

Thanks
John


John Hagstrand
Interage Research, Inc.
18733 State Line Road
Antioch, IL  60002
847 838 5371
 XXXX@XXXXX.COM 
Information Technology Consulting
www.interageresearch.com



---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match

7. invalid memory alloc request size - PostgreSQL

8. ERROR: invalid memory alloc request size 0

"John Hagstrand" < XXXX@XXXXX.COM > writes:
> I'm getting the following error when I try to update or insert into a table.
> This just started happening today.  The table has been working fine up to
> now.  The table has 27,000 rows and 24 columns.

> ERROR:  invalid memory alloc request size 0

What PG version is this, and what exactly is the table schema (and how
did you change it recently)?  And let's see an exact example of a
failing query.  It'd be even nicer if you could get a stack trace from
the errfinish call.

The only recent bugs of this ilk that I can recall had to do with
operations on zero-column tables.  Probably you've found some new
corner case, but there's not enough info here to guess what.

			regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match