Changed user p/w, can't start Sql Server

Hi;
I am running Sql Server dev edition on my home system - not on a domain.
When I installed I selecgted mixed security so can have user/pw ad well as
SSPI. I told it to run the server using my login.
I changed the password for my Windows login and Sql Server will now not
start. If I change back to the old pw it will. How do I get it to update the
pw for my username for when it starts?
thanks - dave"David Thielen" <thielen@.nospam.nospam> wrote in message
news:30A6CEF8-15F4-4C42-9796-F769CCFADEF8@.microsoft.com...
> Hi;
> I am running Sql Server dev edition on my home system - not on a domain.
> When I installed I selecgted mixed security so can have user/pw ad well as
> SSPI. I told it to run the server using my login.
> I changed the password for my Windows login and Sql Server will now not
> start. If I change back to the old pw it will. How do I get it to update
the
> pw for my username for when it starts?
> --
> thanks - dave
Open up AdminTools -> Services
Find the MSSQLServer and SQLServerAgent service and update the passwords
there. Restart the services.
Rick Sawtell
MCT, MCSD, MCDBA|||Administrative Tools, Services, there you select the SQL Server service and
change the password for
the login. this applies for all services in windows, not only SQL Server.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"David Thielen" <thielen@.nospam.nospam> wrote in message
news:30A6CEF8-15F4-4C42-9796-F769CCFADEF8@.microsoft.com...
> Hi;
> I am running Sql Server dev edition on my home system - not on a domain.
> When I installed I selecgted mixed security so can have user/pw ad well as
> SSPI. I told it to run the server using my login.
> I changed the password for my Windows login and Sql Server will now not
> start. If I change back to the old pw it will. How do I get it to update t
he
> pw for my username for when it starts?
> --
> thanks - dave|||Change the password for the MSSQLSERVER service and the SQLSERVERAGENT
service using the control panel service control applet. Next time, use
Enterprise Mangler to change the password for the service before you change
it at the Windows level.
Geoff N. Hiten
Microsoft SQL Server MVP
"David Thielen" <thielen@.nospam.nospam> wrote in message
news:30A6CEF8-15F4-4C42-9796-F769CCFADEF8@.microsoft.com...
> Hi;
> I am running Sql Server dev edition on my home system - not on a domain.
> When I installed I selecgted mixed security so can have user/pw ad well as
> SSPI. I told it to run the server using my login.
> I changed the password for my Windows login and Sql Server will now not
> start. If I change back to the old pw it will. How do I get it to update
> the
> pw for my username for when it starts?
> --
> thanks - dave|||Hi,
After changing the Service startup account password, you need to change that
in Control panel -- admin tools -- services.
How to do:-
1. Control Panel - Admin tools -- Services
2. Double click above the MSSQL Server service
3. In the Log on tab, change the password, Click ok and restart the
service.
Note:
Do the same for SQL Agent service.
Thanks
Hari
SQL Server MVP
"David Thielen" <thielen@.nospam.nospam> wrote in message
news:30A6CEF8-15F4-4C42-9796-F769CCFADEF8@.microsoft.com...
> Hi;
> I am running Sql Server dev edition on my home system - not on a domain.
> When I installed I selecgted mixed security so can have user/pw ad well as
> SSPI. I told it to run the server using my login.
> I changed the password for my Windows login and Sql Server will now not
> start. If I change back to the old pw it will. How do I get it to update
> the
> pw for my username for when it starts?
> --
> thanks - dave|||Thank you everyone. As soon as I saw that answer it was "of course - stupid
me."
thanks - dave
"David Thielen" wrote:

> Hi;
> I am running Sql Server dev edition on my home system - not on a domain.
> When I installed I selecgted mixed security so can have user/pw ad well as
> SSPI. I told it to run the server using my login.
> I changed the password for my Windows login and Sql Server will now not
> start. If I change back to the old pw it will. How do I get it to update t
he
> pw for my username for when it starts?
> --
> thanks - dave

Changed user p/w, can't start Sql Server

