Cannot find mdf files: authentication

Showing posts with label authentication. Show all posts

Tuesday, March 27, 2012

Cannot register server (LOCAL)

I'm trying to register the (LOCAL) database using SQL Server authentication.
However, I get the following message. I still can register other servers
using ip addresses though.
===================================================== Cannot connect to (LOCAL).
--
ADDITIONAL INFORMATION:
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: TCP Provider, error: 0 - No connection could be made because the
target machine actively refused it.) (Microsoft SQL Server, Error: 10061)
=====================================================did you try localhost?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"rkbnair" <rkbnair@.community.nospam> wrote in message
news:5439BC07-3618-4DC5-99BB-7957915C6894@.microsoft.com...
> I'm trying to register the (LOCAL) database using SQL Server authentication.
> However, I get the following message. I still can register other servers
> using ip addresses though.
> =====================================================> Cannot connect to (LOCAL).
> --
> ADDITIONAL INFORMATION:
> 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: TCP Provider, error: 0 - No connection could be made because the
> target machine actively refused it.) (Microsoft SQL Server, Error: 10061)
> =====================================================>|||Hi,
To let me better understand your issue, could you please let me know the
following questions:
1. Did you mean registering server named (local) or a database?
2. How did you perform the registration?
3. Why would you like to register a (local) server (database?) ?
From the error message, it seemed that you were trying to register a
(local) server remotely. "(local)" is preserved keyword for the default
instance of local SQL Server. You can only use it to locally connect to
your default instance of your SQL Server not remotely. Generally it is no
need to register a (local) server, if you want to rename a SQL server
instance, you can use sp_dropserver/sp_addserver stored procedures. You may
refer to:
How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server
2005
http://technet.microsoft.com/en-us/library/ms143799.aspx
Anyway I think that I have not totally understood your scenario. If there
is any misunderstanding, I appreciate your pointing and kindly making some
further explanation.
Thanks and have a nice day!
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||Yes, But no luck on that too.
--
test
"Tibor Karaszi" wrote:
> did you try localhost?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "rkbnair" <rkbnair@.community.nospam> wrote in message
> news:5439BC07-3618-4DC5-99BB-7957915C6894@.microsoft.com...
> > I'm trying to register the (LOCAL) database using SQL Server authentication.
> > However, I get the following message. I still can register other servers
> > using ip addresses though.
> >
> > =====================================================> > Cannot connect to (LOCAL).
> >
> > --
> > ADDITIONAL INFORMATION:
> >
> > 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: TCP Provider, error: 0 - No connection could be made because the
> > target machine actively refused it.) (Microsoft SQL Server, Error: 10061)
> > =====================================================> >
>
>|||Under the registered servers I see the following:
3tsd3b1
3tsd3b1\sqlexpress (which I can connect to successfully)
Under the Server Group I see the following items:
(LOCAL)
10.100.1.67 (which I can connect to successfully))
3TSSD3B1\SQLEXPRESS (which I can connect to successfully)
What should I do to create a database on my local machine.
In other words, what is the equivalent of registering (LOCAL) server in SQL
Server 2000?
"Charles Wang[MSFT]" wrote:
> Hi,
> To let me better understand your issue, could you please let me know the
> following questions:
> 1. Did you mean registering server named (local) or a database?
> 2. How did you perform the registration?
> 3. Why would you like to register a (local) server (database?) ?
> From the error message, it seemed that you were trying to register a
> (local) server remotely. "(local)" is preserved keyword for the default
> instance of local SQL Server. You can only use it to locally connect to
> your default instance of your SQL Server not remotely. Generally it is no
> need to register a (local) server, if you want to rename a SQL server
> instance, you can use sp_dropserver/sp_addserver stored procedures. You may
> refer to:
> How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server
> 2005
> http://technet.microsoft.com/en-us/library/ms143799.aspx
> Anyway I think that I have not totally understood your scenario. If there
> is any misunderstanding, I appreciate your pointing and kindly making some
> further explanation.
> Thanks and have a nice day!
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> =====================================================> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================>
>
>|||I suggest you first check what SQL Server related services you have installed. From that we can see
how many instances of SQL Server you installed.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"rkbnair" <rkbnair@.community.nospam> wrote in message
news:D5D736D2-EFB4-4E02-A37A-7CDE47D5C019@.microsoft.com...
> Under the registered servers I see the following:
> 3tsd3b1
> 3tsd3b1\sqlexpress (which I can connect to successfully)
> Under the Server Group I see the following items:
> (LOCAL)
> 10.100.1.67 (which I can connect to successfully))
> 3TSSD3B1\SQLEXPRESS (which I can connect to successfully)
> What should I do to create a database on my local machine.
> In other words, what is the equivalent of registering (LOCAL) server in SQL
> Server 2000?
>
>
> "Charles Wang[MSFT]" wrote:
>> Hi,
>> To let me better understand your issue, could you please let me know the
>> following questions:
>> 1. Did you mean registering server named (local) or a database?
>> 2. How did you perform the registration?
>> 3. Why would you like to register a (local) server (database?) ?
>> From the error message, it seemed that you were trying to register a
>> (local) server remotely. "(local)" is preserved keyword for the default
>> instance of local SQL Server. You can only use it to locally connect to
>> your default instance of your SQL Server not remotely. Generally it is no
>> need to register a (local) server, if you want to rename a SQL server
>> instance, you can use sp_dropserver/sp_addserver stored procedures. You may
>> refer to:
>> How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server
>> 2005
>> http://technet.microsoft.com/en-us/library/ms143799.aspx
>> Anyway I think that I have not totally understood your scenario. If there
>> is any misunderstanding, I appreciate your pointing and kindly making some
>> further explanation.
>> Thanks and have a nice day!
>> Best regards,
>> Charles Wang
>> Microsoft Online Community Support
>> =====================================================>> When responding to posts, please "Reply to Group" via
>> your newsreader so that others may learn and benefit
>> from this issue.
>> ======================================================>> This posting is provided "AS IS" with no warranties, and confers no rights.
>> ======================================================>>
>>|||The following services are started:
Server Status (green)
Report Server Virtual Directory (Red)
Report Manager Virtual Directory (red)
Windows Service Identity (Green)
Database Setup (Red)
Encryption Keys (Grey)
Initialization (Grey)
Email settings (Yellow)
Execution Account (Yellow)
--
test
"Tibor Karaszi" wrote:
> I suggest you first check what SQL Server related services you have installed. From that we can see
> how many instances of SQL Server you installed.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "rkbnair" <rkbnair@.community.nospam> wrote in message
> news:D5D736D2-EFB4-4E02-A37A-7CDE47D5C019@.microsoft.com...
> > Under the registered servers I see the following:
> > 3tsd3b1
> > 3tsd3b1\sqlexpress (which I can connect to successfully)
> >
> > Under the Server Group I see the following items:
> > (LOCAL)
> > 10.100.1.67 (which I can connect to successfully))
> > 3TSSD3B1\SQLEXPRESS (which I can connect to successfully)
> >
> > What should I do to create a database on my local machine.
> > In other words, what is the equivalent of registering (LOCAL) server in SQL
> > Server 2000?
> >
> >
> >
> >
> > "Charles Wang[MSFT]" wrote:
> >
> >> Hi,
> >> To let me better understand your issue, could you please let me know the
> >> following questions:
> >> 1. Did you mean registering server named (local) or a database?
> >> 2. How did you perform the registration?
> >> 3. Why would you like to register a (local) server (database?) ?
> >>
> >> From the error message, it seemed that you were trying to register a
> >> (local) server remotely. "(local)" is preserved keyword for the default
> >> instance of local SQL Server. You can only use it to locally connect to
> >> your default instance of your SQL Server not remotely. Generally it is no
> >> need to register a (local) server, if you want to rename a SQL server
> >> instance, you can use sp_dropserver/sp_addserver stored procedures. You may
> >> refer to:
> >> How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server
> >> 2005
> >> http://technet.microsoft.com/en-us/library/ms143799.aspx
> >>
> >> Anyway I think that I have not totally understood your scenario. If there
> >> is any misunderstanding, I appreciate your pointing and kindly making some
> >> further explanation.
> >>
> >> Thanks and have a nice day!
> >>
> >> Best regards,
> >> Charles Wang
> >> Microsoft Online Community Support
> >> =====================================================> >> When responding to posts, please "Reply to Group" via
> >> your newsreader so that others may learn and benefit
> >> from this issue.
> >> ======================================================> >> This posting is provided "AS IS" with no warranties, and confers no rights.
> >> ======================================================> >>
> >>
> >>
> >>
> >>
>|||What tool did you use to get that list? None of those looks like the name of a SQL Server 2005
service to me. I suggest you do Run and in there type : services.msc
This starts the "Services" windows applet. In there you look for services where the name starts with
SQL Server, such as :
SQL Server (MSSQLServer)
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"rkbnair" <rkbnair@.community.nospam> wrote in message
news:145F3211-E6D3-4D4F-877B-7F47AE7C7759@.microsoft.com...
> The following services are started:
> Server Status (green)
> Report Server Virtual Directory (Red)
> Report Manager Virtual Directory (red)
> Windows Service Identity (Green)
> Database Setup (Red)
> Encryption Keys (Grey)
> Initialization (Grey)
> Email settings (Yellow)
> Execution Account (Yellow)
> --
> test
>
> "Tibor Karaszi" wrote:
>> I suggest you first check what SQL Server related services you have installed. From that we can
>> see
>> how many instances of SQL Server you installed.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "rkbnair" <rkbnair@.community.nospam> wrote in message
>> news:D5D736D2-EFB4-4E02-A37A-7CDE47D5C019@.microsoft.com...
>> > Under the registered servers I see the following:
>> > 3tsd3b1
>> > 3tsd3b1\sqlexpress (which I can connect to successfully)
>> >
>> > Under the Server Group I see the following items:
>> > (LOCAL)
>> > 10.100.1.67 (which I can connect to successfully))
>> > 3TSSD3B1\SQLEXPRESS (which I can connect to successfully)
>> >
>> > What should I do to create a database on my local machine.
>> > In other words, what is the equivalent of registering (LOCAL) server in SQL
>> > Server 2000?
>> >
>> >
>> >
>> >
>> > "Charles Wang[MSFT]" wrote:
>> >
>> >> Hi,
>> >> To let me better understand your issue, could you please let me know the
>> >> following questions:
>> >> 1. Did you mean registering server named (local) or a database?
>> >> 2. How did you perform the registration?
>> >> 3. Why would you like to register a (local) server (database?) ?
>> >>
>> >> From the error message, it seemed that you were trying to register a
>> >> (local) server remotely. "(local)" is preserved keyword for the default
>> >> instance of local SQL Server. You can only use it to locally connect to
>> >> your default instance of your SQL Server not remotely. Generally it is no
>> >> need to register a (local) server, if you want to rename a SQL server
>> >> instance, you can use sp_dropserver/sp_addserver stored procedures. You may
>> >> refer to:
>> >> How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server
>> >> 2005
>> >> http://technet.microsoft.com/en-us/library/ms143799.aspx
>> >>
>> >> Anyway I think that I have not totally understood your scenario. If there
>> >> is any misunderstanding, I appreciate your pointing and kindly making some
>> >> further explanation.
>> >>
>> >> Thanks and have a nice day!
>> >>
>> >> Best regards,
>> >> Charles Wang
>> >> Microsoft Online Community Support
>> >> =====================================================>> >> When responding to posts, please "Reply to Group" via
>> >> your newsreader so that others may learn and benefit
>> >> from this issue.
>> >> ======================================================>> >> This posting is provided "AS IS" with no warranties, and confers no rights.
>> >> ======================================================>> >>
>> >>
>> >>
>> >>
>> >>|||Hi,
Thanks for your response.
I recommend that you post some screenshots here or or mail them to me
(changliw_at_microsoft_dot_com) so that we can better understand your
issue. Also as Tibor said, please run services.msc from command line and
check what the SQL Server services are listed. The SQL Server service name
is like "SQL Server (<instance name>)" or "MSSQLServer".
Additionally I need to confirm with you several questions for further
research:
a. What is the version of your (local) SQL Server instance, SQL Server 2000
or SQL Server 2005?
b. What is the client tool you use, SQL Server Enterprise Manager or SQL
Server Management Studio?
c. Was "3tsd3b1" the name of your local computer and was "10.100.1.67" the
IP address of your local computer?
Creating a database on your local machine does not mean registering (LOCAL)
server in SQL Server 2000. If you would like to register (LOCAL) server in
SQL Server 2000 (Enterprise Manager ?) , you need to ensure that there is a
SQL Server 2000 default instance (the service name is MSSQLServer in
Services panel) has been installed. Also SQL Server 2000 Enterprise Manager
(EM) cannot manage SQL Server 2005 instance, so if you would like to use
SQL Server 2000 EM to register a SQL Server 2005 instance, it is not
possible to do it. In this case, you have to use SQL Server 2005 Management
Studio (SSMS) to do it.
If there is a SQL Server 2000 default instance installed, you can locally
use either SQL Server 2000 EM or SSMS to connect to it via your computer
name, IP or "(local)" to connect to it. Appreciate your understanding if we
could not cleary understand your issue, it is hard for us to go further.
Thanks for your cooperation and look forward to your response.
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||SQL Server (SQLEXPRESS)
SQL Server Active Directory Helper
SQL Server Analysis Services (MSSQLSERVER)
SQL Server Browser
SQL Server Integration Services
SQL Server Reporting Services (MSSQLSERVER)
SQL Server VSS Writer
--
test
"Tibor Karaszi" wrote:
> What tool did you use to get that list? None of those looks like the name of a SQL Server 2005
> service to me. I suggest you do Run and in there type : services.msc
> This starts the "Services" windows applet. In there you look for services where the name starts with
> SQL Server, such as :
> SQL Server (MSSQLServer)
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "rkbnair" <rkbnair@.community.nospam> wrote in message
> news:145F3211-E6D3-4D4F-877B-7F47AE7C7759@.microsoft.com...
> > The following services are started:
> >
> > Server Status (green)
> > Report Server Virtual Directory (Red)
> > Report Manager Virtual Directory (red)
> > Windows Service Identity (Green)
> > Database Setup (Red)
> > Encryption Keys (Grey)
> > Initialization (Grey)
> > Email settings (Yellow)
> > Execution Account (Yellow)
> >
> > --
> > test
> >
> >
> > "Tibor Karaszi" wrote:
> >
> >> I suggest you first check what SQL Server related services you have installed. From that we can
> >> see
> >> how many instances of SQL Server you installed.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://sqlblog.com/blogs/tibor_karaszi
> >>
> >>
> >> "rkbnair" <rkbnair@.community.nospam> wrote in message
> >> news:D5D736D2-EFB4-4E02-A37A-7CDE47D5C019@.microsoft.com...
> >> > Under the registered servers I see the following:
> >> > 3tsd3b1
> >> > 3tsd3b1\sqlexpress (which I can connect to successfully)
> >> >
> >> > Under the Server Group I see the following items:
> >> > (LOCAL)
> >> > 10.100.1.67 (which I can connect to successfully))
> >> > 3TSSD3B1\SQLEXPRESS (which I can connect to successfully)
> >> >
> >> > What should I do to create a database on my local machine.
> >> > In other words, what is the equivalent of registering (LOCAL) server in SQL
> >> > Server 2000?
> >> >
> >> >
> >> >
> >> >
> >> > "Charles Wang[MSFT]" wrote:
> >> >
> >> >> Hi,
> >> >> To let me better understand your issue, could you please let me know the
> >> >> following questions:
> >> >> 1. Did you mean registering server named (local) or a database?
> >> >> 2. How did you perform the registration?
> >> >> 3. Why would you like to register a (local) server (database?) ?
> >> >>
> >> >> From the error message, it seemed that you were trying to register a
> >> >> (local) server remotely. "(local)" is preserved keyword for the default
> >> >> instance of local SQL Server. You can only use it to locally connect to
> >> >> your default instance of your SQL Server not remotely. Generally it is no
> >> >> need to register a (local) server, if you want to rename a SQL server
> >> >> instance, you can use sp_dropserver/sp_addserver stored procedures. You may
> >> >> refer to:
> >> >> How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server
> >> >> 2005
> >> >> http://technet.microsoft.com/en-us/library/ms143799.aspx
> >> >>
> >> >> Anyway I think that I have not totally understood your scenario. If there
> >> >> is any misunderstanding, I appreciate your pointing and kindly making some
> >> >> further explanation.
> >> >>
> >> >> Thanks and have a nice day!
> >> >>
> >> >> Best regards,
> >> >> Charles Wang
> >> >> Microsoft Online Community Support
> >> >> =====================================================> >> >> When responding to posts, please "Reply to Group" via
> >> >> your newsreader so that others may learn and benefit
> >> >> from this issue.
> >> >> ======================================================> >> >> This posting is provided "AS IS" with no warranties, and confers no rights.
> >> >> ======================================================> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >>
>|||OK. It seems you have installed a named instance of SQL Server express database engine with the
instance name "SQLEXPRESS".
Also, you installed Analysis services and Reporting services as default instances.
So, I assume you want to connect to your express named instance (since that is the only database
engine instance). If you are local on the machine try:
localhost\SQLExpress
Or:
machinename\SQLEXPRESS
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"rkbnair" <rkbnair@.community.nospam> wrote in message
news:83688470-F1FB-4618-B743-D1F9B0B267E2@.microsoft.com...
> SQL Server (SQLEXPRESS)
> SQL Server Active Directory Helper
> SQL Server Analysis Services (MSSQLSERVER)
> SQL Server Browser
> SQL Server Integration Services
> SQL Server Reporting Services (MSSQLSERVER)
> SQL Server VSS Writer
> --
> test
>
> "Tibor Karaszi" wrote:
>> What tool did you use to get that list? None of those looks like the name of a SQL Server 2005
>> service to me. I suggest you do Run and in there type : services.msc
>> This starts the "Services" windows applet. In there you look for services where the name starts
>> with
>> SQL Server, such as :
>> SQL Server (MSSQLServer)
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "rkbnair" <rkbnair@.community.nospam> wrote in message
>> news:145F3211-E6D3-4D4F-877B-7F47AE7C7759@.microsoft.com...
>> > The following services are started:
>> >
>> > Server Status (green)
>> > Report Server Virtual Directory (Red)
>> > Report Manager Virtual Directory (red)
>> > Windows Service Identity (Green)
>> > Database Setup (Red)
>> > Encryption Keys (Grey)
>> > Initialization (Grey)
>> > Email settings (Yellow)
>> > Execution Account (Yellow)
>> >
>> > --
>> > test
>> >
>> >
>> > "Tibor Karaszi" wrote:
>> >
>> >> I suggest you first check what SQL Server related services you have installed. From that we
>> >> can
>> >> see
>> >> how many instances of SQL Server you installed.
>> >>
>> >> --
>> >> Tibor Karaszi, SQL Server MVP
>> >> http://www.karaszi.com/sqlserver/default.asp
>> >> http://sqlblog.com/blogs/tibor_karaszi
>> >>
>> >>
>> >> "rkbnair" <rkbnair@.community.nospam> wrote in message
>> >> news:D5D736D2-EFB4-4E02-A37A-7CDE47D5C019@.microsoft.com...
>> >> > Under the registered servers I see the following:
>> >> > 3tsd3b1
>> >> > 3tsd3b1\sqlexpress (which I can connect to successfully)
>> >> >
>> >> > Under the Server Group I see the following items:
>> >> > (LOCAL)
>> >> > 10.100.1.67 (which I can connect to successfully))
>> >> > 3TSSD3B1\SQLEXPRESS (which I can connect to successfully)
>> >> >
>> >> > What should I do to create a database on my local machine.
>> >> > In other words, what is the equivalent of registering (LOCAL) server in SQL
>> >> > Server 2000?
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > "Charles Wang[MSFT]" wrote:
>> >> >
>> >> >> Hi,
>> >> >> To let me better understand your issue, could you please let me know the
>> >> >> following questions:
>> >> >> 1. Did you mean registering server named (local) or a database?
>> >> >> 2. How did you perform the registration?
>> >> >> 3. Why would you like to register a (local) server (database?) ?
>> >> >>
>> >> >> From the error message, it seemed that you were trying to register a
>> >> >> (local) server remotely. "(local)" is preserved keyword for the default
>> >> >> instance of local SQL Server. You can only use it to locally connect to
>> >> >> your default instance of your SQL Server not remotely. Generally it is no
>> >> >> need to register a (local) server, if you want to rename a SQL server
>> >> >> instance, you can use sp_dropserver/sp_addserver stored procedures. You may
>> >> >> refer to:
>> >> >> How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server
>> >> >> 2005
>> >> >> http://technet.microsoft.com/en-us/library/ms143799.aspx
>> >> >>
>> >> >> Anyway I think that I have not totally understood your scenario. If there
>> >> >> is any misunderstanding, I appreciate your pointing and kindly making some
>> >> >> further explanation.
>> >> >>
>> >> >> Thanks and have a nice day!
>> >> >>
>> >> >> Best regards,
>> >> >> Charles Wang
>> >> >> Microsoft Online Community Support
>> >> >> =====================================================>> >> >> When responding to posts, please "Reply to Group" via
>> >> >> your newsreader so that others may learn and benefit
>> >> >> from this issue.
>> >> >> ======================================================>> >> >> This posting is provided "AS IS" with no warranties, and confers no rights.
>> >> >> ======================================================>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
>>

Cannot register server (LOCAL)

Cannot register local sql server

I am having a problem registering my local SQL server.
When I try to use Windows authentication an error msg
appears saying "cannot open default db, using master db
instead" but it doesn't register. When I try using SQL
Server authentication (using the sa logon) a msg appears
saying "login failed for sa, not associated with a trusted
sql server connection".
I previously had the server registered ok and then it
suddenly stopped working so I deleted it and now it won't
reregister. I have no problem registering other SQL
Servers through EM on my pc. Any ideas how to fix this and
maybe what caused the problem in the first place?
Thanks
DaveTry changing your default database (which sounds like it has been dropped)
using osql e.g.
osql -E -Sservername -dmaster -Q"exec sp_defaultdb
'domain\username','master'"
replacing servername with the server you are trying to register and
domain\username with your nt login.Once this is done try registering the
server again. BTW you can also use Query Analyzer if that is more
comfortable by starting it from the command line and passing the database
e.g.
isqlw -E -dmaster -Sservername
and then run the command
exec sp_defaultdb 'domain\username','master'
again, you should now be able to register the server
The reason the sa login doesn't work is because the server you are
connecting to is set to Windows Authentication only.
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"dave" <anonymous@.discussions.microsoft.com> wrote in message
news:09d301c3b438$d482b550$a001280a@.phx.gbl...
I am having a problem registering my local SQL server.
When I try to use Windows authentication an error msg
appears saying "cannot open default db, using master db
instead" but it doesn't register. When I try using SQL
Server authentication (using the sa logon) a msg appears
saying "login failed for sa, not associated with a trusted
sql server connection".
I previously had the server registered ok and then it
suddenly stopped working so I deleted it and now it won't
reregister. I have no problem registering other SQL
Servers through EM on my pc. Any ideas how to fix this and
maybe what caused the problem in the first place?
Thanks
Dave|||just change the loginmode to 2 in the registry
--
Shaju Thomas
"dave" <anonymous@.discussions.microsoft.com> wrote in message
news:09d301c3b438$d482b550$a001280a@.phx.gbl...
> I am having a problem registering my local SQL server.
> When I try to use Windows authentication an error msg
> appears saying "cannot open default db, using master db
> instead" but it doesn't register. When I try using SQL
> Server authentication (using the sa logon) a msg appears
> saying "login failed for sa, not associated with a trusted
> sql server connection".
> I previously had the server registered ok and then it
> suddenly stopped working so I deleted it and now it won't
> reregister. I have no problem registering other SQL
> Servers through EM on my pc. Any ideas how to fix this and
> maybe what caused the problem in the first place?
> Thanks
> Dave

Tuesday, March 20, 2012

Cannot Open default Database. Login Failed. Problem

I have created an app which use sqlserver exrpress and works fine. I have now craeted a authentication page login.aspx.

I have added users successfully to the asp.net configuartion via the web site admin tool.

When I go to login using my page I get the Cannot open default database.Login failed. Login failed for user servet\aspnet.

I have looked at the asonetdb in sql server management studio and the server\asp net is set up on the database.

Can anyone suggeste what I ma doing wrong or where I might see a work through of the problem.

Thanks

Frank

Please check the properties of 'server\asp net' login in SQL Server Management Studio again:

1. Find its default database in the General panel

2. In the User Mapping panel, make sure its default database has been selected and mapped to a valid user.

|||

The login seems to worjk fine when I run the app using visual web developer - when I try and logn after accessing the system conventially via a web page it doesn't let me login.

Any suggestions.

Frank

|||How do you infer the login works fine? Can you connect to the SQL Server with the login? Or you checked it in SQL logins?

Sunday, March 11, 2012

Cannot login using Integrated Authentication

I can't seem to login using Integrated Authentication. I enter the user name / password and receive "You are not authorized". I messed with everything I can find and no solution.

* I can browse a simple web page.

* I cannot browse LocalStart.asp (get asked for User/Password)

* I can set security on the reports folder to Anon and browse to Home.aspx

* I have disabled the loopbackcheck.

This is my dev box running Media Center 2005 w/SP2, IIS 5.1, SQL Server 2005

Any help would be appreciated.

try going into internet explorer, go to tools / options thne security tab then custom level, right at the bottom of the list check the radio button for login automatically using current username and pass and try again.....

Let m enow the outcome, it may not be this...

|||

The only way that seems to work is if I change it in the Internet zone and not the Intranet zone. Changing the Intranet zone still fails. Doesn't this create a huge security hole because it will now send my username and password to every site that wants it?

|||

Hey Andy,

I fiddled a little bit more and figured out that if I explicitly added http://localhost to my intranet sites it fixed the problem. No need to change the security level setting in the Internet zone. Everything is left at Automatic logon for Intranet only.

Thanks a bunch. You got me on the right track!!!

Paul

Cannot login to SQL Server 2005 using SQL Server Authentication

I am unable to login to Server Management Express using Server
Authentication. I am able to login using Windows Authentication
though. I setup a new logic using Server Authentication but get the
following message:
Cannot connect to MIKE-PC.
===================================
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.)
(.Net SqlClient Data Provider)
For help, click: [url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLS erver&EvtID=233&LinkId=20476[/url]
Server Name: MIKE-PC
Error Number: 233
Severity: 20
State: 0
I am running SQL Server 2005 Express on my local PC and would like to
use the SQL Server Authentication so that a VB programcan access the
database.
Any idea where to look for more info to resolve this?
Thanks in advance,
Mike Polinske
Milwaukee, WI
By default SQL Server is installed to only accept Windows (SSPI)
authentication credentials. You'll need to reconfigure (and restart) SQL
Server to handle mixed-mode security.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Mike Polinske" <mikepolinske@.gmail.com> wrote in message
news:1187031553.693705.10860@.l22g2000prc.googlegro ups.com...
>I am unable to login to Server Management Express using Server
> Authentication. I am able to login using Windows Authentication
> though. I setup a new logic using Server Authentication but get the
> following message:
> Cannot connect to MIKE-PC.
> ===================================
> 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.)
> (.Net SqlClient Data Provider)
> --
> For help, click:
> [url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLS erver&EvtID=233&LinkId=20476[/url]
> --
> Server Name: MIKE-PC
> Error Number: 233
> Severity: 20
> State: 0
> I am running SQL Server 2005 Express on my local PC and would like to
> use the SQL Server Authentication so that a VB programcan access the
> database.
> Any idea where to look for more info to resolve this?
> Thanks in advance,
> Mike Polinske
> Milwaukee, WI
>
|||On Aug 13, 3:12 pm, "William Vaughn" <billvaNoS...@.betav.com> wrote:
> By default SQL Server is installed to only accept Windows (SSPI)
> authentication credentials. You'll need to reconfigure (and restart) SQL
> Server to handle mixed-mode security.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant, Dad, Grandpa
> Microsoft MVP
> INETA Speakerwww.betav.comwww.betav.com/blog/billva
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> __________________________________
> Visitwww.hitchhikerguides.netto get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----X---
>
Thanks Bill, I was able to find the server properry under Security
that controls the authentication and it worked like a charm!!

Cannot login to SQL Server 2005 using SQL Server Authentication

I am unable to login to Server Management Express using Server
Authentication. I am able to login using Windows Authentication
though. I setup a new logic using Server Authentication but get the
following message:
Cannot connect to MIKE-PC.
===================================
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.)
(.Net SqlClient Data Provider)
--
For help, click: http://go.microsoft.com/fwlink?Prod...33&LinkId=20476
--
Server Name: MIKE-PC
Error Number: 233
Severity: 20
State: 0
I am running SQL Server 2005 Express on my local PC and would like to
use the SQL Server Authentication so that a VB programcan access the
database.
Any idea where to look for more info to resolve this?
Thanks in advance,
Mike Polinske
Milwaukee, WIBy default SQL Server is installed to only accept Windows (SSPI)
authentication credentials. You'll need to reconfigure (and restart) SQL
Server to handle mixed-mode security.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Mike Polinske" <mikepolinske@.gmail.com> wrote in message
news:1187031553.693705.10860@.l22g2000prc.googlegroups.com...
>I am unable to login to Server Management Express using Server
> Authentication. I am able to login using Windows Authentication
> though. I setup a new logic using Server Authentication but get the
> following message:
> Cannot connect to MIKE-PC.
> ===================================
> 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.)
> (.Net SqlClient Data Provider)
> --
> For help, click:
> http://go.microsoft.com/fwlink?Prod...33&LinkId=20476
> --
> Server Name: MIKE-PC
> Error Number: 233
> Severity: 20
> State: 0
> I am running SQL Server 2005 Express on my local PC and would like to
> use the SQL Server Authentication so that a VB programcan access the
> database.
> Any idea where to look for more info to resolve this?
> Thanks in advance,
> Mike Polinske
> Milwaukee, WI
>|||On Aug 13, 3:12 pm, "William Vaughn" <billvaNoS...@.betav.com> wrote:
> By default SQL Server is installed to only accept Windows (SSPI)
> authentication credentials. You'll need to reconfigure (and restart) SQL
> Server to handle mixed-mode security.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant, Dad, Grandpa
> Microsoft MVP
> INETA Speakerwww.betav.comwww.betav.com/blog/billva
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no right=
s=2E
> __________________________________
> Visitwww.hitchhikerguides.netto get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----=
--=AD---
>
Thanks Bill, I was able to find the server properry under Security
that controls the authentication and it worked like a charm!!

Cannot login SQL Server with 'sa'

Hi,
After I setup 'sa' password in SQL Server 2005, I get out SQL Server and
re-login using SQL Authentication mode with 'sa' and pasword, I get error:
"A connection was successfully established with the server, but then the
error occured during the login process. (Provider: Shared memeoryprovider,
error 0 - No process is on the other end of the pipe.) (Microsoft SQL Server
: error 233)"
Please help
Thanks
kaiDo you have Shared Memory connections enabled? Run the SQL Server
Configuration Manager and look at the protocols and shared Memory to see if
it is enabled or not.
Andrew J. Kelly SQL MVP
"kai" <kailiang@.earthlink.net> wrote in message
news:5HZqf.9593$nm.595@.newsread2.news.atl.earthlink.net...
> Hi,
> After I setup 'sa' password in SQL Server 2005, I get out SQL Server and
> re-login using SQL Authentication mode with 'sa' and pasword, I get error:
> "A connection was successfully established with the server, but then the
> error occured during the login process. (Provider: Shared memeoryprovider,
> error 0 - No process is on the other end of the pipe.) (Microsoft SQL
> Server : error 233)"
> Please help
> Thanks
> kai
>|||Andrew,
Thanks for your help. I checked it, it is enabled. I found additional
error when I login second time:
"Login failed for user 'sa'.The user is associated with a trusted SQL Server
connection. (Microsoft SQL Server, error: 18452)
Kai
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:%23pGIiaACGHA.736@.TK2MSFTNGP10.phx.gbl...
> Do you have Shared Memory connections enabled? Run the SQL Server
> Configuration Manager and look at the protocols and shared Memory to see
> if it is enabled or not.
> --
> Andrew J. Kelly SQL MVP
>
> "kai" <kailiang@.earthlink.net> wrote in message
> news:5HZqf.9593$nm.595@.newsread2.news.atl.earthlink.net...
>|||See if this may help:
http://support.microsoft.com/?id=328306
Andrew J. Kelly SQL MVP
"kai" <kailiang@.earthlink.net> wrote in message
news:jB_qf.9068$3Z.3336@.newsread1.news.atl.earthlink.net...
> Andrew,
> Thanks for your help. I checked it, it is enabled. I found additional
> error when I login second time:
> "Login failed for user 'sa'.The user is associated with a trusted SQL
> Server connection. (Microsoft SQL Server, error: 18452)
> Kai
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:%23pGIiaACGHA.736@.TK2MSFTNGP10.phx.gbl...
>|||Is it possible you're trying to connect multiple times over the dedicated
Admin connection?
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"kai" <kailiang@.earthlink.net> wrote in message
news:jB_qf.9068$3Z.3336@.newsread1.news.atl.earthlink.net...
> Andrew,
> Thanks for your help. I checked it, it is enabled. I found additional
> error when I login second time:
> "Login failed for user 'sa'.The user is associated with a trusted SQL
> Server connection. (Microsoft SQL Server, error: 18452)
> Kai
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:%23pGIiaACGHA.736@.TK2MSFTNGP10.phx.gbl...
>
>|||Hi Kai,
Generally speaking, error code 18452 suggests SQL Authentication is not
enabled. Would you please check to see whether it was enabled?
- Right Click the instance name in the Object Explorer, select Properties
- Select Security page and make sure SQL Server and Windows Authentication
mode is selected.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Michael ,
Thank you for your help.
It is enabled. I check my other two SQL Servers, they all have the same
problems.
Kai
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:8qxTKFFCGHA.3992@.TK2MSFTNGXA02.phx.gbl...
> Hi Kai,
> Generally speaking, error code 18452 suggests SQL Authentication is not
> enabled. Would you please check to see whether it was enabled?
> - Right Click the instance name in the Object Explorer, select Properties
> - Select Security page and make sure SQL Server and Windows Authentication
> mode is selected.
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Michael,
Thank you very much for your help.
When I installed SQL Server 2005 initially, I use Wondows Authentication
mode. After the installation, I changed to Mixed mode. Then I setup the new
password for 'sa' and other SQL Server logins, I cannot login with any SQL
logins.
I just found out the Login properties (status) for those SQL logins ware
setup to "Disable" by default, after I change them to "Enaled", I can login
with SQL logins.
Thank you so much !!!
Kai
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:g8q%235hfCGHA.3992@.TK2MSFTNGXA02.phx.gbl...
> Hi Kai,
> This issue occurs because SQL Server Management Studio cannot correctly
> report the error when the maximum number of concurrent connections has
> been
> reached.
> To work around this issue, you can use the sp_configure Transact-SQL
> procedure to increase the maximum number of concurrent connections. You
> can
> also manage the instance of SQL Server 2005 in other ways. For example,
> you
> can use the sqlcmd utility.
> To use sp_configure to increase the maximum number of concurrent
> connections, follow these steps:
> 1. Click Start, click Run, type cmd, and then click OK.
> 2. At the command prompt, type the following command, and then press
> ENTER.
> sqlcmd.exe -E -S servername
> 3. When you successfully connect to the instance of SQL Server 2005,
> execute the following Transact-SQL statements at the SQL Server prompt.
> sp_configure 'user connections', <NewNumber>
> Go
> Reconfigure
> Go
> 4. Restart the SQL Server service for the change to take effect.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi Kai,
Happy New Year! You are welcome!
If you have any questions or concerns next time, don't hesitate to let me
know. We are always here to be of assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||By default max no. of connections is set to 10.
To increase the maximum no. of connections
1. In Object Explorer, right-click a server and click Properties.
2. Click the Connections node.
3. Under Connections, in the Max number of concurrent connections box, type
or select a value from 0 through 32767 to set the maximum number of users
that are allowed to connect simultaneously to the instance of SQL Server.
set it to 0 (it means unlimited connections)

Thursday, February 16, 2012

Cannot get AD groups to work in SQL 2k5

I'm trying to get Active Directory groups to work in SQL Server 2k5 so my
users can log in with windows authentication. So I've set up the group in
AD, added the domain users to it, added the group to MS SQL security users,
and assigned a default database to the group. For some odd reason my users
are not able to log in though; I can quickly check this by trying to set up
a
ODBC connection System DSN.
The odd part about this is that if I add a domain user to MS SQL, they have
no problem logging into the database. Understandably I want to avoid adding
each and every user to my database, therefore the use of AD groups that is i
f
they would work.I would expect users to be able to connect via group membership. Do you see
the group members listed when you execute xp_logininfo? Does the group show
as the permission path for a specific user?
EXEC xp_logininfo
@.acctname = 'MyDomain\MyGroup',
@.option = 'members'
EXEC xp_logininfo
@.acctname = 'MyDomain\MyGroupMember'
Hope this helps.
Dan Guzman
SQL Server MVP
"Chandler Chao" <ChandlerChao@.discussions.microsoft.com> wrote in message
news:A2720F69-543C-4DF4-8079-56ACA8776D51@.microsoft.com...
> I'm trying to get Active Directory groups to work in SQL Server 2k5 so my
> users can log in with windows authentication. So I've set up the group in
> AD, added the domain users to it, added the group to MS SQL security
> users,
> and assigned a default database to the group. For some odd reason my
> users
> are not able to log in though; I can quickly check this by trying to set
> up a
> ODBC connection System DSN.
> The odd part about this is that if I add a domain user to MS SQL, they
> have
> no problem logging into the database. Understandably I want to avoid
> adding
> each and every user to my database, therefore the use of AD groups that is
> if
> they would work.|||I was just able to get this working with a some help from this NG.
My SQL Server is configured for Mixed authentication.
I set up my AD groups and added users.
I added logins for each AD group in SQL Server.
I added database users for each AD group and assigned permissions to
objects.
Hope this helps..
Michael
"Chandler Chao" <ChandlerChao@.discussions.microsoft.com> wrote in message
news:A2720F69-543C-4DF4-8079-56ACA8776D51@.microsoft.com...
> I'm trying to get Active Directory groups to work in SQL Server 2k5 so my
> users can log in with windows authentication. So I've set up the group in
> AD, added the domain users to it, added the group to MS SQL security
> users,
> and assigned a default database to the group. For some odd reason my
> users
> are not able to log in though; I can quickly check this by trying to set
> up a
> ODBC connection System DSN.
> The odd part about this is that if I add a domain user to MS SQL, they
> have
> no problem logging into the database. Understandably I want to avoid
> adding
> each and every user to my database, therefore the use of AD groups that is
> if
> they would work.

Tuesday, February 14, 2012

cannot generate sspi context when server in mixed authentication m

We have a situation for which I have been trying to find an explanation for
over a week. A windows 2005 SP1 server which previously ran in Windows
authentication only suddenly caused "cannot generate sspi context" errors
after we switched it to mixed authentication mode.
-SQL service is running with domain account not trusted for delegation
-We have checked for invalid SPNs in the domain and there are none
registered for the SQL Service on this machine
-TCP/IP protocol is enabled on the server
-Named Pipes connections work fine
-After switching back to Windows authentication and clearing the ticket
cache the problem dissapears
If I understand correctly. The default authentication protocol used over
tcp/ip when connecting to SQL Server is Kerberos but if the client cannot
find a valid SPN for the SQL Service on the server then it should fall back
to NTLM. For some reason however, this is not happening as it should.
What is SQL Server service starting as...local system, domain user or domain
admin?
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"DBA72" <DBA72@.discussions.microsoft.com> wrote in message
news:65AFAA64-4847-4034-8745-211ED18ACB0E@.microsoft.com...
> We have a situation for which I have been trying to find an explanation
> for
> over a week. A windows 2005 SP1 server which previously ran in Windows
> authentication only suddenly caused "cannot generate sspi context" errors
> after we switched it to mixed authentication mode.
> -SQL service is running with domain account not trusted for delegation
> -We have checked for invalid SPNs in the domain and there are none
> registered for the SQL Service on this machine
> -TCP/IP protocol is enabled on the server
> -Named Pipes connections work fine
> -After switching back to Windows authentication and clearing the ticket
> cache the problem dissapears
> If I understand correctly. The default authentication protocol used over
> tcp/ip when connecting to SQL Server is Kerberos but if the client cannot
> find a valid SPN for the SQL Service on the server then it should fall
> back
> to NTLM. For some reason however, this is not happening as it should.
>
|||It is starting with a domain user account.
"Kevin3NF" wrote:

> What is SQL Server service starting as...local system, domain user or domain
> admin?
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "DBA72" <DBA72@.discussions.microsoft.com> wrote in message
> news:65AFAA64-4847-4034-8745-211ED18ACB0E@.microsoft.com...
>
>
|||A domain admin will need to create an SPN for the SQL Server service
manually using SetSPN or ADSI (I think)
Local system or domain admin starting sql does this automatically...domain
user does not
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"DBA72" <DBA72@.discussions.microsoft.com> wrote in message
news:F01518D8-9430-49AB-95AC-076BF1C5CF84@.microsoft.com...[vbcol=seagreen]
> It is starting with a domain user account.
> "Kevin3NF" wrote:
|||"Kevin3NF" wrote:

> A domain admin will need to create an SPN for the SQL Server service
> manually using SetSPN or ADSI (I think)
> Local system or domain admin starting sql does this automatically...domain
> user does not
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "DBA72" <DBA72@.discussions.microsoft.com> wrote in message
> news:F01518D8-9430-49AB-95AC-076BF1C5CF84@.microsoft.com...
>
Kevin,
I think you would be right if I was trying to use Kerberos but as I said,
this is not enabled for the sql service account. What I want to do is use
NTLM over tcp/ip
|||If you are getting SSPI error, something is attempting to use
Kerberos...even if that was not your intention. This is more of an Active
Directory issue than SQL Server, so I'm pretty much at the end of my
knowledge base...
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"DBA72" <DBA72@.discussions.microsoft.com> wrote in message
news:6C11E262-B916-42BA-A294-A16FD71FE5C0@.microsoft.com...
>
> "Kevin3NF" wrote:
> Kevin,
> I think you would be right if I was trying to use Kerberos but as I said,
> this is not enabled for the sql service account. What I want to do is use
> NTLM over tcp/ip

cannot generate sspi context when server in mixed authentication m

Cannot generate sspi context

I am using Win2k server(sp4) and Sql 2000(sp4). When register from
enterprise manager by using windows authentication , it was showing 'cannot
generate sspi context'.
When I use FQDN to register, it work fine
Regards,
George.Did you check the event logs on the box where you are trying
to register SQL Server? Look especially for DNS issues,
possibly windows time service issues.
Did you try connecting with named pipes - if that's enabled
on the server?
-Sue
On Thu, 24 May 2007 03:51:00 -0700, George
<George@.discussions.microsoft.com> wrote:

>I am using Win2k server(sp4) and Sql 2000(sp4). When register from
>enterprise manager by using windows authentication , it was showing 'cannot
>generate sspi context'.
>When I use FQDN to register, it work fine
>Regards,
>George.|||Looks like a service principal name (SPN) registration issue! Can you try
troubleshooting steps as in below article ?
http://support.microsoft.com/kb/811889 - How to troubleshoot the "Cannot
generate SSPI context" error message

> enterprise manager by using windows authentication , it was showing 'canno
t
> generate sspi context'.
> When I use FQDN to register, it work fine

Cannot generate sspi context

I am using Win2k server(sp4) and Sql 2000(sp4). When register from
enterprise manager by using windows authentication , it was showing 'cannot
generate sspi context'.
When I use FQDN to register, it work fine
Regards,
George.
Did you check the event logs on the box where you are trying
to register SQL Server? Look especially for DNS issues,
possibly windows time service issues.
Did you try connecting with named pipes - if that's enabled
on the server?
-Sue
On Thu, 24 May 2007 03:51:00 -0700, George
<George@.discussions.microsoft.com> wrote:

>I am using Win2k server(sp4) and Sql 2000(sp4). When register from
>enterprise manager by using windows authentication , it was showing 'cannot
>generate sspi context'.
>When I use FQDN to register, it work fine
>Regards,
>George.
|||Looks like a service principal name (SPN) registration issue! Can you try
troubleshooting steps as in below article ?
http://support.microsoft.com/kb/811889 - How to troubleshoot the "Cannot
generate SSPI context" error message

> enterprise manager by using windows authentication , it was showing 'cannot
> generate sspi context'.
> When I use FQDN to register, it work fine

Sunday, February 12, 2012

Cannot generate SSPI context

We get the "Cannot generate SSPI context" error when trying to use Windows
Authentication. We are using SQL Server 2000 Standard Edition (SP3), and
Windows 2000 5.00.2195 (SP 4). We are using TCP/IP.
Could you please shed some light on why we have to use SQL Server
Authentication?
Thank you.
--
Mikehttp://support.microsoft.com/default.aspx?scid=kb;en-us;811889
"Mike" wrote:
> We get the "Cannot generate SSPI context" error when trying to use Windows
> Authentication. We are using SQL Server 2000 Standard Edition (SP3), and
> Windows 2000 5.00.2195 (SP 4). We are using TCP/IP.
> Could you please shed some light on why we have to use SQL Server
> Authentication?
> Thank you.
> --
> Mike

Tuesday, March 27, 2012

Cannot register server (LOCAL)

Cannot register server (LOCAL)

Cannot register server (LOCAL)

Cannot register local sql server

Tuesday, March 20, 2012

Cannot Open default Database. Login Failed. Problem

Sunday, March 11, 2012

Cannot login using Integrated Authentication

Cannot login to SQL Server 2005 using SQL Server Authentication

Cannot login to SQL Server 2005 using SQL Server Authentication

Cannot login SQL Server with 'sa'

Thursday, February 16, 2012

Cannot get AD groups to work in SQL 2k5

Tuesday, February 14, 2012

cannot generate sspi context when server in mixed authentication m

cannot generate sspi context when server in mixed authentication m

Cannot generate sspi context

Cannot generate sspi context

Sunday, February 12, 2012

Cannot generate SSPI context

Cannot find mdf files

Blog Archive

About Me