Discussion Forums

I am getting and exception when trying to load the raster image GLOBE.JP2

{"A procedure imported by 'MapSuiteECW2005, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' could not be loaded.":"MapSuiteECW2005, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null"}

Inner StackTrace: at MapSuiteGeoRaster.GeoImageECW..ctor()
at CreateGeoImageFile(String filename)
at MapSuiteGeoRaster.GeoImage.LoadFile(String filename)


I am running version 2.18.5.0 of the desktop edition

Any ideas?

spatpat,

Thanks for your post!

Could you verify that you the the following two files in your system32 directory:

msvcp71.dll
msvcr71.dll

If these are missing Map Suite will have issues rendering image layers such as globe.jp2.

ThinkGeo Support

Yes, those files are there.

The Image Layer sample application does work on my computer, but that is not using a JP2 file.

Any ideas?

spatpat,

You should be able to load you jp2 file within the Image App as well. Simply replace one of the path of one of the image files with the path to your jp2.

Is there an associated world file with your image? Map Suite requires this to correctly place the image on the map.

If you receive an error when loading the image in the Image App, we may want to setup an FTP transfer so that we could take a look at the image file.

ThinkGeo Support

If I try and load the jp2 file into the sample image app, I get the same thing.

I am just trying to load the standard RenderUSA 2.0 files.

It is trying to load .\Raster\globe.jp2

there is a globe.jpw file in the same directory.

spatpat,

At this point I would recommend creating a ticket within the Customer Portal. This way we can exchange screenshots and we can see how you are loading the layer.

ThinkGeo Support

I am having this same issue with the sample project. was this ever resolved?
I am running version 2.25.0.0 of the DesktopEdition.

Thanks
Jesse

Jesse,

Usually this issue is a result of a missing msvc*71.dlls. We do have a newer build that I can provide you with that I have not seen this problem with.

ThinkGeo Support