|
Home > Archive > MS SQL Server > February 2006 > Current errorlog not showing
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Current errorlog not showing
|
|
| MarkusB 2006-02-13, 9:23 am |
| Hello everybody,
last week I had to move my master database en with it the location of
my SQL Server errorlogs. Since then new errorlogs are created in the
new location specified in the startup parameter, but in EM I can only
see the archived ones, not the current.
Turns out that xp_enumerrorlogs don't return 0, the number for the
current errorlog. Executing sp_readerrorlog returns the content of
current errorlog.
Any ideas how to fix this?
Tia Markus
| |
| Anith Sen 2006-02-13, 11:23 am |
| From the EM, click on Server properties, General Tab & click startup
parameters. The location of the error log can be changed there.
Alternatively, you can change the location directly in the registry as well.
--
Anith
| |
|
| Have a look at startup parameters in EM. There is a -e entry for the
location of the errorlog, chaging it here should resolve. The value is being
saved under the following Registry Key
HKEY_LOCAL_MACHINE\S
OFTWARE\Microsoft\MS
SQLServer\MSSQLServe
r\Parameters
Open EM / Right Click "Server" / Properties and choose Startup Parameters
--
HTH. Ryan
"MarkusB" <m.bohse@quest-consultants.com> wrote in message
news:1139839000.665337.12560@g44g2000cwa.googlegroups.com...
> Hello everybody,
>
> last week I had to move my master database en with it the location of
> my SQL Server errorlogs. Since then new errorlogs are created in the
> new location specified in the startup parameter, but in EM I can only
> see the archived ones, not the current.
> Turns out that xp_enumerrorlogs don't return 0, the number for the
> current errorlog. Executing sp_readerrorlog returns the content of
> current errorlog.
> Any ideas how to fix this?
>
> Tia Markus
>
| |
| MarkusB 2006-02-13, 11:23 am |
| Thanks guys,
I found the problem in the mean time. I had checked the startup
parameter and the registry before, but missed the fact that there was a
trailing space. This had the annoying effect that archive logs had a
name like ERRORLOG .1 and thus appeared in EM. For the current log
Windows removes the trailing space and that's why xp_enumerrorlogs was
unable to find it.
Markus
|
|
|
|
|