In SQL Server 2005, I renamed a database but it did not rename it in the
login default database. Since this is the default database for the sa
signon, I can't sign into the SQL Server. I am in a catch-22. I have only
one other login to the SQL Server and it also defaults to the same database
that apparently didn't get renamed :(.
Please help me get access to my SQL Server again,
TerryThis is a multi-part message in MIME format.
--030709040002030508020607
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
I answered this in microsoft.public.sqlserver.security.
--
*mike hodgson*
http://sqlnerd.blogspot.com
Terry wrote:
>In SQL Server 2005, I renamed a database but it did not rename it in the
>login default database. Since this is the default database for the sa
>signon, I can't sign into the SQL Server. I am in a catch-22. I have only
>one other login to the SQL Server and it also defaults to the same database
>that apparently didn't get renamed :(.
>Please help me get access to my SQL Server again,
>Terry
>
>
--030709040002030508020607
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>I answered this in microsoft.public.sqlserver.security.</tt><br>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2"><a href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Terry wrote:
<blockquote cite="mid600A72B6-BFBE-4475-BB1A-F6EACEED0CBC@.microsoft.com"
type="cite">
<pre wrap="">In SQL Server 2005, I renamed a database but it did not rename it in the
login default database. Since this is the default database for the sa
signon, I can't sign into the SQL Server. I am in a catch-22. I have only
one other login to the SQL Server and it also defaults to the same database
that apparently didn't get renamed :(.
Please help me get access to my SQL Server again,
Terry
</pre>
</blockquote>
</body>
</html>
--030709040002030508020607--
Showing posts with label default. Show all posts
Showing posts with label default. Show all posts
Tuesday, March 27, 2012
Can't get into sa account
In SQL Server 2005, I renamed a database but it did not rename it in the
login default database. Since this is the default database for the sa
signon, I can't sign into the SQL Server. I am in a catch-22. I have only
one other login to the SQL Server and it also defaults to the same database
that apparently didn't get renamed
.
Please help me get access to my SQL Server again,
Terry
I answered this in microsoft.public.sqlserver.security.
*mike hodgson*
http://sqlnerd.blogspot.com
Terry wrote:
>In SQL Server 2005, I renamed a database but it did not rename it in the
>login default database. Since this is the default database for the sa
>signon, I can't sign into the SQL Server. I am in a catch-22. I have only
>one other login to the SQL Server and it also defaults to the same database
>that apparently didn't get renamed.
>Please help me get access to my SQL Server again,
>Terry
>
>
sql
login default database. Since this is the default database for the sa
signon, I can't sign into the SQL Server. I am in a catch-22. I have only
one other login to the SQL Server and it also defaults to the same database
that apparently didn't get renamed
.Please help me get access to my SQL Server again,
Terry
I answered this in microsoft.public.sqlserver.security.
*mike hodgson*
http://sqlnerd.blogspot.com
Terry wrote:
>In SQL Server 2005, I renamed a database but it did not rename it in the
>login default database. Since this is the default database for the sa
>signon, I can't sign into the SQL Server. I am in a catch-22. I have only
>one other login to the SQL Server and it also defaults to the same database
>that apparently didn't get renamed
.>Please help me get access to my SQL Server again,
>Terry
>
>
sql
Can't get into sa account
In SQL Server 2005, I renamed a database but it did not rename it in the
login default database. Since this is the default database for the sa
signon, I can't sign into the SQL Server. I am in a catch-22. I have only
one other login to the SQL Server and it also defaults to the same database
that apparently didn't get renamed.
Please help me get access to my SQL Server again,
TerryI answered this in microsoft.public.sqlserver.security.
*mike hodgson*
http://sqlnerd.blogspot.com
Terry wrote:
>In SQL Server 2005, I renamed a database but it did not rename it in the
>login default database. Since this is the default database for the sa
>signon, I can't sign into the SQL Server. I am in a catch-22. I have only
>one other login to the SQL Server and it also defaults to the same database
>that apparently didn't get renamed.
>Please help me get access to my SQL Server again,
>Terry
>
>
login default database. Since this is the default database for the sa
signon, I can't sign into the SQL Server. I am in a catch-22. I have only
one other login to the SQL Server and it also defaults to the same database
that apparently didn't get renamed
.Please help me get access to my SQL Server again,
TerryI answered this in microsoft.public.sqlserver.security.
*mike hodgson*
http://sqlnerd.blogspot.com
Terry wrote:
>In SQL Server 2005, I renamed a database but it did not rename it in the
>login default database. Since this is the default database for the sa
>signon, I can't sign into the SQL Server. I am in a catch-22. I have only
>one other login to the SQL Server and it also defaults to the same database
>that apparently didn't get renamed
.>Please help me get access to my SQL Server again,
>Terry
>
>
Sunday, March 25, 2012
Cant find User Default database So, I can't Register my server
Occasionally, I disconnect a database. When I try to reconnect it, I get the
message that SQL "can't find the User default database". Typically, I rein
stall the SQL Server software. There must be a better way. Is there an OSQL
command I can use? How
can I recorver from this condition without riinstalling SQL Server?
Thanks, richardYou can run the OSQL command-line utility to specify an alternate database
context and execute sp_defaultdb to change the default database for a
login. For example:
OSQL -E -d master -Q"sp_defaultdb 'MyLogin', 'MyDatabase'"
Hope this helps.
Dan Guzman
SQL Server MVP
"Richard Muschamp" <dick@.custommicro.com> wrote in message
news:23D9DDF2-EE56-4B8B-8B03-264F006F0B35@.microsoft.com...
> Occasionally, I disconnect a database. When I try to reconnect it, I get
the message that SQL "can't find the User default database". Typically, I
reinstall the SQL Server software. There must be a better way. Is there an
OSQL command I can use? How can I recorver from this condition without
riinstalling SQL Server?
> Thanks, richard|||Hi,
This problem can come due to 2 reasons
1. You have assigned the login a default database and the login do not have
a user assocoated in the default database.
a. Login to Query Analyzer
b. use <dafault databasename>
c. sp_adduser <user name>
d. Assign the required role
2. Database which is given default to the login is dropped or not available.
a. Change the login to point to a different database, Execute the below
from command prompt
b. OSQL -USa -Ppassword -d master -Q"sp_defaultdb 'Login_name', 'New
database which is default'"
Thanks
Hari
MCDBA
"Richard Muschamp" <dick@.custommicro.com> wrote in message
news:23D9DDF2-EE56-4B8B-8B03-264F006F0B35@.microsoft.com...
> Occasionally, I disconnect a database. When I try to reconnect it, I get
the message that SQL "can't find the User default database". Typically, I
reinstall the SQL Server software. There must be a better way. Is there an
OSQL command I can use? How can I recorver from this condition without
riinstalling SQL Server?
> Thanks, richard
message that SQL "can't find the User default database". Typically, I rein
stall the SQL Server software. There must be a better way. Is there an OSQL
command I can use? How
can I recorver from this condition without riinstalling SQL Server?
Thanks, richardYou can run the OSQL command-line utility to specify an alternate database
context and execute sp_defaultdb to change the default database for a
login. For example:
OSQL -E -d master -Q"sp_defaultdb 'MyLogin', 'MyDatabase'"
Hope this helps.
Dan Guzman
SQL Server MVP
"Richard Muschamp" <dick@.custommicro.com> wrote in message
news:23D9DDF2-EE56-4B8B-8B03-264F006F0B35@.microsoft.com...
> Occasionally, I disconnect a database. When I try to reconnect it, I get
the message that SQL "can't find the User default database". Typically, I
reinstall the SQL Server software. There must be a better way. Is there an
OSQL command I can use? How can I recorver from this condition without
riinstalling SQL Server?
> Thanks, richard|||Hi,
This problem can come due to 2 reasons
1. You have assigned the login a default database and the login do not have
a user assocoated in the default database.
a. Login to Query Analyzer
b. use <dafault databasename>
c. sp_adduser <user name>
d. Assign the required role
2. Database which is given default to the login is dropped or not available.
a. Change the login to point to a different database, Execute the below
from command prompt
b. OSQL -USa -Ppassword -d master -Q"sp_defaultdb 'Login_name', 'New
database which is default'"
Thanks
Hari
MCDBA
"Richard Muschamp" <dick@.custommicro.com> wrote in message
news:23D9DDF2-EE56-4B8B-8B03-264F006F0B35@.microsoft.com...
> Occasionally, I disconnect a database. When I try to reconnect it, I get
the message that SQL "can't find the User default database". Typically, I
reinstall the SQL Server software. There must be a better way. Is there an
OSQL command I can use? How can I recorver from this condition without
riinstalling SQL Server?
> Thanks, richard
Tuesday, March 20, 2012
Can't drop constraint
Hello,
I am using SS7.
I have a table with a column "yn_LockOut" with a default set to 0. I tried
to delete the column and got the following:
'tblGuidelineResponseOwner' table
- Error modifying column properties for 'yn_LockOut'.
ODBC error: [Microsoft][ODBC SQL Server Driver][SQL
Server]'DF_tblGuideLineResponse_yn_LockOut' is not a constraint.
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not drop constraint.
See previous errors.
When I ran exec sp_helpconstraint 'tblGuidelineResponseOwner', I got:
constraint_type constraint_name
DEFAULT on column yn_LockOut DF_tblGuideLineResponse_yn_LockOut
I ran:
alter table tblGuidelineResponseOwner DROP CONSTRAINT
DF_tblGuideLineResponse_yn_LockOut
and got the error message:
'DF_tblGuideLineResponse_yn_LockOut' is not a constraint.
Server: Msg 3727, Level 16, State 1, Line 5
Could not drop constraint. See previous errors.
Any help with this would be appreciated.
--
Thanks in advance,
StevenSteven,
Check sp_unbindefault in BOL.
-Mark
This positing is as is
>--Original Message--
>Hello,
>I am using SS7.
>I have a table with a column "yn_LockOut" with a default
set to 0. I tried
>to delete the column and got the following:
>'tblGuidelineResponseOwner' table
>- Error modifying column properties for 'yn_LockOut'.
>ODBC error: [Microsoft][ODBC SQL Server Driver][SQL
>Server]'DF_tblGuideLineResponse_yn_LockOut' is not a
constraint.
>[Microsoft][ODBC SQL Server Driver][SQL Server]Could not
drop constraint.
>See previous errors.
>
>When I ran exec
sp_helpconstraint 'tblGuidelineResponseOwner', I got:
>constraint_type
constraint_name
>DEFAULT on column yn_LockOut
DF_tblGuideLineResponse_yn_LockOut
>
>I ran:
>alter table tblGuidelineResponseOwner DROP CONSTRAINT
>DF_tblGuideLineResponse_yn_LockOut
>and got the error message:
>'DF_tblGuideLineResponse_yn_LockOut' is not a constraint.
>Server: Msg 3727, Level 16, State 1, Line 5
>Could not drop constraint. See previous errors.
>Any help with this would be appreciated.
>--
>Thanks in advance,
>Steven
>
>.
>sql
I am using SS7.
I have a table with a column "yn_LockOut" with a default set to 0. I tried
to delete the column and got the following:
'tblGuidelineResponseOwner' table
- Error modifying column properties for 'yn_LockOut'.
ODBC error: [Microsoft][ODBC SQL Server Driver][SQL
Server]'DF_tblGuideLineResponse_yn_LockOut' is not a constraint.
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not drop constraint.
See previous errors.
When I ran exec sp_helpconstraint 'tblGuidelineResponseOwner', I got:
constraint_type constraint_name
DEFAULT on column yn_LockOut DF_tblGuideLineResponse_yn_LockOut
I ran:
alter table tblGuidelineResponseOwner DROP CONSTRAINT
DF_tblGuideLineResponse_yn_LockOut
and got the error message:
'DF_tblGuideLineResponse_yn_LockOut' is not a constraint.
Server: Msg 3727, Level 16, State 1, Line 5
Could not drop constraint. See previous errors.
Any help with this would be appreciated.
--
Thanks in advance,
StevenSteven,
Check sp_unbindefault in BOL.
-Mark
This positing is as is
>--Original Message--
>Hello,
>I am using SS7.
>I have a table with a column "yn_LockOut" with a default
set to 0. I tried
>to delete the column and got the following:
>'tblGuidelineResponseOwner' table
>- Error modifying column properties for 'yn_LockOut'.
>ODBC error: [Microsoft][ODBC SQL Server Driver][SQL
>Server]'DF_tblGuideLineResponse_yn_LockOut' is not a
constraint.
>[Microsoft][ODBC SQL Server Driver][SQL Server]Could not
drop constraint.
>See previous errors.
>
>When I ran exec
sp_helpconstraint 'tblGuidelineResponseOwner', I got:
>constraint_type
constraint_name
>DEFAULT on column yn_LockOut
DF_tblGuideLineResponse_yn_LockOut
>
>I ran:
>alter table tblGuidelineResponseOwner DROP CONSTRAINT
>DF_tblGuideLineResponse_yn_LockOut
>and got the error message:
>'DF_tblGuideLineResponse_yn_LockOut' is not a constraint.
>Server: Msg 3727, Level 16, State 1, Line 5
>Could not drop constraint. See previous errors.
>Any help with this would be appreciated.
>--
>Thanks in advance,
>Steven
>
>.
>sql
Thursday, March 8, 2012
Can't created a linked server on a named instance to default insta
I have been trying to create a linked server on a named instance to a defaul
t
instance using intergrated security. It seems to work fine from a default
instance to any other SQL instance, including a named instance, but any time
I create the linked server on the named instance a call to the linked server
fails with the error:
Msg 18452, Level 14, State 1, Line 1
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
All servers are running SQL Server 2000 and the only difference in the
installation besides the fact one is named, is that the named instance is SP
4
and all others are SP3.
From a default instance the following works fine:
sp_addlinkedserver 'ORDEV01'
ORDEV01.Master.dbo.sp_helpdb
and the following to a named instance works as well:
sp_addlinkedserver 'LOU\Master'
[LOU\Master].Master.dbo.sp_helpdb
But if I try to created a linked server on the name dinstance LOU\Master I
get the error:
Msg 18452, Level 14, State 1, Line 1
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
Thanks in advance for any help.Byron
Does the instance have Windows Authentication?
"Byron" <Byron@.discussions.microsoft.com> wrote in message
news:CB90A676-83FF-41CC-9C04-221920F998FF@.microsoft.com...
>I have been trying to create a linked server on a named instance to a
>default
> instance using intergrated security. It seems to work fine from a default
> instance to any other SQL instance, including a named instance, but any
> time
> I create the linked server on the named instance a call to the linked
> server
> fails with the error:
> Msg 18452, Level 14, State 1, Line 1
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection.
> All servers are running SQL Server 2000 and the only difference in the
> installation besides the fact one is named, is that the named instance is
> SP4
> and all others are SP3.
> From a default instance the following works fine:
> sp_addlinkedserver 'ORDEV01'
> ORDEV01.Master.dbo.sp_helpdb
> and the following to a named instance works as well:
> sp_addlinkedserver 'LOU\Master'
> [LOU\Master].Master.dbo.sp_helpdb
> But if I try to created a linked server on the name dinstance LOU\Master I
> get the error:
> Msg 18452, Level 14, State 1, Line 1
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection.
> Thanks in advance for any help.
t
instance using intergrated security. It seems to work fine from a default
instance to any other SQL instance, including a named instance, but any time
I create the linked server on the named instance a call to the linked server
fails with the error:
Msg 18452, Level 14, State 1, Line 1
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
All servers are running SQL Server 2000 and the only difference in the
installation besides the fact one is named, is that the named instance is SP
4
and all others are SP3.
From a default instance the following works fine:
sp_addlinkedserver 'ORDEV01'
ORDEV01.Master.dbo.sp_helpdb
and the following to a named instance works as well:
sp_addlinkedserver 'LOU\Master'
[LOU\Master].Master.dbo.sp_helpdb
But if I try to created a linked server on the name dinstance LOU\Master I
get the error:
Msg 18452, Level 14, State 1, Line 1
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
Thanks in advance for any help.Byron
Does the instance have Windows Authentication?
"Byron" <Byron@.discussions.microsoft.com> wrote in message
news:CB90A676-83FF-41CC-9C04-221920F998FF@.microsoft.com...
>I have been trying to create a linked server on a named instance to a
>default
> instance using intergrated security. It seems to work fine from a default
> instance to any other SQL instance, including a named instance, but any
> time
> I create the linked server on the named instance a call to the linked
> server
> fails with the error:
> Msg 18452, Level 14, State 1, Line 1
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection.
> All servers are running SQL Server 2000 and the only difference in the
> installation besides the fact one is named, is that the named instance is
> SP4
> and all others are SP3.
> From a default instance the following works fine:
> sp_addlinkedserver 'ORDEV01'
> ORDEV01.Master.dbo.sp_helpdb
> and the following to a named instance works as well:
> sp_addlinkedserver 'LOU\Master'
> [LOU\Master].Master.dbo.sp_helpdb
> But if I try to created a linked server on the name dinstance LOU\Master I
> get the error:
> Msg 18452, Level 14, State 1, Line 1
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection.
> Thanks in advance for any help.
Sunday, February 19, 2012
Cant connect to SQL server 2000 instance from domain machines
Hi
We currently have installed sql2005 (installed first as default
instance) and sql 2000 with a named instance. When developing sites
and using connection strings, we can access the sql2000 db fine by
using SERVERNAME\INSTANCENAME.
However, if we try to connect via enterprise manager from any other
machine on the domain, we cannot seem to use SERVERNAME\INSTANCENAME
and the instance name alone wont work either.
How do we get round this as at present, we are having to log into the
database server to make any changes etc!!!
Novice here so excuse me if I have missed anything obvious!
Cheers
RajThe easiest workaround would be to connect to the instance using its IP
address followed by a comma and then the port number. You should not use just
hte instance name alone. The SQL Server instance name is not a newtwork name
and won't get resolved to an IP/port number.
Can you connect to the default instance (SQL2005) from a machine where you
can't connect to the SQL2000 instance using ServerName\Instance?
Linchi
"karwalr@.hotmail.com" wrote:
> Hi
> We currently have installed sql2005 (installed first as default
> instance) and sql 2000 with a named instance. When developing sites
> and using connection strings, we can access the sql2000 db fine by
> using SERVERNAME\INSTANCENAME.
> However, if we try to connect via enterprise manager from any other
> machine on the domain, we cannot seem to use SERVERNAME\INSTANCENAME
> and the instance name alone wont work either.
> How do we get round this as at present, we are having to log into the
> database server to make any changes etc!!!
> Novice here so excuse me if I have missed anything obvious!
> Cheers
> Raj
>|||Managed to sort it. I set it up on my client machine Client Network
Alias to map to the server and the port as suggested. Found the
documentation at Microsoft..
http://support.microsoft.com/kb/265808/en-us
Many thanks!
We currently have installed sql2005 (installed first as default
instance) and sql 2000 with a named instance. When developing sites
and using connection strings, we can access the sql2000 db fine by
using SERVERNAME\INSTANCENAME.
However, if we try to connect via enterprise manager from any other
machine on the domain, we cannot seem to use SERVERNAME\INSTANCENAME
and the instance name alone wont work either.
How do we get round this as at present, we are having to log into the
database server to make any changes etc!!!
Novice here so excuse me if I have missed anything obvious!
Cheers
RajThe easiest workaround would be to connect to the instance using its IP
address followed by a comma and then the port number. You should not use just
hte instance name alone. The SQL Server instance name is not a newtwork name
and won't get resolved to an IP/port number.
Can you connect to the default instance (SQL2005) from a machine where you
can't connect to the SQL2000 instance using ServerName\Instance?
Linchi
"karwalr@.hotmail.com" wrote:
> Hi
> We currently have installed sql2005 (installed first as default
> instance) and sql 2000 with a named instance. When developing sites
> and using connection strings, we can access the sql2000 db fine by
> using SERVERNAME\INSTANCENAME.
> However, if we try to connect via enterprise manager from any other
> machine on the domain, we cannot seem to use SERVERNAME\INSTANCENAME
> and the instance name alone wont work either.
> How do we get round this as at present, we are having to log into the
> database server to make any changes etc!!!
> Novice here so excuse me if I have missed anything obvious!
> Cheers
> Raj
>|||Managed to sort it. I set it up on my client machine Client Network
Alias to map to the server and the port as suggested. Found the
documentation at Microsoft..
http://support.microsoft.com/kb/265808/en-us
Many thanks!
Tuesday, February 14, 2012
Can't Connect to Multiple SQL Instances over the Internet with SQL Browser Service
I recently setup mutliple instances of SQL Server Express at my office. I have 1 default instance, and two named instances. I can connect to the named instance of the default port of 1433 with Microsoft SQL Management Studio Express, however the other instances on dynamic TCP ports can not be accessed by the instance name over the internet. I have to specify the dynamic TCP port in this form: xxx.uconn.edu/SQLTEST, Port number. My current thinking is that the SQL Browser service should tell Management Studio Express what dynamic port number each SQL instance is listening to. Any ideas?
hi,
CTJohn23 wrote:
I recently setup mutliple instances of SQL Server Express at my office. I have 1 default instance, and two named instances. I can connect to the named instance of the default port of 1433 with Microsoft SQL Management Studio Express,
TCP/IP 1433 is usually reserved for the default instance...
however the other instances on dynamic TCP ports can not be accessed by the instance name over the internet. I have to specify the dynamic TCP port in this form: xxx.uconn.edu/SQLTEST, Port number. My current thinking is that the SQL Browser service should tell Management Studio Express what dynamic port number each SQL instance is listening to. Any ideas?
the SQLBrowser can not "work" over the internet in that way... all enlistment for instance presence are available via an UDP broadcast call on the local area, when no firewall action is involved...
don't know if the "tool" still relies on SQLBrowseConnect ODBC function, like SQL Server 7.0 and 2000 ListAvailableServer used it, an ODBC function (SQLBrowseConnect()) provided by ODBC libraries installed by Mdac;
this is a mechanism working in broadcast calls, which result never are conclusive and consistent, becouse results are influenced of various servers's answer states, answer time, etc.
Until Mdac 2.5, SQLBrowseConnect function works based on a NetBIOS broadcast, on which SQL Servers respond (Default protocol for SQL Server 7.0), while in SQL Server 2000 the rules changed, because the default client protocol changed to TCP/IP and now a UDP broadcast is used, beside a NetBIOS broadcast, listening on port 1434:
which is using a UDP broadcast on port 1434, if instance do not listen or not respond on time they will not be part of the enumeration.
Some basic rules for 7.0 are:
- SQL Servers have to be running on Windows NT or Windows 2000 and have to listen on Named Pipes, that is why in 7.0 Windows 9x SQL Servers will never show up, because they do not listen on Named Pipes.
- The SQL Server has to be running in order to respond on the broadcast. There is a gray window of 15 minutes after shutdown, where a browse master in the domain may respond on the broadcast and answer.
- If you have routers in your network, that do not pass on NetBIOS broadcasts, this might limit your scope of the broadcast.
- Only servers within the same NT domain (or trust) will get enumerated.
In SQL Server 2000 using MDAC 2.6 this changes a little, because now the default protocol has been changed to be TCP/IP sockets and instead of a NetBIOS broadcast, they use a TCP UDP to detect the servers. The same logic still applies roughly.
- SQL Server that are running
- SQL Server that listening on TCP/IP
- Running on Windows NT or Windows 2000 or Windows 9x
- If you use routers and these are configured not to pass UDP broadcasts, only machines within the same subnet show up.
Upgrading to Service Pack 2 of SQL Server 2000 is required in order to have .ListAvailableServer method to work properly, becouse precding release of Sql-DMO Components of Sql Server 2000 present a bug in this area.
Courtesy of Mr. Gert E.R. Drapers
further Information at
http://sqldev.net/misc.htm
The Service Pack 3a introduced some new amenity in order to prevent MSDE 2000 to be hit by Internet worms like Slammer and Saphire virus and to increase security, so that Microsoft decided to default for disabling SuperSockets Network Protocols on new MSDE 2000 installation.
Instances of SQL Server 2000 SP3a or MSDE 2000 SP3a will stop listening on UDP port 1434 when they are configured to not listen on any network protocols. This will stop enlisting these servers.
Sunday, February 12, 2012
Can't connect to MSDE
I've got two machines: 1) SBS 2003 Server, and 2) WinXP Pro.
SQL Server 2000 is installed on the server box, as well as MSDE for the default
SharePoint and SbsMonitoring databases (SBS setup created those). The
workstation is running MSDE.
The problem is that I can only connect to the workstation's MSDE from the
workstation. EM on the server can see the MSDE instance (the worksation's
machine name appears in the Add SQL Server Registration dialog box), but that's
as far as it can get. When I try to add the instance under a new registration, I
get 'access denied or server doesn't exist' (paraphrased).
I also can't connect via EM to the workstation's MSDE from within a Win98
VirtualPC instance running on the workstation, although I can connect to the
server's instances (both SQL Server and MSDE instances) from within that
instance.
I've compared the property sheets of all the instances to which I can connect
from WinXP, and everything seems to be the same. Nothing shows up in my ISA
logs, so I don't think packets are being blocked. Just in case I created a
temporary packet filter allowing all packets from anywhere (risky, I know), but
it still didn't work. Still nothing in the logs.
Does anyone know what this might be?
TIA,
JeffBy default MSDE doesn't listen to any netlibs. On a regular SQL Server, you configure this using
"Server Network Utility". I'm not sure whether such comes with MSDE, but that would be the place to
start. The name of the exe is svrnetcn.exe
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Jeff Bowman" <write.to.me@.my.addess.com> wrote in message
news:%23Sv%23zABjFHA.3164@.TK2MSFTNGP15.phx.gbl...
> I've got two machines: 1) SBS 2003 Server, and 2) WinXP Pro.
> SQL Server 2000 is installed on the server box, as well as MSDE for the default SharePoint and
> SbsMonitoring databases (SBS setup created those). The workstation is running MSDE.
> The problem is that I can only connect to the workstation's MSDE from the workstation. EM on the
> server can see the MSDE instance (the worksation's machine name appears in the Add SQL Server
> Registration dialog box), but that's as far as it can get. When I try to add the instance under a
> new registration, I get 'access denied or server doesn't exist' (paraphrased).
> I also can't connect via EM to the workstation's MSDE from within a Win98 VirtualPC instance
> running on the workstation, although I can connect to the server's instances (both SQL Server and
> MSDE instances) from within that instance.
> I've compared the property sheets of all the instances to which I can connect from WinXP, and
> everything seems to be the same. Nothing shows up in my ISA logs, so I don't think packets are
> being blocked. Just in case I created a temporary packet filter allowing all packets from anywhere
> (risky, I know), but it still didn't work. Still nothing in the logs.
> Does anyone know what this might be?
> TIA,
> Jeff
>
>|||That did the trick, thanks for the tip! :-)
(BTW, Server Network Utility appears to be installed with Client Tools.)
Tibor Karaszi wrote:
> By default MSDE doesn't listen to any netlibs. On a regular SQL Server, you
> configure this using "Server Network Utility". I'm not sure whether such
> comes with MSDE, but that would be the place to start. The name of the exe is
> svrnetcn.exe
> "Jeff Bowman" <write.to.me@.my.addess.com> wrote in message
> news:%23Sv%23zABjFHA.3164@.TK2MSFTNGP15.phx.gbl...
>> I've got two machines: 1) SBS 2003 Server, and 2) WinXP Pro.
>> SQL Server 2000 is installed on the server box, as well as MSDE for the
>> default SharePoint and SbsMonitoring databases (SBS setup created those).
>> The workstation is running MSDE. The problem is that I can only connect to
>> the workstation's MSDE from the
>> workstation. EM on the server can see the MSDE instance (the worksation's
>> machine name appears in the Add SQL Server Registration dialog box), but
>> that's as far as it can get. When I try to add the instance under a new
>> registration, I get 'access denied or server doesn't exist' (paraphrased). I
>> also can't connect via EM to the workstation's MSDE from within a Win98
>> VirtualPC instance running on the workstation, although I can connect to the
>> server's instances (both SQL Server and MSDE instances) from within that
>> instance. I've compared the property sheets of all the instances to which I
>> can
>> connect from WinXP, and everything seems to be the same. Nothing shows up in
>> my ISA logs, so I don't think packets are being blocked. Just in case I
>> created a temporary packet filter allowing all packets from anywhere (risky,
>> I know), but it still didn't work. Still nothing in the logs. Does anyone
>> know what this might be?
>> TIA,
>> Jeff
SQL Server 2000 is installed on the server box, as well as MSDE for the default
SharePoint and SbsMonitoring databases (SBS setup created those). The
workstation is running MSDE.
The problem is that I can only connect to the workstation's MSDE from the
workstation. EM on the server can see the MSDE instance (the worksation's
machine name appears in the Add SQL Server Registration dialog box), but that's
as far as it can get. When I try to add the instance under a new registration, I
get 'access denied or server doesn't exist' (paraphrased).
I also can't connect via EM to the workstation's MSDE from within a Win98
VirtualPC instance running on the workstation, although I can connect to the
server's instances (both SQL Server and MSDE instances) from within that
instance.
I've compared the property sheets of all the instances to which I can connect
from WinXP, and everything seems to be the same. Nothing shows up in my ISA
logs, so I don't think packets are being blocked. Just in case I created a
temporary packet filter allowing all packets from anywhere (risky, I know), but
it still didn't work. Still nothing in the logs.
Does anyone know what this might be?
TIA,
JeffBy default MSDE doesn't listen to any netlibs. On a regular SQL Server, you configure this using
"Server Network Utility". I'm not sure whether such comes with MSDE, but that would be the place to
start. The name of the exe is svrnetcn.exe
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Jeff Bowman" <write.to.me@.my.addess.com> wrote in message
news:%23Sv%23zABjFHA.3164@.TK2MSFTNGP15.phx.gbl...
> I've got two machines: 1) SBS 2003 Server, and 2) WinXP Pro.
> SQL Server 2000 is installed on the server box, as well as MSDE for the default SharePoint and
> SbsMonitoring databases (SBS setup created those). The workstation is running MSDE.
> The problem is that I can only connect to the workstation's MSDE from the workstation. EM on the
> server can see the MSDE instance (the worksation's machine name appears in the Add SQL Server
> Registration dialog box), but that's as far as it can get. When I try to add the instance under a
> new registration, I get 'access denied or server doesn't exist' (paraphrased).
> I also can't connect via EM to the workstation's MSDE from within a Win98 VirtualPC instance
> running on the workstation, although I can connect to the server's instances (both SQL Server and
> MSDE instances) from within that instance.
> I've compared the property sheets of all the instances to which I can connect from WinXP, and
> everything seems to be the same. Nothing shows up in my ISA logs, so I don't think packets are
> being blocked. Just in case I created a temporary packet filter allowing all packets from anywhere
> (risky, I know), but it still didn't work. Still nothing in the logs.
> Does anyone know what this might be?
> TIA,
> Jeff
>
>|||That did the trick, thanks for the tip! :-)
(BTW, Server Network Utility appears to be installed with Client Tools.)
Tibor Karaszi wrote:
> By default MSDE doesn't listen to any netlibs. On a regular SQL Server, you
> configure this using "Server Network Utility". I'm not sure whether such
> comes with MSDE, but that would be the place to start. The name of the exe is
> svrnetcn.exe
> "Jeff Bowman" <write.to.me@.my.addess.com> wrote in message
> news:%23Sv%23zABjFHA.3164@.TK2MSFTNGP15.phx.gbl...
>> I've got two machines: 1) SBS 2003 Server, and 2) WinXP Pro.
>> SQL Server 2000 is installed on the server box, as well as MSDE for the
>> default SharePoint and SbsMonitoring databases (SBS setup created those).
>> The workstation is running MSDE. The problem is that I can only connect to
>> the workstation's MSDE from the
>> workstation. EM on the server can see the MSDE instance (the worksation's
>> machine name appears in the Add SQL Server Registration dialog box), but
>> that's as far as it can get. When I try to add the instance under a new
>> registration, I get 'access denied or server doesn't exist' (paraphrased). I
>> also can't connect via EM to the workstation's MSDE from within a Win98
>> VirtualPC instance running on the workstation, although I can connect to the
>> server's instances (both SQL Server and MSDE instances) from within that
>> instance. I've compared the property sheets of all the instances to which I
>> can
>> connect from WinXP, and everything seems to be the same. Nothing shows up in
>> my ISA logs, so I don't think packets are being blocked. Just in case I
>> created a temporary packet filter allowing all packets from anywhere (risky,
>> I know), but it still didn't work. Still nothing in the logs. Does anyone
>> know what this might be?
>> TIA,
>> Jeff
Cant connect to membership provider db
I've started developing an ASP.net 2.0 app with VWD Express.
The default membership provider db of SQL Server 5005 Express is not installed on my host servers. So my workaround has been to use a Full blown SQL Server 2005 DB as a custom membership provider declared in web.config.
This works fine on the production server. However, when i try to login from my development app I get Exception # 40 can't connect to SQL server membership provider.. Moreover, my app configuration confirms there is problems connecting to this server in my development environment.
How can I solve this and bring my development app up & running again?
many thanks
If you have access to your Production SQL Server from your development environment, the problem is probably due to your connection string.
For my development, I use SQL Express on my local development box and SQL Server for production. There are two things that you have to do. Keeps separate scripts for changes to the database (from development to production). In addition, a separate web.config for production and development to hold your connection strings.
Can't connect to default database
I installed SQL Server 2005 standard edition. When I am trying to connect
(via SQL Server Management Studio)to the default local dB by using SA. I get
the following error:
Cannot connect to <server name in here>
A connection was successfully established with the server, but then an error
occurred during the login process (provider shared memory provider error 0 -
no process is on the other end of the pipe). Microsoft SQL Server error 233.
I have Shared memory enabled as well as TCP/IP.
Any ideas what's wrong?
Thanks
Wendy
Run the Surface Area Configuration tool to make sure you
have enabled remote connections and with the protocols you
need.
-Sue
On Mon, 13 Mar 2006 13:26:27 -0800, Wendy
<Wendy@.discussions.microsoft.com> wrote:
>I installed SQL Server 2005 standard edition. When I am trying to connect
>(via SQL Server Management Studio)to the default local dB by using SA. I get
>the following error:
>Cannot connect to <server name in here>
>A connection was successfully established with the server, but then an error
>occurred during the login process (provider shared memory provider error 0 -
>no process is on the other end of the pipe). Microsoft SQL Server error 233.
>I have Shared memory enabled as well as TCP/IP.
>Any ideas what's wrong?
>Thanks
>Wendy
(via SQL Server Management Studio)to the default local dB by using SA. I get
the following error:
Cannot connect to <server name in here>
A connection was successfully established with the server, but then an error
occurred during the login process (provider shared memory provider error 0 -
no process is on the other end of the pipe). Microsoft SQL Server error 233.
I have Shared memory enabled as well as TCP/IP.
Any ideas what's wrong?
Thanks
Wendy
Run the Surface Area Configuration tool to make sure you
have enabled remote connections and with the protocols you
need.
-Sue
On Mon, 13 Mar 2006 13:26:27 -0800, Wendy
<Wendy@.discussions.microsoft.com> wrote:
>I installed SQL Server 2005 standard edition. When I am trying to connect
>(via SQL Server Management Studio)to the default local dB by using SA. I get
>the following error:
>Cannot connect to <server name in here>
>A connection was successfully established with the server, but then an error
>occurred during the login process (provider shared memory provider error 0 -
>no process is on the other end of the pipe). Microsoft SQL Server error 233.
>I have Shared memory enabled as well as TCP/IP.
>Any ideas what's wrong?
>Thanks
>Wendy
Can't connect to default database
I installed SQL Server 2005 standard edition. When I am trying to connect
(via SQL Server Management Studio)to the default local dB by using SA. I get
the following error:
Cannot connect to <server name in here>
A connection was successfully established with the server, but then an error
occurred during the login process (provider shared memory provider error 0 -
no process is on the other end of the pipe). Microsoft SQL Server error 233.
I have Shared memory enabled as well as TCP/IP.
Any ideas what's wrong?
Thanks
WendyRun the Surface Area Configuration tool to make sure you
have enabled remote connections and with the protocols you
need.
-Sue
On Mon, 13 Mar 2006 13:26:27 -0800, Wendy
<Wendy@.discussions.microsoft.com> wrote:
>I installed SQL Server 2005 standard edition. When I am trying to connect
>(via SQL Server Management Studio)to the default local dB by using SA. I get
>the following error:
>Cannot connect to <server name in here>
>A connection was successfully established with the server, but then an error
>occurred during the login process (provider shared memory provider error 0 -
>no process is on the other end of the pipe). Microsoft SQL Server error 233.
>I have Shared memory enabled as well as TCP/IP.
>Any ideas what's wrong?
>Thanks
>Wendy
(via SQL Server Management Studio)to the default local dB by using SA. I get
the following error:
Cannot connect to <server name in here>
A connection was successfully established with the server, but then an error
occurred during the login process (provider shared memory provider error 0 -
no process is on the other end of the pipe). Microsoft SQL Server error 233.
I have Shared memory enabled as well as TCP/IP.
Any ideas what's wrong?
Thanks
WendyRun the Surface Area Configuration tool to make sure you
have enabled remote connections and with the protocols you
need.
-Sue
On Mon, 13 Mar 2006 13:26:27 -0800, Wendy
<Wendy@.discussions.microsoft.com> wrote:
>I installed SQL Server 2005 standard edition. When I am trying to connect
>(via SQL Server Management Studio)to the default local dB by using SA. I get
>the following error:
>Cannot connect to <server name in here>
>A connection was successfully established with the server, but then an error
>occurred during the login process (provider shared memory provider error 0 -
>no process is on the other end of the pipe). Microsoft SQL Server error 233.
>I have Shared memory enabled as well as TCP/IP.
>Any ideas what's wrong?
>Thanks
>Wendy
Can't connect to default database
I installed SQL Server 2005 standard edition. When I am trying to connect
(via SQL Server Management Studio)to the default local dB by using SA. I get
the following error:
Cannot connect to <server name in here>
A connection was successfully established with the server, but then an error
occurred during the login process (provider shared memory provider error 0 -
no process is on the other end of the pipe). Microsoft SQL Server error 233.
I have Shared memory enabled as well as TCP/IP.
Any ideas what's wrong?
Thanks
WendyRun the Surface Area Configuration tool to make sure you
have enabled remote connections and with the protocols you
need.
-Sue
On Mon, 13 Mar 2006 13:26:27 -0800, Wendy
<Wendy@.discussions.microsoft.com> wrote:
>I installed SQL Server 2005 standard edition. When I am trying to connect
>(via SQL Server Management Studio)to the default local dB by using SA. I ge
t
>the following error:
>Cannot connect to <server name in here>
>A connection was successfully established with the server, but then an erro
r
>occurred during the login process (provider shared memory provider error 0
-
>no process is on the other end of the pipe). Microsoft SQL Server error 233
.
>I have Shared memory enabled as well as TCP/IP.
>Any ideas what's wrong?
>Thanks
>Wendy
(via SQL Server Management Studio)to the default local dB by using SA. I get
the following error:
Cannot connect to <server name in here>
A connection was successfully established with the server, but then an error
occurred during the login process (provider shared memory provider error 0 -
no process is on the other end of the pipe). Microsoft SQL Server error 233.
I have Shared memory enabled as well as TCP/IP.
Any ideas what's wrong?
Thanks
WendyRun the Surface Area Configuration tool to make sure you
have enabled remote connections and with the protocols you
need.
-Sue
On Mon, 13 Mar 2006 13:26:27 -0800, Wendy
<Wendy@.discussions.microsoft.com> wrote:
>I installed SQL Server 2005 standard edition. When I am trying to connect
>(via SQL Server Management Studio)to the default local dB by using SA. I ge
t
>the following error:
>Cannot connect to <server name in here>
>A connection was successfully established with the server, but then an erro
r
>occurred during the login process (provider shared memory provider error 0
-
>no process is on the other end of the pipe). Microsoft SQL Server error 233
.
>I have Shared memory enabled as well as TCP/IP.
>Any ideas what's wrong?
>Thanks
>Wendy
Friday, February 10, 2012
Can''t connect in Sql Express on local machine
I have SQL Express running on my laptop but are unable to connect to the default database paulm-laptop\sqlexpress
When I try to connect I get the error message
TITLE: Microsoft SQL Server Management Studio Express
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. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
Everything is on my laptop whcih is running Vista Business as an administrator
Any ideas why,
Thanks Paul
Did you enable remote connections for your SQL Server Instance ? If not, have a look at my screencast for more information how to do this.
Jens K. Suessmeyer
http://www.sqlserver2005.de
|||
Since you are on Vista, you should make sure that you are running Managment Studio as Administrator (right click on the shortcut and on Compatibility, choose Run as Administrator) or you can just right click on the shortcut and choose Run as Administrator each time you run it. I have seen this error when running it without it.
Subscribe to:
Posts (Atom)