question

jmcentee avatar image
jmcentee asked

SQL Server 2012 Log

I've just configured a SQL Server 2012 and when I go to view the SQL Server Error Log through the log file Viewer the interface says No log source. By looking at the startup parameters I see the log file location and can see there are log files. It also lets me look at the log files through the file management system. Why doesn't the Log File Viewer work?
sql-server-2012installationerror-log
1 comment
10 |1200 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Just noticed this was tagged as SQL-Azure. Is that right? You wouldn't be able to see the logs at all on a Windows Azure SQL Database. If that tag is right, that might be the problem. But, there is no place to go and look at logs. You can just see certain types of errors in the system tables.
0 Likes 0 ·
jmcentee avatar image
jmcentee answered
I did mis tag this it is SQL Server 2012. I moved the log files changed the location in the start up parameters and restarted SQL Server and now I can see it. It might have had something to do with installing through powershell? Anyway even though the location was accurate moving the file to a new location caused it to see it.
1 comment
10 |1200 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

If this solved the issue you should mark it as the answer so that any one searching for your question will know how you resolved it.
0 Likes 0 ·
Grant Fritchey avatar image
Grant Fritchey answered
Not sure. It should. It's not a problem I've run into. Try opening the interface and then select "Load Log" from the viewer window. You should be able to navigate to where the logs are kept and see them there. Other than that, best guess, there's a security issue with the login that is connecting to SSMS and it can't see the logs?
10 |1200 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Tim avatar image
Tim answered
I have only encountered this on a system when the DBA moved the location of the master database by stopping the service, changing the paths in the startup parameters and accidentally messed up the path for the log file location. There was either an extra slash or colon in the path. Once that was corrected everything was fine. I can only suggest double checking the exact path.
10 |1200 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.