Upgrade to GE 4.5 trouble - admin access to bin folder

Permanently deleted user

May 04, 2016 15:41

This is most likely an internal server problem and not a Latitude issue but wanted to ask/inform about an issue we are having when trying to upgrade from GE 4.4.2 to 4.5. 

 

When running the 4.5 msi, we receive an error part way through (i believe the wizard is at the 'copying new files' stage) saying that the installer has insufficient privileges to access the bin directory in the program x86 REST directory. 

 

I am an admin so should have full rights to do this, and it has never been an issue with previous upgrades. 

 

Also, what's odd is that after the upgrade process is cancelled, the bin directory is completely locked, I cannot ven see what's in it, but it is available at other times.

 

In addition, when forced to cancel to upgrade/install to 4.5, the rolling back of changes to 4.4.2 doesn't completely work and we need to reboot the server and run a repair of 4.4.2 (cannot repair without reboot - with no reboot we get the same insufficient privileges error relating to that bin directory).

 

Very odd and frustrating and as I said likely a server config issue on our end, but wanted to see if anyone else has encountered anything similar, and if there is anything notably different about how the 4.5 msi works compared to the 4.4.2 and earlier msi's.

 

Thanks -

 

Allen

0

• 

  Permanently deleted user

  May 04, 2016 15:44

  Good morning Allen,

   

  Have a look at the known issues KB article here:  https://support.geocortex.com/essentialsGSCkba?sub-nav=kba&main-nav=essentials&#!/feedtype=SINGLE_ARTICLE_SEARCH_RESULT&id=kA3600000008QTC

   

  I think the first entry will solve your issue.  If it does not, please open a support case so we can help you investigate :)

   

  Thanks!

   

  Danny

  0
• 

  Permanently deleted user

  May 04, 2016 15:58

  Thanks for the quick response Danny -

   

  Good to know it's not something we have been doing wrong, or that our server security was changed without our GIS people being informed (which was our suspicion).

   

  So just to clarify as far as order of operations is concerned - Do we recycle the Essentials App Pool or resart IIS BEFORE running the upgrade to ensure it works, or is this a fix to run after the upgrade fails?  How/when to we implement this fix to make sure the upgrade is successful?

  0
• 

  Permanently deleted user

  May 04, 2016 16:28

  Hi Allen,

   

  No problem, glad I was able to help!

   

  The root of this problem seems to lie in IIS holding a lock on that directory and the installer not being able to access it.  You could potentially run the fix before running the installer, but there is no guarantee that a user won't navigate to one of your sites causing the Bin folder to lock again before the installer tries to access it.

   

  My recommendation would be to wait for the installer to throw the error, and then recycle your AppPools if needed (without closing the installer).  Once that is done, click retry in the installer, and it should continue normally.

   

  I hope this answers your question!  If not, please let me know and I would be happy to clarify further.

   

  Cheers,

   

  ?Danny

  0
• 

  Permanently deleted user

  May 09, 2016 15:08

  Thanks Danny - that worked and we're good to go. 

  0

Please sign in to leave a comment.