Monday, May 14, 2012 4:16 PM
OK - first let me start this off by saying this isn't my software so I'm not sure how it's coded.
And if it's in the 'wrong' forum, I'm sorry about that, too..
Last week a data conversion was attempted going from Pervaisive to Sql server 2008 R2 running on 2008 (64 bit) server. The database software was installed as was their tables. They (the idiot consultant) loaded the client software on the server and they could communicate and run fine. He said the connection is "OleDb" but I don't think he actually knows.
The problem was that when he installed a client on the same domain the client couldn't talk to the database. He never gave me an answer or an error, just, "it isn't working".. I asked him if he had turned on everything, enabled all protocols and he said yes. He thought it was problem with the firewall. The server's don't have firewalls on them, but the client does. We control the firewall thru a group policy. We tried to amend the policy but couldn't get it to work.
Mr. Genius's answer was to remove the machine from domain so he could get the firewall change in.
I thought this was strange, not to mention a security issue. Has anyone run into this issue on a Windows 7 client? All of our 2005 database apps are running fine on win 7 clients and I didn't have to change ANYTHING!
Monday, May 14, 2012 4:24 PM
Are there any errors in the SQL Server error log?
Does the application have an error log?
Is the 2008 instance a default or named instance?
Can you see any obviously named config files that have connection strings in them, or ODBC connections, etc?
SQL Server DBA
Please click "Propose As Answer" if a post solves your problem, or "Vote As Helpful" if a post has been useful to you