03-13-2017 02:54 PM
I repeat the process of uninstalling WebMap, clean up and install it again. This time I deliberately restart the IIS a couple of time and restart the server after doing the clean up. However, it still shows the same problem.
Is there any difference in the process of creating/validating components Backend or BackendWMPS compared to the one of AdminPortal?
It looks like it somehow triggers a trap or fault in the process.
03-21-2017 07:52 AM
I believe there shouldn't be anything different between the Configuration Wizard trying to create the Admin Portal, Backend or the BackendWMPS. All three are Admin Console type instances, although kept in a different Instance-hive (hidden from the GUI).
Looks like there is a bit more cleaning to do.
03-23-2017 01:25 PM
Would you mind explaining further what cleaning I should do?
I am not aware of other places, apart from IIS, registry and WebMap physical location.
03-29-2017 01:21 AM
In IIS there are several applications and virtual directories created on install which might not have been cleaned up properly in your case:
1. AdminConsole (a virtual folder pointing to the IIS WebSite's physical location subdirectory, by default C:\inetpub\wwwroot\AdminConsole)
2. AdminConsole/App (a sub-app of the folder)
3. AdminConsole/AdminPortal (a special administrative instance, whose physical location by default is in %CommonProgramFiles%\Hexagon\Services\AdminInstances\AdminPortal)
4. Backend (a special administrative instance, physical location is %CommonProgramFiles%\Hexagon\Services\AdminInstances\Backend)
5. BackendWMPS (physical location %CommonProgramFiles%\Hexagon\Services\AdminInstances\BackendWMPS)
6. geospatial (this is the main Welcome Page)
You should track them all down in IIS before installing WebMap anew and remove them, together with any Application Pools created specifically for them. It is a good idea to do an IIS reset afterwards, so that all resources get a chance to be released finally.
03-29-2017 02:15 PM
Thank you for looking at this.
After I uninstall webmap, I do remove those applications above in IIS, I also remove their application pools. I even remove all WebMap virtual directories such as GeospatialPortalDoc and GeospatialPortalImages.
I also delete their physical instances as you listed above.
Finally, I open the registry. From HKEY_LOCAL_MACHINE -> SOFTWARE -> Wow6432Node -> Intergraph -> Geospatial Server
If my cleaning method is enough then could be something else that causes the failure.
04-04-2017 08:32 AM
I have the same situation with an update to WebMap 2016 from 2015 and everythig suggested I still tried. Since I was in a urgency I had to restore a snapshoot with 2015 installation. I would like to update again to 2016 but we need proper instructions to avoid this problem on adminportal creation.
04-04-2017 08:53 AM - edited 04-04-2017 08:57 AM
I ran into this issue in the past on a VM upgrade 2015 to 2016 and resolved the issue by cross checking the prerequisites/system requirements and enable/install .NET 4.5 framework and Windows Identity Foundation. Once installed and registered the configuration process completed the task of create AdminPortal during a reinstall process.
It is worth checking prerequisites/system requirements on the OS.
If this has been done/confirmed please disregard this note.
04-04-2017 09:07 AM
I'm doing now a shanpshoot of VM, and I hope that during this week I will try to install webmap 2016 and if it fails again I will try to follow your suggestion.
04-05-2017 12:23 AM - edited 04-10-2017 11:33 PM
I was testing something related to AdminPortal recently and got into situation that the complete installation got broken. These steps helped me to recover:
Hopefully I didn't miss anything in this list
Then, after reset, I started the installations again:
AdminConsole was now fixed and it displayed the previous services as I didn't modify the related folders and registry entries.
HTH others ;-)