Sync Error - Site not running - Cannot sync page content between two environments

MIdhun Sai Paluri asked on March 24, 2016 17:42

Hello all,

I am trying to sync a page between two environments and am getting the following error. Any ideas why?

SyncServer.ServerError: [SyncServer.ProcessSyncTask]: Site not running.

My environment:

  1. I installed Kentico 9 instance and a site on an Azure Box with its internal IP -
  2. I installed another Kentico 9 instance and the same above site on another Azure Box with its internal IP - Both azure machines are exactly running the same sites.
  3. I am using 14 day trial licenses on both of them as I am still evaluating Kentico 9.
  4. I switched off the firewalls and explicitly opened ports on both systems - incoming and outgoing to make sure that firewall is not blocking this sync operation.
  5. I can access on and vice versa too.
  6. The same page is there in both the environments already. I just edited on line of text on and want to see this change go to using the staging module.
  7. On, I added the server in the staging module.
  8. On, I made sure that the check box is checked on the Settings -> Versioning & Synchronication -> Staging -> Enable staging service
  9. I configured both the Kentico instances in such a way that they both have the same code name.

Is there anything else that I am missing here? Any ideas please?

Thanks, Midhun.

Correct Answer

Trevor Fayas answered on March 24, 2016 18:31

Kentico bases the "site" on the URL.

So the question is, doe Kentico recognize a website with the 'domain' of '' and ''?

What i would do is whatever the domain address for the sites are, add a host file to point the for that domain on the sibling box (ex. put a host file for on the server, and a host file entry for on the second server).

Tell me if that was the problem!

1 votesVote for this answer Unmark Correct answer

Recent Answers

Brenden Kehren answered on March 24, 2016 21:15

You most likely have the sites configured incorrectly. To get a proper test setup one server as the target and one as the source. For purposes of testing, do this:

  • Make the testing or source server.
    Go to Settings>Versioning & Synchronization>Staging and check Log content changes and Log object changes in the Client (source only) section. Uncheck all other options in that section.
  • Make the production or target server.
    Go to Settings>Versioning & Synchronization>Staging and uncheck all the options in the Client (source only) section. Then in the Staging service (target only) section, enable the staging service and enter your username and password, which will be used on the Source ( server.
  • Go back to the server and go to the Staging application. You should receive a notice at the top stating no servers are enabled. Click on the Server tab and add a new server. Use as the domain and enter the user and password you entered in the second bullet point on the target server.

What I'm guessing is you don't have the target server enabled and you might be trying to do bi-directional staging which ideally works when you have a single direction working properly. Also no need to setup a code name for a server, just configure as the documentation states to start with for single direction (dev -> live)

3 votesVote for this answer Mark as a Correct answer

MIdhun Sai Paluri answered on March 29, 2016 15:43

Thanks Trevor for your solution. Kentico needs the working URL with domain name instead of for the synchronization to work.

Thanks Brenden for the detailed steps. I did configure my sites as per your instructions initially.

One more important point to note here is that:

Synchronization will work only if the domain url of the site has the license. In my case, I had requested and got the license for first trial version but for the second trial site that I was running on another machine, did not have a license to run the So, -> synchronization was working but the vice versa is not working.

Thanks for your inputs.

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.