APOLLO & ECW/JP2 Discussions

[rgoodman]

We are trying to licence ECW for ArcGIS 2016 on a Windows Server 2016 Datacentre machine hosted on Amazon EC2. The licence log file reports 

15:28:24 (INGRTS) EXITING DUE TO SIGNAL 51 Exit reason 28
15:28:28 (lmgrd) INGRTS exited with status 51 (HOSTID does not match the license server environment (Cloud|Virtual|Physical))

I have checked the public IP address (Amazon EIP) via whatismyipaddress.com. However, the Show Host ID tool does NOT show an EIP address.  Thus I think there is something on this machine blocking our licencing software from resolving the EIP.

I have already downgraded the licence admin tool to version v11.11.1 MR1, after https://community.hexagongeospatial.com/t5/ERDAS-APOLLO-Q-A/HOSTID-on-the-SERVER-line-needs-the-serv...

[rgoodman]

We think is because AWS made a change so that it does not reestablish the route necessary to get to the profile service at address 169.254.169.254. Does our licence tool just use http://169.254.169.254/latest/meta-data/ to to retrieve the metadata?

See https://forums.aws.amazon.com/thread.jspa?threadID=246520

[R.McCleese]

Looking at the user interface, I can see that this is not the Geospatial Licensing 2018 software, but likely an older version.

This problem was introduced within the Flexera FNP software starting with 11.13.1; Flexera has depreciated use of AMZN_IID and AMZN_EIP.

Use VM_UUID and INTERNET instead of AMZN_IID and AMZN_EIP.

Flexera plans to start supporting AMZN_EIP in Flexera FNP version 11.14.1, but Geospatial Licensing 2018 is using version 11.14.0.

You can get the INTERNET address to generate your license using the following from a command prompt:

“C:\Program Files (x86)\Hexagon\Geospatial Licensing 2018\program\lmutil.exe” lmhostid -internet v4

You can get the VM_UUID address to generate your license using the following from a command prompt:

“c:\Program Files (x86)\Hexagon\Geospatial Licensing 2018\program\lmutil.exe” lmhostid -ptype VM –uuid