Re: Access Violation in SQL Server Native Client
- From: "Dieter Pelz" <dieterp@xxxxxxxxxxxxx>
- Date: Tue, 6 Mar 2007 19:54:27 +0100
Hello,
sorry I thought an "Access Violation Exception" is clear enough, so I don't translated the German error message.
Best Regards
Dieter Pelz
"Charles Wang[MSFT]" <changliw@xxxxxxxxxxxxxxxxxxxx> schrieb im Newsbeitrag news:0ojLLawXHHA.3856@xxxxxxxxxxxxxxxxxxxxxxxxx
Hi, Dieter,
I understand that you encountered the Geman error message when you usd the
statement:
" insert into FACFG_SML_IDX
(FACFG_SML_IDX.WERK_ID,FACFG_SML_IDX.SML_ID,FACFG_SML_IDX.LAST_INDEX)
values
(?,?,0)" in SQLDescribeParam; however it succeeded when you used " insert
into FACFG_SML_IDX (WERK_ID,SML_ID,LAST_INDEX) values (?,?,0)".
If I have misunderstood, please let me know.
Appreciate your understanding that our MSDN Managed Newsgroups are focused
on English language support. It will be able to let us better understand
your issue clearly if you could do some translation in your future posts.
Anyway, after compare the following two articles:
http://msdn2.microsoft.com/de-de/library/33xdxt7x(vs.80).aspx
http://msdn2.microsoft.com/en-us/library/33xdxt7x(vs.80).aspx
, I know that the corresponding english meaning is "Attempted to read or
write protected memory. This is often an indication that other memory has
been corrupted".
I will write a test project to see if I can reproduce your issue and I will
let you know as soon as possible. Also, since the error indicates that this
is a memory related issue, you may also carefully check if there are some
array overflow issues.
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
======================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================
.
- Follow-Ups:
- Re: Access Violation in SQL Server Native Client
- From: Charles Wang[MSFT]
- Re: Access Violation in SQL Server Native Client
- From: Charles Wang[MSFT]
- Re: Access Violation in SQL Server Native Client
- References:
- Access Violation in SQL Server Native Client
- From: Dieter Pelz
- RE: Access Violation in SQL Server Native Client
- From: Charles Wang[MSFT]
- Access Violation in SQL Server Native Client
- Prev by Date: RE: Access Violation in SQL Server Native Client
- Next by Date: Re: Access Violation in SQL Server Native Client
- Previous by thread: RE: Access Violation in SQL Server Native Client
- Next by thread: Re: Access Violation in SQL Server Native Client
- Index(es):
Relevant Pages
|
Loading