Blog

When moving content from one environment to another, you need to ensure that every item is successfully copied. If there's a problem, you need to be aware of it. Razl logs all the steps it completes and returns an error when there's an issue with the synchronization. The logs come in handy when you are looking for data from past operations or looking for additional information as to why an operation failed. 

If you haven't used the logging capabilities of Razl, or you don't know where the log files are saved, this is configured in Razl's settings button: 







If you're executing scripts, another way of saving logs is to pipe the output of the console to a text file and save the log there. 

Razl logs everything in its log files. If all works properly, you'll only see INFO entries in the log files. Most of the information entries are self-explanatory.  

Here are some examples:  

INFO  Razl Starting 

INFO  Settings saved 

INFO  Connected to sitecore:  Name: <connection name>, Url: <Url of the Sitecore instance>, Path: <path to the webroot>, Package: False 

INFO  Connection: <connection name> - Added 

INFO  CopyItem Started Id: <item id>, Path: <path in the Sitecore tree>, From: <connection name>, To: <connection name> 

INFO  CopyItem Finish Id: <item id>, Path: <path in the Sitecore tree>, From: <connection name>, To: <connection name> 

INFO  Starting Razl Script Mode 

INFO  Read XML connection <connection name> 

INFO  Read XML command 'CopyItem' 

INFO  Installed connector for connection <connection name> 

INFO  Starting Razl Script Mode Finished 

In case of an error, Razl will stop the process, and an error message will pop-up. Usually, the errors are logged with much more detail there.  

Below are some common errors seen when supporting Razl: 

CallService Protocol Exceptions and CallService Exceptions 

These exceptions are followed by a long stack trace in the log files, which can usually point you to the problem. The exception indicates that Sitecore threw an error when Razl tried to use the service. If a web page HTML follows the error, or the stack trace mentions any error codes, you should review the Sitecore logs, the IIS logs, and the Windows Event logs for additional information.  

Console error: Cannot find source parent 

Razl throws this error if there's an invalid item ID in the script or a corrupted item in the Sitecore tree. Again, you'll probably find additional information in the Sitecore logs, or you'll notice a problem when browsing this item.  

An error occurred when checking for a license @ <date and time>. The error message is: The activation was rejected by the server. 

Razl also logs information for problems occurring when communicating with the license server or the license key. If you see the above error, there's probably another installation of Razl using the same license key, or there's a problem with the key itself. In this case, please contact the Hedgehog support team.

The connector test failed. The reason is 'Can't install connector. The web root can't be found.' 

This error appears when the webroot location is not specified in the Razl connection settings. This can be fixed by opening the connection manager and entering the proper location for the connection you're trying to use. 



Learn more about the features of Razl 4.0 including the new Connection Manager window.