I am having the same problem too.
ArcGIS 10.3, StreetMap Premium 2014 release 3. "Could not install the license". Have ESRI resend the licence, still the same error. Anybody has any idea what is going on?
2015.1 installed without any problem on that machine.
First, make sure that your StreetMap Premium license file has not expired, check for an expiration date on the end of the license file name, for example: nahr_fgdb_2015.1_na_all_11_12_15.sdlic. This license file expires on 11/12/2015.
Next, check the StreetMap Premium resource pages to make sure that you are using the appropriate version of the license file with the same product vintage. Each StreetMap Premium product has its own unique license file and license files are not transferable between versions. The StreetMap Premium product resource page/system requirements link is located here:
2015 system requirements—StreetMap Premium for ArcGIS | ArcGIS for Server
Check under the Previous Version link on the left-hand side for 2013 and 2014 version requirements.
StreetMap Premium products (specifically licensed File Geodatabase products are not compatible with ArcGIS software versions earlier than 10.1 SP1).
I know this is an old thread, but we're experiencing this very same issue for 10.3.1. Most users can install the license fine, but some are having "Could not install the license" issues.
The license file is not expired, and the product in question is StreetMap Premium for ArcGIS North America 2016 Release 2.
Has anyone found a solution?
Thanks,
Ryan
This probably isn't very helpful.. but I was able to install the license after upgrading my OS to Windows 10 and reinstalling all my programs.
Hi Ryan,
I wondered if you got this resolved and were able to update your Street Map Premium license in the end?
We are experiencing the same but with 10.6.1
Been in contact with Esri support and they have sent me several new licenses and none have been successful.
Thanks!
Caroline
Hi Caroline,
No, we couldn't ever figure it out. All of our computers ended up getting Windows upgrades and that seemed to make the problem disappear. Not an ideal solution, I know.
Ryan