I am just starting out with Wise and have already run into a problem that seems to have me stumped.
We have installed SQL 2008, IIS, and Wise Professional on a Windows Vista workstation to allow it to act as the Wise Server. We then installed the client on an XP Workstation to allow it to act as the "clean" machine.

Whenever we open Wise on the client, it is not able to connect to SQL on the server.
Gives an Error 52.
Does anyone know what this means or what might be causing it?

Some troubleshooting details:
Can connect directly from the ODBC connections back to the server.
The computers are not in a domain, they are in a workgroup.
Have created the same user account\password on both systems.
Installation on client and "server" was flawless.
During client install, pointed to the server as laid out in the installations docs.
Installed the Network Client version, for the smallest footprint.
Firewalls are disabled on both systems.
Can telnet to and from each system.

As another point of order, I want to go ahead and put this out there:
I realize that this is not the best set up, and I realize that we can use VM. However, for our environment (famous last words) we have to show it working in the physical, workgroup environment before we can get approval to move forward with the virtual domain environment.

Thanks for any help you can offer.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Also, on Vista, UAC is turned off. In SQL, dual authentication is enabled - none of the NT user accounts or SQL accounts will allow the Wise client to connect to the Wise Server.
Answered 11/19/2009 by: cuttst
Senior Yellow Belt

Please log in to comment
1
C:\>net helpmsg 52
"You were not connected because a duplicate name exists on the network. If joining a domain, go to System in Control Panel to change the computer name and try again."

Hope that help
Answered 11/19/2009 by: AngelD
Red Belt

Please log in to comment
0
That is what we originally thought as well, but it is not the case. We are set up in a workgroup and there are no duplicate names on the network.
Answered 11/19/2009 by: cuttst
Senior Yellow Belt

Please log in to comment
0
Connection failed
SQL State '01000'
SQL Server error 52
[microsoft][ODBC SQL Server Driver][DBNETLIB]Connection Open
Connection failed
SQL State '08001
SQL Error 17
[microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.
Answered 11/19/2009 by: cuttst
Senior Yellow Belt

Please log in to comment
0
Played around with cliconfg a bit and no dice, did change the error to (see below) for a while, but I believe that is just becasue I was changing from named pipes to tcp\ip and back and forth. Still the same general problem was present.

Connection failed
SQL State '01000'
SQL Server error 10061
[microsoft][ODBC SQL Server Driver][DBNETLIB]Connection Open
Connection failed
SQL State '08001
SQL Error 17
[microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.

Any help anyone could offer would be great, after three days of research and nothing... I think it is strange that these errors don't bring up more info from the search engines.
Answered 11/19/2009 by: cuttst
Senior Yellow Belt

Please log in to comment
0
Anybody? a little help, please?
Answered 11/20/2009 by: cuttst
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity