Just want to confirm that this solution is what worked for us. We had our IT turn off the firewall on the server that is hosting our new SQL instance, and vi-oh-lay, the tool ran just fine. We narrowed it down to this as the probable source of the error by attempting to connect to the new SQL instance using Management Studio on a local machine (i.e. not on/within the server itself), and the attempt failed, so that more or less confirmed that "access" to the server was limited. Anyhow, thanks for the tip to help us narrow it down!