Unsolved
This post is more than 5 years old
11 Posts
0
7163
December 16th, 2009 00:00
Centera SDK 3.2.687 problem with reading/writing in protected memory
Hello together,
we have the problem that some timesour SDK will prdouce the following ErrorMessage and let our application (BizTalk 2006 R2) get offline for a short time.
System.AccessViolationException: Es wurde versucht, im geschützten Speicher zu lesen oder zu schreiben. Dies ist häufig ein Hinweis darauf, dass anderer Speicher beschädigt ist.
bei EMC.Centera.FPApi.SDK.FPClip_Open(FPPoolRef inPool, String inClipID, FPInt inOpenMode)
bei EMC.Centera.SDK.FPClip..ctor(FPPool inPool, String inClipID, Int32 inOpenMode) bei EBV.Backend.BizTalk.CenteraAdapter.CenteraHelper.Retrieve(CenteraRequest request) bei EBV.Backend.BizTalk.CenteraAdapter.CenteraAdapterOutboundHandler.Execute(Message message, TimeSpan timeout)Sorry that the Message is in german, but the servers are german ones.
So do you have any idea what this message say and how we can troubleshoot this???
We are using the newest SDK Version (3.2.687) on server side and the Centera Star version 4.02 on the Centera side.
The application are two BizTalk 2006 R2 server that are pumping a lot of pictures into the Centera via the SDK.
For any answer we are very happy.
Thanks and best regards
HZD_Mai
mckeown_paul
409 Posts
0
December 16th, 2009 02:00
Hi
as this fault is occuring on a production system I would recommend that you place a call into your local EMC customer support centre as this forum is for answering sdk development questions.
gstuartemc
2 Intern
•
417 Posts
0
December 16th, 2009 03:00
There would have been a suffix on the zip file that you downloaded before building and installing it. This information is unlikely to have been carried over into a production environment, so I would recommend that you download the latest version, build it and then compare it to the one you have deployed.
HZD_Mai
11 Posts
0
December 16th, 2009 03:00
Hello,
how can i find ou which version i'm using???
Thanks fo your fast help.
HZD_Mai
mckeown_paul
409 Posts
0
December 16th, 2009 03:00
Hi
It's good that you have a ticket opened with EMC support on this however EMC support should escalate this issue through our normal channels and not suggest you should use these or other forums to try and find a fix yourself. Not that I'm saying you can't, by all means ask and if anyone has a suggestion please port. My intention was to ensure that your were not ONLY using this forum to try and get a fix for a problem in a production environment.
Access violations are very hard to debug and will require the help of EMC support to get resolved.
gstuartemc
2 Intern
•
417 Posts
0
December 16th, 2009 03:00
HZD_Mai
11 Posts
0
December 16th, 2009 03:00
Hello Paul McKeown,
thenaks for your reply. We have a seperated ticket by EMC opend. But the problem is that EMC at one point say ok we don't have any idea, please go to the Community and aks there.
So now i have made it twice, we haven an open EMC call and an community question.
Bescause it could be that onbe person have an idea where we have to look for.
Best regards.
HZD_Mai
HZD_Mai
11 Posts
0
December 16th, 2009 04:00
Hello,
could it be that this is the version: WinDev8a???
Best regards
HZD_Mai
HZD_Mai
11 Posts
0
December 16th, 2009 04:00
Hello,
i have give these question to our development. When i have a answer for this i will write back to you.
Thanks and best regards
gstuartemc
2 Intern
•
417 Posts
0
December 16th, 2009 04:00
No, that's the build of Dev Studio you used.
The assembly number may tell you, but I do not believe this has always been updated correctly.
RonaldHempel
5 Posts
0
December 22nd, 2009 01:00
Hello,
I'm doing the development of the application HZD_Mai is talking about so I'm trying to give you more details.
I did not keep the zip file so I can't tell you the version number at this point. The only information I have is the assembly version which is 3.1.1
Kind regards,
Ronald
RonaldHempel
5 Posts
0
December 22nd, 2009 02:00
That is the version the EMC people pointed us to when we started our development about a year ago. Anyway, I'll download the newest version and hopefully this will fix the issue.
Thank you for your help.
With kind regards,
Ronald
gstuartemc
2 Intern
•
417 Posts
0
December 22nd, 2009 02:00
gstuartemc
2 Intern
•
417 Posts
0
December 22nd, 2009 03:00
Hi Ronald - I can understand that you were pointed at using the 3.2.687 SDK, but you should always be using the most recent version of the .NET wrapper.
The dependency on Perl (which patched the IL to fix the protected memory issue) was removed some time ago but without knowing exactly when you downloaded it (or the name of the package you downloaded) then I cannot comment further.
The latest package has also fixed the version number - this is now updated in the assembly details.
RonaldHempel
5 Posts
0
December 22nd, 2009 07:00
Hi,
I meant we were pointed to this version of the.Net Wrapper.
Could you please provide a link I can check regularly to find the most recent version of the wrapper?
Thank you very much in advance.
Ciao
Ronald
aluitink
11 Posts
0
June 15th, 2011 09:00
I have been seeing these same errors. After some digging I am guessing the issue is related to the MarshalPtrToUtf8 custom marshal method called by SDK.FPClip_Create8(p,n)
It appeared these errors only occured while writting a clip attribute with double byte characters. But after futher debugging I have just confused myself further. While debugging I can get this to occur even when generating clips that worked in production. While running in production I could only get this to happen when generating clips with attributes that contain double byte characters.
The exception is thrown right as MarshalPtrToUtf8 goes out of scope, as soon as that happen I receive the exception.
I'm wondering if anyone can enlighten me to some possible reasons for this strange behavior. We are currently implementing a new way of using the Centera API but one of our customers is experiencing this issue currently and we would like to determine why and try to provide a fix.
Currently we are stuck with the 3.1.1 version.
Thanks,
Andy