11/22/2024 11:55:56 AM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss using the SalesLogix OLE DB Provider from external applications (including usage of built-in provider procedures). View the code of conduct for posting guidelines.
|
|
|
|
Attempted to read or white protected memory. This is often an indication that other memory is corrupt
Posted: 25 Jun 09 4:21 PM
|
Hi everyone,
I really need your help.
I've coded a c# (asp.net) application using SLXOLEDB provider to load data from SLX database. When performing tests through MSSQL DB everything works as expected, however, the same tests performed from customer Oracle environment once in a while and no logical demeanor the system fires the following error message: "Attempted to read or white protected memory. This is often an indication that other memory is corrupt".
I've been focused to solve this but unfortunately I could not succeed or find out any trace about the error.
Any insight or possible help will be appreciated.
Thank you in advance. |
|
|
|
Re: Attempted to read or white protected memory. This is often an indication that other memory is corrupt
Posted: 25 Jun 09 6:25 PM
|
Have you looked at memory utilization stats when this occurs?
Does it happne on an specific query?
How much data are you handling? And, do you know if this error is coming from SLX or from the Oracle driver?
Have you tried to find any patches or updates to the Oracle driver?
SalesLogix OLEDB Provider doesn't intercepts the calls to parse the SQL statement and add Security, but the connection is still made by the Underlying database provider directly. Thus maybe you need to be looking in that direction.
|
|
|
|
Re: Attempted to read or white protected memory. This is often an indication that other memory is corrupt
Posted: 29 Jun 09 11:35 AM
|
Have you looked at memory utilization stats when this occurs?
Yes, the system doesn’t overtake 42MB.
Does it happen on an specific query?
No necessarily so, however most of the time it occurs when executing two specific queries in which I have a “case when” statement.
How much data are you handling? And, do you know if this error is coming from SLX or from the Oracle driver?
It is a very simple query, there is no significant amount of data bypassed. Considering the fact that it doesn’t happen from MSSQL environment I assume the error is coming from Oracle driver.
Yes I did. I could not find any addressed fix towards Oracle driver and even though Microsoft has already identified the error there is no fix available too.
SalesLogix OLEDB Provider doesn't intercepts the calls to parse the SQL statement and add Security, but the connection is still made by the Underlying database provider directly. Thus maybe you need to be looking in that direction.
Ok, I will take this. I have observed that if a change the way I use database calls the error decreases substantially nevertheless I need to use the statement condition “Case When” into my selects. |
|
|
| |
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|