Can't get in to SQLServer 2005 express with a Privileged account

Bummer. I can't remember the SA password. I had setup a user account, but I can't change anything or add any new accounts using this login. I can't get in using the windows authentication method no matter how I am logged into this machine.

Any suggestions? I have never been able to use Windows Authentication. There must be something I'm missing here. I have spent hours and hours trying to get into this machine. I just want to replicate a database. This is very frustrating.

Thanks guys.

How are you connecting to SQL Server? On Express edition, Windows authentication should always work even if you are non-admin.

You can also try using Windows Authentication with a user account that is a machine admin.

Alternatively, members of this Windows Group: SQLServer2005MSSQLUSER$<machine_name>$<instance_name> should also have access. Please replace the <machine_name> and <instance_name> variables with the appropriate values for your installation. So if you add your Windows user to this group, you should also have access.

What error message are you seeing?

Sung

|||

It was telling me that I couldn't access the default database. I found where someone said to do:

sqlcmd -E -d master

That allowed me to get the SQLCMD prompt. I didn't know what to do after that. I found in the SQL Server 2005 Administrator's Pocket Consultant that you can make any user an administrator by issuing the command:

sp_addsrvrolemember 'login', 'sysadmin'

That did the trick. I was able to elevate the one login that I knew to sysadmin status. From there I had full access and privileges.

Thanks for your response.

Cant connect to sqlserver

I use connection string like that:
server=10.10.10.1;uid=xuser;pwd=xpasword;database= xdatabase;Connection
Timeout=60;Pooling=True;Min Pool Size=1;Max Pool Size=50
And I can't connect to the server.
when I connect to \\10.10.10.1\c$ with administrator rights then connection
to sqlserver (10.10.10.1) works.
What is wrong?
Remis
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Remis" <remiskaune@.kalnieciai.lt> schrieb im Newsbeitrag
news:OZpGYODaFHA.2900@.TK2MSFTNGP15.phx.gbl...
>I use connection string like that:
> server=10.10.10.1;uid=xuser;pwd=xpasword;database= xdatabase;Connection
> Timeout=60;Pooling=True;Min Pool Size=1;Max Pool Size=50
> And I can't connect to the server.
> when I connect to \\10.10.10.1\c$ with administrator rights then
> connection to sqlserver (10.10.10.1) works.
> What is wrong?
> Remis
>
|||Try to check out on what port your sqlserver is listening on and use this in
your connection string to connect to the server.Even the share c$ uses
another port than the sql server standard (or that you have defined) it
could be blocked by a firewall whereas the share access port isnt blocked.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Remis" <remiskaune@.kalnieciai.lt> schrieb im Newsbeitrag
news:OZpGYODaFHA.2900@.TK2MSFTNGP15.phx.gbl...
>I use connection string like that:
> server=10.10.10.1;uid=xuser;pwd=xpasword;database= xdatabase;Connection
> Timeout=60;Pooling=True;Min Pool Size=1;Max Pool Size=50
> And I can't connect to the server.
> when I connect to \\10.10.10.1\c$ with administrator rights then
> connection to sqlserver (10.10.10.1) works.
> What is wrong?
> Remis
>

Cant connect to sqlserver

I use connection string like that:
server=10.10.10. 1;uid=xuser;pwd=xpasword;database=xdatab
ase;Connection
Timeout=60;Pooling=True;Min Pool Size=1;Max Pool Size=50
And I can't connect to the server.
when I connect to \\10.10.10.1\c$ with administrator rights then connection
to sqlserver (10.10.10.1) works.
What is wrong?
RemisHTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"Remis" <remiskaune@.kalnieciai.lt> schrieb im Newsbeitrag
news:OZpGYODaFHA.2900@.TK2MSFTNGP15.phx.gbl...
>I use connection string like that:
> server=10.10.10. 1;uid=xuser;pwd=xpasword;database=xdatab
ase;Connection
> Timeout=60;Pooling=True;Min Pool Size=1;Max Pool Size=50
> And I can't connect to the server.
> when I connect to \\10.10.10.1\c$ with administrator rights then
> connection to sqlserver (10.10.10.1) works.
> What is wrong?
> Remis
>|||Try to check out on what port your sqlserver is listening on and use this in
your connection string to connect to the server.Even the share c$ uses
another port than the sql server standard (or that you have defined) it
could be blocked by a firewall whereas the share access port isnt blocked.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"Remis" <remiskaune@.kalnieciai.lt> schrieb im Newsbeitrag
news:OZpGYODaFHA.2900@.TK2MSFTNGP15.phx.gbl...
>I use connection string like that:
> server=10.10.10. 1;uid=xuser;pwd=xpasword;database=xdatab
ase;Connection
> Timeout=60;Pooling=True;Min Pool Size=1;Max Pool Size=50
> And I can't connect to the server.
> when I connect to \\10.10.10.1\c$ with administrator rights then
> connection to sqlserver (10.10.10.1) works.
> What is wrong?
> Remis
>

Can't Connect to SQL db

Going a bit crazy. Have sqlserver all installed and running. I have a
security problem I think- have read many other news posts that SOUND
similar but e.g. My SQL Server configuration manager doesnt seem to
have seccurity options let alone offer the possibility of allowing a
'mix' of SQL/ windows requests.

For logon in SQL Server configuration manager 'built- in account'
local system is selected rather than the 'this account' option which
has stars in the password field and no username options.

This is myconnection string: kris\ is this local machine

myConnection = New SqlConnection("server=kris
\SQLEXPRESS;uid=sa;pwd=;database=pubs")

This is the error I get
System.Data.SqlClient.SqlException was unhandled
Class=14
ErrorCode=-2146232060
LineNumber=65536
Message="Login failed for user 'sa'. The user is not associated with
a trusted SQL Server connection."
Number=18452
Procedure=""
Server="kris\SQLEXPRESS"

Any ideas?DanWeaver (danofweaver@.googlemail.com) writes:

Quote:

Originally Posted by

This is myconnection string: kris\ is this local machine
>
myConnection = New SqlConnection("server=kris
\SQLEXPRESS;uid=sa;pwd=;database=pubs")
>
This is the error I get
System.Data.SqlClient.SqlException was unhandled
Class=14
ErrorCode=-2146232060
LineNumber=65536
Message="Login failed for user 'sa'. The user is not associated with
a trusted SQL Server connection."
Number=18452
Procedure=""
Server="kris\SQLEXPRESS"

Have you enabled you server for SQL authetnication? By default,
SQL Server permits only Window authentication.

Do you have any particular reason you want to use SQL authentication?
Else, change "uid=sa;pwd=" to "Integrated Security=SSPI".

Quote:

Originally Posted by

For logon in SQL Server configuration manager 'built- in account'
local system is selected rather than the 'this account' option which
has stars in the password field and no username options.

Note that his is about how SQL Server logs into Windows. That's a
different thing.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||

Quote:

Originally Posted by

Do you have any particular reason you want to use SQL authentication?
Else, change "uid=sa;pwd=" to "Integrated Security=SSPI".

Thanks, Erland. That helped move me on- in fact the first time I tried
it it seemed to work (though my record was not added- posibly as there
already existed a record with same id) Anyway- I cant experiment with
that cos shorlty after I could no longer connect- seems strange- I
checked the table after first successful run to see if it had updated
and ran the code again- got a message "another process is locking the
db"- great I thought- all is working- and closed the connection in
VS-
now though the connection gets stuck at login and says:

Cannot open database "pubs" requested by the login. The login failed.
Login failed for user 'KRISLAPTOP\Kris'.|||DanWeaver (danofweaver@.googlemail.com) writes:

Quote:

Originally Posted by

Quote:

Originally Posted by

>Do you have any particular reason you want to use SQL authentication?
>Else, change "uid=sa;pwd=" to "Integrated Security=SSPI".

>
Thanks, Erland. That helped move me on- in fact the first time I tried
it it seemed to work (though my record was not added- posibly as there
already existed a record with same id) Anyway- I cant experiment with
that cos shorlty after I could no longer connect- seems strange- I
checked the table after first successful run to see if it had updated
and ran the code again- got a message "another process is locking the
db"- great I thought- all is working- and closed the connection in
VS-
now though the connection gets stuck at login and says:
>
Cannot open database "pubs" requested by the login. The login failed.
Login failed for user 'KRISLAPTOP\Kris'.

Seems like that either your user is not present in the pubs database,
or the database has somehow gone away.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Thanks, Erland. Something fishy was ocurring with the dbs- deleted
them and reconnected and set permissions again- seems to work now.

Cheers, more challenging questions (when I am more informed!) will
probably follow.

Dan

Quote:

Originally Posted by

Seems like that either your user is not present in the pubs database,
or the database has somehow gone away.
>
--
Erland Sommarskog, SQL Server MVP, esq...@.sommarskog.se
>
Books Online for SQL Server 2005 athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
Books Online for SQL Server 2000 athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

Can't connect to mssql

Hi
I installed ASP and MSSQL(SQL Express Edition, SQL Manager 2005 for SQL
Server Lite).
- ASP is runnig correctly
- With SQL Manager 2005 for SQL I can create Databases and tabels and some
records...
I can not connect from an ASP script (example follows at the end). I've get
an error message in the internet explorer (after loading my asp script):
"Technical Information (for support personnel)
Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user 'sa'.
The user is not associated with a trusted SQL Server connection.
/index.asp, line 22
Browser Type:
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; InfoPath.1; .NET
CLR 2.0.50727)
Page:
GET /index.asp
Time:
Freitag, 29. September 2006, 09:13:42
More information:
Microsoft Support "
I've looked at this site:
http://support.microsoft.com/defaul...kb;en-us;555332 but it
doesn't help me cause I cant find the properties of the Resulution.
I've got no idea what else I can do Hopfully you understanding my crap
english;)
Thanks for helping!
Pascal Suter
By the way I was talking about this asp script:
<% OPTION EXPLICIT %>
<%
'declare the variables
Dim Connection
Dim ConnString
Dim Recordset
Dim SQL
'define the connection string, specify database driver
ConnString="DRIVER=SQL Server;SERVER=localhost\SQLEXPRESS;UID=s
a;" & _
"PWD=;DATABASE=master"
'declare the SQL statement that will query the database
SQL= "SELECT test FROM test"
'create an instance of the ADO connection and recordset objects
Set Connection = Server.CreateObject("ADODB.Connection")
Set Recordset = Server.CreateObject("ADODB.Recordset")
'Open the connection to the database
Connection.Open ConnString
'Open the recordset object executing the SQL statement and return records
Recordset.Open SQL,Connection
'first of all determine whether there are any records
If Recordset.EOF Then
Response.Write("No records returned.")
Else
'if there are records then loop through the fields
Do While NOT Recordset.Eof
Response.write Recordset("test")
Response.write "<br>"
Recordset.MoveNext
Loop
End If
'close the connection and recordset objects to free up resources
Recordset.Close
Set Recordset=nothing
Connection.Close
Set Connection=nothing
%>YOu have only Windows Authentication enbaled but you are using a SQL
user in your connection string. Either use integrated authentication or
switch to Mixed mode. More details on that on my website under the
screencasts sections
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
--|||Jens schrieb:

> YOu have only Windows Authentication enbaled but you are using a SQL
> user in your connection string. Either use integrated authentication or
> switch to Mixed mode. More details on that on my website under the
> screencasts sections
Thanks for your help. But it's exactly the same problem like in my link
below. There's a different program then I have. Unfortunatly I can't find
this settings. Probably the not exists? I have really no idea how I can fix
it|||Jens schrieb:

> YOu have only Windows Authentication enbaled but you are using a SQL
> user in your connection string. Either use integrated authentication or
> switch to Mixed mode. More details on that on my website under the
> screencasts sections
> HTH, Jens K. Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
I've done this change, but if I want login on Microsoft SQL Server
Management Studio Express the login fails. Where can I change/create Login
names and permissions?
thanks for your help
Pascal Suter|||Am I something like a selfentertainer?;) However, I found a solution for my
problem but acutally your link was the key!
great thanks
Pascal Suter|||I am having the same problem, I did look in the registry but did not find
anything that would help me. I wish you would have expanded upon your last
post to explain what you actually did to solve the problem. I think what yo
u
did will solve my problem also.
"Suter" wrote:

> Am I something like a selfentertainer?;) However, I found a solution for m
y
> problem but acutally your link was the key!
> great thanks
> Pascal Suter
>

Can't connect to mssql

Hi
I installed ASP and MSSQL(SQL Express Edition, SQL Manager 2005 for SQL
Server Lite).
- ASP is runnig correctly
- With SQL Manager 2005 for SQL I can create Databases and tabels and some
records...
I can not connect from an ASP script (example follows at the end). I've get
an error message in the internet explorer (after loading my asp script):
"Technical Information (for support personnel)
Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'sa'.
The user is not associated with a trusted SQL Server connection.
/index.asp, line 22
Browser Type:
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; InfoPath.1; .NET
CLR 2.0.50727)
Page:
GET /index.asp
Time:
Freitag, 29. September 2006, 09:13:42
More information:
Microsoft Support "
I've looked at this site:
http://support.microsoft.com/default...b;en-us;555332 but it
doesn't help me cause I cant find the properties of the Resulution.
I've got no idea what else I can do Hopfully you understanding my crap
english;)
Thanks for helping!
Pascal Suter
By the way I was talking about this asp script:
<% OPTION EXPLICIT %>
<%
'declare the variables
Dim Connection
Dim ConnString
Dim Recordset
Dim SQL
'define the connection string, specify database driver
ConnString="DRIVER=SQL Server;SERVER=localhost\SQLEXPRESS;UID=sa;" & _
"PWD=;DATABASE=master"
'declare the SQL statement that will query the database
SQL= "SELECT test FROM test"
'create an instance of the ADO connection and recordset objects
Set Connection = Server.CreateObject("ADODB.Connection")
Set Recordset = Server.CreateObject("ADODB.Recordset")
'Open the connection to the database
Connection.Open ConnString
'Open the recordset object executing the SQL statement and return records
Recordset.Open SQL,Connection
'first of all determine whether there are any records
If Recordset.EOF Then
Response.Write("No records returned.")
Else
'if there are records then loop through the fields
Do While NOT Recordset.Eof
Response.write Recordset("test")
Response.write "<br>"
Recordset.MoveNext
Loop
End If
'close the connection and recordset objects to free up resources
Recordset.Close
Set Recordset=nothing
Connection.Close
Set Connection=nothing
%>
YOu have only Windows Authentication enbaled but you are using a SQL
user in your connection string. Either use integrated authentication or
switch to Mixed mode. More details on that on my website under the
screencasts sections
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||Jens schrieb:

> YOu have only Windows Authentication enbaled but you are using a SQL
> user in your connection string. Either use integrated authentication or
> switch to Mixed mode. More details on that on my website under the
> screencasts sections
Thanks for your help. But it's exactly the same problem like in my link
below. There's a different program then I have. Unfortunatly I can't find
this settings. Probably the not exists? I have really no idea how I can fix
it
|||Jens schrieb:

> YOu have only Windows Authentication enbaled but you are using a SQL
> user in your connection string. Either use integrated authentication or
> switch to Mixed mode. More details on that on my website under the
> screencasts sections
> HTH, Jens K. Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
I've done this change, but if I want login on Microsoft SQL Server
Management Studio Express the login fails. Where can I change/create Login
names and permissions?
thanks for your help
Pascal Suter
|||Am I something like a selfentertainer?;) However, I found a solution for my
problem but acutally your link was the key!
great thanks
Pascal Suter

Can't connect to database due to Windows authentication

