'OSGeo.GDAL.GdalPINVOKE'
I get the following error dialog box everytime I start DNR GPS:
SetupGDAL
gdal_csharp - The type initializer for 'OSGeo.GDAL.GdalPINVOKE' threw as exception.
The program then opens up but when I select Track>Download I get the following exception dialog box:
GPS_Download
ogr_csharp - The type initializer for 'OSGeo.OGR.OgrPINVOKE' threw an exception.
I've attached an image of the two exception dialog boxes.
I'm runing DNR GPS from a shortcut pointing to the executable file in the same directory where the other DNR GPS files are located.
Windows 7, 64 bit
DNRGPS version 6.0.0.11
Thanks
SetupGDAL
gdal_csharp - The type initializer for 'OSGeo.GDAL.GdalPINVOKE' threw as exception.
The program then opens up but when I select Track>Download I get the following exception dialog box:
GPS_Download
ogr_csharp - The type initializer for 'OSGeo.OGR.OgrPINVOKE' threw an exception.
I've attached an image of the two exception dialog boxes.
I'm runing DNR GPS from a shortcut pointing to the executable file in the same directory where the other DNR GPS files are located.
Windows 7, 64 bit
DNRGPS version 6.0.0.11
Thanks
Leave a comment
file:crmIKaZear4yWCacwqjQXA
Word DOC with images of error messages
Word DOC with images of error messages
on 2012-08-22 18:50 *
By david.wheelock
Hello.
I'm not on the development staff, but I have some computers with this problem, so I've been following this issue. Here's what's going on with this.
There are a whole slew of tickets with these csharp pinvoke errors. There's one ticket that someone set up as as the "Summary" ticket, 122. I "Related" this ticket to that one.
The developers have worked on this problem, but can't pin it down. Apparently, it only affects a small number of machines, maybe 5-10%. The kicker is that none of the machines at MIDNR are affected so the MIDNR staff don't have any actual warm boxes to experiment on.
However, the problem does NOT seem like it will go away or that there's anything that will fix it completely, at present. At first it seemed like it might be just an XP issue, but there are also Windows 7 computers reporting the problem. Both 32 and 64 bit computers are affected. So, we know that it's not an OS issue and upgrading the OS is not a permanent fix. Getting a new computer or OS upgrade might fix the probably temporarily, but there's no guarantee that it would be a permanent fix.
We're just staying with old DNR Garmin at our shop till this problem is addressed.
I'm not on the development staff, but I have some computers with this problem, so I've been following this issue. Here's what's going on with this.
There are a whole slew of tickets with these csharp pinvoke errors. There's one ticket that someone set up as as the "Summary" ticket, 122. I "Related" this ticket to that one.
The developers have worked on this problem, but can't pin it down. Apparently, it only affects a small number of machines, maybe 5-10%. The kicker is that none of the machines at MIDNR are affected so the MIDNR staff don't have any actual warm boxes to experiment on.
However, the problem does NOT seem like it will go away or that there's anything that will fix it completely, at present. At first it seemed like it might be just an XP issue, but there are also Windows 7 computers reporting the problem. Both 32 and 64 bit computers are affected. So, we know that it's not an OS issue and upgrading the OS is not a permanent fix. Getting a new computer or OS upgrade might fix the probably temporarily, but there's no guarantee that it would be a permanent fix.
We're just staying with old DNR Garmin at our shop till this problem is addressed.
on 2012-08-22 22:55 *
By squangle12
I would be more than happy to provide that machine to experiment on. Win7, Arcgis 10.0, GPS.
Please contact me.
Steve Kennedy
Senior GIS Specialist
Ventura County Fire Department
165 Durley Ave, Camarillo, CA 93010
(805) 383-4767 office
(805) 383-4780 fax
Steve.Kennedy@Ventura.org
"David Wheelock (david.wheelock)" dnrgps@alerts.assembla.com 08/22/2012 06:20
alert by David Wheelock (david.wheelock) in space DNRGPS Comment (by David Wheelock):
Hello.
I'm not on the development staff, but I have some computers with this problem, so I've been following this issue. Here's what's going on with this.
There are a whole slew of tickets with these csharp pinvoke errors. There's one ticket that someone set up as as the "Summary" ticket, 122. I "Related" this ticket to that one.
The developers have worked on this problem, but can't pin it down. Apparently, it only affects a small number of machines, maybe 5-10%. The kicker is that none of the machines at MIDNR are affected so the MIDNR staff don't have any actual warm boxes to experiment on.
However, the problem does NOT seem like it will go away or that there's anything that will fix it completely, at present. At first it seemed like it might be just an XP issue, but there are also Windows 7 computers reporting the problem. Both 32 and 64 bit computers are affected. So, w e know that it's not an OS issue and upgrading the OS is not a permanent fix. Getting a new computer or OS upgrade might fix the probably temporarily, but there's no guarantee that it would be a permanent fix.
We're just staying with old DNR Garmin at our shop till this problem is addressed.
More details
If you no longer wish to receive these emails or if you would like to change the default frequency, click here to change your email notification settings for DNRGPS
Assembla | Workspaces to accelerate software teams
Please contact me.
Steve Kennedy
Senior GIS Specialist
Ventura County Fire Department
165 Durley Ave, Camarillo, CA 93010
(805) 383-4767 office
(805) 383-4780 fax
Steve.Kennedy@Ventura.org
"David Wheelock (david.wheelock)" dnrgps@alerts.assembla.com 08/22/2012 06:20
alert by David Wheelock (david.wheelock) in space DNRGPS Comment (by David Wheelock):
Hello.
I'm not on the development staff, but I have some computers with this problem, so I've been following this issue. Here's what's going on with this.
There are a whole slew of tickets with these csharp pinvoke errors. There's one ticket that someone set up as as the "Summary" ticket, 122. I "Related" this ticket to that one.
The developers have worked on this problem, but can't pin it down. Apparently, it only affects a small number of machines, maybe 5-10%. The kicker is that none of the machines at MIDNR are affected so the MIDNR staff don't have any actual warm boxes to experiment on.
However, the problem does NOT seem like it will go away or that there's anything that will fix it completely, at present. At first it seemed like it might be just an XP issue, but there are also Windows 7 computers reporting the problem. Both 32 and 64 bit computers are affected. So, w e know that it's not an OS issue and upgrading the OS is not a permanent fix. Getting a new computer or OS upgrade might fix the probably temporarily, but there's no guarantee that it would be a permanent fix.
We're just staying with old DNR Garmin at our shop till this problem is addressed.
More details
If you no longer wish to receive these emails or if you would like to change the default frequency, click here to change your email notification settings for DNRGPS
Assembla | Workspaces to accelerate software teams
on 2012-09-09 04:12 *
By OutdoorsJM
Hello all,
I was also have the same problems described on this ticket, and a number of others, and I think I finally found the problem! I suspect that the issue has something to do with the Environment Path(s) not being set correctly? I know in the older versions of windows there was a limit to the Path length and I have a lot of programs installed so I imagine mine is pretty long. Anyhow, what I ended up doing that fixed the problem for me was to go into the dnrgps\GDAL\bin folder and copied the dll files there and pasted them into the root of the dnrgps folder - i.e. same folder where the dnrgps.exe file is located. This seemed to work on my end! I also slectively deleted each dll that I copied - restarting the program each time - until I narrowed it down to the "libeay32.dll" file which seems to be the one causing my problem. So you may only have to copy that file, but I decided to keep all of them in the new location just in case it is the PATH issue and the program needs to access one of the others... There may be a better way to do this, and I'd be interested in knowing if anyone else finds a solution, but after MUCH searching on this site and others, and some experimenting on 5 different machines this worked for me! Hope it helps...
I was also have the same problems described on this ticket, and a number of others, and I think I finally found the problem! I suspect that the issue has something to do with the Environment Path(s) not being set correctly? I know in the older versions of windows there was a limit to the Path length and I have a lot of programs installed so I imagine mine is pretty long. Anyhow, what I ended up doing that fixed the problem for me was to go into the dnrgps\GDAL\bin folder and copied the dll files there and pasted them into the root of the dnrgps folder - i.e. same folder where the dnrgps.exe file is located. This seemed to work on my end! I also slectively deleted each dll that I copied - restarting the program each time - until I narrowed it down to the "libeay32.dll" file which seems to be the one causing my problem. So you may only have to copy that file, but I decided to keep all of them in the new location just in case it is the PATH issue and the program needs to access one of the others... There may be a better way to do this, and I'd be interested in knowing if anyone else finds a solution, but after MUCH searching on this site and others, and some experimenting on 5 different machines this worked for me! Hope it helps...
on 2012-09-14 03:20 *
By squangle12
Thank you!
"Chris Pouliot (chpoulio)" dnrgps@alerts.assembla.com 09/13/2012 08:06
alert by Chris Pouliot (chpoulio) in space DNRGPS Comment (by Chris Pouliot):
Fixed in new release 6.0.0.15. See Bug 49 for more information.
More details
If you no longer wish to receive these emails or if you would like to change the default frequency, click here to change your email notification settings for DNRGPS
Assembla | Workspaces to accelerate software teams
"Chris Pouliot (chpoulio)" dnrgps@alerts.assembla.com 09/13/2012 08:06
alert by Chris Pouliot (chpoulio) in space DNRGPS Comment (by Chris Pouliot):
Fixed in new release 6.0.0.15. See Bug 49 for more information.
More details
If you no longer wish to receive these emails or if you would like to change the default frequency, click here to change your email notification settings for DNRGPS
Assembla | Workspaces to accelerate software teams