Geocortex Core Error during upgrade
When upgrading from essentials 4.5.1 to 4.6 during the post install I get an error "Failed to connect to Geocortex Core. The operation timed out". I cannot finish the upgrade. Any ideas?
0
-
I am getting the exact same error
Haven't been able to figure it out yet0 -
Try restarting IIs. 0 -
Thanks
Still doesn't work
I am getting the same error0 -
Chris and Craig,
Please email support@latitudegeo.com and a new support case will be created for you. Upgrade issues do not require support hours unless the issue is directly related to the environment or an unsupported configuration. Your case will be set to the highest priority and an analyst will contact you ASAP.
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 Partner0 -
Hi,
If you are having this issue, can you please check and see if you have a directory similar to my example below? On C or alternate drive letter.
C:\Program Files\Latitude Geographics\Geocortex Application Services 2\
In this directory we are looking for a folder called "onprem". It will be further into the folder structure, I've included an example from our developer.
C:\Program Files\Latitude Geographics\Geocortex Application Services 2\Data\DocumentStore\DocumentStore{NODE-NAME}\nodes\0\indices\
If the "onprem" folder exists, please stop the CORE service, delete the "onprem" folder only, start CORE, and try running the POST Installer.0 -
Hi Mike,
I tried going through these steps but am still unable to connect to CORE. The process keeps timing out.0 -
Hi,
Deleting the "onprem" folder from \Geocortex Application Services 2\ will only fix this issue if you have Core installed to the default folder structure. This issue appears to be multi faceted.
If you have Core and/or \Geocortex Application Services 2\ data on a drive other than "C" and you made a custom file path you could have issues and it may require help from Support directly.
Thanks
Mike Ketler0 -
For those interested, I spoke with Support Directly, we fixed the problem by uninstalling/re-installing Geocortex Core 0 -
Thanks Chris, can we have instructions on how to do the uninstall/reinstall? 0 -
Wayne from supported helped me out. I would suggest submitting a request in case your situation is different.
However for me, he simply unistalled Geocortex Core through the Features and Programs, deleted the Geocortex Core folder found: C:\Program Files\Latitude Geographics\ Then ran the Post installer, which then successfully installed Geocortex Core.0 -
Hi,
Uninstalling Core and deleting the directories will remove any Instant Search data and will clear out your security store. This could cause issues if your viewers use the Identity Server for sign in.
Thanks,
Mike Ketler0 -
Thanks Mike!
Exactly the reason I suggest contacting support!0 -
I did not have this problem on dev box, but production box did. Here are the details:
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 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)
Tried the uninstall, delete core folder, reboot, reinstall method and still failed to connect.0 -
Tried uninstalling/reinstalling the core as per the above advice but after some digging found out it was a proxy issue in the end. Due to the introduction of Elasticsearch the server checks its own web page when connecting to Geocortex Core under the Post Install but this was failing. Ticking the bypass proxy for local addresses in the IE settings resolved this issue 0 -
I encountered this error as well and was able to resolve it by UNCHECKING "SSL" during the Core installation wizard (when you're entering the cluster information). 0 -
Hi Ethan,
I have the same issue as you have or had. Were you able to fix it and could you tell me how?
Thx.0 -
I installed GE 4.9.1 on two identical blank servers today (W2012R2). The issue described above occured on both servers. I was able to get it working by uninstalling core and restarting post install. Then at the create/join cluster part I had to deselect "use SSL", otherwise it would hang again (even though SSL should be working perfectly fine). 0 -
Upgrading from GE 4.6.3 to 4.10.1 today, I ran into this. Uninstalling Core and (trying to) restart the post install did not work. For whatever reason, the Core service was stopped and could not be restarted. Rebooting the server took care of it. 0 -
Just ran into this issue after upgrade. Tried stoping/starting the Core service but it just timed out. Followed the uninstall Core and deleting the folder from the Aug 26 '16 thread and it worked. 0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
19 Kommentare