Could not find sever 'C:\Microsoft Press\ADO' in sys.server

**BillAndrews** · 11-02-2007, 03:57 AM

I'm trying to use the book "Microsoft - ADO.NET 2.0 Step by step".
The examples all use a database that is in the C:\Microsoft Press\...\ADOStepbyStep.mdf.
I have successfully open this file in SQLExpress. I can get to data in the tables etc...
BUT when I'm in Visual Studio 2005 I make an Attachment. -- test connection works.
BUT when I click on the tables node I get the following error and have no idea what to do with it.

Unspecified error
Could not find sever 'C:\Microsoft Press\ADO' in sys.server. Verify that the correct server name was
specified. If necessary, execute the stored procedure sp_addlinkedserver to add the server to sys.servers.
OK

**wisemx** · 11-02-2007, 04:28 AM

From within VS youshould use virtual paths for everything to work in the server that VS creates.

**BillAndrews** · 11-02-2007, 04:59 AM

example please

**wisemx** · 11-02-2007, 05:49 AM

Well...I just opened both eyes and read your original post, missed the fact you had the error opening nodes.
At that point within VS there are only two things I've seen causing this sort of error;
Firewalls or read-only MDF files.
I can't think of anything else that would cause this.

11-02-2007, 03:57 AM	#1
BillAndrews Join Date: Sep 2007 Posts: 6	Could not find sever 'C:\Microsoft Press\ADO' in sys.server I'm trying to use the book "Microsoft - ADO.NET 2.0 Step by step". The examples all use a database that is in the C:\Microsoft Press\...\ADOStepbyStep.mdf. I have successfully open this file in SQLExpress. I can get to data in the tables etc... BUT when I'm in Visual Studio 2005 I make an Attachment. -- test connection works. BUT when I click on the tables node I get the following error and have no idea what to do with it. Unspecified error Could not find sever 'C:\Microsoft Press\ADO' in sys.server. Verify that the correct server name was specified. If necessary, execute the stored procedure sp_addlinkedserver to add the server to sys.servers. OK

11-02-2007, 04:28 AM	#2
wisemx Join Date: Mar 2006 Location: Johnson City, TN. U.S.A. Posts: 4,385	From within VS youshould use virtual paths for everything to work in the server that VS creates. __________________ Technical Evangelist Contact me to... Request new Webcasts This is my asp.net Blog for DASP and Microsoft Then there's the Overload of my Daily I.T. News/Alerts on AllTop

11-02-2007, 05:49 AM	#4
wisemx Join Date: Mar 2006 Location: Johnson City, TN. U.S.A. Posts: 4,385	Well...I just opened both eyes and read your original post, missed the fact you had the error opening nodes. At that point within VS there are only two things I've seen causing this sort of error; Firewalls or read-only MDF files. I can't think of anything else that would cause this. __________________ Technical Evangelist Contact me to... Request new Webcasts This is my asp.net Blog for DASP and Microsoft Then there's the Overload of my Daily I.T. News/Alerts on AllTop

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

11-02-2007, 04:59 AM	#3
BillAndrews Join Date: Sep 2007 Posts: 6	example please