Jason Zander
07-23-2009, 05:32 PM
Issue: Installing a new server to replace an old server. The old server had been installed with anything before L4C 3.5a. The new server is using the newest full installer (currently L4C 3.5a full installer). The old clients will not be able to connect to the new server.
Cause: New installations of Liberty are installed with a Named Instance of SQL. Due to a change on Microsoft's SQL server, this is a requirement that was not in place with older versions. Also, a different password to the database is required.
Resolution: see steps below..
**Important**
Please read this thread in its entirety and make sure you or your technician understand this document.
Your old MS SQL Server name would show 'Server' vs 'Server\Liberty' (the \Liberty indicating the Named Instance).
An older, non instance of SQL:
<img src="http://resaleworld.com/videos/jason/2009-07-23_1722.png">
A newer, SQL with an instance of Liberty:
<img src="http://resaleworld.com/videos/jason/2009-07-23_1722_001.png">
In the 2 examples above, the non-instance SQL is an older installation while the other is a new install (3.5a full install).
The old clients will not be able to connect immediately to the new server. Two things need to be done to allow the old clients to connect.
The first is updating the DB Password. A utility has been created to update each client with the new strong password.
http://files.rswhost.com/utilities/reg_pwd_strong.EXE
You will need to download and run that on all clients to update the password. You will not need to run this on the server as it already has the new password.
The other thing needed is to point each client machine to the new server. This requires you to use the RWDBUtil program. You can find that at C:\RWD\RWDButil.exe
In my example, my client machine is pointing to the server called SONNYXPS. This was my old server that I am going to be replacing.
<img src="http://resaleworld.com/videos/jason/2009-07-23_1726.png">
Since I want to connect it to the new server, I will need to change the Server Name field to the new server. In this case, it is on my new machine called VMWINXPPRO. However, since this new machine has the instance name, I need to include that as well. So, my RWDBUtil program will now look as follows:
<img src="http://resaleworld.com/videos/jason/2009-07-23_1728.png">
Once you change the server name. Click Connect To Server, you will then need to select the Production Database Name and the Training Database Name. These by default will be RWD and RWD_Train respectively.
The old clients should now be able to connect to the new server. You will still need to map the network drive so that your emails and reports work, but that is covered in the normal networking guide (http://files.rswhost.com/docs/nwguide.pdf) and thus will not be included in this tutorial.
Cause: New installations of Liberty are installed with a Named Instance of SQL. Due to a change on Microsoft's SQL server, this is a requirement that was not in place with older versions. Also, a different password to the database is required.
Resolution: see steps below..
**Important**
Please read this thread in its entirety and make sure you or your technician understand this document.
Your old MS SQL Server name would show 'Server' vs 'Server\Liberty' (the \Liberty indicating the Named Instance).
An older, non instance of SQL:
<img src="http://resaleworld.com/videos/jason/2009-07-23_1722.png">
A newer, SQL with an instance of Liberty:
<img src="http://resaleworld.com/videos/jason/2009-07-23_1722_001.png">
In the 2 examples above, the non-instance SQL is an older installation while the other is a new install (3.5a full install).
The old clients will not be able to connect immediately to the new server. Two things need to be done to allow the old clients to connect.
The first is updating the DB Password. A utility has been created to update each client with the new strong password.
http://files.rswhost.com/utilities/reg_pwd_strong.EXE
You will need to download and run that on all clients to update the password. You will not need to run this on the server as it already has the new password.
The other thing needed is to point each client machine to the new server. This requires you to use the RWDBUtil program. You can find that at C:\RWD\RWDButil.exe
In my example, my client machine is pointing to the server called SONNYXPS. This was my old server that I am going to be replacing.
<img src="http://resaleworld.com/videos/jason/2009-07-23_1726.png">
Since I want to connect it to the new server, I will need to change the Server Name field to the new server. In this case, it is on my new machine called VMWINXPPRO. However, since this new machine has the instance name, I need to include that as well. So, my RWDBUtil program will now look as follows:
<img src="http://resaleworld.com/videos/jason/2009-07-23_1728.png">
Once you change the server name. Click Connect To Server, you will then need to select the Production Database Name and the Training Database Name. These by default will be RWD and RWD_Train respectively.
The old clients should now be able to connect to the new server. You will still need to map the network drive so that your emails and reports work, but that is covered in the normal networking guide (http://files.rswhost.com/docs/nwguide.pdf) and thus will not be included in this tutorial.