I am using SQLServer 2000 and for reasons unknown the name of the server got
changed so that it did not match the name of the machine. I discovered this
when our application could not connect to the database.
I changed the servername using:
exec sp_dropserver 'SSM_6000_A', 'droplogins'
exec sp_addserver 'SSM_6000_C', 'local'
I stopped and started the server and when I checked the name of the server
using
SELECT @.@.SERVERNAME
I got the correct name, SSM_6000_C
I still could not connect to the database but I thought I had to recreate
the logins.
I deleted one of the users and logins and tried to recreate it and I get the
error:
"ERROR15401: WindowsNT user or group 'user-name' not found. Check
the name again."
The server is on our network. I can go to folders, etc. on the network once
I log in using my network account.
What is wrong?
Is there someplace within SQLServer that did not get the server name change?
Where can I check?
I went to a DTS package and was configuring a query in an Execute SQL Task
and the server name was the old name.
Thanks for your help!!
Gloria
To create new logins you can use EM, but login are only existing windows
user names, so if you use windows only authentication, you can add only
existing windows user names for new logins.
Regards,
Daniel
"Gloria" <Gloria@.discussions.microsoft.com> wrote in message
news:B17D383B-15DC-40C7-92EB-8A2F5B3CEB60@.microsoft.com...
> I am using SQLServer 2000 and for reasons unknown the name of the server
got
> changed so that it did not match the name of the machine. I discovered
this
> when our application could not connect to the database.
> I changed the servername using:
> exec sp_dropserver 'SSM_6000_A', 'droplogins'
> exec sp_addserver 'SSM_6000_C', 'local'
> I stopped and started the server and when I checked the name of the server
> using
> SELECT @.@.SERVERNAME
> I got the correct name, SSM_6000_C
> I still could not connect to the database but I thought I had to recreate
> the logins.
> I deleted one of the users and logins and tried to recreate it and I get
the
> error:
> "ERROR15401: WindowsNT user or group 'user-name' not found. Check
> the name again."
> The server is on our network. I can go to folders, etc. on the network
once
> I log in using my network account.
> What is wrong?
> Is there someplace within SQLServer that did not get the server name
change?
> Where can I check?
> I went to a DTS package and was configuring a query in an Execute SQL Task
> and the server name was the old name.
> Thanks for your help!!
> Gloria
>
|||Hi Daniel,
I only want to create user names from Windows logins. The problem is EM
won't let me create Windows logins.
When I try to create a new login by picking a name from the domain list, I
get the error message:
"Error15401:WindowsNT user or group 'domain\user_name' not found.
Check the name again."
I checked the servername to make sure after I changed it that if matches the
machine name and it does. Is it possible that somewhere in the bowels of
SQLServer the servername did not get changed and this mismatch is causing the
problem?
If so, how can I check this?
Does it check in the registry somewhere the name of the server?
Thanks again,
Gloria
"Daniel Joskovski" wrote:

> To create new logins you can use EM, but login are only existing windows
> user names, so if you use windows only authentication, you can add only
> existing windows user names for new logins.
> Regards,
> Daniel
> "Gloria" <Gloria@.discussions.microsoft.com> wrote in message
> news:B17D383B-15DC-40C7-92EB-8A2F5B3CEB60@.microsoft.com...
> got
> this
> the
> once
> change?
>
>
|||Hi
You could also try to take the server out of your domain, and then join it
to the domain again. Sometimes you have to take a server out of the domain
before it's properly "connected" to the AD again - especially when you mess
around with servernames.
Regards
Steen
Gloria wrote:[vbcol=seagreen]
> Hi Daniel,
> I only want to create user names from Windows logins. The problem is
> EM won't let me create Windows logins.
> When I try to create a new login by picking a name from the domain
> list, I get the error message:
> "Error15401:WindowsNT user or group 'domain\user_name' not found.
> Check the name again."
> I checked the servername to make sure after I changed it that if
> matches the machine name and it does. Is it possible that somewhere
> in the bowels of SQLServer the servername did not get changed and
> this mismatch is causing the problem?
> If so, how can I check this?
> Does it check in the registry somewhere the name of the server?
> Thanks again,
> Gloria
> "Daniel Joskovski" wrote:
|||Hi
What do you mean by "taking the server out of the domain"? Does our Network
Adminstrator have to take it off of the network and then add it again?
I can connect to our company network using the computer the SQL Server is on
but the SQL Server does not recognize it. Is there a way I can disconnect
then reconnect just the SQL Server?
Is this what typically happens when you change the servername?
What is the correct procedure?
Thanks,
Gloria
"Steen Persson" wrote:

> Hi
> You could also try to take the server out of your domain, and then join it
> to the domain again. Sometimes you have to take a server out of the domain
> before it's properly "connected" to the AD again - especially when you mess
> around with servernames.
> Regards
> Steen
> Gloria wrote:
>
>
|||Hi Gloria
You might have to have your network administrator to do this. It will
require an account that has admin priveledges on your domain.
I don't know if there is a "correct procedure" for changing a servername,
but generally I'd take the server out of the domain - change the name and
then join the server to the domain again. This is not only relevant for
SQLServer, but for every kind of servers. In some cases you can get away
with just renaming the server while it's still a member of the domain, but
in some cases you see weird things and problems afterwards. Therefore I
prefer to do the steps above.
IMHO you shouldn't change a servername without knowing the consequences it
can have on the network. If you don't know about how to remove and join a
server to/from a Domain, I think you should leave the name change to
somebody else...:-).
Regards
Steen
Gloria wrote:[vbcol=seagreen]
> Hi
> What do you mean by "taking the server out of the domain"? Does our
> Network Adminstrator have to take it off of the network and then add
> it again?
> I can connect to our company network using the computer the SQL
> Server is on but the SQL Server does not recognize it. Is there a
> way I can disconnect then reconnect just the SQL Server?
> Is this what typically happens when you change the servername?
> What is the correct procedure?
> Thanks,
> Gloria
> "Steen Persson" wrote:
|||Hi,
I agree that you should not change things without knowing the consequences
but when you are trying to fix a problem and the documentation is inadequate,
you do the best you can.
The original problem was that our application could not connect to the
database. I discovered that the machine name and the SQLServer name did not
match. Now the computer that has SQLServer is connected to the network and
works fine. The domain is recognized by the computer. Changing the server
name to match the machine name should allow the network domain to be
recognized by SQLServer, shouldn't it?
When you select Windows authentication and the network domain and user names
are shown, where is this coming from?
Doesn't SQLServer use the same information when connecting to the network as
the computer does?
Thanks,
Gloria
"Steen Persson" wrote:

> Hi Gloria
> You might have to have your network administrator to do this. It will
> require an account that has admin priveledges on your domain.
> I don't know if there is a "correct procedure" for changing a servername,
> but generally I'd take the server out of the domain - change the name and
> then join the server to the domain again. This is not only relevant for
> SQLServer, but for every kind of servers. In some cases you can get away
> with just renaming the server while it's still a member of the domain, but
> in some cases you see weird things and problems afterwards. Therefore I
> prefer to do the steps above.
> IMHO you shouldn't change a servername without knowing the consequences it
> can have on the network. If you don't know about how to remove and join a
> server to/from a Domain, I think you should leave the name change to
> somebody else...:-).
> Regards
> Steen
>
> Gloria wrote:
>
>
|||Hi
Since your problem is with the NTAuthentication and Domain name, it could
very well be that the server and/or Domain Controller isn't in "sync". Since
there has been messed with the servernames, the first thing I'd try would be
to re-join the server to the domain. In the AD you have a lot of pointers
and settings (DNS, SPN, WINS etc.) that holds a servername. If you just
change a servername when the server are in the Domain, some of these might
not be correctly updated where others will. This can very well cause a
number of weird issues that isn't explainable. When you take the server out
of the domain, the AD will remove all the references to the "old"
servername. When you then join the server back into the domain with the new
name, it will be correctly updated throughout the entire domain and all
pointers and references will be refreshed to reflect the new name.
It might not be the reason or solution in your case, but it's quite easy to
do so it would definately do one the first thing I'd try.
Regards
Steen
Gloria wrote:[vbcol=seagreen]
> Hi,
> I agree that you should not change things without knowing the
> consequences but when you are trying to fix a problem and the
> documentation is inadequate, you do the best you can.
> The original problem was that our application could not connect to the
> database. I discovered that the machine name and the SQLServer name
> did not match. Now the computer that has SQLServer is connected to
> the network and works fine. The domain is recognized by the
> computer. Changing the server name to match the machine name should
> allow the network domain to be recognized by SQLServer, shouldn't it?
> When you select Windows authentication and the network domain and
> user names are shown, where is this coming from?
> Doesn't SQLServer use the same information when connecting to the
> network as the computer does?
> Thanks,
> Gloria
> "Steen Persson" wrote:
|||Hi Steen,
Many, many thanks. Worked like a charm!!
Gloria
"Steen Persson" wrote:

> Hi
> Since your problem is with the NTAuthentication and Domain name, it could
> very well be that the server and/or Domain Controller isn't in "sync". Since
> there has been messed with the servernames, the first thing I'd try would be
> to re-join the server to the domain. In the AD you have a lot of pointers
> and settings (DNS, SPN, WINS etc.) that holds a servername. If you just
> change a servername when the server are in the Domain, some of these might
> not be correctly updated where others will. This can very well cause a
> number of weird issues that isn't explainable. When you take the server out
> of the domain, the AD will remove all the references to the "old"
> servername. When you then join the server back into the domain with the new
> name, it will be correctly updated throughout the entire domain and all
> pointers and references will be refreshed to reflect the new name.
> It might not be the reason or solution in your case, but it's quite easy to
> do so it would definately do one the first thing I'd try.
> Regards
> Steen
> Gloria wrote:
>
>

Can't connect to database due to Windows authentication

I am using SQLServer 2000 and for reasons unknown the name of the server got
changed so that it did not match the name of the machine. I discovered this
when our application could not connect to the database.
I changed the servername using:
exec sp_dropserver 'SSM_6000_A', 'droplogins'
exec sp_addserver 'SSM_6000_C', 'local'
I stopped and started the server and when I checked the name of the server
using
SELECT @.@.SERVERNAME
I got the correct name, SSM_6000_C
I still could not connect to the database but I thought I had to recreate
the logins.
I deleted one of the users and logins and tried to recreate it and I get the
error:
"ERROR15401: WindowsNT user or group 'user-name' not found. Check
the name again."
The server is on our network. I can go to folders, etc. on the network once
I log in using my network account.
What is wrong?
Is there someplace within SQLServer that did not get the server name change?
Where can I check?
I went to a DTS package and was configuring a query in an Execute SQL Task
and the server name was the old name.
Thanks for your help!!
GloriaTo create new logins you can use EM, but login are only existing windows
user names, so if you use windows only authentication, you can add only
existing windows user names for new logins.
Regards,
Daniel
"Gloria" <Gloria@.discussions.microsoft.com> wrote in message
news:B17D383B-15DC-40C7-92EB-8A2F5B3CEB60@.microsoft.com...
> I am using SQLServer 2000 and for reasons unknown the name of the server
got
> changed so that it did not match the name of the machine. I discovered
this
> when our application could not connect to the database.
> I changed the servername using:
> exec sp_dropserver 'SSM_6000_A', 'droplogins'
> exec sp_addserver 'SSM_6000_C', 'local'
> I stopped and started the server and when I checked the name of the server
> using
> SELECT @.@.SERVERNAME
> I got the correct name, SSM_6000_C
> I still could not connect to the database but I thought I had to recreate
> the logins.
> I deleted one of the users and logins and tried to recreate it and I get
the
> error:
> "ERROR15401: WindowsNT user or group 'user-name' not found. Check
> the name again."
> The server is on our network. I can go to folders, etc. on the network
once
> I log in using my network account.
> What is wrong?
> Is there someplace within SQLServer that did not get the server name
change?
> Where can I check?
> I went to a DTS package and was configuring a query in an Execute SQL Task
> and the server name was the old name.
> Thanks for your help!!
> Gloria
>|||Hi Daniel,
I only want to create user names from Windows logins. The problem is EM
won't let me create Windows logins.
When I try to create a new login by picking a name from the domain list, I
get the error message:
"Error15401:WindowsNT user or group 'domain\user_name' not found.
Check the name again."
I checked the servername to make sure after I changed it that if matches the
machine name and it does. Is it possible that somewhere in the bowels of
SQLServer the servername did not get changed and this mismatch is causing th
e
problem?
If so, how can I check this?
Does it check in the registry somewhere the name of the server?
Thanks again,
Gloria
"Daniel Joskovski" wrote:

> To create new logins you can use EM, but login are only existing windows
> user names, so if you use windows only authentication, you can add only
> existing windows user names for new logins.
> Regards,
> Daniel
> "Gloria" <Gloria@.discussions.microsoft.com> wrote in message
> news:B17D383B-15DC-40C7-92EB-8A2F5B3CEB60@.microsoft.com...
> got
> this
> the
> once
> change?
>
>|||Hi
You could also try to take the server out of your domain, and then join it
to the domain again. Sometimes you have to take a server out of the domain
before it's properly "connected" to the AD again - especially when you mess
around with servernames.
Regards
Steen
Gloria wrote:[vbcol=seagreen]
> Hi Daniel,
> I only want to create user names from Windows logins. The problem is
> EM won't let me create Windows logins.
> When I try to create a new login by picking a name from the domain
> list, I get the error message:
> "Error15401:WindowsNT user or group 'domain\user_name' not found.
> Check the name again."
> I checked the servername to make sure after I changed it that if
> matches the machine name and it does. Is it possible that somewhere
> in the bowels of SQLServer the servername did not get changed and
> this mismatch is causing the problem?
> If so, how can I check this?
> Does it check in the registry somewhere the name of the server?
> Thanks again,
> Gloria
> "Daniel Joskovski" wrote:
>|||Hi
What do you mean by "taking the server out of the domain"? Does our Network
Adminstrator have to take it off of the network and then add it again?
I can connect to our company network using the computer the SQL Server is on
but the SQL Server does not recognize it. Is there a way I can disconnect
then reconnect just the SQL Server?
Is this what typically happens when you change the servername?
What is the correct procedure?
Thanks,
Gloria
"Steen Persson" wrote:

> Hi
> You could also try to take the server out of your domain, and then join it
> to the domain again. Sometimes you have to take a server out of the domain
> before it's properly "connected" to the AD again - especially when you mes
s
> around with servernames.
> Regards
> Steen
> Gloria wrote:
>
>|||Hi Gloria
You might have to have your network administrator to do this. It will
require an account that has admin priveledges on your domain.
I don't know if there is a "correct procedure" for changing a servername,
but generally I'd take the server out of the domain - change the name and
then join the server to the domain again. This is not only relevant for
SQLServer, but for every kind of servers. In some cases you can get away
with just renaming the server while it's still a member of the domain, but
in some cases you see weird things and problems afterwards. Therefore I
prefer to do the steps above.
IMHO you shouldn't change a servername without knowing the consequences it
can have on the network. If you don't know about how to remove and join a
server to/from a Domain, I think you should leave the name change to
somebody else...:-).
Regards
Steen
Gloria wrote:[vbcol=seagreen]
> Hi
> What do you mean by "taking the server out of the domain"? Does our
> Network Adminstrator have to take it off of the network and then add
> it again?
> I can connect to our company network using the computer the SQL
> Server is on but the SQL Server does not recognize it. Is there a
> way I can disconnect then reconnect just the SQL Server?
> Is this what typically happens when you change the servername?
> What is the correct procedure?
> Thanks,
> Gloria
> "Steen Persson" wrote:
>|||Hi,
I agree that you should not change things without knowing the consequences
but when you are trying to fix a problem and the documentation is inadequate
,
you do the best you can.
The original problem was that our application could not connect to the
database. I discovered that the machine name and the SQLServer name did not
match. Now the computer that has SQLServer is connected to the network and
works fine. The domain is recognized by the computer. Changing the server
name to match the machine name should allow the network domain to be
recognized by SQLServer, shouldn't it?
When you select Windows authentication and the network domain and user names
are shown, where is this coming from?
Doesn't SQLServer use the same information when connecting to the network as
the computer does?
Thanks,
Gloria
"Steen Persson" wrote:

> Hi Gloria
> You might have to have your network administrator to do this. It will
> require an account that has admin priveledges on your domain.
> I don't know if there is a "correct procedure" for changing a servername,
> but generally I'd take the server out of the domain - change the name and
> then join the server to the domain again. This is not only relevant for
> SQLServer, but for every kind of servers. In some cases you can get away
> with just renaming the server while it's still a member of the domain, but
> in some cases you see weird things and problems afterwards. Therefore I
> prefer to do the steps above.
> IMHO you shouldn't change a servername without knowing the consequences it
> can have on the network. If you don't know about how to remove and join a
> server to/from a Domain, I think you should leave the name change to
> somebody else...:-).
> Regards
> Steen
>
> Gloria wrote:
>
>|||Hi
Since your problem is with the NTAuthentication and Domain name, it could
very well be that the server and/or Domain Controller isn't in "sync". Since
there has been messed with the servernames, the first thing I'd try would be
to re-join the server to the domain. In the AD you have a lot of pointers
and settings (DNS, SPN, WINS etc.) that holds a servername. If you just
change a servername when the server are in the Domain, some of these might
not be correctly updated where others will. This can very well cause a
number of weird issues that isn't explainable. When you take the server out
of the domain, the AD will remove all the references to the "old"
servername. When you then join the server back into the domain with the new
name, it will be correctly updated throughout the entire domain and all
pointers and references will be refreshed to reflect the new name.
It might not be the reason or solution in your case, but it's quite easy to
do so it would definately do one the first thing I'd try.
Regards
Steen
Gloria wrote:[vbcol=seagreen]
> Hi,
> I agree that you should not change things without knowing the
> consequences but when you are trying to fix a problem and the
> documentation is inadequate, you do the best you can.
> The original problem was that our application could not connect to the
> database. I discovered that the machine name and the SQLServer name
> did not match. Now the computer that has SQLServer is connected to
> the network and works fine. The domain is recognized by the
> computer. Changing the server name to match the machine name should
> allow the network domain to be recognized by SQLServer, shouldn't it?
> When you select Windows authentication and the network domain and
> user names are shown, where is this coming from?
> Doesn't SQLServer use the same information when connecting to the
> network as the computer does?
> Thanks,
> Gloria
> "Steen Persson" wrote:
>|||Hi Steen,
Many, many thanks. Worked like a charm!!
Gloria
"Steen Persson" wrote:

> Hi
> Since your problem is with the NTAuthentication and Domain name, it could
> very well be that the server and/or Domain Controller isn't in "sync". Sin
ce
> there has been messed with the servernames, the first thing I'd try would
be
> to re-join the server to the domain. In the AD you have a lot of pointers
> and settings (DNS, SPN, WINS etc.) that holds a servername. If you just
> change a servername when the server are in the Domain, some of these might
> not be correctly updated where others will. This can very well cause a
> number of weird issues that isn't explainable. When you take the server ou
t
> of the domain, the AD will remove all the references to the "old"
> servername. When you then join the server back into the domain with the ne
w
> name, it will be correctly updated throughout the entire domain and all
> pointers and references will be refreshed to reflect the new name.
> It might not be the reason or solution in your case, but it's quite easy t
o
> do so it would definately do one the first thing I'd try.
> Regards
> Steen
> Gloria wrote:
>
>

Can't connect to database due to Windows authentication

I am using SQLServer 2000 and for reasons unknown the name of the server got
changed so that it did not match the name of the machine. I discovered this
when our application could not connect to the database.
I changed the servername using:
exec sp_dropserver 'SSM_6000_A', 'droplogins'
exec sp_addserver 'SSM_6000_C', 'local'
I stopped and started the server and when I checked the name of the server
using
SELECT @.@.SERVERNAME
I got the correct name, SSM_6000_C
I still could not connect to the database but I thought I had to recreate
the logins.
I deleted one of the users and logins and tried to recreate it and I get the
error:
"ERROR15401: WindowsNT user or group 'user-name' not found. Check
the name again."
The server is on our network. I can go to folders, etc. on the network once
I log in using my network account.
What is wrong?
Is there someplace within SQLServer that did not get the server name change?
Where can I check?
I went to a DTS package and was configuring a query in an Execute SQL Task
and the server name was the old name.
Thanks for your help!!
GloriaTo create new logins you can use EM, but login are only existing windows
user names, so if you use windows only authentication, you can add only
existing windows user names for new logins.
Regards,
Daniel
"Gloria" <Gloria@.discussions.microsoft.com> wrote in message
news:B17D383B-15DC-40C7-92EB-8A2F5B3CEB60@.microsoft.com...
> I am using SQLServer 2000 and for reasons unknown the name of the server
got
> changed so that it did not match the name of the machine. I discovered
this
> when our application could not connect to the database.
> I changed the servername using:
> exec sp_dropserver 'SSM_6000_A', 'droplogins'
> exec sp_addserver 'SSM_6000_C', 'local'
> I stopped and started the server and when I checked the name of the server
> using
> SELECT @.@.SERVERNAME
> I got the correct name, SSM_6000_C
> I still could not connect to the database but I thought I had to recreate
> the logins.
> I deleted one of the users and logins and tried to recreate it and I get
the
> error:
> "ERROR15401: WindowsNT user or group 'user-name' not found. Check
> the name again."
> The server is on our network. I can go to folders, etc. on the network
once
> I log in using my network account.
> What is wrong?
> Is there someplace within SQLServer that did not get the server name
change?
> Where can I check?
> I went to a DTS package and was configuring a query in an Execute SQL Task
> and the server name was the old name.
> Thanks for your help!!
> Gloria
>|||Hi Daniel,
I only want to create user names from Windows logins. The problem is EM
won't let me create Windows logins.
When I try to create a new login by picking a name from the domain list, I
get the error message:
"Error15401:WindowsNT user or group 'domain\user_name' not found.
Check the name again."
I checked the servername to make sure after I changed it that if matches the
machine name and it does. Is it possible that somewhere in the bowels of
SQLServer the servername did not get changed and this mismatch is causing the
problem?
If so, how can I check this?
Does it check in the registry somewhere the name of the server?
Thanks again,
Gloria
"Daniel Joskovski" wrote:
> To create new logins you can use EM, but login are only existing windows
> user names, so if you use windows only authentication, you can add only
> existing windows user names for new logins.
> Regards,
> Daniel
> "Gloria" <Gloria@.discussions.microsoft.com> wrote in message
> news:B17D383B-15DC-40C7-92EB-8A2F5B3CEB60@.microsoft.com...
> > I am using SQLServer 2000 and for reasons unknown the name of the server
> got
> > changed so that it did not match the name of the machine. I discovered
> this
> > when our application could not connect to the database.
> > I changed the servername using:
> > exec sp_dropserver 'SSM_6000_A', 'droplogins'
> > exec sp_addserver 'SSM_6000_C', 'local'
> > I stopped and started the server and when I checked the name of the server
> > using
> > SELECT @.@.SERVERNAME
> > I got the correct name, SSM_6000_C
> > I still could not connect to the database but I thought I had to recreate
> > the logins.
> >
> > I deleted one of the users and logins and tried to recreate it and I get
> the
> > error:
> > "ERROR15401: WindowsNT user or group 'user-name' not found. Check
> > the name again."
> >
> > The server is on our network. I can go to folders, etc. on the network
> once
> > I log in using my network account.
> >
> > What is wrong?
> > Is there someplace within SQLServer that did not get the server name
> change?
> > Where can I check?
> >
> > I went to a DTS package and was configuring a query in an Execute SQL Task
> > and the server name was the old name.
> >
> > Thanks for your help!!
> > Gloria
> >
>
>|||Hi
You could also try to take the server out of your domain, and then join it
to the domain again. Sometimes you have to take a server out of the domain
before it's properly "connected" to the AD again - especially when you mess
around with servernames.
Regards
Steen
Gloria wrote:
> Hi Daniel,
> I only want to create user names from Windows logins. The problem is
> EM won't let me create Windows logins.
> When I try to create a new login by picking a name from the domain
> list, I get the error message:
> "Error15401:WindowsNT user or group 'domain\user_name' not found.
> Check the name again."
> I checked the servername to make sure after I changed it that if
> matches the machine name and it does. Is it possible that somewhere
> in the bowels of SQLServer the servername did not get changed and
> this mismatch is causing the problem?
> If so, how can I check this?
> Does it check in the registry somewhere the name of the server?
> Thanks again,
> Gloria
> "Daniel Joskovski" wrote:
>> To create new logins you can use EM, but login are only existing
>> windows user names, so if you use windows only authentication, you
>> can add only existing windows user names for new logins.
>> Regards,
>> Daniel
>> "Gloria" <Gloria@.discussions.microsoft.com> wrote in message
>> news:B17D383B-15DC-40C7-92EB-8A2F5B3CEB60@.microsoft.com...
>> I am using SQLServer 2000 and for reasons unknown the name of the
>> server got changed so that it did not match the name of the
>> machine. I discovered this when our application could not connect
>> to the database.
>> I changed the servername using:
>> exec sp_dropserver 'SSM_6000_A', 'droplogins'
>> exec sp_addserver 'SSM_6000_C', 'local'
>> I stopped and started the server and when I checked the name of the
>> server using
>> SELECT @.@.SERVERNAME
>> I got the correct name, SSM_6000_C
>> I still could not connect to the database but I thought I had to
>> recreate the logins.
>> I deleted one of the users and logins and tried to recreate it and
>> I get the error:
>> "ERROR15401: WindowsNT user or group 'user-name' not found.
>> Check the name again."
>> The server is on our network. I can go to folders, etc. on the
>> network once I log in using my network account.
>> What is wrong?
>> Is there someplace within SQLServer that did not get the server
>> name change? Where can I check?
>> I went to a DTS package and was configuring a query in an Execute
>> SQL Task and the server name was the old name.
>> Thanks for your help!!
>> Gloria|||Hi
What do you mean by "taking the server out of the domain"? Does our Network
Adminstrator have to take it off of the network and then add it again?
I can connect to our company network using the computer the SQL Server is on
but the SQL Server does not recognize it. Is there a way I can disconnect
then reconnect just the SQL Server?
Is this what typically happens when you change the servername?
What is the correct procedure?
Thanks,
Gloria
"Steen Persson" wrote:
> Hi
> You could also try to take the server out of your domain, and then join it
> to the domain again. Sometimes you have to take a server out of the domain
> before it's properly "connected" to the AD again - especially when you mess
> around with servernames.
> Regards
> Steen
> Gloria wrote:
> > Hi Daniel,
> > I only want to create user names from Windows logins. The problem is
> > EM won't let me create Windows logins.
> > When I try to create a new login by picking a name from the domain
> > list, I get the error message:
> > "Error15401:WindowsNT user or group 'domain\user_name' not found.
> > Check the name again."
> >
> > I checked the servername to make sure after I changed it that if
> > matches the machine name and it does. Is it possible that somewhere
> > in the bowels of SQLServer the servername did not get changed and
> > this mismatch is causing the problem?
> > If so, how can I check this?
> > Does it check in the registry somewhere the name of the server?
> >
> > Thanks again,
> > Gloria
> >
> > "Daniel Joskovski" wrote:
> >
> >> To create new logins you can use EM, but login are only existing
> >> windows user names, so if you use windows only authentication, you
> >> can add only existing windows user names for new logins.
> >>
> >> Regards,
> >> Daniel
> >>
> >> "Gloria" <Gloria@.discussions.microsoft.com> wrote in message
> >> news:B17D383B-15DC-40C7-92EB-8A2F5B3CEB60@.microsoft.com...
> >> I am using SQLServer 2000 and for reasons unknown the name of the
> >> server got changed so that it did not match the name of the
> >> machine. I discovered this when our application could not connect
> >> to the database.
> >> I changed the servername using:
> >> exec sp_dropserver 'SSM_6000_A', 'droplogins'
> >> exec sp_addserver 'SSM_6000_C', 'local'
> >> I stopped and started the server and when I checked the name of the
> >> server using
> >> SELECT @.@.SERVERNAME
> >> I got the correct name, SSM_6000_C
> >> I still could not connect to the database but I thought I had to
> >> recreate the logins.
> >>
> >> I deleted one of the users and logins and tried to recreate it and
> >> I get the error:
> >> "ERROR15401: WindowsNT user or group 'user-name' not found.
> >> Check the name again."
> >>
> >> The server is on our network. I can go to folders, etc. on the
> >> network once I log in using my network account.
> >>
> >> What is wrong?
> >> Is there someplace within SQLServer that did not get the server
> >> name change? Where can I check?
> >>
> >> I went to a DTS package and was configuring a query in an Execute
> >> SQL Task and the server name was the old name.
> >>
> >> Thanks for your help!!
> >> Gloria
>
>|||Hi Gloria
You might have to have your network administrator to do this. It will
require an account that has admin priveledges on your domain.
I don't know if there is a "correct procedure" for changing a servername,
but generally I'd take the server out of the domain - change the name and
then join the server to the domain again. This is not only relevant for
SQLServer, but for every kind of servers. In some cases you can get away
with just renaming the server while it's still a member of the domain, but
in some cases you see weird things and problems afterwards. Therefore I
prefer to do the steps above.
IMHO you shouldn't change a servername without knowing the consequences it
can have on the network. If you don't know about how to remove and join a
server to/from a Domain, I think you should leave the name change to
somebody else...:-).
Regards
Steen
Gloria wrote:
> Hi
> What do you mean by "taking the server out of the domain"? Does our
> Network Adminstrator have to take it off of the network and then add
> it again?
> I can connect to our company network using the computer the SQL
> Server is on but the SQL Server does not recognize it. Is there a
> way I can disconnect then reconnect just the SQL Server?
> Is this what typically happens when you change the servername?
> What is the correct procedure?
> Thanks,
> Gloria
> "Steen Persson" wrote:
>> Hi
>> You could also try to take the server out of your domain, and then
>> join it to the domain again. Sometimes you have to take a server out
>> of the domain before it's properly "connected" to the AD again -
>> especially when you mess around with servernames.
>> Regards
>> Steen
>> Gloria wrote:
>> Hi Daniel,
>> I only want to create user names from Windows logins. The problem
>> is EM won't let me create Windows logins.
>> When I try to create a new login by picking a name from the domain
>> list, I get the error message:
>> "Error15401:WindowsNT user or group 'domain\user_name' not
>> found. Check the name again."
>> I checked the servername to make sure after I changed it that if
>> matches the machine name and it does. Is it possible that somewhere
>> in the bowels of SQLServer the servername did not get changed and
>> this mismatch is causing the problem?
>> If so, how can I check this?
>> Does it check in the registry somewhere the name of the server?
>> Thanks again,
>> Gloria
>> "Daniel Joskovski" wrote:
>> To create new logins you can use EM, but login are only existing
>> windows user names, so if you use windows only authentication, you
>> can add only existing windows user names for new logins.
>> Regards,
>> Daniel
>> "Gloria" <Gloria@.discussions.microsoft.com> wrote in message
>> news:B17D383B-15DC-40C7-92EB-8A2F5B3CEB60@.microsoft.com...
>> I am using SQLServer 2000 and for reasons unknown the name of the
>> server got changed so that it did not match the name of the
>> machine. I discovered this when our application could not connect
>> to the database.
>> I changed the servername using:
>> exec sp_dropserver 'SSM_6000_A', 'droplogins'
>> exec sp_addserver 'SSM_6000_C', 'local'
>> I stopped and started the server and when I checked the name of
>> the server using
>> SELECT @.@.SERVERNAME
>> I got the correct name, SSM_6000_C
>> I still could not connect to the database but I thought I had to
>> recreate the logins.
>> I deleted one of the users and logins and tried to recreate it and
>> I get the error:
>> "ERROR15401: WindowsNT user or group 'user-name' not found.
>> Check the name again."
>> The server is on our network. I can go to folders, etc. on the
>> network once I log in using my network account.
>> What is wrong?
>> Is there someplace within SQLServer that did not get the server
>> name change? Where can I check?
>> I went to a DTS package and was configuring a query in an Execute
>> SQL Task and the server name was the old name.
>> Thanks for your help!!
>> Gloria|||Hi,
I agree that you should not change things without knowing the consequences
but when you are trying to fix a problem and the documentation is inadequate,
you do the best you can.
The original problem was that our application could not connect to the
database. I discovered that the machine name and the SQLServer name did not
match. Now the computer that has SQLServer is connected to the network and
works fine. The domain is recognized by the computer. Changing the server
name to match the machine name should allow the network domain to be
recognized by SQLServer, shouldn't it?
When you select Windows authentication and the network domain and user names
are shown, where is this coming from?
Doesn't SQLServer use the same information when connecting to the network as
the computer does?
Thanks,
Gloria
"Steen Persson" wrote:
> Hi Gloria
> You might have to have your network administrator to do this. It will
> require an account that has admin priveledges on your domain.
> I don't know if there is a "correct procedure" for changing a servername,
> but generally I'd take the server out of the domain - change the name and
> then join the server to the domain again. This is not only relevant for
> SQLServer, but for every kind of servers. In some cases you can get away
> with just renaming the server while it's still a member of the domain, but
> in some cases you see weird things and problems afterwards. Therefore I
> prefer to do the steps above.
> IMHO you shouldn't change a servername without knowing the consequences it
> can have on the network. If you don't know about how to remove and join a
> server to/from a Domain, I think you should leave the name change to
> somebody else...:-).
> Regards
> Steen
>
> Gloria wrote:
> > Hi
> > What do you mean by "taking the server out of the domain"? Does our
> > Network Adminstrator have to take it off of the network and then add
> > it again?
> > I can connect to our company network using the computer the SQL
> > Server is on but the SQL Server does not recognize it. Is there a
> > way I can disconnect then reconnect just the SQL Server?
> >
> > Is this what typically happens when you change the servername?
> > What is the correct procedure?
> >
> > Thanks,
> > Gloria
> > "Steen Persson" wrote:
> >
> >> Hi
> >>
> >> You could also try to take the server out of your domain, and then
> >> join it to the domain again. Sometimes you have to take a server out
> >> of the domain before it's properly "connected" to the AD again -
> >> especially when you mess around with servernames.
> >>
> >> Regards
> >> Steen
> >>
> >> Gloria wrote:
> >> Hi Daniel,
> >> I only want to create user names from Windows logins. The problem
> >> is EM won't let me create Windows logins.
> >> When I try to create a new login by picking a name from the domain
> >> list, I get the error message:
> >> "Error15401:WindowsNT user or group 'domain\user_name' not
> >> found. Check the name again."
> >>
> >> I checked the servername to make sure after I changed it that if
> >> matches the machine name and it does. Is it possible that somewhere
> >> in the bowels of SQLServer the servername did not get changed and
> >> this mismatch is causing the problem?
> >> If so, how can I check this?
> >> Does it check in the registry somewhere the name of the server?
> >>
> >> Thanks again,
> >> Gloria
> >>
> >> "Daniel Joskovski" wrote:
> >>
> >> To create new logins you can use EM, but login are only existing
> >> windows user names, so if you use windows only authentication, you
> >> can add only existing windows user names for new logins.
> >>
> >> Regards,
> >> Daniel
> >>
> >> "Gloria" <Gloria@.discussions.microsoft.com> wrote in message
> >> news:B17D383B-15DC-40C7-92EB-8A2F5B3CEB60@.microsoft.com...
> >> I am using SQLServer 2000 and for reasons unknown the name of the
> >> server got changed so that it did not match the name of the
> >> machine. I discovered this when our application could not connect
> >> to the database.
> >> I changed the servername using:
> >> exec sp_dropserver 'SSM_6000_A', 'droplogins'
> >> exec sp_addserver 'SSM_6000_C', 'local'
> >> I stopped and started the server and when I checked the name of
> >> the server using
> >> SELECT @.@.SERVERNAME
> >> I got the correct name, SSM_6000_C
> >> I still could not connect to the database but I thought I had to
> >> recreate the logins.
> >>
> >> I deleted one of the users and logins and tried to recreate it and
> >> I get the error:
> >> "ERROR15401: WindowsNT user or group 'user-name' not found.
> >> Check the name again."
> >>
> >> The server is on our network. I can go to folders, etc. on the
> >> network once I log in using my network account.
> >>
> >> What is wrong?
> >> Is there someplace within SQLServer that did not get the server
> >> name change? Where can I check?
> >>
> >> I went to a DTS package and was configuring a query in an Execute
> >> SQL Task and the server name was the old name.
> >>
> >> Thanks for your help!!
> >> Gloria
>
>|||Hi
Since your problem is with the NTAuthentication and Domain name, it could
very well be that the server and/or Domain Controller isn't in "sync". Since
there has been messed with the servernames, the first thing I'd try would be
to re-join the server to the domain. In the AD you have a lot of pointers
and settings (DNS, SPN, WINS etc.) that holds a servername. If you just
change a servername when the server are in the Domain, some of these might
not be correctly updated where others will. This can very well cause a
number of weird issues that isn't explainable. When you take the server out
of the domain, the AD will remove all the references to the "old"
servername. When you then join the server back into the domain with the new
name, it will be correctly updated throughout the entire domain and all
pointers and references will be refreshed to reflect the new name.
It might not be the reason or solution in your case, but it's quite easy to
do so it would definately do one the first thing I'd try.
Regards
Steen
Gloria wrote:
> Hi,
> I agree that you should not change things without knowing the
> consequences but when you are trying to fix a problem and the
> documentation is inadequate, you do the best you can.
> The original problem was that our application could not connect to the
> database. I discovered that the machine name and the SQLServer name
> did not match. Now the computer that has SQLServer is connected to
> the network and works fine. The domain is recognized by the
> computer. Changing the server name to match the machine name should
> allow the network domain to be recognized by SQLServer, shouldn't it?
> When you select Windows authentication and the network domain and
> user names are shown, where is this coming from?
> Doesn't SQLServer use the same information when connecting to the
> network as the computer does?
> Thanks,
> Gloria
> "Steen Persson" wrote:
>> Hi Gloria
>> You might have to have your network administrator to do this. It will
>> require an account that has admin priveledges on your domain.
>> I don't know if there is a "correct procedure" for changing a
>> servername, but generally I'd take the server out of the domain -
>> change the name and then join the server to the domain again. This
>> is not only relevant for SQLServer, but for every kind of servers.
>> In some cases you can get away with just renaming the server while
>> it's still a member of the domain, but in some cases you see weird
>> things and problems afterwards. Therefore I prefer to do the steps
>> above.
>> IMHO you shouldn't change a servername without knowing the
>> consequences it can have on the network. If you don't know about how
>> to remove and join a server to/from a Domain, I think you should
>> leave the name change to somebody else...:-).
>> Regards
>> Steen
>>
>> Gloria wrote:
>> Hi
>> What do you mean by "taking the server out of the domain"? Does our
>> Network Adminstrator have to take it off of the network and then add
>> it again?
>> I can connect to our company network using the computer the SQL
>> Server is on but the SQL Server does not recognize it. Is there a
>> way I can disconnect then reconnect just the SQL Server?
>> Is this what typically happens when you change the servername?
>> What is the correct procedure?
>> Thanks,
>> Gloria
>> "Steen Persson" wrote:
>> Hi
>> You could also try to take the server out of your domain, and then
>> join it to the domain again. Sometimes you have to take a server
>> out of the domain before it's properly "connected" to the AD again
>> - especially when you mess around with servernames.
>> Regards
>> Steen
>> Gloria wrote:
>> Hi Daniel,
>> I only want to create user names from Windows logins. The problem
>> is EM won't let me create Windows logins.
>> When I try to create a new login by picking a name from the domain
>> list, I get the error message:
>> "Error15401:WindowsNT user or group 'domain\user_name' not
>> found. Check the name again."
>> I checked the servername to make sure after I changed it that if
>> matches the machine name and it does. Is it possible that
>> somewhere in the bowels of SQLServer the servername did not get
>> changed and this mismatch is causing the problem?
>> If so, how can I check this?
>> Does it check in the registry somewhere the name of the server?
>> Thanks again,
>> Gloria
>> "Daniel Joskovski" wrote:
>> To create new logins you can use EM, but login are only existing
>> windows user names, so if you use windows only authentication,
>> you can add only existing windows user names for new logins.
>> Regards,
>> Daniel
>> "Gloria" <Gloria@.discussions.microsoft.com> wrote in message
>> news:B17D383B-15DC-40C7-92EB-8A2F5B3CEB60@.microsoft.com...
>>> I am using SQLServer 2000 and for reasons unknown the name of
>>> the server got changed so that it did not match the name of the
>>> machine. I discovered this when our application could not
>>> connect to the database.
>>> I changed the servername using:
>>> exec sp_dropserver 'SSM_6000_A', 'droplogins'
>>> exec sp_addserver 'SSM_6000_C', 'local'
>>> I stopped and started the server and when I checked the name of
>>> the server using
>>> SELECT @.@.SERVERNAME
>>> I got the correct name, SSM_6000_C
>>> I still could not connect to the database but I thought I had to
>>> recreate the logins.
>>>
>>> I deleted one of the users and logins and tried to recreate it
>>> and I get the error:
>>> "ERROR15401: WindowsNT user or group 'user-name' not
>>> found. Check the name again."
>>>
>>> The server is on our network. I can go to folders, etc. on the
>>> network once I log in using my network account.
>>>
>>> What is wrong?
>>> Is there someplace within SQLServer that did not get the server
>>> name change? Where can I check?
>>>
>>> I went to a DTS package and was configuring a query in an
>>> Execute SQL Task and the server name was the old name.
>>>
>>> Thanks for your help!!
>>> Gloria|||Hi Steen,
Many, many thanks. Worked like a charm!!
Gloria
"Steen Persson" wrote:
> Hi
> Since your problem is with the NTAuthentication and Domain name, it could
> very well be that the server and/or Domain Controller isn't in "sync". Since
> there has been messed with the servernames, the first thing I'd try would be
> to re-join the server to the domain. In the AD you have a lot of pointers
> and settings (DNS, SPN, WINS etc.) that holds a servername. If you just
> change a servername when the server are in the Domain, some of these might
> not be correctly updated where others will. This can very well cause a
> number of weird issues that isn't explainable. When you take the server out
> of the domain, the AD will remove all the references to the "old"
> servername. When you then join the server back into the domain with the new
> name, it will be correctly updated throughout the entire domain and all
> pointers and references will be refreshed to reflect the new name.
> It might not be the reason or solution in your case, but it's quite easy to
> do so it would definately do one the first thing I'd try.
> Regards
> Steen
> Gloria wrote:
> > Hi,
> >
> > I agree that you should not change things without knowing the
> > consequences but when you are trying to fix a problem and the
> > documentation is inadequate, you do the best you can.
> >
> > The original problem was that our application could not connect to the
> > database. I discovered that the machine name and the SQLServer name
> > did not match. Now the computer that has SQLServer is connected to
> > the network and works fine. The domain is recognized by the
> > computer. Changing the server name to match the machine name should
> > allow the network domain to be recognized by SQLServer, shouldn't it?
> >
> > When you select Windows authentication and the network domain and
> > user names are shown, where is this coming from?
> > Doesn't SQLServer use the same information when connecting to the
> > network as the computer does?
> >
> > Thanks,
> > Gloria
> > "Steen Persson" wrote:
> >
> >> Hi Gloria
> >>
> >> You might have to have your network administrator to do this. It will
> >> require an account that has admin priveledges on your domain.
> >> I don't know if there is a "correct procedure" for changing a
> >> servername, but generally I'd take the server out of the domain -
> >> change the name and then join the server to the domain again. This
> >> is not only relevant for SQLServer, but for every kind of servers.
> >> In some cases you can get away with just renaming the server while
> >> it's still a member of the domain, but in some cases you see weird
> >> things and problems afterwards. Therefore I prefer to do the steps
> >> above.
> >>
> >> IMHO you shouldn't change a servername without knowing the
> >> consequences it can have on the network. If you don't know about how
> >> to remove and join a server to/from a Domain, I think you should
> >> leave the name change to somebody else...:-).
> >>
> >> Regards
> >> Steen
> >>
> >>
> >> Gloria wrote:
> >> Hi
> >> What do you mean by "taking the server out of the domain"? Does our
> >> Network Adminstrator have to take it off of the network and then add
> >> it again?
> >> I can connect to our company network using the computer the SQL
> >> Server is on but the SQL Server does not recognize it. Is there a
> >> way I can disconnect then reconnect just the SQL Server?
> >>
> >> Is this what typically happens when you change the servername?
> >> What is the correct procedure?
> >>
> >> Thanks,
> >> Gloria
> >> "Steen Persson" wrote:
> >>
> >> Hi
> >>
> >> You could also try to take the server out of your domain, and then
> >> join it to the domain again. Sometimes you have to take a server
> >> out of the domain before it's properly "connected" to the AD again
> >> - especially when you mess around with servernames.
> >>
> >> Regards
> >> Steen
> >>
> >> Gloria wrote:
> >> Hi Daniel,
> >> I only want to create user names from Windows logins. The problem
> >> is EM won't let me create Windows logins.
> >> When I try to create a new login by picking a name from the domain
> >> list, I get the error message:
> >> "Error15401:WindowsNT user or group 'domain\user_name' not
> >> found. Check the name again."
> >>
> >> I checked the servername to make sure after I changed it that if
> >> matches the machine name and it does. Is it possible that
> >> somewhere in the bowels of SQLServer the servername did not get
> >> changed and this mismatch is causing the problem?
> >> If so, how can I check this?
> >> Does it check in the registry somewhere the name of the server?
> >>
> >> Thanks again,
> >> Gloria
> >>
> >> "Daniel Joskovski" wrote:
> >>
> >> To create new logins you can use EM, but login are only existing
> >> windows user names, so if you use windows only authentication,
> >> you can add only existing windows user names for new logins.
> >>
> >> Regards,
> >> Daniel
> >>
> >> "Gloria" <Gloria@.discussions.microsoft.com> wrote in message
> >> news:B17D383B-15DC-40C7-92EB-8A2F5B3CEB60@.microsoft.com...
> >>> I am using SQLServer 2000 and for reasons unknown the name of
> >>> the server got changed so that it did not match the name of the
> >>> machine. I discovered this when our application could not
> >>> connect to the database.
> >>> I changed the servername using:
> >>> exec sp_dropserver 'SSM_6000_A', 'droplogins'
> >>> exec sp_addserver 'SSM_6000_C', 'local'
> >>> I stopped and started the server and when I checked the name of
> >>> the server using
> >>> SELECT @.@.SERVERNAME
> >>> I got the correct name, SSM_6000_C
> >>> I still could not connect to the database but I thought I had to
> >>> recreate the logins.
> >>>
> >>> I deleted one of the users and logins and tried to recreate it
> >>> and I get the error:
> >>> "ERROR15401: WindowsNT user or group 'user-name' not
> >>> found. Check the name again."
> >>>
> >>> The server is on our network. I can go to folders, etc. on the
> >>> network once I log in using my network account.
> >>>
> >>> What is wrong?
> >>> Is there someplace within SQLServer that did not get the server
> >>> name change? Where can I check?
> >>>
> >>> I went to a DTS package and was configuring a query in an
> >>> Execute SQL Task and the server name was the old name.
> >>>
> >>> Thanks for your help!!
> >>> Gloria
>
>