login failed for user error

This summary is not available. Please click here to view the post.

login failed for user error

This summary is not available. Please click here to view the post.

Login Failed

Yesterday my sql server was running properly but after reinstalling primary
domain controller I failed to login like when I login through windows
authentication so it gave an error that login failed and if I log through sa
password then it gave login failed for default database.
Can any body give me some idea what I have to do ?
Thanks
Noor
Hi,
Are you using domain OS user as the service startup account for MSSQL Server
service.
Then did you consider those:-
1. Did you recreated the same Domain user in PDC
2. By any change did you change the domain name. If yes then you have to
redefine service startup account ,
recreate OS users to access SQL Server.
Thanks
Hari
MCDBA
"Noor" <noor@.ngsol.com> wrote in message
news:#1aHrrHSEHA.380@.tk2msftngp13.phx.gbl...
> Yesterday my sql server was running properly but after reinstalling
primary
> domain controller I failed to login like when I login through windows
> authentication so it gave an error that login failed and if I log through
sa
> password then it gave login failed for default database.
> Can any body give me some idea what I have to do ?
> Thanks
> Noor
>
|||Thanks for your reply but I wanna reply your questions. like you asked
Are you using domain OS user as the service startup account for MSSQL Server
service.
No... MsSqlServer and SqlServer Agent service use LocalSystem account.
1. Did you recreated the same Domain user in PDC
YES.. Same domain
2. By any change did you change the domain name. If yes then you have to
redefine service startup account , recreate OS users to access SQL Server.
Nothing changes but we resinstall the whole system so recreated all the
users.
One more error while restarting the sql server service.
Could not start the SQLSERVERAGENT service on Local Computer.
The service did not return an error. This could be an internal Windows
error or an internal service error.
If the problem persists, contact your system administrator.
Waiting for your reply
Noor
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:uWQHgEJSEHA.3444@.TK2MSFTNGP12.phx.gbl...
> Hi,
> Are you using domain OS user as the service startup account for MSSQL
Server[vbcol=seagreen]
> service.
> Then did you consider those:-
> 1. Did you recreated the same Domain user in PDC
> 2. By any change did you change the domain name. If yes then you have to
> redefine service startup account ,
> recreate OS users to access SQL Server.
> Thanks
> Hari
> MCDBA
> "Noor" <noor@.ngsol.com> wrote in message
> news:#1aHrrHSEHA.380@.tk2msftngp13.phx.gbl...
> primary
through
> sa
>
|||Hi ,
Try starting SQL Server from command prompt.
sqlservr.exe -c
here it gives you the detail of the cause for failure.
Note:
If you reconstruct the PDC server , on recreating the user all the SID to
the user will change, in this case you may need
to revoke and provide access for the users using Trusted connection (OS
Users) in sql server.
Thanks
Hari
MCDBA
"Noor" <noor@.ngsol.com> wrote in message
news:uqDjSsJSEHA.3420@.TK2MSFTNGP11.phx.gbl...
> Thanks for your reply but I wanna reply your questions. like you asked
> Are you using domain OS user as the service startup account for MSSQL
Server
> service.
> No... MsSqlServer and SqlServer Agent service use LocalSystem account.
> 1. Did you recreated the same Domain user in PDC
> YES.. Same domain
> 2. By any change did you change the domain name. If yes then you have to
> redefine service startup account , recreate OS users to access SQL
Server.
> Nothing changes but we resinstall the whole system so recreated all the
> users.
> One more error while restarting the sql server service.
> Could not start the SQLSERVERAGENT service on Local Computer.
> The service did not return an error. This could be an internal Windows
> error or an internal service error.
> If the problem persists, contact your system administrator.
> Waiting for your reply
> Noor
>
> "Hari" <hari_prasad_k@.hotmail.com> wrote in message
> news:uWQHgEJSEHA.3444@.TK2MSFTNGP12.phx.gbl...
> Server
> through
>
|||Thanks Hari, here is the result after using sqlserver.exe -c
D:\Program Files\Microsoft SQL Server\MSSQL\Binn>sqlservr.exe -c
2004-06-03 10:19:21.03 server initerrlog: Could not open error log file
'D:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'. Operating system
error =32(The process cannot access the file because it is being used by
another process.).
2004-06-03 10:19:21.35 server initerrlog: Could not open error log file
'D:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'. Operating system
error =32(The process cannot access the file because it is being used by
another process.).
2004-06-03 10:19:21.68 server initerrlog: Could not open error log file
'D:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'. Operating system
error =32(The process cannot access the file because it is being used by
another process.).
2004-06-03 10:19:22.00 server initerrlog: Could not open error log file
'D:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'. Operating system
error =32(The process cannot access the file because it is being used by
another process.).
2004-06-03 10:19:22.31 server initerrlog: Could not open error log file
'D:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'. Operating system
error =32(The process cannot access the file because it is being used by
another process.).
2004-06-03 10:19:22.62 server initerrlog: Could not open error log file
'D:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'. Operating system
error =32(The process cannot access the file because it is being used by
another process.).
2004-06-03 10:19:22.93 server initerrlog: Could not open error log file
'D:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'. Operating system
error =32(The process cannot access the file because it is being used by
another process.).
2004-06-03 10:19:23.25 server initerrlog: Could not open error log file
'D:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'. Operating system
error =32(The process cannot access the file because it is being used by
another process.).
2004-06-03 10:19:23.56 server initerrlog: Could not open error log file
'D:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'. Operating system
error =32(The process cannot access the file because it is being used by
another process.).
2004-06-03 10:19:23.87 server initerrlog: Could not open error log file
'D:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'. Operating system
error =32(The process cannot access the file because it is being used by
another process.).
2004-06-03 10:19:24.18 server initerrlog: Could not open error log file
'D:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'. Operating system
error =32(The process cannot access the file because it is being used by
another process.).
Any idea what I have to next ?
Thanks
Noor
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:%23dwn8gKSEHA.2372@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> Hi ,
> Try starting SQL Server from command prompt.
> sqlservr.exe -c
> here it gives you the detail of the cause for failure.
> Note:
> If you reconstruct the PDC server , on recreating the user all the SID to
> the user will change, in this case you may need
> to revoke and provide access for the users using Trusted connection (OS
> Users) in sql server.
> Thanks
> Hari
> MCDBA
> "Noor" <noor@.ngsol.com> wrote in message
> news:uqDjSsJSEHA.3420@.TK2MSFTNGP11.phx.gbl...
> Server
> Server.
to[vbcol=seagreen]
windows
>
|||Hi,
Do you have multiple instances of SQL Server running in the same machine.
If Yes, stop all the SQL Agent and MSSQL Server service. Then try to start 1
Instance.
Thanks
Hari
MCDBA
"Noor" <noor@.ngsol.com> wrote in message
news:uBD7IoSSEHA.2908@.TK2MSFTNGP10.phx.gbl...
> Thanks Hari, here is the result after using sqlserver.exe -c
> D:\Program Files\Microsoft SQL Server\MSSQL\Binn>sqlservr.exe -c
> 2004-06-03 10:19:21.03 server initerrlog: Could not open error log file
> 'D:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'. Operating
system
> error =32(The process cannot access the file because it is being used by
> another process.).
> 2004-06-03 10:19:21.35 server initerrlog: Could not open error log file
> 'D:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'. Operating
system
> error =32(The process cannot access the file because it is being used by
> another process.).
> 2004-06-03 10:19:21.68 server initerrlog: Could not open error log file
> 'D:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'. Operating
system
> error =32(The process cannot access the file because it is being used by
> another process.).
> 2004-06-03 10:19:22.00 server initerrlog: Could not open error log file
> 'D:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'. Operating
system
> error =32(The process cannot access the file because it is being used by
> another process.).
> 2004-06-03 10:19:22.31 server initerrlog: Could not open error log file
> 'D:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'. Operating
system
> error =32(The process cannot access the file because it is being used by
> another process.).
> 2004-06-03 10:19:22.62 server initerrlog: Could not open error log file
> 'D:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'. Operating
system
> error =32(The process cannot access the file because it is being used by
> another process.).
> 2004-06-03 10:19:22.93 server initerrlog: Could not open error log file
> 'D:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'. Operating
system
> error =32(The process cannot access the file because it is being used by
> another process.).
> 2004-06-03 10:19:23.25 server initerrlog: Could not open error log file
> 'D:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'. Operating
system
> error =32(The process cannot access the file because it is being used by
> another process.).
> 2004-06-03 10:19:23.56 server initerrlog: Could not open error log file
> 'D:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'. Operating
system
> error =32(The process cannot access the file because it is being used by
> another process.).
> 2004-06-03 10:19:23.87 server initerrlog: Could not open error log file
> 'D:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'. Operating
system
> error =32(The process cannot access the file because it is being used by
> another process.).
> 2004-06-03 10:19:24.18 server initerrlog: Could not open error log file
> 'D:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'. Operating
system[vbcol=seagreen]
> error =32(The process cannot access the file because it is being used by
> another process.).
> Any idea what I have to next ?
> Thanks
> Noor
>
> "Hari" <hari_prasad_k@.hotmail.com> wrote in message
> news:%23dwn8gKSEHA.2372@.TK2MSFTNGP12.phx.gbl...
to[vbcol=seagreen]
to[vbcol=seagreen]
the[vbcol=seagreen]
Windows[vbcol=seagreen]
MSSQL[vbcol=seagreen]
have[vbcol=seagreen]
> to
reinstalling
> windows
>
|||Yes there two instances I have installed in the same machine but only once
instance is running currently but still giving me the same error.
SQL Server Enterprise Manager
A connection could not be established to (LOCAL).
Reason: Login failed for user 'NGSOL\noor'..
Please verify SQL Server is running and check your SQL Server registration
properties (by right-clicking on the (LOCAL) node) and try again.
OK
Thanks
NOOR
"Hari" <hari_prasad_k@.hotmail.com> wrote in message
news:uyO29SVSEHA.2716@.tk2msftngp13.phx.gbl...
> Hi,
> Do you have multiple instances of SQL Server running in the same machine.
> If Yes, stop all the SQL Agent and MSSQL Server service. Then try to start
1[vbcol=seagreen]
> Instance.
> Thanks
> Hari
> MCDBA
>
> "Noor" <noor@.ngsol.com> wrote in message
> news:uBD7IoSSEHA.2908@.TK2MSFTNGP10.phx.gbl...
file[vbcol=seagreen]
> system
file[vbcol=seagreen]
> system
file[vbcol=seagreen]
> system
file[vbcol=seagreen]
> system
file[vbcol=seagreen]
> system
file[vbcol=seagreen]
> system
file[vbcol=seagreen]
> system
file[vbcol=seagreen]
> system
file[vbcol=seagreen]
> system
file[vbcol=seagreen]
> system
file[vbcol=seagreen]
> system
> to
(OS[vbcol=seagreen]
asked[vbcol=seagreen]
MSSQL[vbcol=seagreen]
account.[vbcol=seagreen]
have[vbcol=seagreen]
> to
> the
> Windows
> MSSQL
> have
> reinstalling
log
>

Login alert

Hi all,
I want to be notified when certain users log in to SQL. I configured SQL
Mail, it works properly with several events e.g. 'Login created', but not
with "Login succeded for user '%ls' (18455). The event is set to be written
in Windows eventlog and the Audit levels is set to full. However, the alert
is not fired.
I would appreciate any idea.
Thanks,
Kolos
Kolos,
For nontrusted alerts you need to use 18454, for trusted use, 18453. The
below script works for me for alerting me to anyone logging on using
'sa' as a non-trusted connection.
IF (EXISTS (SELECT name FROM msdb.dbo.sysalerts WHERE name = N'sa login
success'))
-- Delete the alert with the same name.
EXECUTE msdb.dbo.sp_delete_alert @.name = N'sa login success'
BEGIN
EXECUTE msdb.dbo.sp_add_alert @.name = N'sa login success', @.message_id =
18454, @.severity = 0, @.enabled = 1, @.delay_between_responses = 60,
@.include_event_description_in = 4, @.event_description_keyword =
N'''sa''', @.category_name = N'[Uncategorized]'
EXECUTE msdb.dbo.sp_add_notification @.alert_name = N'sa login success',
@.operator_name = N'mark', @.notification_method = 1
END
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Kolos wrote:
> Hi all,
> I want to be notified when certain users log in to SQL. I configured SQL
> Mail, it works properly with several events e.g. 'Login created', but not
> with "Login succeded for user '%ls' (18455). The event is set to be written
> in Windows eventlog and the Audit levels is set to full. However, the alert
> is not fired.
> I would appreciate any idea.
> Thanks,
> Kolos
|||1. Ensure the event is in the NT application log and that it comes from
sqlserver
2 Ensure that SQL Agent is running
3. Ensure that you have the proper alert setup and that is has either
notification or job set to run
4. Ensure that the operator or job is set up correctly
If the NT application log gets full, no more events can be added and
therefore alerts will not fire...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Kolos" <Kolos@.discussions.microsoft.com> wrote in message
news:41585EB8-D279-4A9D-B67E-C4F2776FA720@.microsoft.com...
> Hi all,
> I want to be notified when certain users log in to SQL. I configured SQL
> Mail, it works properly with several events e.g. 'Login created', but not
> with "Login succeded for user '%ls' (18455). The event is set to be
written
> in Windows eventlog and the Audit levels is set to full. However, the
alert
> is not fired.
> I would appreciate any idea.
> Thanks,
> Kolos

Login alert

Hi all,
I want to be notified when certain users log in to SQL. I configured SQL
Mail, it works properly with several events e.g. 'Login created', but not
with "Login succeded for user '%ls' (18455). The event is set to be written
in Windows eventlog and the Audit levels is set to full. However, the alert
is not fired.
I would appreciate any idea.
Thanks,
KolosKolos,
For nontrusted alerts you need to use 18454, for trusted use, 18453. The
below script works for me for alerting me to anyone logging on using
'sa' as a non-trusted connection.
IF (EXISTS (SELECT name FROM msdb.dbo.sysalerts WHERE name = N'sa login
success'))
-- Delete the alert with the same name.
EXECUTE msdb.dbo.sp_delete_alert @.name = N'sa login success'
BEGIN
EXECUTE msdb.dbo.sp_add_alert @.name = N'sa login success', @.message_id =18454, @.severity = 0, @.enabled = 1, @.delay_between_responses = 60,
@.include_event_description_in = 4, @.event_description_keyword =N'''sa''', @.category_name = N'[Uncategorized]'
EXECUTE msdb.dbo.sp_add_notification @.alert_name = N'sa login success',
@.operator_name = N'mark', @.notification_method = 1
END
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Kolos wrote:
> Hi all,
> I want to be notified when certain users log in to SQL. I configured SQL
> Mail, it works properly with several events e.g. 'Login created', but not
> with "Login succeded for user '%ls' (18455). The event is set to be written
> in Windows eventlog and the Audit levels is set to full. However, the alert
> is not fired.
> I would appreciate any idea.
> Thanks,
> Kolos|||1. Ensure the event is in the NT application log and that it comes from
sqlserver
2 Ensure that SQL Agent is running
3. Ensure that you have the proper alert setup and that is has either
notification or job set to run
4. Ensure that the operator or job is set up correctly
If the NT application log gets full, no more events can be added and
therefore alerts will not fire...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Kolos" <Kolos@.discussions.microsoft.com> wrote in message
news:41585EB8-D279-4A9D-B67E-C4F2776FA720@.microsoft.com...
> Hi all,
> I want to be notified when certain users log in to SQL. I configured SQL
> Mail, it works properly with several events e.g. 'Login created', but not
> with "Login succeded for user '%ls' (18455). The event is set to be
written
> in Windows eventlog and the Audit levels is set to full. However, the
alert
> is not fired.
> I would appreciate any idea.
> Thanks,
> Kolos

Login alert

Hi all,
I want to be notified when certain users log in to SQL. I configured SQL
Mail, it works properly with several events e.g. 'Login created', but not
with "Login succeded for user '%ls' (18455). The event is set to be written
in Windows eventlog and the Audit levels is set to full. However, the alert
is not fired.
I would appreciate any idea.
Thanks,
KolosKolos,
For nontrusted alerts you need to use 18454, for trusted use, 18453. The
below script works for me for alerting me to anyone logging on using
'sa' as a non-trusted connection.
IF (EXISTS (SELECT name FROM msdb.dbo.sysalerts WHERE name = N'sa login
success'))
-- Delete the alert with the same name.
EXECUTE msdb.dbo.sp_delete_alert @.name = N'sa login success'
BEGIN
EXECUTE msdb.dbo.sp_add_alert @.name = N'sa login success', @.message_id =
18454, @.severity = 0, @.enabled = 1, @.delay_between_responses = 60,
@.include_event_description_in = 4, @.event_description_keyword =
N'''sa''', @.category_name = N'[Uncategorized]'
EXECUTE msdb.dbo.sp_add_notification @.alert_name = N'sa login success',
@.operator_name = N'mark', @.notification_method = 1
END
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Kolos wrote:
> Hi all,
> I want to be notified when certain users log in to SQL. I configured SQL
> Mail, it works properly with several events e.g. 'Login created', but not
> with "Login succeded for user '%ls' (18455). The event is set to be writte
n
> in Windows eventlog and the Audit levels is set to full. However, the aler
t
> is not fired.
> I would appreciate any idea.
> Thanks,
> Kolos|||1. Ensure the event is in the NT application log and that it comes from
sqlserver
2 Ensure that SQL Agent is running
3. Ensure that you have the proper alert setup and that is has either
notification or job set to run
4. Ensure that the operator or job is set up correctly
If the NT application log gets full, no more events can be added and
therefore alerts will not fire...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Kolos" <Kolos@.discussions.microsoft.com> wrote in message
news:41585EB8-D279-4A9D-B67E-C4F2776FA720@.microsoft.com...
> Hi all,
> I want to be notified when certain users log in to SQL. I configured SQL
> Mail, it works properly with several events e.g. 'Login created', but not
> with "Login succeded for user '%ls' (18455). The event is set to be
written
> in Windows eventlog and the Audit levels is set to full. However, the
alert
> is not fired.
> I would appreciate any idea.
> Thanks,
> Kolos