Even though i see all the errorlog files physically stored in the log directory, I am not seeing any errorlog info on Enterprice Manager. I see all files like errorlog, errorlog1, errorlog2, etc, when i click current errorlog, it shows nothing, Please help me what could be the problem?
I don't know what I am doing wrong. In my environment, we have monitoring tool that scan through sql errorlog every 10minutes to capture some error that occurs. I have been trying for days now to create an alert for any of our failed backup to appear in the sql errorlog with the code below. After I add message to the sysmessage table with sp_addmessage, and raising the error with log option, I modified the existing scheduled backup job by creating an alert with the num in the code. For some reason, this error will not just show up in the sql errorlog when it failed. Has anyone any advise on what to do?
The code is:
sp_addmessage 50001, 25, 'Backup Failed for the '%.*ls' database.Please Contact MSSQL DBA Immediately!!!! ' GO DECLARE @DBID INT SET @DBID = DB_ID() DECLARE @DBNAME NVARCHAR(128) SET @DBNAME = DB_NAME() RAISERROR (50001, 25, 1, @DBID, @DBNAME) with log GO Thanks SA
what does the error "login failed-User: Reason : Not associated with a trusted SQL Server connection" means in the errorlog? it keeps on writing in the errorlog. what could be the caused of this? and how to correct this?
Hi....Does anyone know if there is a similar command to SQL2K's DBCC ERRORLOG. I'm currently writing a preventative maintenance script and want to force archiving of errorlogs. Any help greatly appreciated.
I am getting a recurring error in my errorlog. This is the error: "BlkHeader from strip 0 At 13531e00 ExpectedAt 13531e00 Size c00 PrevSize 200" Has anyone seen this before?
I just spent the better part of a full day trying to figure out why my MSSQLSERVER service wouldn't start. Finally, after someone suggested I check out "C:Program FilesMicrosoft SQL Server[Instance Name]LogErrorLog" I found my problem. I opened it up to find: (newbie mistake, I know now!!)
2005-12-21 19:27:46.60 server SQL Server evaluation period has expired
So I thought I would pass this onto everyone I can think of so you will not make the mistake I just did.
It would have been nice if Microsoft, like just about every other software company out there, would have been loud & obnoxious about their trial software expiring. Instead they have to put a poor newbie soul thru what I just went thru.
*sigh*
Well if I helped 1 person with this, I've done some good!
I need to move the errorlog files from the d: drive to the e: drive on my NT servers. Does anyone know a way to accomplish this without having to re-install? Thanks tcb
We're running SQL 6.5 SP3, we recycle our SQL server every day, somehow starting last December, the errorlog kept appending to the previous one without starting a new log, and it keeps on growing, any one knows anywhere I should look into ? If SQL behaves properly, it should starts a new log after each recycle. I checked from Technet this problem may occur in 4.2 but I haven't seen anything in 6.5....Thanks Anthony
We have set up a couple of SQL Server 2005 systems and I have foundthat the format of the ERRORLOG files and the SQL Agent's log filesare Unicode or some format that findstr cannot parse properly. "find"parses them fine, but it doesn't have the capabilities that I need --specifically, I can't search for multiple strings in one search.I see the checkbox on the SQL Agent's for "Write OEM File", but it isgrayed out so I am not able to try checking that. I also don't knowif that would affect the server's ERRORLOG file too or just theAgent's log file.So what am I missing? What is everyone else doing who is used tohaving scripts to parse these files looking for strings that indicateproblems? Is there a server setting that will force it to go back toa plain ANSI text file format for log files? Is that a bad thing todo?Thanks in advance for any insight,Teresa Masino
Hi I was not able to connect to SQL Server machine. On examining the Error log (which was huge 53MB), I found the following messages that filled 95% of the logfile. Is this something to do with memory allocation.
Someone, please let me know what is going on. After the server reboot everything works fine. I am worrired that this message may occur again.
Thanks Machilu
2004-11-30 20:15:03.64 logon Login failed for user 'NT AUTHORITYSYSTEM'
2004-12-01 08:15:03.77 logon Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
2004-12-01 00:47:25.28 spid70 WARNING: Failed to reserve contiguous memory of Size= 65536. 2004-12-01 00:47:25.31 spid70 Buffer Distribution: Stolen=127590 Free=4176 Procedures=182443 Inram=0 Dirty=14180 Kept=0 I/O=0, Latched=154, Other=10049 2004-12-01 00:47:25.31 spid70 Buffer Counts: Commited=338592 Target=338592 Hashed=24383 InternalReservation=357 ExternalReservation=0 Min Free=256 2004-12-01 00:47:25.31 spid70 Procedure Cache: TotalProcs=66212 TotalPages=182443 InUsePages=88547 2004-12-01 00:47:25.31 spid70 Dynamic Memory Manager: Stolen=310033 OS Reserved=38512 OS Committed=38457 OS In Use=38388 Query Plan=332158 Optimizer=0 General=15540 Utilities=8 Connection=473 2004-12-01 00:47:25.31 spid70 Global Memory Objects: Resource=10685 Locks=119 SQLCache=4540 Replication=2 LockBytes=2 ServerGlobal=45 Xact=201 2004-12-01 00:47:25.31 spid70 Query Memory Manager: Grants=0 Waiting=0 Maximum=92118 Available=92118 2004-12-01 00:50:04.10 logon Login failed for user 'NT AUTHORITYSYSTEM'. 2004-12-01 00:50:04.32 logon Login failed for user 'NT AUTHORITYSYSTEM'. 2004-12-01 00:51:08.78 spid70 WARNING: Failed to reserve contiguous memory of Size= 65536. 2004-12-01 00:51:08.82 spid70 Buffer Distribution: Stolen=138829 Free=5944 Procedures=169283 Inram=0 Dirty=14431 Kept=0 I/O=0, Latched=154, Other=9951 2004-12-01 00:51:08.82 spid70 Buffer Counts: Commited=338592 Target=338592 Hashed=24536 InternalReservation=360 ExternalReservation=0 Min Free=256 2004-12-01 00:51:08.82 spid70 Procedure Cache: TotalProcs=67783 TotalPages=169283 InUsePages=76116 2004-12-01 00:51:08.82 spid70 Dynamic Memory Manager: Stolen=308112 OS Reserved=38512 OS Committed=38457 OS In Use=38398 Query Plan=330249 Optimizer=0 General=15535 Utilities=8 Connection=476 2004-12-01 00:51:08.82 spid70 Global Memory Objects: Resource=10685 Locks=118 SQLCache=4540 Replication=2 LockBytes=2 ServerGlobal=45 Xact=202
recently, I use the following script(somebody else) to create a database on a remote server: the script is as follow: /*************************/ CREATE DATABASE [ErrorLog] GO
if not exists (select * from master.dbo.syslogins where loginname = N'ErrorLog') BEGIN declare @logindb nvarchar(132), @loginlang nvarchar(132) select @logindb = N'Navigator', @loginlang = N'us_english' if @logindb is null or not exists (select * from master.dbo.sysdatabases where name = @logindb) select @logindb = N'master' if @loginlang is null or (not exists (select * from master.dbo.syslanguages where name = @loginlang) and @loginlang <> N'us_english') select @loginlang = @@language exec sp_addlogin N'ErrorLog', 'secret', @logindb, @loginlang END GO
if not exists (select * from dbo.sysusers where name = N'ErrorLog' and uid < 16382) EXEC sp_grantdbaccess N'ErrorLog', N'ErrorLog' GO
Grant select, insert On Errors to ErrorLog /***************************/ in my *.asp program, I used the following string to connect to the database on the remote server. /******** con.open "dsn=ErrorLog;uid=ErrorLog;pwd=secret;" ********/ the following message comes up: /********/ Error Type: Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D) [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'ErrorLog'. /*********/ what is the problem here? when I set up dsn ErrorLOG, I used "abc" userID and password "XXX" which is our server database administrator assigned to me. I tested connection in odbc, it is OK I just don't get, ther user ErrorLog already had login id and granted access to database errorlog. any clue, please help! Betty