GMSC Discussions

[JohnMcMahon]

HI All,

We are getting an exception when trying to display ECW data in GMSC.

The exception clearly states that we are missing the 'Microsoft Visual C++ 2010 Feature Pack Redistributable Package'

What is not clear is where this package is required.

Must it be installed on the client machine or on the server?

Being a java exception I would have to assume it is needed on the client, but does this mean every client needs the distributable in order to use ECW?

If it is needed on the server, then is it required even if we have the 'Microsoft Visual C++ 2012 Redistributable' installed?

Thanks for any replies.

John

java.util.concurrent.ExecutionException: java.lang.UnsatisfiedLinkError: Required component 'Microsoft Visual C++ 2010 Feature Pack Redistributable Package' is missing!
 at java.util.concurrent.FutureTask.report(Unknown Source)
 at java.util.concurrent.FutureTask.get(Unknown Source)
 at com.intergraph.web.core.data.loader.ParallelFeatureLoader.startLoading(ParallelFeatureLoader.java:88)
 at com.intergraph.web.core.data.loader.LoaderPool.doLoading(LoaderPool.java:107)
 at com.intergraph.web.core.data.loader.LoaderPool.loadFeatures(LoaderPool.java:75)
 at com.intergraph.web.core.browsing.BaseMapContentLoader.loadContentRequest(BaseMapContentLoader.java:71)
 at com.intergraph.web.core.browsing.MapContentController.run(MapContentController.java:88)
Caused by: java.lang.UnsatisfiedLinkError: Required component 'Microsoft Visual C++ 2010 Feature Pack Redistributable Package' is missing!
 at com.intergraph.web.plugin.ecw.IWSLoader.processTile(IWSLoader.java:102)
 at com.intergraph.web.core.data.loader.ParallelFeatureLoader$1.call(ParallelFeatureLoader.java:70)
 at com.intergraph.web.core.data.loader.ParallelFeatureLoader$1.call(ParallelFeatureLoader.java:64)
 at java.util.concurrent.FutureTask.run(Unknown Source)
 at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
 at java.util.concurrent.FutureTask.run(Unknown Source)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
 at java.lang.Thread.run(Unknown Source)

[gmueller · Accepted solution]

Hi John,

It is needed on client. ECW support uses Java native library binding which needs this package.

Best regards,

Gerd

[MahaKamal]

Hello,

I need to know how to use Extended raster format support at the GMSC 2016. i have tried new feature, but i have not found a raster type

[MahaKamal]

Hello,

Please i need an urgent help..

May you please, send the steps to display ecw at GMSC?

Is there is a way to display ecw and any other raster format at GMSC2016 without using Appolo nor webmap.

Thanks in advance

[MahaKamal]

Hello,

May you please, send all the steps to display raster format (.ecw, .img,...) at GMSC 2016. as it is stated that the new version support the native raster format. can i add the raster file directly at gmsc admin as feature?

[sturcato]

The way to set up the feature itself has no changed, but here are additional raster formats supported.

You basically have to register the raster file in a database where the boundig box of the feature will be stored. For instance in GeoMedia you would use "Insert georeferenced image" command. Then in the admin you can specify the feature manually (new feature -> (New feature) ->  database) or import the definition (new feature -> (Import from database) Database).

HTH,

Stefano

[MahaKamal]

Thank you.

iam getting "unexpected error" while trying to load features from geomedia access library. the log file stated that "The Microsoft Access database engine cannot find the input table or query 'LibraryObjects'. Make sure it exists and that its name is spelled correctly."

May you please tell me what is the reason & how to fix it

[sturcato]

it seems to be related to the GM metadata configuration. Please try importing it directly from the database instead.

Stefano

[MahaKamal]

Iam already trying to import it from database and it gives that error. How to adjust the GM metadata config to resolve it.

Thank you

[sturcato]

you are importing from GM Access library, which is a different workflow. In the import from database there is no need to have GM metadata.