October 18, 2018 at 5:44 am
Hi Guys,
For some reason when I expand the SQL Server Error logs under the management tab in SSMS, I can only see the current log, and 3 archive logs. The problem is that the archive logs are about 8 months old, so I need to see the logs between those logs and the current log. When I go tho the MSSQL\Log directory, I can see 29 error log files(what is specified in the settings to keep), but they are not appearing in SSMS.
Can anyone assist in this matter? How do I make those files appear in SSMS?
Thanks in advance.
October 18, 2018 at 6:11 am
I have found the issue, it seems that when the logs get cycled, sql server seems to leave a space before the full stop and the number e.g ERRORLOG .1
So when I manually remove the space, I can refresh the logs in SSMS and it gets picked up. Can anyone tell my why SQL server is leaving the space there or where I can go to fix it?
October 22, 2018 at 3:47 am
Hi Guys,
I have found and fixed this issue. We use a Powershell script to do unattended installs of our SQL Server environments. In the script, there was a space after the error log startup parameter, which caused the space in the name when cycling the logs. I just went into the service properties, removed the space, and restarted the service. After that was done, I ran sp_cycle_errorlog and it was working perfectly.
This can be seen as resolved and this topic can be closed.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply