|
|
Posted by Ted on 10/01/03 11:56
Erland Sommarskog wrote:
> Ted (r.ted.byers@rogers.com) writes:
> > Can SQL Express be told to use a default instance? If so, how?
>
> Yes. When you install SQL Express you get a screen where you can choose
> the name of your instance and also select a default instance. If memory
> serves the Express install has a "Show advanced install options" or
> somesuch. You may have select that to get that screen.
>
OK I am running a test of this, and to do so, I created a named
instance. This is on my own LAN, so we're dealing with a peer to peer
WXP LAN, and the developer's edition of SQL Server 2005. With local
access, everything works fine, with mixed authentication. But the
following shows what happens when I try remote access.
===========session start================
C:\FVA\Code>sqlcmd -S RNDWORKSTATION\QAENV -U myuid -P mypwd
HResult 0xFFFFFFFF, Level 16, State 1
SQL Network Interfaces: Error Locating Server/Instance Specified
[xFFFFFFFF].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred
while establishing a connection to the server. When connecting to SQL
Server 2005, this failure may be caused by the fact that under the
default settings SQL Server does not allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
C:\FVA\Code>sqlcmd -S RNDWORKSTATION -U myuid -P mypwd
1> exit
C:\FVA\Code>
===============session end===============
As you can see, remote access to the default instance works fine, but I
get an error when I try to access the named instance.
I have used the SQL Server Management Studio to verify that mixed
authentication, and remote connections, are enabled on the named
instance (and the uid was create in the same way, using the same pwd,
on both instances).
I assume I missed something, but what, and where do I look in SQL
Server 2005 Management Studio to find the settings I need to change to
fix this?
Thanks.
Ted
Navigation:
[Reply to this message]
|