April 2, 2026 at 2:11 pm
The file FDLAUNCHERRORLOG gets created in the default <instance>\MSSQL\Log folder.
So far, I've found absolutely no way to change that location. The link to a MS URL in a similar posted question here on SSC is Forbidden.
I asked our in-house AI, and it told me about the "SQL Server Fallback Database feature". I think it may have been hallucinating...
Any ideas?
Thanks!
April 2, 2026 at 3:37 pm
Have you looked on the startup parameters for the SQL Server service in SQL Server Configuration Manager? There is an option to configure the location of the error log there. Maybe it helps ...
April 2, 2026 at 6:21 pm
Yup. That setting applies to the SQL Server service error logs.
The SQL Agent error logs are set by
EXEC msdb.dbo.sp_set_sqlagent_properties @errorlog_file = ...
I've read that the FDLaunch error log is only set in the registry, but there are no registry settings that I can find that match what I found on-line.
Our in-house AI tried your suggestion first. When I explained that was SQL Server service error logs, it apologized and made something up, then when I pointed out that wasn't a thing, it doubled down. Finally, it vaguely suggested I go play - carefully, mind you - in the registry, without providing any specifics.
April 21, 2026 at 10:04 am
There isn’t a way to change the location of FDLAUNCHERRORLOG. It is created automatically by Microsoft SQL Server and is always stored in the default <instance>\MSSQL\log folder, with no option to move it somewhere else.
If this location is causing a problem, you can either move the entire SQL Server log folder or use a symbolic link as a workaround. Also, the “fallback database feature” you mentioned is not related to this.
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply