# Exception\_access\_violation

**URL:** <https://discourse.f2i-consulting.com/t/exception-access-violation/229>\
**Category:** FETPAPI\
**Created:** [May 11, 2023, 11:40am UTC](https://discourse.f2i-consulting.com/t/exception-access-violation/229 "2023-05-11T11:40:00Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![asim.jadoon](https://discourse.f2i-consulting.com/user_avatar/discourse.f2i-consulting.com/asim.jadoon/32/103_2.png) [@asim.jadoon](https://discourse.f2i-consulting.com/u/asim.jadoon)\
**Post date:** [May 11, 2023, 11:40am UTC](https://discourse.f2i-consulting.com/t/exception-access-violation/229/1 "2023-05-11T11:40:00Z")

</div>

Hi @philippeVerney,

My application is crashing while reading grid values in global crs (getZValuesInGlobalCrs).

I understand this will require more investigation, but by looking at the log can you please get some rough idea what probably can be wrong? Please note that this error is not consistent and occurs rarely.

Error Log: [hs\_err\_pid3456 (Standalone).log - Google&nbsp;Drive](https://drive.google.com/file/d/1tzJ2nHqxvqeHlNobKbb-773qbBcXG59M/view?usp=sharing)

Thanks,  
Asim

---

<div class="post-metadata">

**Author:** ![philippeVerney](https://discourse.f2i-consulting.com/user_avatar/discourse.f2i-consulting.com/philippeverney/32/29_2.png) [@philippeVerney](https://discourse.f2i-consulting.com/u/philippeVerney)\
**Post date:** [May 11, 2023, 12:24pm UTC](https://discourse.f2i-consulting.com/t/exception-access-violation/229/2 "2023-05-11T12:24:07Z")

</div>

Hi @asim.jadoon

We have fixed some errors in FETPAPI during the two last weeks.  
Yours might be one which is now fixed since we have faced a similar symptom before the recent fixes.

You should shift to FESAPI 2.6.0.0 and latest FETPAPI and do your test again.  
Notice that for now, we face some issue connecting with OSDU M17. But if you test against the open etp server docker image, it should be all fine.

---

<div class="post-metadata">

**Author:** ![asim.jadoon](https://discourse.f2i-consulting.com/user_avatar/discourse.f2i-consulting.com/asim.jadoon/32/103_2.png) [@asim.jadoon](https://discourse.f2i-consulting.com/u/asim.jadoon)\
**Post date:** [May 11, 2023, 12:49pm UTC](https://discourse.f2i-consulting.com/t/exception-access-violation/229/3 "2023-05-11T12:49:45Z")

</div>

Thank you very much @philippeVerney. We will build the versions you have suggested and test again. Just wondering do you have any build pipeline from where we can get the latest builds? We have been struggling to build them ourselves.

---

<div class="post-metadata">

**Author:** ![philippeVerney](https://discourse.f2i-consulting.com/user_avatar/discourse.f2i-consulting.com/philippeverney/32/29_2.png) [@philippeVerney](https://discourse.f2i-consulting.com/u/philippeVerney)\
**Post date:** [May 11, 2023, 12:56pm UTC](https://discourse.f2i-consulting.com/t/exception-access-violation/229/4 "2023-05-11T12:56:00Z")

</div>

Not yet unfortunately. I fully understand that it is not convenient at all to build all what is needed by yourselves.

FESAPI, which has been sponsored and which is more mature, delivers binaries in C# and JAVA in releases (assect section) : [Release v2.6.0.0 · F2I-Consulting/fesapi · GitHub](https://github.com/F2I-Consulting/fesapi/releases/tag/v2.6.0.0) and I can provide some others if needed  
It may save you some time.  
For FETPAPI, I unfortunately run out of time. I could find some and a paying customer (C++ flavor) asked for some improvements which explain the recent changes. I expect some others soon but my 2023 year start to now be fully booked…

---

<div class="post-metadata">

**Author:** ![asim.jadoon](https://discourse.f2i-consulting.com/user_avatar/discourse.f2i-consulting.com/asim.jadoon/32/103_2.png) [@asim.jadoon](https://discourse.f2i-consulting.com/u/asim.jadoon)\
**Post date:** [May 11, 2023, 1:06pm UTC](https://discourse.f2i-consulting.com/t/exception-access-violation/229/5 "2023-05-11T13:06:23Z")

</div>

I totally understand that. You’ve always been very supportive and I really appreciate that. If you get a chance to build FETPAPI (for yourself or anyone else) please do share a copy with me.

---

<div class="post-metadata">

**Author:** ![philippeVerney](https://discourse.f2i-consulting.com/user_avatar/discourse.f2i-consulting.com/philippeverney/32/29_2.png) [@philippeVerney](https://discourse.f2i-consulting.com/u/philippeVerney)\
**Post date:** [May 11, 2023, 3:24pm UTC](https://discourse.f2i-consulting.com/t/exception-access-violation/229/6 "2023-05-11T15:24:20Z")

</div>

I just discussed with some other adopters and I am going to make a commit hopefully tomorow porting FETPAPI master to FESAPI v2.7.  
So please wait a bit for your builds. Next monday should be fine!

I am afraid that, if you adopt FESAPI v2.6 now, you will have soon to adopt FESAPI v2.7.

---

<div class="post-metadata">

**Author:** ![asim.jadoon](https://discourse.f2i-consulting.com/user_avatar/discourse.f2i-consulting.com/asim.jadoon/32/103_2.png) [@asim.jadoon](https://discourse.f2i-consulting.com/u/asim.jadoon)\
**Post date:** [May 22, 2023, 11:45am UTC](https://discourse.f2i-consulting.com/t/exception-access-violation/229/7 "2023-05-22T11:45:51Z")

</div>

@philippeVerney Can you please share the release date (tentative maybe) for FETPAPI?

---

<div class="post-metadata">

**Author:** ![philippeVerney](https://discourse.f2i-consulting.com/user_avatar/discourse.f2i-consulting.com/philippeverney/32/29_2.png) [@philippeVerney](https://discourse.f2i-consulting.com/u/philippeVerney)\
**Post date:** [May 22, 2023, 2:06pm UTC](https://discourse.f2i-consulting.com/t/exception-access-violation/229/8 "2023-05-22T14:06:42Z")

</div>

Hi Asim

Please try to create new post for new topic. It would help future search.  
As said in [Reading resqml data using fetpapi - #3 by philippeVerney](https://discourse.f2i-consulting.com/t/reading-resqml-data-using-fetpapi/220/3)

> The plan is to make a first release in 2023. I think it will be second semester.  
> I don’t expect huge changes in FETPAPI. Cleaning and testing are the main things to do.

For now, we observe a good stability on Windows and on most of Linux OS. However, we have one last rare but critical bug on a particular Linux platform which we are investigating. This prevents any release for now.  
Plenty of improvements are planned : performance, documentation, example, … but this should not stop a release,it could be part of next minor further versions.