i have my SQL server 2005 crashing when Events log is full
I have a hacker attacking my DB with a brut force tool but whereas he does not have the password, event log registers his access attempts as Failure Audit.
I have thousands of lines of "Failure Audit" in my event log
The event logs are set to be overwritten automatically when they reach 16Mb but it's not working correctly, they r not overwriting their content.
2007-05-14 01:57:11.57 spid80 The current event was not reported to the Windows Events log. Operating system error = 1502(The event log file is full.). You may need to clear the Windows Events log if it is full.
SQL Agent cannot starts because it's not able to write in the event log that it's starting and when it cannot write in event log, it does not start and my sql server crashed
My Question is simply how to fix this issue once for all
I just recently replaced my old HP laptop with a Sony VAIO. I installed all of my development software on it, including SQL Server 2005 and the studio. At some point when I am using the studio on this new laptop, if I try to resize any of the columns to better fit the data, it crashes my laptop. I get the infamous Blue Screen of Death.
The laptop is a Sony Vaio BX670P and it has Win XP SP2 with all of the latest and greatest updates loaded on it.
The BSD blames a driver for causing the crash and points out "win32k.exe" specifically. This has never happened to me before.
Hi,I'm accessing a pair of databases with ASP/ADO,and using stored procedures on the first access.The first access works OK - everything gets writtento where it's supposed to be.On attempting to write to a pair of database tablesin the second database (second access attempt),the server crashes, as does the app, and I get the following error:--------------------------------------------------------------------Server Error in '/Webfolder01' Application.Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.Exception Details: System.Data.SqlClient.SqlException: A transport-level error has occurred when receiving results from the server. (provider: Shared Memory Provider, error: 0 - The pipe has been ended.)--------------------------------------------------------------------After this, I have to go into the services panel and restart SQL 2005.This doesn't happen if I use small test data sets in the first access,and I can comment out the second access attempt, and the first accessexecutes just fine with both the large and small data sets,so I'm thinking that this has something to do with synchronisation:Perhaps the second attempt is being made before the server is ready.Is there something that I need to do to make certain that SQL 2005is ready to receive data?I'm using SqlBulkCopy with both accesses, but I don't see how thatcould be a problem.--------------------------------------------------------------------[SqlException (0x80131904): A transport-level error has occurred when receiving results from the server. (provider: Shared Memory Provider, error: 0 - The pipe has been ended.)] System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) +857370 System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +734982 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188 System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error) +556 System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj) +164 System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32 bytesExpected) +34 System.Data.SqlClient.TdsParserStateObject.ReadBuffer() +30 System.Data.SqlClient.TdsParserStateObject.ReadByte() +17 System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +59 System.Data.SqlClient.SqlBulkCopy.WriteToServerInternal() +1327 System.Data.SqlClient.SqlBulkCopy.WriteRowSourceToServer (Int32 columnCount) +916 System.Data.SqlClient.SqlBulkCopy.WriteToServer(DataTable table, DataRowState rowState) +176 System.Data.SqlClient.SqlBulkCopy.WriteToServer(DataTable table) +6 Database_control.DB_ctrl_class.load_datatable_to_DB_table(DB_ref_class src_table) in i:Virtual WebfoldersDBctrl.cs:978--------------------------------------------------------------------THANK YOU VERY MUCH!!!
I'm having many many issues installing sql server management tools. i had visual studio 2005 installed first, but uninstalled and sql related things before trying to install sql server management tools again - i also deleted the program files/microsoft sql server/ folder so there are no references.
Firstly the system configuration check gives me a warning that the system doesn't meet the recommended hardware requirements - this is wrong... i've got 2.33Ghz dual core + 1gb of ram...
I select just management tools + client connectivity to install and click next -> the setup support files/native client/owc11 etc all install fine but workstation components etc fail and the setup log appears to either be empty and not available and MSXML6 fails... after clicking finish the installer appears to crash - : "Microsoft SQL Server 2005 Setup has encountered a problem and needs to close. We are sorry for the inconvenience"... I have tried all sorts of variations on this install and have had no problems in the past - please help!
The setup log from the MSXML6 failure - === Verbose logging started: 18/03/2008 12:34:09 Build type: SHIP UNICODE 3.01.4000.4039 Calling process: C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe === MSI (c) (5C:78) [12:34:09:067]: Resetting cached policy values MSI (c) (5C:78) [12:34:09:067]: Machine policy value 'Debug' is 0 MSI (c) (5C:78) [12:34:09:067]: ******* RunEngine: ******* Product: {AEB9948B-4FF2-47C9-990E-47014492A0FE} ******* Action: ******* CommandLine: ********** MSI (c) (5C:78) [12:34:09:067]: Client-side and UI is none or basic: Running entire install on the server. MSI (c) (5C:78) [12:34:09:067]: Grabbed execution mutex. MSI (c) (5C:78) [12:34:09:067]: Cloaking enabled. MSI (c) (5C:78) [12:34:09:067]: Attempting to enable all disabled priveleges before calling Install on Server MSI (c) (5C:78) [12:34:09:067]: Incrementing counter to disable shutdown. Counter after increment: 0 MSI (s) (28:E4) [12:34:09:113]: Grabbed execution mutex. MSI (s) (28:74) [12:34:09:113]: Resetting cached policy values MSI (s) (28:74) [12:34:09:113]: Machine policy value 'Debug' is 0 MSI (s) (28:74) [12:34:09:113]: ******* RunEngine: ******* Product: {AEB9948B-4FF2-47C9-990E-47014492A0FE} ******* Action: ******* CommandLine: ********** MSI (s) (28:74) [12:34:09:113]: Machine policy value 'DisableUserInstalls' is 0 MSI (s) (28:74) [12:34:09:113]: MainEngineThread is returning 1605 MSI (c) (5C:78) [12:34:09:113]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI (c) (5C:78) [12:34:09:113]: MainEngineThread is returning 1605 === Verbose logging stopped: 18/03/2008 12:34:09 ===
The log summary:
Microsoft SQL Server 2005 9.00.1399.06 ============================== OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600) Time : Tue Mar 18 12:05:06 2008
EOC429 : The current system does not meet recommended hardware requirements for this SQL Server release. For detailed hardware requirements, see the readme file or SQL Server Books Online. Machine : EOC429 Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_EOC429_SQLSupport_1.log -------------------------------------------------------------------------------- Machine : EOC429 Product : Microsoft SQL Server Native Client Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_EOC429_SQLNCLI_1.log -------------------------------------------------------------------------------- Machine : EOC429 Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_EOC429_OWC11_1.log -------------------------------------------------------------------------------- Machine : EOC429 Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_EOC429_BackwardsCompat_1.log --------------------------------------------------------------------------------
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.
Hello experts. I have been searching for anything about this but found very little. What are the events logged in SQL Server Error Logs aside from Successful/Failed Login, Backup/Restore/Recover database and, start/init sql server? Can we configure this to log other events, like CREATE or DBCC events for example? If so, how? Thanks a lot.
Kind of a weird problem. Just migrated some Access tables to SQL 2005 backend. This is only happening on one users machine, WinXP and Access 2003 with the linked tables to SQL 2005. When they try to run a query that has a date criteria, Access will crash. Any other type of criteria, the query works fine. Things I have tried: 1) Installing Office Service Pack 3 2) Repairing Office 2003
We have found that it is common for Visual Studio 2005 to crash when editing or running SSIS packages -- from CTP versions through beta versions and including the release version.
Of course we kept hoping that newer releases would become more stable, or at least more robust -- and now I'm hoping there will be a service pack, which might make it more robust?
I am running SMS ontop of SQL 7. I keep getting these SQL dump files and cant figure out where to begin. Can somebody help and put me on the right path?
2001-07-22 12:08:55.46 spid12 Process ID 12 attempting to unlock unowned resource PAG: 7:1:507423.. 2001-07-22 12:13:21.29 spid8 Error: 1203, Severity: 20, State: 1 2001-07-22 12:13:21.29 spid8 Process ID 8 attempting to unlock unowned resource PAG: 7:1:505802.. 2001-07-22 15:15:48.20 spid11 Using 'sqlimage.dll' version '4.0.5' Dump thread - spid = 11, PSS = 0x700634b4, EC = 0x216da084 Stack Dump being sent to D:MSSQL7logSQL02866.dmp ************************************************** ***************************** * * BEGIN STACK DUMP: * 07/22/01 15:16:00 spid 11 * * Input Buffer 417 bytes - * INSERT INTO Summarizers_Status (SiteCode, MessageDLL, MessageID, Status, * Updated, GUID_ID) SELECT DISTINCT SiteCode, "SMS_RES1.DLL", 40, (SELECT * ISNULL(MAX(x.Status), 0) FROM Summarizer_SiteSystem x WHERE x.SiteCode * = a.SiteCode), (SELECT ISNULL(MAX(x.TimeReported), '1/1/1998 01:00') FRO * M Summarizer_SiteSystem x WHERE x.SiteCode = a.SiteCode), "{78B42510-ABB * D-11d1-BB12-3A84C6000000}" FROM Summarizer_SiteSystem a * ************************************************** ***************************** ------------------------------------------------------------------------------- Short Stack Dump 0x77f67a6b Module(ntdll+7a6b) (ZwGetContextThread+b) 0x00784f83 Module(sqlservr+384f83) (utassert_fail+19f) 0x005b572c Module(sqlservr+1b572c) (ExecutionContext::Cleanup+9d) 0x004eb421 Module(sqlservr+eb421) (ExecutionContext::Purge+45) 0x004eb182 Module(sqlservr+eb182) (stopsubprocess+e5) 0x004e9d4e Module(sqlservr+e9d4e) (subproc_main+174) 0x41092a47 Module(ums+2a47) (ProcessWorkRequests+ec) 0x4109326b Module(ums+326b) (ThreadStartRoutine+138) 0x7800bee4 Module(MSVCRT+bee4) (beginthread+ce) 0x77f04ede Module(KERNEL32+4ede) (lstrcmpiW+be) 2001-07-22 15:16:01.24 kernel SQL Server Assertion: File: <proc.c>, line=1927 Failed Assertion = 'm_activeSdesList.Head () == NULL'. 2001-07-22 15:16:01.31 spid11 Using 'sqlimage.dll' version '4.0.5' Dump thread - spid = 11, PSS = 0x700634b4, EC = 0x216da084 Stack Dump being sent to D:MSSQL7logSQL02867.dmp
Help!!! our sql server (7.0) crashed today because it's running out of space, apparently as a result of some process(es) loading data onto it that left less than one mb of free space on the C/ drive. Most of the data and backups are on the D/ drive which has tons of free space. The swap file was on C/ but the dba moved it after today's episode. His diagnosis is that there are files being created in the server's cache that are clogging it up. What I really need to find out if there are any temp files generated by scheduled packages that could cause this to happen? We are relatively new to executing jobs on the sql server, so this was not an anticipated situation. Essentially, this server has about 12 jobs that import and transform data from an AS/400 server onto the SQL Server every week. We've been running the jobs for about 4 months and just about 3 weeks ago I noticed a big degradation in the server's performance. Also, how can I find out which physical drive the jobs are residing on? Could anyone suggest on the best course of action please?
Irene out if there are some sort of temp files that are generated when the scheduler executes jobs on the server.
Hi All Last to last friday, the server crashed.We had to restart the machine to bring up the sql server.Initially we thought this as a one odd instance.This friday, almost the same time, it crashed again. By the time users complained saying they are not able to acces the application, the server froze.I was not able to see the processes running during this time. Now I realised there is a potential problem. I check all the logs - > SQL Server log, SQL Agent log, Event viewer. I dont see any error messages related to this. Since both weekends it happened at the same time, I assume that there might be some job running on the friday evening which is bringing the server down. I checked for all the scheduled jobs and didnt find anything. So I assume this might be because of some adhoc jobs ran from the application which is causing this issue. This have been highly escalated by the users and I have to act :mad: I am planning to put a trace to see the happenings during this time. Questions 1) What all parameters(in the profiler) should i take into consideration 2) Any other ways of troubleshooting the same. 3) Any whitepapers / documents to similar issues Plz respond,my job is at stake :( Thanks Sree
Please direct me to detailed causes of SQL server crashing after a 17805 Invalid Buffer Received From Client. Our production server goes down, following this msg. We applied service pack 5a, and it is still crashing. It crashes using either NAMED PIPES or TCP/IP protocol (via ODBC) The driver versions are older, ODBC 3.0 and SQL Server 2.65, respectively. I need some direction on this. I'm leaning towards the possibility that this is an application problem. Any help, any configuration setting changes, upgrades, workarounds, will be accepted. Thank you much!
We're having trouble with Enterprise manager when trying to view views or table data/properties, we get an access violation error and the database crashes sometimes corrupting tables. Ive seen some posts stating a post SP3 for SQL Server is required and some posts saying client access should be modfied. However our enterprise manager clients are registered with SA so I dont think that is an issue. Can anyone give me some help with this and/or direct me to the hotfix please.
I got a server that Crashed. My network group was able to get it up and running but it's vary fragile. One of the disk is done. What's the best way to get the my database:tables,views,stored procedured,dts packages, jobs off the bad server without crashing it again? I used the databae copy utility but found out that some of the database are replicated and it wont allow it to copy.
I had the following erroneous code in a SQL Server stored C# procedure:
class P
{
private DateTime? e;
public P(
DateTime? e)
{
this.e= e;
}
public DateTime? E
{
get
{
return E; // correction return e;
}
set
{
E= value; // correction e = value;
}
}
}
Calling the getter of E of the class P creates an infinite number of method calls. This causes the .NET stack overflow. This sometimes caused our SQL crash. Here's the log:
29.3.2007 9:46:08 A fatal error occurred in .NET Framework runtime. The server is shutting down.
29.3.2007 9:46:10 Microsoft SQL Server 2005 - 9.00.2153.00 (X64)
May 9 2006 13:58:37
Copyright (c) 1988-2005 Microsoft Corporation
In my opinion an error in SQL server CLR stored procedure must not be able to crash the whole SQL Server, as it seems to do. Could someone verify this?
What makes finding problems like this problematic is that the only error is like ".NET stack overflow". No pointer to where in the code the error occured. It took hours for me to find the problem
I've installed the client tools on my notebook, and EM normally works properly. However, sometimes Enterprise Manager will crash on me for no obvious reason(it generates errors, but this takes forever, so i kill it). It is not consistent, nor can I reproduce the error, but it happens about once a day, never at the same time. Anyone else see this? My pc has win2K professional on it.
Does anyone know if it is possible to do Post-Build Events in Reporting Services? I am using Visual Studio 2005 Team Edition and creating Reports under the Business Intelligence Projects.
When creating C# projects, when you right click on the solution and go to properties there is a tab for Build Events at which point you can create Pre-build and Post-build events; however I am not finding this option available within a Reports project. Does anyone know if this is possible to do in Reporting Services?
Basically what I am trying to accomplish is, I am having to create multiple template files and there are multiple developers going to be working on this project and I would like to create a batch file of some sort that copies the template files that are created into the IDEPrivateAssembliesProjectItemsReportProject directory each time the project is built.
I am not sure if I have posted something about this, but I can't believe there is not a single person out there that is using a procedure written in SQL in order to schedule sending of an email, if data hasn't been submitted. I have had some hits and some help from some people but I am pretty much still stuck.
How is everybody else doing these sorts of thing,scheduling an email to be sent to a user if he/she hasn't submitted data,somebody must be doing it? A sample, help ,anything???
I have been tasked with auditing all DDL and selected DML events on a production server and logging them to a table. My solution is to use CDC for the DML and a Server-Level trigger for the DDL. Because there should never but much DDL activity on the server (except when performing update tasks) I don't need to worry about the trigger consuming too many resources.
My question is this: Is there any single specification such as DDL_LEVEL_EVENTS that can capture all DDL activity or do I need to specify each and every DDL action in the trigger?
I am backing up my all the databases (around 50 servers and 500 database) using scheduled jobs. I backup my transaction log files at every two hours of interval and databases on daily basis.
I have set option of "Write to Windows Application Event Log" - When job fails during the creation of job in the "Notification Tab" of Create New Job.
As per documentation SQL server automatically records some of the events to windows application event log. After succesful completion of Log backup and DB backup, event gets logged in Windows Application Event Log. And when job fails, I get two events logged in the Windows Application Event Log file, one due to my setting and other automatically by SQL Server.
Due to this Windows event log file is growing much faster and I have to clear it in every 3-4 days.
My quesiton - Is there a way such that to get only failures event logged in Windows Application event log file and any successful backup jobs should not go to Windows application event file?
Can any suggest some idea what should I do?
I am using SQL Server 2000 with SP3 on Windows 2000 Advanced server. Some of my databases are still using Version 7.0/6.5 on NT.
I use this code in a utility procedure (for performance testing) but it is really slow.
For example, a session with three events is taking 5 seconds to complete this query:
DECLARE @xml xml= ( SELECT CAST(xet.target_data AS xml) FROM sys.dm_xe_session_targets AS xet JOIN sys.dm_xe_sessions AS xe ON (xe.address = xet.event_session_address) WHERE xe.name = @name );
I am wanting to get/filter on all queries and procs that take longer than 2 seconds to run (I'll balance real values later) but I'm not sure which Action out of the XE that I need.
I am using SQL Server 2014 and thought I had used sqlserver.sql_statement_completed.duration > 2000 in a previous version.
I am trying to use xquery to get event data back from extended events. I am trying to use some sample data from Grant Fritchey but I am getting null records back. Below is the xml - I just want to retrieve a distinct list of the client_hostname and client_app_name.
WITH xEvents AS (SELECT object_name AS xEventName, CAST (event_data AS xml) AS xEventData FROM sys.fn_xe_file_target_read_file ('C:LoginTraceShared_0*.xel', NULL, NULL, NULL)) SELECT distinct top 1000 xEventName, xEventData.value('(/event/data[@action_name=''Client_APP_Name'']/value)[1]','varchar') Client_APP_Name, xEventData.value('(/event/data[@action_name=''Client_Host_Name'']/value)[1]','varchar') Client_Host_Name FROM xEvents
I know very little about Extended Events, but I know it is supposed to be more powerful than Profiler. The SQL Instance involved is 2008R2. I was asked whether we could capture when a stored proc was called with a certain parameter. So for example, if dbo.usp_mystoredproc is called and is passed a value of '12345a' for @customer, can that be captured? I would want to know the time it was called, the parameter and parameter value. Probably would be interested in the SPID or LoginName as well.
I need to find any stored procedures that have not been used over a certain time period.
I have set up an extended events session to gather sp_statement_starting and _completed.
The trace returns the object_id's of many stored procedures. I then query the sys.procedures and plug in the object_id to return the stored proc name.
Do I have to repeat this process for every different object_id or is there a way I can query the trace results, using the object_id as my search criteria as one query ?
I am setting up extended events more or less just fine, however I am a bit confused as to how to read and load them into a table for querying. In particular the offset part - is there a way to load just a given dates worth in?
I've got the files configured to be 20MB before rolling over, the XE is running all the time.
So if i load in the full file now, say that covers 2.5 days worth, when I load it again tomorrow to get the updated data I'm also reloading today, which is a waste?
I presume I am going about this wrong, but lack an example that really goes into detail of practicalities of loading this data.
We are planning to convert or change all existing Traces to Extended Events in SQL server 2012. What is the procedure to convert custom traces. We have already created some below custom traces: like this we are planning to convert for all servers.
I would like to AUTOMATICALLY count the event for the month BEFORE today
and
count the events remaining in the month (including those for today).
I can count the events remaining in the month manually with this query (today being March 20):
SELECT Count(EventID) AS [Left for Month], FROM RECalendar WHERE (EventTimeBegin >= DATEADD(DAY, 1, (CONVERT(char(10), GETDATE(), 101))) AND EventTimeBegin < DATEADD(DAY, 12, (CONVERT(char(10), GETDATE(), 101))))
Could anyone provide me with the correct syntax to count the events for the current month before today
and
to count the events remaining in the month, including today.
Has anybody had any problems with mmc crashing when running Enterprise Manager on SQL Server 7.0/SP1? This occurs on a fairly regular basis on several of our development NT client machines (NT SP4 and SP5). We are running Version 1.1 of mmc. Is there a later version (or service pack) we need to be using?
OK, I'm having fun here. I have 3 anonymous subscribers using merge replication all, including the server, on SQL 2000 Server SP3a.
2 of the 3 subscribers crash during the merge process, a Dr Watson error log comes up saying that the replmerg.exe has died.
I have checked for orphaned processes of the same name to no avail. Just in case I made a mistake, I rebooted the server to ensure that any orhpaned processes were killed. No Joy.
