May 21, 2007 at 1:35 pm
I went into SQL EM to look at my SQL Server Logs and there are NONE!
I checked my Startup Parameters and it shows the path to my log directory and it looks correct. It looks as if the Backups I run via Maintenance plans have been creating their logs in seperate .txt files but I have no Server logs.
I created a new folder and changed the path to the errorlog in the startup parameters, but still no logs?
Not sure how to fix it!!!
May 22, 2007 at 4:37 am
What happens if your run sp_cycle_errorlog ? Can you or is it safe for you to stop and start SQL Sever ?
May 22, 2007 at 5:45 am
I tried sp_cycle_errorlog last night and also stopped and started the instance. I still have no logs??
May 22, 2007 at 6:02 am
I am doing some digging to see what I might come up with as I am curious and might hit the problem myself some day. Just to rule out the obviouse etc, does the account under which SQL Server is running have access to the folder specified in the startup parameters ? Also Just a thought it might be a permissions issue. Derek
May 22, 2007 at 6:03 am
One other thing, are your SQL Server Agent log files being created ?
May 22, 2007 at 6:41 am
Yes, In the same destination folder where I should see current and past errlog files, I have 3 Agnet Log files called sqlagent.1 sqlagent.2 and sqlagent.out
May 22, 2007 at 7:22 am
Would you mind posting your startup parameters ? Also logon to the server with the SQL Server account and using notepad see can you save a txt file to the folder. I know this is grasping at straws here, but just to rule out the obvious. Other members may be aware of some obscure setting that may be in one of the master tables that could be causing this. Might be worth your while making a call to MS.
May 22, 2007 at 7:46 am
Also, search out "errorlog" on your system on all drives and be sure they're not getting put somewhere weird.
Are they also not appearing in EM?
May 22, 2007 at 9:25 am
They are also NOT apprearing in EM.
Here are my startup parameters:
-dF:\DR_datafiles\master\masater.mdf
-lE:\DR_logfiles\master\mastlog.ldf
-ef:\dr_datafiles\log\errorlog
I logged onto the database server with the domain account that starts the services and I CAN write to the location on the F: drive where the logs should be. I then did a search and found the log files in a different location!!! I think someone has been messin with my server! Anyway, I moved them to f:\dr_datafiles\log\ and restarted my sql server. I can now see my errorlogs from EM (current and 6 previous) but they are a few days old and I can't make them refresh! tried checkpointing the log through query analyzer .. still only see the old logs.
May 22, 2007 at 9:37 am
I waded thru the Micorsoft Knowledge Base and found absolutely nothing even resembling this issue. But at least you have found them. Now you can see them in EM, well that's progress. When you say checkpointing do you mean sp_cycle_errorlog ? It would be interesting to try sp_cycle_errorlog now. Can you backup a transaction log or run a DBCC command and see if the current log is being updated ?
May 22, 2007 at 12:10 pm
WHen I run any maintenance JOBS, it is writing to a file called SQLAGENT.OUT
Still, the sp_cycle_errolog appears to run, but does nothing - does not checkpoint the log. still not seeing any current log.
I can successfully run a DBCC CHECKDB but when I try and backup a transaction log, I get this error:
sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.
This is so baffling
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply