Home > Forum > Installation > How to migrate webcon to new servers

How to migrate webcon to new servers
0

Hello,

is there a guide on how to move both databases and the portal to new servers?
I tried to backup the databases, restore them on new database server and then perform upgrade on the new application server, but the installation fails when connecting to the Search Server:

06-02-2025 19:02:51 msg: Step2 src: Upgrade
06-02-2025 19:02:55 msg: Sql version: 14.0.3480.1 src: SqlServerVersionChecker
06-02-2025 19:02:59 msg: Url to Solr:
http://[SERVERNAME]:8983/solr/BPS_Activities/query?q=*:*&q.op=OR&indent=true&fq=TS_Insert:[2025-01-06T19:02:59.060Z%20TO%20NOW]&fq=-User_Name:"WebCon%20Workflow%20Service"&rows=0&wt=json
06-02-2025 19:03:01 msg: System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it [::1]:8983
at System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult)
at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
--- End of inner exception stack trace ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at WebCon.WorkFlow.Installer.Steps.Prerequisites.SearchServer.SolrMigrateHelper.d__27.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at WebCon.WorkFlow.Installer.Steps.Prerequisites.SearchServer.SolrMigrateHelper.GetRowsNumberFromSolr()
at WebCon.WorkFlow.Installer.Steps.Prerequisites.SearchServer.SolrBpsActivitiesMigrationPrerequisite.Work() src: SolrBpsActivitiesMigrationPrerequisite

I have installed the SearchServer service from the MSI and changed the Url in the tools section of the Installer.
I can start the service, but it just stops after some time without any errors in Event log.

Thanks,
Filip

MVP

Hi Filip,

could you elaborate on what you actually did?
- How is your farm setup, multiple servers, single server with WEBCON and SOLR and one database server?
- Any connection to old server?
- What do you mean with "both databases"?


If I would move a database to a new environment which consists of a single application server and database server I would:
- Do a complete WEBCON installation on the new server.
- Deactivate the license in the old environment
- Activate the license in the new environment.
- Reconfigure the global settings on the new environment
- Copy the existing content/attachment/archive databases to the new database server
- Replace the new content database in the ContentDatabase table of the config database with the old database name

This assumes that the old and new environment uses the same environment "Type" for example production.


You can also read up on it here:
https://community.webcon.com/posts/post/changing-the-name-of-the-application-server-vs-webcon-bps/528/3

https://daniels-notes.de/posts/2024/checklist-for-copying-artifacts-to-another-config-database
https://daniels-notes.de/posts/2023/copy-a-database

Best regards,
Daniel

In reply to: Daniel Krüger (Cosmo Consult)

Hi Filip,

could you elaborate on what you actually did?
- How is your farm setup, multiple servers, single server with WEBCON and SOLR and one database server?
- Any connection to old server?
- What do you mean with "both databases"?


If I would move a database to a new environment which consists of a single application server and database server I would:
- Do a complete WEBCON installation on the new server.
- Deactivate the license in the old environment
- Activate the license in the new environment.
- Reconfigure the global settings on the new environment
- Copy the existing content/attachment/archive databases to the new database server
- Replace the new content database in the ContentDatabase table of the config database with the old database name

This assumes that the old and new environment uses the same environment "Type" for example production.


You can also read up on it here:
https://community.webcon.com/posts/post/changing-the-name-of-the-application-server-vs-webcon-bps/528/3

https://daniels-notes.de/posts/2024/checklist-for-copying-artifacts-to-another-config-database
https://daniels-notes.de/posts/2023/copy-a-database

Best regards,
Daniel

Hi,

I need to move webcon databases and rename them in the process. Then I have to install webcon on new server and connect it to the renamed databases.
I can't install new instance, because the databases have to be pre-created by another team. The setup account does not have the permissions to do that.

Anyway I managed to solve the SearchServer issue. As it turns out you when doing this sort of stuff you have to move to the same version of webcon... If you use newer version it tries to connect to the old search server version to migrate stuff and the old server does not exist...
(I tried to install the search server manually, but that didn't work.)

Thanks for the info and for the links :)
Filip

Privacy overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognizing you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.


To see a full list of the cookies we use and learn more about their purposes, visit our Privacy Policy.