Skip to main content

Object reference not set to an instance of an object when adding new layer to service

Comments

5 comments

  • Permanently deleted user
    Hi Lauren, we started getting this when we did an upgrade of GE. We narrowed it down to some RSS layers in a folder on the site. Removing the RSS layers allowed us to make changes to the site after that. 

     

    A few others have posted with a similar question from my memory and some have mentioned that it was due to multple ID in the native id attribute in the site.xml. 

     

    Not much to go on sorry. Hope it works out.
    0
  • Lauren MacLean
    We ended up removing the whole service and re-adding it.

     

    I've just realised that I'm not getting notified when someone responds to one of my questions, else I could have checked if the nativeID was the problem! We haven't had a recurrence since but if it doesn happen again I'll check this. Thanks!
    0
  • Permanently deleted user
    Hi Lauren, there was an issue where notifications weren't getting sent out for responses from some users earlier this year. I'm confident we've managed to fix this, but if you find you're still not getting notifications for new posts, please do (To: community@geocortex.com) let me know.
    0
  • Permanently deleted user
    Hi, I am also experiencing the same issue when adding a new group layer to a service. Has anyone found the definite solution for this?

     

     
    0
  • Permanently deleted user
    I was able to go into the Site.xml and add the layer.  I just copied the script of another layer and made the edits.  Enter the name the same as it is in the site directory and change the Native ID to whatever ID shows for the layer in the Site Directory.  Then reload the site and try adding the layer and saving.

     

    Also, when republishing the service, make sure the new layer is at the bottom. This will assign it a new ID rather than shuffling the existing ID's around.
    0

Please sign in to leave a comment.