Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / .NET SDK / December 2003

Tip: Looking for answers? Try searching our database.

SQL Server Does Not Exist

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Alphonse Giambrone - 02 Dec 2003 20:25 GMT
I am trying to run the samples from the SDK quickstart and get the error
'SQL Server does not exist...".
I have SQL Server 2000 Developer edition installed and am guessing the the
problem is because all of the samples are using "server=(local)\NetSDK" in
the connect string.
Is there any way to get this to run without changing all the connect strings
and rebuilding everything?

Signature

Alphonse Giambrone
Email: a-giam at customdatasolutions dot us

Michael Shao [MSFT] - 03 Dec 2003 03:00 GMT
Hi Alphonse,

Thanks for your post. Based on your description, this problem is mostly due
to using the wrong server name to connect to SQL Server. I would like you
to check the following points to find and use the correct server name.

Did you install the SQL Server on the local machine? If so, what is the
kind of the instance of SQL Server you want to connect, named instance or
default instance?
Generally, we use "(local)" (for the instance which is installed on the
local machine) or computer_name as the server name to connect to the
default instance. For named instance, we need to use
computer_name\instance_nameas the server name to connect.

To determine if you have the named instance on your computer, please
perform the following steps.
1. Start' Run' Type "services.msc"
2. In the services list pane, check and see if you have services like
MSSQL$<instance name>. If so, this service is the named instance. You need
to connect it using <computer name>\<instance name> as the server name
string.

Note: MSSQLSERVER is the default SQL Server service.

For more information regarding named instance and default instance, please
refer to the following article on SQL Server Books Online.
Topic: "Multiple Instances of SQL Server"

Please feel free to post in the group if this solves your problem or if you
would like further assistance.

Regards,   

Michael Shao
Microsoft Online Partner Support
Signature

Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Alphonse Giambrone - 03 Dec 2003 03:23 GMT
Thanks for the reply.

In services, I have "MSSQLServer", no $ and no other instance.
I have SqlServer 2000 Developer edition installed on the local machine.
I have used it with other samples, demos and code of my own referencing
'localmachine' in the connection string.
My problem is not in code that I have written, but in running the SDK
Quickstart samples.
I have looked at the code in the samples and it references a named instance
"server=(local)\NetSDK".
There are many files in the samples with the reference and I really don't
want to change and rebuild them all.
Isn't there some way around the problem like maybe somehow creating an
'alias' server name??
It does not make sense to me that the creators of the SDK would require a
specific named instance of SQL Server to be installed.

Signature

Alphonse Giambrone
Email: a-giam at customdatasolutions dot us

> Hi Alphonse,
>
[quoted text clipped - 33 lines]
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
Michael Shao [MSFT] - 03 Dec 2003 06:32 GMT
Hi Alphonse,

Thanks for your response. Please try to perform the following steps, which
should meet your requirements.

1. Start'All programs ' Microsoft SQL Server ' Client Network Utility.
2. Choose Alias Tab ' Press Add button.
3. Select TCP/IP in the Network libraries option group
4. Type "(local)\NetSDK" (not including quotation marks) in the Server
alias box.
5. Type "(local)" (not including quotation marks) in the Server name box.
6. Then Press OK to finish the configuration.

After using the configuration, you can use "(local)\NetSDK" as the server
name to connect to your local SQL Server instance. It works on my computer.

Please feel free to post in the group if this solves your problem or if you
would like further assistance.

Regards,   

Michael Shao
Microsoft Online Partner Support
Signature

Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Alphonse Giambrone - 03 Dec 2003 13:15 GMT
That did it!
Thank you, I knew there had to be a simple solution.

Signature

Alphonse Giambrone
Email: a-giam at customdatasolutions dot us

> Hi Alphonse,
>
[quoted text clipped - 21 lines]
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.