Skip to main content
Known Participant
Oct 2, 2025 2:06 PM UTC

We have installed 15.8.8 on a new test server but the GIS config is not working.

We have installed 15.8.8 on a new server, migrating from Win2016 to 2022, to prepare for making the jump to 23.x. 15.8.8 is all up and running BUT the GIS bits are not happy. In Administration | GIS | Services display

  • Service Resources tab displays all the saved settings same as the old test server
  • Service Layers tab shows the assets and the service they are mapped to but the layer settings are not there and nothing appears in the dropdown selectors when you open them.

 

I'm sure there's some config element I've missed somewhere but I'm scratching my head. Any suggestions or ideas what to look for would be appreciated.

    4 replies

    Known Participant
    Oct 2, 2025 4:09 PM UTC

    An addendum here: opening the map and legend one layer throws a load error but all the others are there and can be switched on and off.

    Translate
    New Participant
    Oct 2, 2025 4:09 PM UTC

    If you are using any secured GIS Services, you may need to update those. We have SSO setup with our secured services and we sometimes lose authentication in our test environment because its not used as frequently and that is the same behavior we will see.

    Translate
    Known Participant
    Oct 2, 2025 4:09 PM UTC

    If you are using any secured GIS Services, you may need to update those. We have SSO setup with our secured services and we sometimes lose authentication in our test environment because its not used as frequently and that is the same behavior we will see.

    Thank you Eva. We did find the answer, I'll post a separate answer so others can see it easily.

    Translate
    Known Participant
    Oct 2, 2025 4:09 PM UTC

    AND THE ANSWER IS: web.config TargetFramework issue. In doing the install we had issues getting the embedded Crystal Reports to work due to a .Net misconfig and missing entries in the registry on the server (I'm not really familiar with that). Changing the TargetFramework to 4.0 made the embedded Crystal engine functionality work and on we went with testing. At some point a server admin found and corrected the registry problem but I was never informed so the TargetFramework never got reset to 4.8. Once we set it to 4.8 the GIS bits were happy again.

    Translate