Viewing 7 posts - 1 through 7 (of 7 total)
It looks like the problem is solved with this. The program works fine on a fresh install of Windows. On the 2nd computer having the issues, the tech tried reinstalling...
May 7, 2008 at 10:05 am
Yep, I have verified that there is no firewall on the server or workstation that would be blocking this.
Yesterday the tech had started putting a new hard drive on one...
May 7, 2008 at 5:52 am
To update on the situation here, I was able to get these workstations to connect with TCP/IP. I was being dumb and had it connecting to servername\instance instead of the...
May 5, 2008 at 3:08 pm
Provider=SQLOLEDB.1;User ID=User;Password=SomePass;Data Source=ServerName\Instance,6006;Initial Catalog=ourdb;MultipleActiveResultSets=True
Provider=SQLOLEDB.1;User ID=User;Password=SomePass;Data Source=ServerName\Instance,6006;Initial Catalog=ourdb;Network Library=DBMSSOCN;MultipleActiveResultSets=True
We've tried both of these. We've also substituted the server name with IP, and have tried different ports.
When we try the connection string...
May 2, 2008 at 7:00 am
Thanks for the reply. We have tried using the IP instead of computer name in the Data Source part of the connection string. Is there another area that'd be useful?
I...
May 2, 2008 at 6:34 am
Adam Haines (12/14/2007)
Then see if you can get to it. You...
December 18, 2007 at 9:23 am
Thanks for the reply. Actually I will have to try this again tomorrow. I recently did a full backup of all the databases, and it seems like whenever I do...
December 14, 2007 at 11:08 am
Viewing 7 posts - 1 through 7 (of 7 total)