Hoppa till huvudinnehållet

Essentials 4.6 Core Timeout

Erik Engstrom
After upgrading from Essentials 4.5.1 to 4.6 I can't seem to connect to the Core anymore...

 

When I upgraded our instance, it asked if I wanted to create a new cluster, or join an existing one with a shared secret. I had never done this before, as this was the first instance of the upgrade, so I chose a new cluster and entered a new shared secret. The upgrade happened without issue. 

 

I went to the post-installation and it seemed to install some new core files and then when it got to the initialization of the Core, it would fail with cause as a timeout. I can't get into the post-install configuration.

 

Does anybody know how I might troubleshoot this, or have experienced such a thing?
0

Kommentarer

11 kommentarer

Datum Röster
  • Erik Engstrom
    System.TimeoutException: The operation has timed out.

     

       at Geocortex.Platform.Role.Documents.DocumentStoreClient.<PerformPeekDocument>d__117.MoveNext()

     

    --- End of stack trace from previous location where exception was thrown ---

     

       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

     

       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

     

       at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()

     

       at Geocortex.Platform.Role.Documents.Sentry.Block[TResult](Task`1 task)

     

       at Geocortex.Platform.Role.Documents.DocumentStoreClient.Marshal[TResult](Task`1 task)

     

       at Geocortex.Platform.Role.Documents.DocumentStoreClient.PeekDocument(String id, Boolean throwIfMissing)

     

       at Geocortex.Essentials.PostInstall.EssentialsPostInstall.TestConnectionToCore(InitWindow window)

     

       at Geocortex.Essentials.PostInstall.EssentialsPostInstall.StartupAsync(InitWindow window)
    0
  • Cattyann Campbell
    I ran into this also here is what worked for me
    1. Uninstall
    2. Reintall
    3. Choose a new cluster and accept the default odd name it provided
    4. Add a simple secret mine was under 9 chacaters no numbers or special characters
    5. The post installer ran and all was well 
    Some people suggest contacting support. If the above does not work I would contact them.
    0
  • Permanently deleted user
    Hi Erik,

     

    Uninstalling Core and removing all the residual Core files and re-installing Core will most likely fix the issue but you will loose things like Instant Search indexes, permission settings and saved projects.  You may be able to revive it without uninstalling Core by following the "Known 4.6" issues in the KBA section of this website.  Deleting a folder called "onprem" may fix it for you.  If you're not worried about losing your Core data it's a good method of starting fresh and getting the folder names reset to the correct folder names (Geocortex Application Services 2 is an old folder name and no longer used).

     

    FYI, Core can be removed using the Add/Remove programs control panel and it can be re-installed by running the Post Installer.

     

    Regards,

     

    Wayne Richard

     

    Latitude Geographics Group Ltd.

     

    Head Office: 300 – 1117 Wharf Street  Victoria, BC Canada V8W 1T7

     

    Tel: (250) 381-8130 | Fax: (250) 381-8132 | wrichard@latitudegeo.com

     

    Developers of Geocortex web-based mapping software | www.geocortex.com

     

    An Esri Platinum Business Partner
    0
  • Erik Engstrom
    Thanks Wayne... I looked for the onprem file, but was not found in my GAS2 folder, in fact it looks like the DATA folders were removed during the upgrade process?

     

    It's likely I'll need to uninstall, but want to see if there is anyway we can preserve our security logins when/if we encounter the same issue on our production environment. I have a support ticket and will speak to support regarding the issue. 
    0
  • Erik Engstrom
    For the record, deleting "onprem" ended up working for us, however the location of our folder differed a bit from what was in the KBA.

     

    Thanks again Wayne.
    0
  • Chris Roberts
    I just want to jump on the coat tails of this one  with a somewhat related question.

     

    I have had issues in the past that could only be resolved by unintalling and reinstalling Core, previously this had no flow on impacts as we arent using Instant Search and it was easy enough to re-establish permissions.  However since we have now introduced Saved Projects unistalling Core will have a significant impact on our users!

     

    In the event of an emergency, is there a way of backing up the data store prior to uninstalling Core so that it cant be reinstated again without the loss of any saved projects?

     

    Cheers

     

    Chris
    0
  • Permanently deleted user
    Hey Erik,

     

    Where did you find the "onprem" folder?

     

    Thanks!
    0
  • Erik Engstrom
    E:\Latitude Geographics\Geocortex Application Services\Data\DocumentStore\DocumentStore\<server name>\nodes\0\indices

     

    Note that <server name> may not necessarily be the server name, because it was also the suggested cluster name. Not sure what the parameter is referring to. We store our Core data on our E:\ because it contains data stored from instant search and we have isolated it from our C:\ for file storage reasons.
    0
  • Permanently deleted user
    Wayne or Erik, I am new to installing GE. I have uninstalled the Core, reinstalled it and while trying to run the Post Installer, I get the same timeout error listed above. This is a fresh server - could there be something missing that I hadn't yet configured in IIS? Any advice on why this timeout could occur or good documents for running through a first install of GE? I checked out the standard help docs and think I followed the isntructions precisely. 
    0
  • Permanently deleted user
    Hi Melanie,

     

    The timeout is typically caused by Geocortex Core not running and it may be not running for a number of reasons.  If you check the taskmanager > processes tab, do you see a bunch of Geocortex Core processes or just 2?  The Core log files should hold a clue (C:\Program Files\Latitude Geographics\Geocortex Core\Data\Logs\Bootstrapper.console).  A common issue is checking the SSL checkbox during the Core installation process and the server not supporting the SSL3 protocol.   Uninstalling Core and unchecking the SSL checkbox during the Core installation would resolve it.   

     

    I would recommend submitting a support case if you cannot see an obvious issue in the logs.

     

    Regards,

     

    Wayne Richard

     

    Latitude Geographics Group Ltd.

     

    Head Office: 300 – 1117 Wharf Street  Victoria, BC Canada V8W 1T7

     

    Tel: (250) 381-8130 | Fax: (250) 381-8132 | wrichard@latitudegeo.com 

     

    Developers of Geocortex web-based mapping software | www.geocortex.com

     

    An Esri Platinum Business Partner

     

     
    0
  • Permanently deleted user
    Thanks Wayne. I did not know that it required SSL3, I have SSL2. So unchecking that box fixed it. 

     

    For the future users who need to know how to check what version of SSL protocol they have I did the following:
    1. Click Start, click Run, type regedt32 or type regedit, and then click OK.
    2. In Registry Editor, locate the following registry key: HKey_Local_Machine\System\CurrentControlSet\Control\SecurityProviders \SCHANNEL\Protocols
    3. The folders there should indicate what protocols are available. For example I did not have a SSL 3.0 folder, only SSL 2.0
    0

Du måste logga in om du vill lämna en kommentar.

Hittade du inte vad du sökte?

Nytt inlägg