Hi,
How would one make SQL SERVER Log the IP on failed login attempt ?In SQL2005 this is done by default for failed logins and recorded in the SQL
error log. In SQL2000 you can't do it that effectively (you could get
hostname from a profiler trace but since this can be set in the connection
string it's not reliable)
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
"Tony B." <Test@.spam.ca> wrote in message
news:uh837Qy4GHA.3964@.TK2MSFTNGP04.phx.gbl...
> Hi,
> How would one make SQL SERVER Log the IP on failed login attempt ?
>
>|||Tony/Jasper,
I didn't find any good solutions to prevent hacking of my servers either
so I wrote a utility program to help.
http://www.creeksolutions.com/Produ...92/Default.aspx
BlockSSHacking runs as a Windows service protecting your SQL Server from
brute force hacking attempts coming from the Internet.
The service checks your system every 5 minutes (configurable setting)
for evidence of ongoing hacking. If such attempts are in progress then
those source addresses are blocked from future access to your server
(quickly leading to you recovering your bandwidth).
BlockSSHacking notifies you via email when it has blocked someone from
hacking your system.
Henrik
Jasper Smith wrote:
> In SQL2005 this is done by default for failed logins and recorded in the S
QL
> error log. In SQL2000 you can't do it that effectively (you could get
> hostname from a profiler trace but since this can be set in the connection
> string it's not reliable)
>
Showing posts with label failed. Show all posts
Showing posts with label failed. Show all posts
Friday, March 30, 2012
Log IP Address of attempted logins
I have the security audit logging failed attempts on my MS SQL server.
Is there a way to log the ip address of these attempts?<ryanmhuc@.yahoo.com> wrote in message
news:1107959222.248752.282110@.z14g2000cwz.googlegr oups.com...
>I have the security audit logging failed attempts on my MS SQL server.
> Is there a way to log the ip address of these attempts?
Is there a way to log the ip address of these attempts?<ryanmhuc@.yahoo.com> wrote in message
news:1107959222.248752.282110@.z14g2000cwz.googlegr oups.com...
>I have the security audit logging failed attempts on my MS SQL server.
> Is there a way to log the ip address of these attempts?
Not from MSSQL itself, but you can use OS-level tools:
http://groups.google.ch/groups?hl=e...tngxa06.phx.gbl
Simon
log in failed for user [servername]\ASPNET
can anyone help me with this error message, i follow the instruction of someone in other forum, but i cant find where the SQL Server Enterprise manager is, i am using MSDE.One way To see SQL Server Enterprise manager is to install SQL server :)|||If you don't have Enterprise Manage, you can use the command-line utility OSQL that comes with SQL Server.
You will have a 1> prompt.
Go to the command prompt and type in:
osql -S [servername]\instancename -E -q
You will have a 1> prompt.
use yourdatabasename
goEXEC sp_grantlogin '[servername]\ASPNET'
goEXEC sp_grantdbaccess '[servername]\ASPNET''
go
You can also read this post by David Wier:Error Using Trusted Connection in DB Connection String. I don't recommend adding the ASPNET account as a db_owner, however, so I'd leave off that command at the end.
Terri
log in failed
does anybody know what's wrong with this:
[SqlException: Login failed for user 'username\ASPNET'.]
System.Data.SqlClient.ConnectionPool.GetConnection(Boolean& isInTransaction)
System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction)
System.Data.SqlClient.SqlConnection.Open()
LouMayuga.lou_register.submit_button_Click(Object sender, EventArgs e) in c:\inetpub\wwwroot\LouMayuga\lou_register.aspx.vb:94
System.Web.UI.WebControls.Button.OnClick(EventArgs e)
System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
System.Web.UI.Page.ProcessRequestMain()
I can't insert my data to my datbase and always got this kind of comment. I wonder whats wrong!
this is my code:
Private Sub submit_button_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles submit_button.Click
Me.SqlInsertCommand1 = New System.Data.SqlClient.SqlCommand
Me.SqlConnection1 = New System.Data.SqlClient.SqlConnection
Me.SqlDataAdapter1 = New System.Data.SqlClient.SqlDataAdapter
Me.SqlInsertCommand1.CommandText = "INSERT INTO [Log In] ([User Name], [User Password]) VALUES (@.Param1, @.Param2); SE" & _
"LECT [User Id], [User Name], [User Password] FROM [Log In]"
Me.SqlInsertCommand1.Connection = Me.SqlConnection1
Me.SqlInsertCommand1.Parameters.Add(New System.Data.SqlClient.SqlParameter("@.Param1", System.Data.SqlDbType.VarChar, 50, "User Name"))
Me.SqlInsertCommand1.Parameters.Add(New System.Data.SqlClient.SqlParameter("@.Param2", System.Data.SqlDbType.VarChar, 50, "User Password"))
Me.SqlConnection1.ConnectionString = "workstation id=""EFREN-0SLIO0"";packet size=4096;user id=efren;integrated securi" & _
"ty=SSPI;data source=""efrenmay-0slio0"";persist security info=False;initial catalo" & _
"g=BizTalkDTADb"
Me.SqlConnection1.Open()
Me.SqlDataAdapter1.InsertCommand = Me.SqlInsertCommand1
Me.SqlDataAdapter1.SelectCommand = Me.SqlSelectCommand1
Me.SqlDataAdapter1.TableMappings.AddRange(New System.Data.Common.DataTableMapping() {New System.Data.Common.DataTableMapping("Table", "Log In", New System.Data.Common.DataColumnMapping() {New System.Data.Common.DataColumnMapping("User Id", "User Id"), New System.Data.Common.DataColumnMapping("User Name", "User Name"), New System.Data.Common.DataColumnMapping("User Password", "User Password")})})
Me.SqlConnection1.Close()
End Subview post 673219
hth
Wednesday, March 28, 2012
Log files..
Okay, i must be going crazy. I created a log file;executed the package, it failed in Conrol flow. As expected there was a log file with all the info. Minutes later, i happend to change the connection in the connection manager, and now my log file is not generating any enteries. I have seen this behaviour many times, where it will some times create a log and other time don't. Most of my events are OnError so it should create some log?
I don't understand
-kuspaw
how odd,
when you define a log by means of SSIS log provider for Text Files you must choose for every task all those events in which are you interested (at least on Control Flow layer)
|||Acually it happens quite often when i manually delete contents of log file, it stops writting to it. I tried OnError, OnPreExecute, OnFailure events but no contents in log file. I can see errors in output window but package is not writting anything to log file.
-kushpaw
Monday, March 12, 2012
Log file failed to grow despite lots of free disk space
Hello -
I had a strange problem last night and I wanted to ask if anyone else
has ever experienced it.
I have a transaction log set to Auto-grow by 10% with unrestricted
file growth. When I left last night the .ldf file took up 3GB of
space but only about 10% of it was used. I also had an additional 2GB
of free space on the disk which holds the log.
When I came in this morning, queries were timing out because the log
was full. The log file had NOT grown and Windows was reporting 2GB of
free space.
I cleared out a few other files, freeing up another 1GB and all of the
sudden the log grew and queries started working again.
Does anybody know what could have happened here? Are there any
reasons why the log file would fail to grow into remaining disk space?
Or, alternatively, could Windows ever report an incorrect amount of
free disk space?
Thanks!
David SimardSometimes, grow doesn't seem to be fast enough for the modifications. Could be such a case...
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"DaveS" <davesimard@.hotmail.com> wrote in message
news:f8e708df.0310210656.2c65881b@.posting.google.com...
> Hello -
> I had a strange problem last night and I wanted to ask if anyone else
> has ever experienced it.
> I have a transaction log set to Auto-grow by 10% with unrestricted
> file growth. When I left last night the .ldf file took up 3GB of
> space but only about 10% of it was used. I also had an additional 2GB
> of free space on the disk which holds the log.
> When I came in this morning, queries were timing out because the log
> was full. The log file had NOT grown and Windows was reporting 2GB of
> free space.
> I cleared out a few other files, freeing up another 1GB and all of the
> sudden the log grew and queries started working again.
> Does anybody know what could have happened here? Are there any
> reasons why the log file would fail to grow into remaining disk space?
> Or, alternatively, could Windows ever report an incorrect amount of
> free disk space?
> Thanks!
> David Simard|||See if your error log contains a 'log file is full' message.
If so, it's the problem mentioned by tibor
This is the
"DaveS" <davesimard@.hotmail.com> wrote in message
news:f8e708df.0310210656.2c65881b@.posting.google.com...
> Hello -
> I had a strange problem last night and I wanted to ask if anyone else
> has ever experienced it.
> I have a transaction log set to Auto-grow by 10% with unrestricted
> file growth. When I left last night the .ldf file took up 3GB of
> space but only about 10% of it was used. I also had an additional 2GB
> of free space on the disk which holds the log.
> When I came in this morning, queries were timing out because the log
> was full. The log file had NOT grown and Windows was reporting 2GB of
> free space.
> I cleared out a few other files, freeing up another 1GB and all of the
> sudden the log grew and queries started working again.
> Does anybody know what could have happened here? Are there any
> reasons why the log file would fail to grow into remaining disk space?
> Or, alternatively, could Windows ever report an incorrect amount of
> free disk space?
> Thanks!
> David Simard|||If that were the case, wouldn't the problem resolve itself in moments?
We had queries timing out over a period of a few hours.
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se> wrote in message news:<uZTzBoGmDHA.372@.TK2MSFTNGP11.phx.gbl>...
> Sometimes, grow doesn't seem to be fast enough for the modifications. Could be such a case...
> --
> Tibor Karaszi, SQL Server MVP
> Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "DaveS" <davesimard@.hotmail.com> wrote in message
> news:f8e708df.0310210656.2c65881b@.posting.google.com...
> > Hello -
> >
> > I had a strange problem last night and I wanted to ask if anyone else
> > has ever experienced it.
> >
> > I have a transaction log set to Auto-grow by 10% with unrestricted
> > file growth. When I left last night the .ldf file took up 3GB of
> > space but only about 10% of it was used. I also had an additional 2GB
> > of free space on the disk which holds the log.
> >
> > When I came in this morning, queries were timing out because the log
> > was full. The log file had NOT grown and Windows was reporting 2GB of
> > free space.
> >
> > I cleared out a few other files, freeing up another 1GB and all of the
> > sudden the log grew and queries started working again.
> >
> > Does anybody know what could have happened here? Are there any
> > reasons why the log file would fail to grow into remaining disk space?
> > Or, alternatively, could Windows ever report an incorrect amount of
> > free disk space?
> >
> > Thanks!
> >
> > David Simard|||Actually, now that you mention it: no, there weren't any 'log file is
full' messages in the log. I just assumed that was the problem since
the queries starting running again right after the log file grew.
But I guess I know what happens when you assume...
"Stressed" <k@.c.co.uk> wrote in message news:<#me0n5HmDHA.644@.TK2MSFTNGP11.phx.gbl>...
> See if your error log contains a 'log file is full' message.
> If so, it's the problem mentioned by tibor
> This is the
> "DaveS" <davesimard@.hotmail.com> wrote in message
> news:f8e708df.0310210656.2c65881b@.posting.google.com...
> > Hello -
> >
> > I had a strange problem last night and I wanted to ask if anyone else
> > has ever experienced it.
> >
> > I have a transaction log set to Auto-grow by 10% with unrestricted
> > file growth. When I left last night the .ldf file took up 3GB of
> > space but only about 10% of it was used. I also had an additional 2GB
> > of free space on the disk which holds the log.
> >
> > When I came in this morning, queries were timing out because the log
> > was full. The log file had NOT grown and Windows was reporting 2GB of
> > free space.
> >
> > I cleared out a few other files, freeing up another 1GB and all of the
> > sudden the log grew and queries started working again.
> >
> > Does anybody know what could have happened here? Are there any
> > reasons why the log file would fail to grow into remaining disk space?
> > Or, alternatively, could Windows ever report an incorrect amount of
> > free disk space?
> >
> > Thanks!
> >
> > David Simard|||Any other 'interesting' messages in the error log on the run up to this?
"DaveS" <davesimard@.hotmail.com> wrote in message
news:f8e708df.0310220842.f863fef@.posting.google.com...
> Actually, now that you mention it: no, there weren't any 'log file is
> full' messages in the log. I just assumed that was the problem since
> the queries starting running again right after the log file grew.
> But I guess I know what happens when you assume...
> "Stressed" <k@.c.co.uk> wrote in message
news:<#me0n5HmDHA.644@.TK2MSFTNGP11.phx.gbl>...
> > See if your error log contains a 'log file is full' message.
> >
> > If so, it's the problem mentioned by tibor
> >
> > This is the
> >
> > "DaveS" <davesimard@.hotmail.com> wrote in message
> > news:f8e708df.0310210656.2c65881b@.posting.google.com...
> > > Hello -
> > >
> > > I had a strange problem last night and I wanted to ask if anyone else
> > > has ever experienced it.
> > >
> > > I have a transaction log set to Auto-grow by 10% with unrestricted
> > > file growth. When I left last night the .ldf file took up 3GB of
> > > space but only about 10% of it was used. I also had an additional 2GB
> > > of free space on the disk which holds the log.
> > >
> > > When I came in this morning, queries were timing out because the log
> > > was full. The log file had NOT grown and Windows was reporting 2GB of
> > > free space.
> > >
> > > I cleared out a few other files, freeing up another 1GB and all of the
> > > sudden the log grew and queries started working again.
> > >
> > > Does anybody know what could have happened here? Are there any
> > > reasons why the log file would fail to grow into remaining disk space?
> > > Or, alternatively, could Windows ever report an incorrect amount of
> > > free disk space?
> > >
> > > Thanks!
> > >
> > > David Simard
I had a strange problem last night and I wanted to ask if anyone else
has ever experienced it.
I have a transaction log set to Auto-grow by 10% with unrestricted
file growth. When I left last night the .ldf file took up 3GB of
space but only about 10% of it was used. I also had an additional 2GB
of free space on the disk which holds the log.
When I came in this morning, queries were timing out because the log
was full. The log file had NOT grown and Windows was reporting 2GB of
free space.
I cleared out a few other files, freeing up another 1GB and all of the
sudden the log grew and queries started working again.
Does anybody know what could have happened here? Are there any
reasons why the log file would fail to grow into remaining disk space?
Or, alternatively, could Windows ever report an incorrect amount of
free disk space?
Thanks!
David SimardSometimes, grow doesn't seem to be fast enough for the modifications. Could be such a case...
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"DaveS" <davesimard@.hotmail.com> wrote in message
news:f8e708df.0310210656.2c65881b@.posting.google.com...
> Hello -
> I had a strange problem last night and I wanted to ask if anyone else
> has ever experienced it.
> I have a transaction log set to Auto-grow by 10% with unrestricted
> file growth. When I left last night the .ldf file took up 3GB of
> space but only about 10% of it was used. I also had an additional 2GB
> of free space on the disk which holds the log.
> When I came in this morning, queries were timing out because the log
> was full. The log file had NOT grown and Windows was reporting 2GB of
> free space.
> I cleared out a few other files, freeing up another 1GB and all of the
> sudden the log grew and queries started working again.
> Does anybody know what could have happened here? Are there any
> reasons why the log file would fail to grow into remaining disk space?
> Or, alternatively, could Windows ever report an incorrect amount of
> free disk space?
> Thanks!
> David Simard|||See if your error log contains a 'log file is full' message.
If so, it's the problem mentioned by tibor
This is the
"DaveS" <davesimard@.hotmail.com> wrote in message
news:f8e708df.0310210656.2c65881b@.posting.google.com...
> Hello -
> I had a strange problem last night and I wanted to ask if anyone else
> has ever experienced it.
> I have a transaction log set to Auto-grow by 10% with unrestricted
> file growth. When I left last night the .ldf file took up 3GB of
> space but only about 10% of it was used. I also had an additional 2GB
> of free space on the disk which holds the log.
> When I came in this morning, queries were timing out because the log
> was full. The log file had NOT grown and Windows was reporting 2GB of
> free space.
> I cleared out a few other files, freeing up another 1GB and all of the
> sudden the log grew and queries started working again.
> Does anybody know what could have happened here? Are there any
> reasons why the log file would fail to grow into remaining disk space?
> Or, alternatively, could Windows ever report an incorrect amount of
> free disk space?
> Thanks!
> David Simard|||If that were the case, wouldn't the problem resolve itself in moments?
We had queries timing out over a period of a few hours.
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se> wrote in message news:<uZTzBoGmDHA.372@.TK2MSFTNGP11.phx.gbl>...
> Sometimes, grow doesn't seem to be fast enough for the modifications. Could be such a case...
> --
> Tibor Karaszi, SQL Server MVP
> Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "DaveS" <davesimard@.hotmail.com> wrote in message
> news:f8e708df.0310210656.2c65881b@.posting.google.com...
> > Hello -
> >
> > I had a strange problem last night and I wanted to ask if anyone else
> > has ever experienced it.
> >
> > I have a transaction log set to Auto-grow by 10% with unrestricted
> > file growth. When I left last night the .ldf file took up 3GB of
> > space but only about 10% of it was used. I also had an additional 2GB
> > of free space on the disk which holds the log.
> >
> > When I came in this morning, queries were timing out because the log
> > was full. The log file had NOT grown and Windows was reporting 2GB of
> > free space.
> >
> > I cleared out a few other files, freeing up another 1GB and all of the
> > sudden the log grew and queries started working again.
> >
> > Does anybody know what could have happened here? Are there any
> > reasons why the log file would fail to grow into remaining disk space?
> > Or, alternatively, could Windows ever report an incorrect amount of
> > free disk space?
> >
> > Thanks!
> >
> > David Simard|||Actually, now that you mention it: no, there weren't any 'log file is
full' messages in the log. I just assumed that was the problem since
the queries starting running again right after the log file grew.
But I guess I know what happens when you assume...
"Stressed" <k@.c.co.uk> wrote in message news:<#me0n5HmDHA.644@.TK2MSFTNGP11.phx.gbl>...
> See if your error log contains a 'log file is full' message.
> If so, it's the problem mentioned by tibor
> This is the
> "DaveS" <davesimard@.hotmail.com> wrote in message
> news:f8e708df.0310210656.2c65881b@.posting.google.com...
> > Hello -
> >
> > I had a strange problem last night and I wanted to ask if anyone else
> > has ever experienced it.
> >
> > I have a transaction log set to Auto-grow by 10% with unrestricted
> > file growth. When I left last night the .ldf file took up 3GB of
> > space but only about 10% of it was used. I also had an additional 2GB
> > of free space on the disk which holds the log.
> >
> > When I came in this morning, queries were timing out because the log
> > was full. The log file had NOT grown and Windows was reporting 2GB of
> > free space.
> >
> > I cleared out a few other files, freeing up another 1GB and all of the
> > sudden the log grew and queries started working again.
> >
> > Does anybody know what could have happened here? Are there any
> > reasons why the log file would fail to grow into remaining disk space?
> > Or, alternatively, could Windows ever report an incorrect amount of
> > free disk space?
> >
> > Thanks!
> >
> > David Simard|||Any other 'interesting' messages in the error log on the run up to this?
"DaveS" <davesimard@.hotmail.com> wrote in message
news:f8e708df.0310220842.f863fef@.posting.google.com...
> Actually, now that you mention it: no, there weren't any 'log file is
> full' messages in the log. I just assumed that was the problem since
> the queries starting running again right after the log file grew.
> But I guess I know what happens when you assume...
> "Stressed" <k@.c.co.uk> wrote in message
news:<#me0n5HmDHA.644@.TK2MSFTNGP11.phx.gbl>...
> > See if your error log contains a 'log file is full' message.
> >
> > If so, it's the problem mentioned by tibor
> >
> > This is the
> >
> > "DaveS" <davesimard@.hotmail.com> wrote in message
> > news:f8e708df.0310210656.2c65881b@.posting.google.com...
> > > Hello -
> > >
> > > I had a strange problem last night and I wanted to ask if anyone else
> > > has ever experienced it.
> > >
> > > I have a transaction log set to Auto-grow by 10% with unrestricted
> > > file growth. When I left last night the .ldf file took up 3GB of
> > > space but only about 10% of it was used. I also had an additional 2GB
> > > of free space on the disk which holds the log.
> > >
> > > When I came in this morning, queries were timing out because the log
> > > was full. The log file had NOT grown and Windows was reporting 2GB of
> > > free space.
> > >
> > > I cleared out a few other files, freeing up another 1GB and all of the
> > > sudden the log grew and queries started working again.
> > >
> > > Does anybody know what could have happened here? Are there any
> > > reasons why the log file would fail to grow into remaining disk space?
> > > Or, alternatively, could Windows ever report an incorrect amount of
> > > free disk space?
> > >
> > > Thanks!
> > >
> > > David Simard
Log File Error
Good Morning
We have a nightly DTS job, which uploads data, to a number of tables (35
tables). However the DTS job failed last night, due to the following error
returned :
****
Error Source: Microsoft OLE DB Provider for SQL Server
Error Description:The log file for database 'G_Data' is full. Back up the
transaction log for the database to free up some log space.
****
However, on the properties of the Database (G_Data) , the option for Auto
File Growth was selected and Increase by 20 percent. So I am somewhat
puzzled that there error occured?
This isn't a recurring error, since the last time this error had happened
was about 6 months ago - Is it in connnection with the frequency of jobs
that I am runnning or is there something wrong with the settings I have
selected?
Kind Regards
Ricky
(Win2K Server/SQL2K-SP4)maybe an_available_free_space_of_the_volume_wh
ich_the_tlog_is_resided_on <
a_current_size_of_the_tlog * 1.2
--
Andrey Odegov
avodeGOV@.yandex.ru
(remove GOV to respond)
"Ricky" <MSN.MSN.com> wrote in message
news:ebu38YSDGHA.2436@.TK2MSFTNGP15.phx.gbl...
> Good Morning
> We have a nightly DTS job, which uploads data, to a number of tables (35
> tables). However the DTS job failed last night, due to the following
> error
> returned :
> ****
> Error Source: Microsoft OLE DB Provider for SQL Server
> Error Description:The log file for database 'G_Data' is full. Back up the
> transaction log for the database to free up some log space.
> ****
> However, on the properties of the Database (G_Data) , the option for Auto
> File Growth was selected and Increase by 20 percent. So I am somewhat
> puzzled that there error occured?
> This isn't a recurring error, since the last time this error had happened
> was about 6 months ago - Is it in connnection with the frequency of jobs
> that I am runnning or is there something wrong with the settings I have
> selected?
> Kind Regards
> Ricky
> (Win2K Server/SQL2K-SP4)
>|||A file will only grow until there's enough free space on the disk. More
critically - why don't you backup your transaction log?
ML
http://milambda.blogspot.com/|||After backing up, do I delete it?
"ML" <ML@.discussions.microsoft.com> wrote in message
news:19632D48-8D08-4F4D-97EE-B0F0C2F2A4E8@.microsoft.com...
> A file will only grow until there's enough free space on the disk. More
> critically - why don't you backup your transaction log?
>
> ML
> --
> http://milambda.blogspot.com/|||... or an account which the sql server runs in is restricted with quota
settings of the volume
--
Andrey Odegov
avodeGOV@.yandex.ru
(remove GOV to respond)
"Andrey Odegov" <avodeGOV@.mail.ru> wrote in message
news:eiUSgySDGHA.2300@.TK2MSFTNGP15.phx.gbl...
> maybe an_available_free_space_of_the_volume_wh
ich_the_tlog_is_resided_on <
> a_current_size_of_the_tlog * 1.2
> --
> Andrey Odegov
> avodeGOV@.yandex.ru
> (remove GOV to respond)
> "Ricky" <MSN.MSN.com> wrote in message
> news:ebu38YSDGHA.2436@.TK2MSFTNGP15.phx.gbl...
>|||NO! After you back it up, there should be free space available because the
backed-up transactions can be overwritten.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ricky" <MSN.MSN.com> wrote in message
news:u1lVCCTDGHA.2040@.TK2MSFTNGP14.phx.gbl...
> After backing up, do I delete it?
> "ML" <ML@.discussions.microsoft.com> wrote in message
> news:19632D48-8D08-4F4D-97EE-B0F0C2F2A4E8@.microsoft.com...
>
We have a nightly DTS job, which uploads data, to a number of tables (35
tables). However the DTS job failed last night, due to the following error
returned :
****
Error Source: Microsoft OLE DB Provider for SQL Server
Error Description:The log file for database 'G_Data' is full. Back up the
transaction log for the database to free up some log space.
****
However, on the properties of the Database (G_Data) , the option for Auto
File Growth was selected and Increase by 20 percent. So I am somewhat
puzzled that there error occured?
This isn't a recurring error, since the last time this error had happened
was about 6 months ago - Is it in connnection with the frequency of jobs
that I am runnning or is there something wrong with the settings I have
selected?
Kind Regards
Ricky
(Win2K Server/SQL2K-SP4)maybe an_available_free_space_of_the_volume_wh
ich_the_tlog_is_resided_on <
a_current_size_of_the_tlog * 1.2
--
Andrey Odegov
avodeGOV@.yandex.ru
(remove GOV to respond)
"Ricky" <MSN.MSN.com> wrote in message
news:ebu38YSDGHA.2436@.TK2MSFTNGP15.phx.gbl...
> Good Morning
> We have a nightly DTS job, which uploads data, to a number of tables (35
> tables). However the DTS job failed last night, due to the following
> error
> returned :
> ****
> Error Source: Microsoft OLE DB Provider for SQL Server
> Error Description:The log file for database 'G_Data' is full. Back up the
> transaction log for the database to free up some log space.
> ****
> However, on the properties of the Database (G_Data) , the option for Auto
> File Growth was selected and Increase by 20 percent. So I am somewhat
> puzzled that there error occured?
> This isn't a recurring error, since the last time this error had happened
> was about 6 months ago - Is it in connnection with the frequency of jobs
> that I am runnning or is there something wrong with the settings I have
> selected?
> Kind Regards
> Ricky
> (Win2K Server/SQL2K-SP4)
>|||A file will only grow until there's enough free space on the disk. More
critically - why don't you backup your transaction log?
ML
http://milambda.blogspot.com/|||After backing up, do I delete it?
"ML" <ML@.discussions.microsoft.com> wrote in message
news:19632D48-8D08-4F4D-97EE-B0F0C2F2A4E8@.microsoft.com...
> A file will only grow until there's enough free space on the disk. More
> critically - why don't you backup your transaction log?
>
> ML
> --
> http://milambda.blogspot.com/|||... or an account which the sql server runs in is restricted with quota
settings of the volume
--
Andrey Odegov
avodeGOV@.yandex.ru
(remove GOV to respond)
"Andrey Odegov" <avodeGOV@.mail.ru> wrote in message
news:eiUSgySDGHA.2300@.TK2MSFTNGP15.phx.gbl...
> maybe an_available_free_space_of_the_volume_wh
ich_the_tlog_is_resided_on <
> a_current_size_of_the_tlog * 1.2
> --
> Andrey Odegov
> avodeGOV@.yandex.ru
> (remove GOV to respond)
> "Ricky" <MSN.MSN.com> wrote in message
> news:ebu38YSDGHA.2436@.TK2MSFTNGP15.phx.gbl...
>|||NO! After you back it up, there should be free space available because the
backed-up transactions can be overwritten.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ricky" <MSN.MSN.com> wrote in message
news:u1lVCCTDGHA.2040@.TK2MSFTNGP14.phx.gbl...
> After backing up, do I delete it?
> "ML" <ML@.discussions.microsoft.com> wrote in message
> news:19632D48-8D08-4F4D-97EE-B0F0C2F2A4E8@.microsoft.com...
>
Friday, February 24, 2012
Log Backup Job works, but reports failure.
All the transaction logs are created, but the Application log entry below
appears, and the job shows as having failed.
Any ideas, anyone?
Thanks,
Jim
Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 8/2/2005
Time: 9:47:24 AM
User: N/A
Computer: GENOME-MARS
Description:
SQL Server Scheduled Job 'Transaction Log Backup Job for DB Maintenance Plan
'DB Maintenance Plan 1'' (0xAF8C5DECB6A71142915AA55ED294E0B4) - Status:
Failed - Invoked on: 2005-08-02 09:07:42 - Message: The job failed. The Job
was invoked by User UAB\jmoon. The last step to run was step 1 (Step 1).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Start Enterprise Mangler. Drill down to Management | Database Maintenance
Plans. Right click and select "Maintenance Plan History...". Set the
filters to isolate the plan that failed. Select the entry for the plan and
the failure date, click the "Properties..." button to see the details of why
it failed.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Jim" <please.reply@.group> wrote in message
news:upRvnl4lFHA.3656@.TK2MSFTNGP09.phx.gbl...
> All the transaction logs are created, but the Application log entry below
> appears, and the job shows as having failed.
> Any ideas, anyone?
> Thanks,
> Jim
> --
> Event Type: Warning
> Event Source: SQLSERVERAGENT
> Event Category: Job Engine
> Event ID: 208
> Date: 8/2/2005
> Time: 9:47:24 AM
> User: N/A
> Computer: GENOME-MARS
> Description:
> SQL Server Scheduled Job 'Transaction Log Backup Job for DB Maintenance
> Plan 'DB Maintenance Plan 1'' (0xAF8C5DECB6A71142915AA55ED294E0B4) -
> Status: Failed - Invoked on: 2005-08-02 09:07:42 - Message: The job
> failed. The Job was invoked by User UAB\jmoon. The last step to run was
> step 1 (Step 1).
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> ----
>
|||Here's the explanation!
http://support.microsoft.com/default...&Product=sql2k
Simple recovery model is the culprit--can't do transaction log backups...
Jim
"Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in message
news:u%23LtDp4lFHA.2628@.tk2msftngp13.phx.gbl...
> Start Enterprise Mangler. Drill down to Management | Database Maintenance
> Plans. Right click and select "Maintenance Plan History...". Set the
> filters to isolate the plan that failed. Select the entry for the plan
> and the failure date, click the "Properties..." button to see the details
> of why it failed.
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Jim" <please.reply@.group> wrote in message
> news:upRvnl4lFHA.3656@.TK2MSFTNGP09.phx.gbl...
>
appears, and the job shows as having failed.
Any ideas, anyone?
Thanks,
Jim
Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 8/2/2005
Time: 9:47:24 AM
User: N/A
Computer: GENOME-MARS
Description:
SQL Server Scheduled Job 'Transaction Log Backup Job for DB Maintenance Plan
'DB Maintenance Plan 1'' (0xAF8C5DECB6A71142915AA55ED294E0B4) - Status:
Failed - Invoked on: 2005-08-02 09:07:42 - Message: The job failed. The Job
was invoked by User UAB\jmoon. The last step to run was step 1 (Step 1).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Start Enterprise Mangler. Drill down to Management | Database Maintenance
Plans. Right click and select "Maintenance Plan History...". Set the
filters to isolate the plan that failed. Select the entry for the plan and
the failure date, click the "Properties..." button to see the details of why
it failed.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Jim" <please.reply@.group> wrote in message
news:upRvnl4lFHA.3656@.TK2MSFTNGP09.phx.gbl...
> All the transaction logs are created, but the Application log entry below
> appears, and the job shows as having failed.
> Any ideas, anyone?
> Thanks,
> Jim
> --
> Event Type: Warning
> Event Source: SQLSERVERAGENT
> Event Category: Job Engine
> Event ID: 208
> Date: 8/2/2005
> Time: 9:47:24 AM
> User: N/A
> Computer: GENOME-MARS
> Description:
> SQL Server Scheduled Job 'Transaction Log Backup Job for DB Maintenance
> Plan 'DB Maintenance Plan 1'' (0xAF8C5DECB6A71142915AA55ED294E0B4) -
> Status: Failed - Invoked on: 2005-08-02 09:07:42 - Message: The job
> failed. The Job was invoked by User UAB\jmoon. The last step to run was
> step 1 (Step 1).
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> ----
>
|||Here's the explanation!
http://support.microsoft.com/default...&Product=sql2k
Simple recovery model is the culprit--can't do transaction log backups...
Jim
"Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in message
news:u%23LtDp4lFHA.2628@.tk2msftngp13.phx.gbl...
> Start Enterprise Mangler. Drill down to Management | Database Maintenance
> Plans. Right click and select "Maintenance Plan History...". Set the
> filters to isolate the plan that failed. Select the entry for the plan
> and the failure date, click the "Properties..." button to see the details
> of why it failed.
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Jim" <please.reply@.group> wrote in message
> news:upRvnl4lFHA.3656@.TK2MSFTNGP09.phx.gbl...
>
Log Backup Job works, but reports failure.
All the transaction logs are created, but the Application log entry below
appears, and the job shows as having failed.
Any ideas, anyone?
Thanks,
Jim
--
Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 8/2/2005
Time: 9:47:24 AM
User: N/A
Computer: GENOME-MARS
Description:
SQL Server Scheduled Job 'Transaction Log Backup Job for DB Maintenance Plan
'DB Maintenance Plan 1'' (0xAF8C5DECB6A71142915AA55ED294E0B4) - Status:
Failed - Invoked on: 2005-08-02 09:07:42 - Message: The job failed. The Job
was invoked by User UAB\jmoon. The last step to run was step 1 (Step 1).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
----
--Start Enterprise Mangler. Drill down to Management | Database Maintenance
Plans. Right click and select "Maintenance Plan History...". Set the
filters to isolate the plan that failed. Select the entry for the plan and
the failure date, click the "Properties..." button to see the details of why
it failed.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Jim" <please.reply@.group> wrote in message
news:upRvnl4lFHA.3656@.TK2MSFTNGP09.phx.gbl...
> All the transaction logs are created, but the Application log entry below
> appears, and the job shows as having failed.
> Any ideas, anyone?
> Thanks,
> Jim
> --
> Event Type: Warning
> Event Source: SQLSERVERAGENT
> Event Category: Job Engine
> Event ID: 208
> Date: 8/2/2005
> Time: 9:47:24 AM
> User: N/A
> Computer: GENOME-MARS
> Description:
> SQL Server Scheduled Job 'Transaction Log Backup Job for DB Maintenance
> Plan 'DB Maintenance Plan 1'' (0xAF8C5DECB6A71142915AA55ED294E0B4) -
> Status: Failed - Invoked on: 2005-08-02 09:07:42 - Message: The job
> failed. The Job was invoked by User UAB\jmoon. The last step to run was
> step 1 (Step 1).
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> ----
--
>|||Here's the explanation!
http://support.microsoft.com/defaul...2&Product=sql2k
Simple recovery model is the culprit--can't do transaction log backups...
Jim
"Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in message
news:u%23LtDp4lFHA.2628@.tk2msftngp13.phx.gbl...
> Start Enterprise Mangler. Drill down to Management | Database Maintenance
> Plans. Right click and select "Maintenance Plan History...". Set the
> filters to isolate the plan that failed. Select the entry for the plan
> and the failure date, click the "Properties..." button to see the details
> of why it failed.
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Jim" <please.reply@.group> wrote in message
> news:upRvnl4lFHA.3656@.TK2MSFTNGP09.phx.gbl...
>
appears, and the job shows as having failed.
Any ideas, anyone?
Thanks,
Jim
--
Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 8/2/2005
Time: 9:47:24 AM
User: N/A
Computer: GENOME-MARS
Description:
SQL Server Scheduled Job 'Transaction Log Backup Job for DB Maintenance Plan
'DB Maintenance Plan 1'' (0xAF8C5DECB6A71142915AA55ED294E0B4) - Status:
Failed - Invoked on: 2005-08-02 09:07:42 - Message: The job failed. The Job
was invoked by User UAB\jmoon. The last step to run was step 1 (Step 1).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
----
--Start Enterprise Mangler. Drill down to Management | Database Maintenance
Plans. Right click and select "Maintenance Plan History...". Set the
filters to isolate the plan that failed. Select the entry for the plan and
the failure date, click the "Properties..." button to see the details of why
it failed.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Jim" <please.reply@.group> wrote in message
news:upRvnl4lFHA.3656@.TK2MSFTNGP09.phx.gbl...
> All the transaction logs are created, but the Application log entry below
> appears, and the job shows as having failed.
> Any ideas, anyone?
> Thanks,
> Jim
> --
> Event Type: Warning
> Event Source: SQLSERVERAGENT
> Event Category: Job Engine
> Event ID: 208
> Date: 8/2/2005
> Time: 9:47:24 AM
> User: N/A
> Computer: GENOME-MARS
> Description:
> SQL Server Scheduled Job 'Transaction Log Backup Job for DB Maintenance
> Plan 'DB Maintenance Plan 1'' (0xAF8C5DECB6A71142915AA55ED294E0B4) -
> Status: Failed - Invoked on: 2005-08-02 09:07:42 - Message: The job
> failed. The Job was invoked by User UAB\jmoon. The last step to run was
> step 1 (Step 1).
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> ----
--
>|||Here's the explanation!
http://support.microsoft.com/defaul...2&Product=sql2k
Simple recovery model is the culprit--can't do transaction log backups...
Jim
"Geoff N. Hiten" <sqlcraftsman@.gmail.com> wrote in message
news:u%23LtDp4lFHA.2628@.tk2msftngp13.phx.gbl...
> Start Enterprise Mangler. Drill down to Management | Database Maintenance
> Plans. Right click and select "Maintenance Plan History...". Set the
> filters to isolate the plan that failed. Select the entry for the plan
> and the failure date, click the "Properties..." button to see the details
> of why it failed.
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Jim" <please.reply@.group> wrote in message
> news:upRvnl4lFHA.3656@.TK2MSFTNGP09.phx.gbl...
>
Log Agent fails "could not execute sp_repldone / sp_replcounters"
The Log Reader Agent has failed again with the error "Could not execute
sp_repldone/sp_replcounters.." and we are unable to restart the agent.
MSrepl_transactions table holds two entries on the Distribution database one
dated 9-24 and the other 10-10, and the xact_id is not the same as the one
listed with sp_replcmds run on the publisher. What can we do to restart the
Log Agent and not loose any transactions?
Please help...
Thanks,
Fidel Arbizu.
enable logging as per this kb and post the log back here.
http://support.microsoft.com/default...b;en-us;312292
"farbizu" <farbizu@.discussions.microsoft.com> wrote in message
news:8903046C-0E27-4200-AED8-C411BDF18E34@.microsoft.com...
> The Log Reader Agent has failed again with the error "Could not execute
> sp_repldone/sp_replcounters.." and we are unable to restart the agent.
> MSrepl_transactions table holds two entries on the Distribution database
> one
> dated 9-24 and the other 10-10, and the xact_id is not the same as the one
> listed with sp_replcmds run on the publisher. What can we do to restart
> the
> Log Agent and not loose any transactions?
> Please help...
> Thanks,
> Fidel Arbizu.
>
sp_repldone/sp_replcounters.." and we are unable to restart the agent.
MSrepl_transactions table holds two entries on the Distribution database one
dated 9-24 and the other 10-10, and the xact_id is not the same as the one
listed with sp_replcmds run on the publisher. What can we do to restart the
Log Agent and not loose any transactions?
Please help...
Thanks,
Fidel Arbizu.
enable logging as per this kb and post the log back here.
http://support.microsoft.com/default...b;en-us;312292
"farbizu" <farbizu@.discussions.microsoft.com> wrote in message
news:8903046C-0E27-4200-AED8-C411BDF18E34@.microsoft.com...
> The Log Reader Agent has failed again with the error "Could not execute
> sp_repldone/sp_replcounters.." and we are unable to restart the agent.
> MSrepl_transactions table holds two entries on the Distribution database
> one
> dated 9-24 and the other 10-10, and the xact_id is not the same as the one
> listed with sp_replcmds run on the publisher. What can we do to restart
> the
> Log Agent and not loose any transactions?
> Please help...
> Thanks,
> Fidel Arbizu.
>
Subscribe to:
Posts (Atom)