New "Client" PC Installation Issues

[Support Team]

Issue: Server name on server shows 'Server'. Client PC is trying to connect to <blank>\Liberty (where <blank> would be your server's name.

Cause: New installations of Liberty attempt to connect to a Named Instance of SQL. Old installations do NOT have a Named Instance though. Also, old installations utilize a different password to connect to the database. New installations will put a new (and ultimately, "wrong") password in the Registry.

Resolution: see below...

IMPORTANT!!!

IF your server actually says 'Server\Liberty', then you just need to enter Server\Liberty (where "Server" = your server's name) into the database settings window. You will then be connected to your server and can disregard this article.

Before installing Liberty on a new client PC - one that will connect to your existing Liberty server - please read this thread. As outlined in the My Resaleworld FAQ entry, you won't be able to connect a new client to an existing server IF the following conditions are true:

- Your MS SQL Server Name shows 'Server' vs. 'Server\Liberty'

<img src="http://resaleworld.com/videos/dean/2009-07-17_1301.png"/>

New, "Full Installers" for Liberty - versions 3.5a and above - will install what is called a "Named Instance" for MS SQL Server. This leads to 2 issues:

1. At the end of the Client install, the Database Settings window will appear and it will be prompting you for your server's name\Liberty...

<img src="http://resaleworld.com/videos/dean/2009-07-17_1303.png"/>

You DO NOT want to enter 'Server\Liberty' here though. You will need to enter the Server Name your SQL Server Service Manager shows, on your main server. e.g. in my example above, my Server name is just 'Dean'.

2. Even if you DO enter the correct server name, there is one last issue - the password our new installers inserts into the Registry on your Client PCs, isn't the same password that your server is using. This is VERY EASY to fix though! I've made a patch for this and it can be downloaded here...

http://files.rswhost.com/utilities/reg_pwd.EXE

***If your systems are working fine or if you are NOT experiencing this EXACT issue, do not install this patch!!!***

To properly install a Client installation of Liberty on a network that shows 'Server' name only AND you are using a new download/CD with version 3.5a on it, this is how you would install and connect your new Client PC:

1. Install a "Client" version of Liberty
2. At the end of the installation, when the Database Settings Window appears, cancel out of it.
3. Download and install the "reg_pwd" patch above - ONLY TO YOUR NEW CLIENT PC, NOT TO YOUR SERVER!!!
4. Re-run the Database Settings utility via My Computer > Local Disk C: > RWD > RWDBUtil.exe.

You will now be able to successfully connect your Client PC to your Liberty Server. You'll know you're connected when you hit "Connect To Server" and see the little drop-downs beneath become available. Click the drop-down under "Production Database" and select 'RWD'. For the "Training Database," select 'RWD_Train'.

Don't forget to read our Network Guide (http://files.rswhost.com/docs/nwguide.pdf) so you can properly map a Network Drive! Without this, you won't be able to run reports!

IF your server actually says 'Server\Liberty', then you just need to enter Server\Liberty (where "Server" = your server's name) into the database settings window.

[downtownconsign]

I did what was suggested and still receiving the following error:
Unable to connect to server
(DNETLIB) Connection open (connect()). SQl Server does not exit or access denied.
Please advice.

[Support Team]

Could you verify the following for us?

- On your server, what does your MS SQL Server show for its "Server" name?

Start > Run > sqlmangr launches the following...

<img src="http://resaleworld.com/videos/dean/2009-07-21_1045.png"/>

- On your server, what does the DB Password key in your Windows Registry Editor show?

Start > Run > regedit > HKEY_LOCAL_MACHINE\SOFTWARE\ResaleWorld.com\RWD\Da tabase

<img src="http://resaleworld.com/videos/dean/2009-07-21_1047.png"/>
<img src="http://resaleworld.com/videos/dean/2009-07-21_1048.png"/>
<img src="http://resaleworld.com/videos/dean/2009-07-21_1048_001.png"/>
<img src="http://resaleworld.com/videos/dean/2009-07-21_1049.png"/>

<img src="http://resaleworld.com/videos/dean/2009-07-21_1049_001.png"/>

- On your new client (workstation) computer, what are you entering for the "Server Name"?
- On your new client (workstation) computer, what does ITS DBPassword key show via the Windows Registry Editor? (utilize the screen shots above to get to the DBPassword key on your client PC).

Keep us posted!

[downtownconsign]

The MS SQl Server name shown 'DC\Liberty'
The DB password key from regedit is
5349821EB5669ABFA45C53B2E136A66C37271DBD0BC644C9

Thanks.
David

[downtownconsign]

Any update...
The latest error message I get is:
"Unable to connect to server (dbnetlib) connection open(connect()). Specified SQL server not found"
Thanks.

[Support Team]

This error is basically saying, the workstation can't get through to the MS SQL Server running on the server computer.

Just so we can verify each side of the network here, you posted...

The MS SQl Server name shown 'DC\Liberty'
The DB password key from regedit is
5349821EB5669ABFA45C53B2E136A66C37271DBD0BC644C9

Is this true on the new workstation PC as well? Let us know what you're seeing on the new workstation, in regard to its Registry settings.

In addition to verifying the above, some basic network troubleshooting must take place:

- Are you able to view your server, from your workstation, via UNC (Universal Naming Convention)? e.g. Start > Run \\server

<img src="http://resaleworld.com/videos/dean/2009-07-27_1021.png"/>

- Are you able to PING your server? e.g. Start > Run > cmd > type ping servername and then hit Enter

<img src="http://resaleworld.com/videos/dean/2009-07-27_1019.png"/>

Let us know the results of the above!

[downtownconsign]

Problem still persist - receiving unable to connect to server(dbnetlib) connection open(connect()). Specified SQl server not found"

On the workstation the value of DB password was not the same (start with 6xxxx..) and I changed it to match with the server and also the servername.

I was able to see the server via UNC, it dropped me right into RWD folder on the server ( I checked and I have full access fron the workstation).

There is no problem with pinging the server I received the reply.

Thanks.
David

[JARREDS]

Are you running as an ADMINISTRATOR?

Sure the MSDE Engine is Started?

[Support Team]

The workstation showed the 6xxxxx password? I think we might be a little backwards here, which is what I was worried about. This stuff can get hairy if even one detail is missed

To review:

- Workstation showed 6xxxxx, which differed from the server's. This means, the server is a 'new' server which had the 5xxxxx password. This also means, the server is a named instance - i.e. SERVER\Liberty.

The workstation will never connect unless it A) uses the settings the server was configured with and B) it is pointed to the right "name".

Before any further changes are made, we need answers to the following:

- What does your MS SQL Server show for its Server name? This was something we didn't receive a response to from the 07-21-2009 10:47 AM post.

Let us know this and we'll go from here. I think something is being overlooked...

[Support Team]

Are you running as an ADMINISTRATOR?

I just wanted to make sure I covered this as well - you do not need to be running as administrator to access MS SQL Server or to utilize Liberty. Commonly, many create/manage users via User Accounts in Control Panel...

<img src="http://resaleworld.com/videos/dean/2009-07-29_1021.png"/>

This is not where one would want to create/manage accounts, as there are only two choices:

<img src="http://resaleworld.com/videos/dean/2009-07-29_1022.png"/>

Users should be created/managed via Local Users and Groups...

<img src="http://resaleworld.com/videos/dean/2009-07-29_1023.png"/>

This provides true control over Users and Groups, which is something one needs if they want to have a user that runs Liberty, yet isn't an Administrator. I created an article on creating users and groups + assigning the appropriate Permissions to run Liberty...

http://forums.resaleworld.com/showthread.php?t=2753

I have a feeling that downtownconsign has a MS SQL Server installation that shows SERVER\Liberty, yet SERVER is the name being utilized via RWDBUtil.exe.

There is a very short list of things that can be "wrong" here:

- The Client PC is passing the wrong password through to the server
- The Client PC is passing the wrong MS SQL Server name through to the server

Other than that, security products could be at play - e.g. the Windows Firewall, etc.

[downtownconsign]

What does your MS SQL Server show for its Server name? This was something we didn't receive a response to from the 07-21-2009 10:47 AM post >>>> It is DC\Liberty

I am running Administartor on both PC and I made the Userid and pswd the same on the server and workstation.

I have the window firewall turnoff and also Mc Afee.

From netstat it shown the workstation local address connection is established with the server (DC).

I am using 2Wire dsl/router to connect peer to peer (between server to workstation).

I am getting desperate to get my client to work...

Thanks.
David

[downtownconsign]

Okay, I got it to work.
From another forum I read " Client Install Question". I used CLICONFG utility to create an alias for the server name and also I checked that both TCPIP ports ( Server and workstation) are the same which is port 1433. Once, that is done...I was able to establish the connection from the workstation to the server.

[Support Team]

If the ports were set to anything other than 1433 (the default port for MS SQL Server), this means someone or something changed that setting. Older versions of MSDE (e.g. SP2 and below) had vulnerabilities resolved in SP3a and above. Security applications can modify this setting - even Windows Hotfixes too.

Glad to see everything is up and running now!

[susansselection]

I have had the same problems. I have tried the CLICONFG and still no connection. I have hit a brick wall.

[Angel Vazquez]

If your still having a problem with connecting a client PC, please check the following as well.

1. Make sure your Windows Firewall is disabled on both the server and client PC.
From your dekstop click on the Start menu > Control Panel > Windows Firewall.

<img src="http://resaleworld.com/videos/angel/MB_Images/2009-10-08_1442.png">

2. Also check for any Anti-virus security that may be enabled. Some security programs may contain a built-in personal firewall, system guard, or real-time protection. These can sometimes play a role in preventing client pc's from connecting a SQL database server. Disable any personal firewall ot system guard offered by your Anti-virus security to test. If you find your security program is the culprit, we recommend contacting the software vendor for assistance with adding programs to the exception list. You should also be able to find information on how to do this yourself within the Anti-virus software help section.