Hi;
I am running Sql Server dev edition on my home system - not on a domain.
When I installed I selecgted mixed security so can have user/pw ad well as
SSPI. I told it to run the server using my login.
I changed the password for my Windows login and Sql Server will now not
start. If I change back to the old pw it will. How do I get it to update the
pw for my username for when it starts?
--
thanks - dave"David Thielen" <thielen@.nospam.nospam> wrote in message
news:30A6CEF8-15F4-4C42-9796-F769CCFADEF8@.microsoft.com...
> Hi;
> I am running Sql Server dev edition on my home system - not on a domain.
> When I installed I selecgted mixed security so can have user/pw ad well as
> SSPI. I told it to run the server using my login.
> I changed the password for my Windows login and Sql Server will now not
> start. If I change back to the old pw it will. How do I get it to update
the
> pw for my username for when it starts?
> --
> thanks - dave
Open up AdminTools -> Services
Find the MSSQLServer and SQLServerAgent service and update the passwords
there. Restart the services.
Rick Sawtell
MCT, MCSD, MCDBA|||Administrative Tools, Services, there you select the SQL Server service and change the password for
the login. this applies for all services in windows, not only SQL Server.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"David Thielen" <thielen@.nospam.nospam> wrote in message
news:30A6CEF8-15F4-4C42-9796-F769CCFADEF8@.microsoft.com...
> Hi;
> I am running Sql Server dev edition on my home system - not on a domain.
> When I installed I selecgted mixed security so can have user/pw ad well as
> SSPI. I told it to run the server using my login.
> I changed the password for my Windows login and Sql Server will now not
> start. If I change back to the old pw it will. How do I get it to update the
> pw for my username for when it starts?
> --
> thanks - dave|||Change the password for the MSSQLSERVER service and the SQLSERVERAGENT
service using the control panel service control applet. Next time, use
Enterprise Mangler to change the password for the service before you change
it at the Windows level.
Geoff N. Hiten
Microsoft SQL Server MVP
"David Thielen" <thielen@.nospam.nospam> wrote in message
news:30A6CEF8-15F4-4C42-9796-F769CCFADEF8@.microsoft.com...
> Hi;
> I am running Sql Server dev edition on my home system - not on a domain.
> When I installed I selecgted mixed security so can have user/pw ad well as
> SSPI. I told it to run the server using my login.
> I changed the password for my Windows login and Sql Server will now not
> start. If I change back to the old pw it will. How do I get it to update
> the
> pw for my username for when it starts?
> --
> thanks - dave|||Hi,
After changing the Service startup account password, you need to change that
in Control panel -- admin tools -- services.
How to do:-
1. Control Panel - Admin tools -- Services
2. Double click above the MSSQL Server service
3. In the Log on tab, change the password, Click ok and restart the
service.
Note:
Do the same for SQL Agent service.
Thanks
Hari
SQL Server MVP
"David Thielen" <thielen@.nospam.nospam> wrote in message
news:30A6CEF8-15F4-4C42-9796-F769CCFADEF8@.microsoft.com...
> Hi;
> I am running Sql Server dev edition on my home system - not on a domain.
> When I installed I selecgted mixed security so can have user/pw ad well as
> SSPI. I told it to run the server using my login.
> I changed the password for my Windows login and Sql Server will now not
> start. If I change back to the old pw it will. How do I get it to update
> the
> pw for my username for when it starts?
> --
> thanks - dave|||Thank you everyone. As soon as I saw that answer it was "of course - stupid
me."
--
thanks - dave
"David Thielen" wrote:
> Hi;
> I am running Sql Server dev edition on my home system - not on a domain.
> When I installed I selecgted mixed security so can have user/pw ad well as
> SSPI. I told it to run the server using my login.
> I changed the password for my Windows login and Sql Server will now not
> start. If I change back to the old pw it will. How do I get it to update the
> pw for my username for when it starts?
> --
> thanks - dave

Changed user p/w, can't start Sql Server

Hi;
I am running Sql Server dev edition on my home system - not on a domain.
When I installed I selecgted mixed security so can have user/pw ad well as
SSPI. I told it to run the server using my login.
I changed the password for my Windows login and Sql Server will now not
start. If I change back to the old pw it will. How do I get it to update the
pw for my username for when it starts?
thanks - dave
"David Thielen" <thielen@.nospam.nospam> wrote in message
news:30A6CEF8-15F4-4C42-9796-F769CCFADEF8@.microsoft.com...
> Hi;
> I am running Sql Server dev edition on my home system - not on a domain.
> When I installed I selecgted mixed security so can have user/pw ad well as
> SSPI. I told it to run the server using my login.
> I changed the password for my Windows login and Sql Server will now not
> start. If I change back to the old pw it will. How do I get it to update
the
> pw for my username for when it starts?
> --
> thanks - dave
Open up AdminTools -> Services
Find the MSSQLServer and SQLServerAgent service and update the passwords
there. Restart the services.
Rick Sawtell
MCT, MCSD, MCDBA
|||Administrative Tools, Services, there you select the SQL Server service and change the password for
the login. this applies for all services in windows, not only SQL Server.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"David Thielen" <thielen@.nospam.nospam> wrote in message
news:30A6CEF8-15F4-4C42-9796-F769CCFADEF8@.microsoft.com...
> Hi;
> I am running Sql Server dev edition on my home system - not on a domain.
> When I installed I selecgted mixed security so can have user/pw ad well as
> SSPI. I told it to run the server using my login.
> I changed the password for my Windows login and Sql Server will now not
> start. If I change back to the old pw it will. How do I get it to update the
> pw for my username for when it starts?
> --
> thanks - dave
|||Change the password for the MSSQLSERVER service and the SQLSERVERAGENT
service using the control panel service control applet. Next time, use
Enterprise Mangler to change the password for the service before you change
it at the Windows level.
Geoff N. Hiten
Microsoft SQL Server MVP
"David Thielen" <thielen@.nospam.nospam> wrote in message
news:30A6CEF8-15F4-4C42-9796-F769CCFADEF8@.microsoft.com...
> Hi;
> I am running Sql Server dev edition on my home system - not on a domain.
> When I installed I selecgted mixed security so can have user/pw ad well as
> SSPI. I told it to run the server using my login.
> I changed the password for my Windows login and Sql Server will now not
> start. If I change back to the old pw it will. How do I get it to update
> the
> pw for my username for when it starts?
> --
> thanks - dave
|||Hi,
After changing the Service startup account password, you need to change that
in Control panel -- admin tools -- services.
How to do:-
1. Control Panel - Admin tools -- Services
2. Double click above the MSSQL Server service
3. In the Log on tab, change the password, Click ok and restart the
service.
Note:
Do the same for SQL Agent service.
Thanks
Hari
SQL Server MVP
"David Thielen" <thielen@.nospam.nospam> wrote in message
news:30A6CEF8-15F4-4C42-9796-F769CCFADEF8@.microsoft.com...
> Hi;
> I am running Sql Server dev edition on my home system - not on a domain.
> When I installed I selecgted mixed security so can have user/pw ad well as
> SSPI. I told it to run the server using my login.
> I changed the password for my Windows login and Sql Server will now not
> start. If I change back to the old pw it will. How do I get it to update
> the
> pw for my username for when it starts?
> --
> thanks - dave
|||Thank you everyone. As soon as I saw that answer it was "of course - stupid
me."
thanks - dave
"David Thielen" wrote:

> Hi;
> I am running Sql Server dev edition on my home system - not on a domain.
> When I installed I selecgted mixed security so can have user/pw ad well as
> SSPI. I told it to run the server using my login.
> I changed the password for my Windows login and Sql Server will now not
> start. If I change back to the old pw it will. How do I get it to update the
> pw for my username for when it starts?
> --
> thanks - dave

Changed sa password - can't connect via Enterprise Manager now

A client of mine changed his SA password "because it hadn't been changed in
a
while". Now nobody can get into the server via Enterprise Manager trying to
Connect on the server yields an error:
A connection could not be established to SERVER1.
Reason: login failed for user 'sa'.
Please verify SQL Server is running and check your SQL Server Registration
properties (by right-clicking on the SERVER1 node) and try again.
Of course, if I right-click on the SERVER1 node, I get the same message.
My client remembers the password he set; I managed to use it to get into
Query Analyzer, which prompts for a login each time it opens. But no luck
with Enterprise Manager. It's just trying to log in as sa without prompting
for a pw.
What can I do?
I already tried running sp_Password to change the pw back to what it was.
Still can't connect to the SQL Server via Enterprise Manager.Change the server registration to use Windows Auth instead of SQL Auth?
http://www.aspfaq.com/
(Reverse address to reply.)
"Norrick" <Norrick@.discussions.microsoft.com> wrote in message
news:90915AE8-8D8E-4CC9-ABA3-0C7FC52A7BBA@.microsoft.com...
> A client of mine changed his SA password "because it hadn't been changed
in a
> while". Now nobody can get into the server via Enterprise Manager trying
to
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without
prompting
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.|||Before connecting to server1 in EM, right click on it and edit the entry to
use the new password.
"Norrick" wrote:

> A client of mine changed his SA password "because it hadn't been changed i
n a
> while". Now nobody can get into the server via Enterprise Manager trying t
o
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without promptin
g
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.|||In SQLEM, right-click on the server registration, and Edit settings. In the
dialog, change the login information.
You should probably be using Windows Authentication and if you can not
because you are remoting, create another login that only you know the
password to and use that to login. No one should ever use the sa account
unless there is an emergency. Each user should have their own SQL Server
login created, or only Windows Authenticated, which would give each user
their own login--unless, of cours, you share your network logins too.
Sincerely,
Anthony Thomas
"Norrick" wrote:

> A client of mine changed his SA password "because it hadn't been changed i
n a
> while". Now nobody can get into the server via Enterprise Manager trying t
o
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without promptin
g
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.|||Sorry, you said "remembers" and somehow I read "doesn't remember"...
You can right-click the server, "Edit SQL Server Registration Properties..."
and change the password there.
http://www.aspfaq.com/
(Reverse address to reply.)
"Norrick" <Norrick@.discussions.microsoft.com> wrote in message
news:90915AE8-8D8E-4CC9-ABA3-0C7FC52A7BBA@.microsoft.com...
> A client of mine changed his SA password "because it hadn't been changed
in a
> while". Now nobody can get into the server via Enterprise Manager trying
to
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without
prompting
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.

Changed sa password - can't connect via Enterprise Manager now

A client of mine changed his SA password "because it hadn't been changed in a
while". Now nobody can get into the server via Enterprise Manager trying to
Connect on the server yields an error:
A connection could not be established to SERVER1.
Reason: login failed for user 'sa'.
Please verify SQL Server is running and check your SQL Server Registration
properties (by right-clicking on the SERVER1 node) and try again.
Of course, if I right-click on the SERVER1 node, I get the same message.
My client remembers the password he set; I managed to use it to get into
Query Analyzer, which prompts for a login each time it opens. But no luck
with Enterprise Manager. It's just trying to log in as sa without prompting
for a pw.
What can I do?
I already tried running sp_Password to change the pw back to what it was.
Still can't connect to the SQL Server via Enterprise Manager.Change the server registration to use Windows Auth instead of SQL Auth?
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Norrick" <Norrick@.discussions.microsoft.com> wrote in message
news:90915AE8-8D8E-4CC9-ABA3-0C7FC52A7BBA@.microsoft.com...
> A client of mine changed his SA password "because it hadn't been changed
in a
> while". Now nobody can get into the server via Enterprise Manager trying
to
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without
prompting
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.|||Before connecting to server1 in EM, right click on it and edit the entry to
use the new password.
"Norrick" wrote:
> A client of mine changed his SA password "because it hadn't been changed in a
> while". Now nobody can get into the server via Enterprise Manager trying to
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without prompting
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.|||Sorry, you said "remembers" and somehow I read "doesn't remember"...
You can right-click the server, "Edit SQL Server Registration Properties..."
and change the password there.
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Norrick" <Norrick@.discussions.microsoft.com> wrote in message
news:90915AE8-8D8E-4CC9-ABA3-0C7FC52A7BBA@.microsoft.com...
> A client of mine changed his SA password "because it hadn't been changed
in a
> while". Now nobody can get into the server via Enterprise Manager trying
to
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without
prompting
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.|||In SQLEM, right-click on the server registration, and Edit settings. In the
dialog, change the login information.
You should probably be using Windows Authentication and if you can not
because you are remoting, create another login that only you know the
password to and use that to login. No one should ever use the sa account
unless there is an emergency. Each user should have their own SQL Server
login created, or only Windows Authenticated, which would give each user
their own login--unless, of cours, you share your network logins too.
Sincerely,
Anthony Thomas
"Norrick" wrote:
> A client of mine changed his SA password "because it hadn't been changed in a
> while". Now nobody can get into the server via Enterprise Manager trying to
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without prompting
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.

Changed sa password - can't connect via Enterprise Manager now

A client of mine changed his SA password "because it hadn't been changed in a
while". Now nobody can get into the server via Enterprise Manager trying to
Connect on the server yields an error:
A connection could not be established to SERVER1.
Reason: login failed for user 'sa'.
Please verify SQL Server is running and check your SQL Server Registration
properties (by right-clicking on the SERVER1 node) and try again.
Of course, if I right-click on the SERVER1 node, I get the same message.
My client remembers the password he set; I managed to use it to get into
Query Analyzer, which prompts for a login each time it opens. But no luck
with Enterprise Manager. It's just trying to log in as sa without prompting
for a pw.
What can I do?
I already tried running sp_Password to change the pw back to what it was.
Still can't connect to the SQL Server via Enterprise Manager.
Change the server registration to use Windows Auth instead of SQL Auth?
http://www.aspfaq.com/
(Reverse address to reply.)
"Norrick" <Norrick@.discussions.microsoft.com> wrote in message
news:90915AE8-8D8E-4CC9-ABA3-0C7FC52A7BBA@.microsoft.com...
> A client of mine changed his SA password "because it hadn't been changed
in a
> while". Now nobody can get into the server via Enterprise Manager trying
to
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without
prompting
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.
|||Before connecting to server1 in EM, right click on it and edit the entry to
use the new password.
"Norrick" wrote:

> A client of mine changed his SA password "because it hadn't been changed in a
> while". Now nobody can get into the server via Enterprise Manager trying to
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without prompting
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.
|||In SQLEM, right-click on the server registration, and Edit settings. In the
dialog, change the login information.
You should probably be using Windows Authentication and if you can not
because you are remoting, create another login that only you know the
password to and use that to login. No one should ever use the sa account
unless there is an emergency. Each user should have their own SQL Server
login created, or only Windows Authenticated, which would give each user
their own login--unless, of cours, you share your network logins too.
Sincerely,
Anthony Thomas
"Norrick" wrote:

> A client of mine changed his SA password "because it hadn't been changed in a
> while". Now nobody can get into the server via Enterprise Manager trying to
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without prompting
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.
|||Sorry, you said "remembers" and somehow I read "doesn't remember"...
You can right-click the server, "Edit SQL Server Registration Properties..."
and change the password there.
http://www.aspfaq.com/
(Reverse address to reply.)
"Norrick" <Norrick@.discussions.microsoft.com> wrote in message
news:90915AE8-8D8E-4CC9-ABA3-0C7FC52A7BBA@.microsoft.com...
> A client of mine changed his SA password "because it hadn't been changed
in a
> while". Now nobody can get into the server via Enterprise Manager trying
to
> Connect on the server yields an error:
>
> A connection could not be established to SERVER1.
> Reason: login failed for user 'sa'.
> Please verify SQL Server is running and check your SQL Server Registration
> properties (by right-clicking on the SERVER1 node) and try again.
>
> Of course, if I right-click on the SERVER1 node, I get the same message.
> My client remembers the password he set; I managed to use it to get into
> Query Analyzer, which prompts for a login each time it opens. But no luck
> with Enterprise Manager. It's just trying to log in as sa without
prompting
> for a pw.
> What can I do?
> I already tried running sp_Password to change the pw back to what it was.
> Still can't connect to the SQL Server via Enterprise Manager.

changed my login password??

I changed my login password to my computer, now I can't start my SQL
services. It says it can't start because of login falure?
Nevermind. I figured it out
|||You need to change password for MSSQLSERVER and SQLSERVERAGENT services.
Go to Computer management console and for this services change password on
the LogOn tab.
I hope this will help.
Ana
"DaveF" <dfetrow@.geodecisions.com> wrote in message
news:OmVPiGoNEHA.2708@.TK2MSFTNGP10.phx.gbl...
> I changed my login password to my computer, now I can't start my SQL
> services. It says it can't start because of login falure?
> --
>
>

changed listening port - cant connect Mangement Studio ?

Hi,
I have "SQL 2005 express edition" running on 2003 standard (R2).
I used the "SQL Server Configuration Manager" to changed the listening port
from 1433 to 1722.
I do this by following these instructions:
http://msdn2.microsoft.com/en-us/library/ms177440.aspx
Under "Protocols for MSSQLSERVER"
TCP/IP
IP1 = 1722
IP2 = 1722
IPALL = 1722
(dynamic ports are blank)
Under "SQL Native Client Configuration"
TCP/IP = 1722
Internally from an other machine i can run the following from a cmd prompt
"telnet 192.168.2.6 1722" and i get a connection.
When running "SQL Server Management Studio Express" however i now cannot
connect. I enter 192.168.2.6:1722 as the connection IP and it times out with
the following:
"Cannot connect ... an error has occurred ... maybe caused by the fact
that under default settings SQL Server does not allow remote connection".
This is a incorrect as it works on 1433 fine. (also tried connection
Management Studio as 192.168.2.6 1722 (i.e a space between ip and port)
but no banana.
Thank for any help
Scottscott wrote:
> Hi,
> I have "SQL 2005 express edition" running on 2003 standard (R2).
> I used the "SQL Server Configuration Manager" to changed the listening por
t
> from 1433 to 1722.
> I do this by following these instructions:
> http://msdn2.microsoft.com/en-us/library/ms177440.aspx
> Under "Protocols for MSSQLSERVER"
> TCP/IP
> IP1 = 1722
> IP2 = 1722
> IPALL = 1722
> (dynamic ports are blank)
> Under "SQL Native Client Configuration"
> TCP/IP = 1722
> Internally from an other machine i can run the following from a cmd prompt
> "telnet 192.168.2.6 1722" and i get a connection.
> When running "SQL Server Management Studio Express" however i now cannot
> connect. I enter 192.168.2.6:1722 as the connection IP and it times out wi
th
> the following:
> "Cannot connect ... an error has occurred ... maybe caused by the fact
> that under default settings SQL Server does not allow remote connection".
> This is a incorrect as it works on 1433 fine. (also tried connection
> Management Studio as 192.168.2.6 1722 (i.e a space between ip and port)
> but no banana.
> Thank for any help
> Scott
>
Use a comma in Management Studio, like this: 192.168.2.6,1722
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||perfect, thanks
Scott

changed listening port - cant connect Mangement Studio ?

Hi,
I have "SQL 2005 express edition" running on 2003 standard (R2).
I used the "SQL Server Configuration Manager" to changed the listening port
from 1433 to 1722.
I do this by following these instructions:
http://msdn2.microsoft.com/en-us/library/ms177440.aspx
Under "Protocols for MSSQLSERVER"
TCP/IP
IP1 = 1722
IP2 = 1722
IPALL = 1722
(dynamic ports are blank)
Under "SQL Native Client Configuration"
TCP/IP = 1722
Internally from an other machine i can run the following from a cmd prompt
"telnet 192.168.2.6 1722" and i get a connection.
When running "SQL Server Management Studio Express" however i now cannot
connect. I enter 192.168.2.6:1722 as the connection IP and it times out with
the following:
"Cannot connect ... an error has occurred ... maybe caused by the fact
that under default settings SQL Server does not allow remote connection".
This is a incorrect as it works on 1433 fine. (also tried connection
Management Studio as 192.168.2.6 1722 (i.e a space between ip and port)
but no banana.
Thank for any help
Scottscott wrote:
> Hi,
> I have "SQL 2005 express edition" running on 2003 standard (R2).
> I used the "SQL Server Configuration Manager" to changed the listening port
> from 1433 to 1722.
> I do this by following these instructions:
> http://msdn2.microsoft.com/en-us/library/ms177440.aspx
> Under "Protocols for MSSQLSERVER"
> TCP/IP
> IP1 = 1722
> IP2 = 1722
> IPALL = 1722
> (dynamic ports are blank)
> Under "SQL Native Client Configuration"
> TCP/IP = 1722
> Internally from an other machine i can run the following from a cmd prompt
> "telnet 192.168.2.6 1722" and i get a connection.
> When running "SQL Server Management Studio Express" however i now cannot
> connect. I enter 192.168.2.6:1722 as the connection IP and it times out with
> the following:
> "Cannot connect ... an error has occurred ... maybe caused by the fact
> that under default settings SQL Server does not allow remote connection".
> This is a incorrect as it works on 1433 fine. (also tried connection
> Management Studio as 192.168.2.6 1722 (i.e a space between ip and port)
> but no banana.
> Thank for any help
> Scott
>
Use a comma in Management Studio, like this: 192.168.2.6,1722
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||perfect, thanks
Scott

Changed default table for sa signon and can't get authenticated

In SQL Server 2005, I renamed a database that is also the default database
for the sa signon and now I can't sign into the SQL Server, because although
I have the correct sa password, the default database is not there anymore so
I can't pass the authentication in order to change the default sa database t
o
one that exists. I am in a catch-22. Seems when I changed the database
name, it should have changed it in the default logins as well. At this
point, I have only one other login to the SQL Server and it also defaults to
the database that doesn't exist anymore .
Please help me get access to my SQL Server again,
TerryJust specify which DB to use when you connect with sqlcmd.exe (the
commandline SQL client that replaces osql.exe). Get a DOS prompt, cd to
the \Program Files\Microsoft SQL Server\90\Tools\Binn (if it's not on
your path), and run "sqlcmd -S <servername> -U sa -P <password> -d
master". (The -d option specifies the DB to use.) That should log you
into your SQL instance with your 'sa' login and start you off in the
master database. From there just change your default DB for 'sa' with
"exec sp_defaultdb 'sa', 'master'". Or you could just run the whole
command on the cmdline like:
sqlcmd -S <servername> -U sa -P <password> -d master -Q "exec
sp_defaultdb 'sa', 'master'"
This leads to a couple points:
1) why are you using your 'sa' login anyway (this should pretty much be
a last resort).
2) why did you need to change the default DB for this login.
3) why aren't you using trusted logins? (although the SQL login in SQL
2005 are more secure that with SQL 2000)
Anyway, good luck with it.
*mike hodgson*
http://sqlnerd.blogspot.com
Terry wrote:

>In SQL Server 2005, I renamed a database that is also the default database
>for the sa signon and now I can't sign into the SQL Server, because althoug
h
>I have the correct sa password, the default database is not there anymore s
o
>I can't pass the authentication in order to change the default sa database
to
>one that exists. I am in a catch-22. Seems when I changed the database
>name, it should have changed it in the default logins as well. At this
>point, I have only one other login to the SQL Server and it also defaults t
o
>the database that doesn't exist anymore .
>Please help me get access to my SQL Server again,
>Terry
>
>

Change Username/password

The login for our sql server is the default sa with a password.
I would like to remove the password but cant find where I can actually do
this.
Can someone help ?
TIASetting a blank SA password is not a good idea, it can leave your machine
open to virus attacks. You'd be better off setting the SA password to
something nobody knows and create a new account for people to use with only
the permissions they require.
A. Change the password of a login without a former password
This example changes the password for the login Victoria from a NULL
password to "B3r12-36".
EXEC sp_password NULL, 'B3r12-36', 'Victoria'
--
HTH
Ryan Waight, MCDBA, MCSE
"Poppy" <paul.diamond@.NOSPAMthemedialounge.com> wrote in message
news:OQjbrDEqDHA.2964@.tk2msftngp13.phx.gbl...
> The login for our sql server is the default sa with a password.
> I would like to remove the password but cant find where I can actually do
> this.
> Can someone help ?
> TIA
>|||Poppy wrote:
> The login for our sql server is the default sa with a password.
> I would like to remove the password but cant find where I can
> actually do this.
> Can someone help ?
> TIA
you really dont want to do this. the sa login is the 'system
administrator' to sql and having no password on it will open a massive
hole in your security. You should ideally only use the sa on the server
itself (to prevent sniffer attacks). You should create a seperate login
for day to day activities.
--
Br,
Mark Broadbent
mcdba , mcse+i
=============|||Hi,
You can login to Sql Query analyzer using NT
Administrator ( Provider this has permission to access
sql) and you can reset/change the password using
sp_password - stored procedure.
Pls try this out . Hope this will do the needful.
Raghu
>--Original Message--
>The login for our sql server is the default sa with a
password.
>I would like to remove the password but cant find where I
can actually do
>this.
>Can someone help ?
>TIA
>
>.
>|||>--Original Message--
>Poppy wrote:
>> The login for our sql server is the default sa with a
password.
>> I would like to remove the password but cant find where
I can
>> actually do this.
>> Can someone help ?
>> TIA
>you really dont want to do this. the sa login is
the 'system
>administrator' to sql and having no password on it will
open a massive
>hole in your security. You should ideally only use the sa
on the server
>itself (to prevent sniffer attacks). You should create a
seperate login
>for day to day activities.
>--
>Br,
>Mark Broadbent
>mcdba , mcse+i
>=============>.
>Yes .. you are right ! and If Mr.Poppy had forgotten the
sa password , then change with above step and set the
right password for security reasons.
Raghu

Change SQL 2000 Server 64bit collation

Please point me to the procedure for changing the collation sequence on 64bit
installation of SQL Server 2000 (SP4). I can't find anything in KB or BOL.
Thanks,
Tom
Hi
Collations are a different levels, so there is not one place you will need
to change it. Changing the Collation of 64bit SQL Server is no different to
changing it on 32bit SQL Server. If this is a fresh install and you don't
have any databases to change then the best option is probably to re-install.
You can use rebuildm.exe to change the master database with a different
collation. Each database can have the collation changed using the ALTER
DATABASE command, this will not change the collation of existing columns that
have been set to the original collation. To do that you will need to run a
script that uses the ALTER TABLE command. If you the column are indexes or a
primary key, or have Foreign Keys pointing to them, the constraint will need
to be dropped. There are many threads on this for example
http://tinyurl.com/ky3q
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/arch...
Other links that may be useful:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/arch...
John
"T Morris" wrote:

> Please point me to the procedure for changing the collation sequence on 64bit
> installation of SQL Server 2000 (SP4). I can't find anything in KB or BOL.
> Thanks,
> Tom
|||Since I didn't find Rebuildm.exe in the binn folder for the 64bit
installation I thought there might be a different procedure.
But per your email, I use the same procedure. And I must find the
rebuildm.exe program.
Am I correct?
Thanks,
Tom
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Collations are a different levels, so there is not one place you will need
> to change it. Changing the Collation of 64bit SQL Server is no different to
> changing it on 32bit SQL Server. If this is a fresh install and you don't
> have any databases to change then the best option is probably to re-install.
> You can use rebuildm.exe to change the master database with a different
> collation. Each database can have the collation changed using the ALTER
> DATABASE command, this will not change the collation of existing columns that
> have been set to the original collation. To do that you will need to run a
> script that uses the ALTER TABLE command. If you the column are indexes or a
> primary key, or have Foreign Keys pointing to them, the constraint will need
> to be dropped. There are many threads on this for example
> http://tinyurl.com/ky3q
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/arch...
> Other links that may be useful:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/arch...
> John
> "T Morris" wrote:
|||Hi
I usually favour re-install rather than rebuildm.exe and on the 32 bit
version it is in the ...\80\tools\binn directory.
John
"T Morris" wrote:
[vbcol=seagreen]
> Since I didn't find Rebuildm.exe in the binn folder for the 64bit
> installation I thought there might be a different procedure.
> But per your email, I use the same procedure. And I must find the
> rebuildm.exe program.
> Am I correct?
> Thanks,
> Tom
> "John Bell" wrote:

Change recovery model

I can't change the recovery model from full to simple on one of my SQL 2000
server databases. I can change it for the other user databases but just not
the one I want to change. Any idea how to fix this problem?
Thanks,
Gracie
What happens when you try to change it? And how are you doing that? Any
error messages?
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"gracie" <gracie@.discussions.microsoft.com> wrote in message
news:1A5B440C-1163-40C6-A312-B7B467FC4095@.microsoft.com...
> I can't change the recovery model from full to simple on one of my SQL
2000
> server databases. I can change it for the other user databases but just
not
> the one I want to change. Any idea how to fix this problem?
> Thanks,
> Gracie
|||What error message do you get?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"gracie" <gracie@.discussions.microsoft.com> wrote in message
news:1A5B440C-1163-40C6-A312-B7B467FC4095@.microsoft.com...
I can't change the recovery model from full to simple on one of my SQL 2000
server databases. I can change it for the other user databases but just not
the one I want to change. Any idea how to fix this problem?
Thanks,
Gracie
|||I'm trying it through EM. Not error msg the ok button is greyed out/
"Tom Moreau" wrote:

> What error message do you get?
> --
> Tom
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com/sql
>
> "gracie" <gracie@.discussions.microsoft.com> wrote in message
> news:1A5B440C-1163-40C6-A312-B7B467FC4095@.microsoft.com...
> I can't change the recovery model from full to simple on one of my SQL 2000
> server databases. I can change it for the other user databases but just not
> the one I want to change. Any idea how to fix this problem?
> Thanks,
> Gracie
>
|||Try running it through QA with an ALTER DATABASE. Also, are you a member of
the appropriate roles?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"gracie" <gracie@.discussions.microsoft.com> wrote in message
news:06E1EDD1-27D4-4C12-B652-037B9B220A5B@.microsoft.com...
I'm trying it through EM. Not error msg the ok button is greyed out/
"Tom Moreau" wrote:

> What error message do you get?
> --
> Tom
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinnaclepublishing.com/sql
>
> "gracie" <gracie@.discussions.microsoft.com> wrote in message
> news:1A5B440C-1163-40C6-A312-B7B467FC4095@.microsoft.com...
> I can't change the recovery model from full to simple on one of my SQL
2000
> server databases. I can change it for the other user databases but just
not
> the one I want to change. Any idea how to fix this problem?
> Thanks,
> Gracie
>
|||Use Query Analyzer
ALTER DATABASE databasename SET RECOVERY SIMPLE
If this doesn't work, tell us what error you get...
http://www.aspfaq.com/
(Reverse address to reply.)
"gracie" <gracie@.discussions.microsoft.com> wrote in message
news:06E1EDD1-27D4-4C12-B652-037B9B220A5B@.microsoft.com...[vbcol=seagreen]
> I'm trying it through EM. Not error msg the ok button is greyed out/
> "Tom Moreau" wrote:
2000[vbcol=seagreen]
not[vbcol=seagreen]
|||Worked, thanks!
"Aaron [SQL Server MVP]" wrote:

> Use Query Analyzer
> ALTER DATABASE databasename SET RECOVERY SIMPLE
> If this doesn't work, tell us what error you get...
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
> "gracie" <gracie@.discussions.microsoft.com> wrote in message
> news:06E1EDD1-27D4-4C12-B652-037B9B220A5B@.microsoft.com...
> 2000
> not
>
>

change MSDB owner

My Production's SQL2k MSDB & Model database owner is my old NT Domain
Administrator (olddomain/administrator). Can't remember how it ended that
way. Master owner is SA.
We have completed domain migration to Active Directory, if sp_changedbowner
is not going to allow me to change DB owner for MSDB & Model, does that mean
I got to keep my PDC (NT Domain) forever ?
Surely there must be a work-around for this.
Warning !!!
The following script is not a standard procedure:
[script]
use master
go
exec sp_configure 'allow updates', 1
reconfigure with override
go
update sysdatabases
set sid = 0x01
where name = 'model'
go
sp_configure 'allow updates', 0
reconfigure with override
[/script]
Cristian Lefter, SQL Server MVP
"pohkeat" <pohkeat@.hotmail.com> wrote in message
news:OYIkV$$HFHA.720@.TK2MSFTNGP10.phx.gbl...
> My Production's SQL2k MSDB & Model database owner is my old NT Domain
> Administrator (olddomain/administrator). Can't remember how it ended that
> way. Master owner is SA.
> We have completed domain migration to Active Directory, if
> sp_changedbowner
> is not going to allow me to change DB owner for MSDB & Model, does that
> mean
> I got to keep my PDC (NT Domain) forever ?
> Surely there must be a work-around for this.
>