How to connect to the UAT databases using Siteore Rocks

Posted on

This post won’t explain how to install Sitecore rocks and connect to local machine. Please see John’s blog post in depth first for more details: https://community.sitecore.net/technical_blogs/b/sitecorejohn_blog/posts/sitecore-rocks-connections

The intent of this post is to give guidance on how to connect to the UAT or any environments using Sitecore Rocks. Although it may be a very old information, I sometimes forgot the steps to do it hence I created this post.

Prerequisite: Ensure that you ping the CM server.

To connect:

    1. Open the Sitecore Rocks in Visual Studio Professional, Ultimate or Enterprise.
    2. Create a connection, hostname: <CM URL> and the SC Admin Username and Password.
    3. Click Test, if the “Do you want to update server components” prompted you, click Yes.

  1. Click Update button, click OK.
  2. Put your files in the Desktop, and you’ll get 2 folders with Sitecore rocks files inside.

  1. Drop the files in your UAT/PROD CM servers
    1. \bin\Sitecore.Rocks.Server.dll
    2. \sitecore\shell\WebService\Browse.aspx
    3. \sitecore\shell\WebService\Service2.asmx
      1. Hard Rock Web Service – Service2.asmx – Has more features that Good Old Web Service like XPath Analyzer.
      2. Good Old Web Service – Service.asmx
    4. \sitecore\shell\WebService\Sitecore.Rocks.Validation.ashx
  2. Once the files were dropped, from your favorite browser, acess this URL http://<CM_URL>/sitecore/shell/WebService/Service2.asmx
  3. You should see a page like this.

  1. If instead you see a ‘Document not found’, in IIS ensure that the /sitecore/shell/WebService folder Anonymous Authentication status is Enabled.


  1. Go back to your Visual Studio and try to establish a connection to your UAT/PROD CM servers again.
  2. At this point, you should be able to connect to the core, master and web database of your UAT/PROD CM servers.

Try it and let me know if it works for you.




Simple way to check UAT connection to Production database server

Posted on Updated on

Today, I had a chance to talk with our Senior Solution Architect via Skype about checking the connection between UAT environment and Production database server.

The goal is just to check if it’s working, as we’re planning to create a mimic of Production CM and CD in the UAT environment using the production database server

Note that this concept is also applicable to the rest of the environments,

  1. SIT > UAT
  2. UAT > SIT
  3. SIT > PROD
  4. PROD > SIT
  5. Others

A very high-level representational diagram:

UAT connecting to Production database server diagram.png
Two-way connection

So, to check, Open the command prompt and start typing the below command.



telnet 1433

Important note: 1433 is the default TCP port of the SQL Server default instance. This is the common port allowed through the firewall. It applies to routine connections to the default installation of the Database Engine, or named instance that is the only instance running on the computer. More about configuring the Windows Firewall to Allow SQL server access here.

You would be able to see this window if successful connection.


For failed connection, you would encountered a Connection failed message.


Happy Sitecore’ing!

How to connect to two (2) sitecore instances from virtual machine / rdp simultaneously

Posted on Updated on

In this post, I would tackle the procedure on how to establish a connection from a virtual machine a.k.a RDP on your local machine.

Important note: This is for Development / System Integration (SIT) environment only.

The two (2) things:

  1. Configure to expose the two (2) SC instances to your network.
    1. Assumption: You’re connected on the same network.
  2. Connect from your local machine.
    1. Assumption: You’re connected to LAN. 🙂

The why? 

1. Easy to access

2. Less stress/processes on the virtual machine.

Let’s imagine you’re working with other 5 developers, and everyone are trying to connect to it. All of you may – for sure – experience the so-called ‘slowness’.

3. Easy to configure

The scenario:

Say you’re working on an upgrade, and you want to access both SC instances simultaneously . This time, not inside a virtual machine because your team should also connect to it and should be composed to the Project Manager, QA, FE and your boss. Amazing! 🙂

The variables:

Sitecore Instance 1: local.sitecore.com (eg. v. 7.2)

Sitecore Instance 2: upgraded.sitecore.net (eg. v.8.1 Update-3)


1.  Configure your two (2) SC instances from the virtual machine

In IIS, for local.sitecore.com, leave the Host Name empty, Port to 80 – default and IP Address to All Unassigned.

local.sitecore.com IIS bindings

In IIS, for upgrade.sitecore.com,

upgrade.sitecore.com:80 * : The binding when accessing the site inside RDP

upgrade.sitecore.com:80 : The binding when accessing the site outside RDP (This is what we want)

upgrade.sitecore.com:443 : The binding when accessing the site secured outside RDP (https)

More about creating self-assigned certificate here.

upgrade.sitecore.com IIS bindings

For hackers out there, FYI, the IP address is fake.

hacker everywhere

Leave as is. This is the default value of the SC instances upon installation.

File location : C:\Windows\System32\drivers\etc\host


2.  Connect from your local machine

Update your host file.

File location : C:\Windows\System32\drivers\etc\host


Note: For some cases, you need to put the website in your proxy settings, but for this case we don’t need to.

At this point, you would be able to access you site from your favorite browser in your local machine. What you only need to do is, just type the local.sitecore.com OR upgrade.sitecore.com in your browser.