Skip to content
benjf.com
benjf.com

  • Home
  • About
  • ✞ Faith
  • Opinion
    • Politics
    • Health
    • Movies
    • Music
    • ☺ For Fun
    • Random Awesomeness
  • Technology
    • Desktop
    • Android
    • ✉ Email
    • Privacy
    • Programming
      • HTML
      • CSS
      • Javascript
        • jQuery
      • PHP
      • SQL
        • SQL Server
      • Powershell
      • MS Access
      • WordPress
  • Productivity
benjf.com

Moving FDLAUNCHERLOG in SQL Server

Writer #1, 2018-05-16

EDIT: I had two scenarios like this. The one written about here worked. The other one failed. The actual solution came from sql-ution.com. The solution is to fix the registry with the new value. And just in case his website comes offline before mine does, I'll post the code:

Since I'm nostalgic for my wasted efforts, I'll keep my past solution here… you know, the one that half worked.

Recently, I had a situation where SQL Server was installed to an incorrect directory. Everything was on the right drive but was not laid out according to our standard folder structure, so the real issue was that it looked messy. On a multi-instance server, messy is not good. In the long run, a messy folder structure can make maintenance difficult as you struggle to remember which directory went with which instance, so I wanted to fix it.

I got everything moved except one file called FDLAUNCHERLOG. What's going on? For some reason, Microsoft has provided no way to move this one little file and has made it impossible to clean up the old folder structure.

I found a solution.

Getting the databases moved is relatively straight forward and those instructions are all over the web so I'll spare you that detail. System databases are more challenging, but again, that's been written about.

What I did not find was how to move the FDLAUNCHERLOG file. Honestly, I don't care that much about it except for the fact that SQL cannot live without it. It happens that you cannot remove the original installation folder because this one file is locked by the operating system while SQL Server is running. If you try stopping SQL Server and removing the file then SQL Server cannot start back up. It really really wants that file to be there. Really. So, you'd think the information found in that file would be earth-shattering, right? It must be truly vital to SQL Server if there is no way to move it and SQL refuses to start without it. Well, here's a look at what you'll find there:

2018-05-15 12:31:05.323    MSSQLFDLauncher$SQLInstance service successfully started.
2018-05-15 12:31:06.323    MSSQLFDLauncher$SQLInstance service received control message.
2018-05-15 12:31:06.433    MSSQLFDLauncher$SQLInstance service successfully launched FDHost.exe Process(process id = 11864).
2018-05-15 16:15:04.917    MSSQLFDLauncher$SQLInstance service stopped.

It's a log. Why, SQL, why?

On Microsoft's MSDN webpage called "How can we move FT data folder and FDLaunchErrorLog", they tell us that there is no way to move the file. You must reinstall SQL Server. There are some suggestions that say to hack the registry, which sometimes is a fine idea, but other websites that suggest it also include comments saying that it is a failure. And if some people say it fails, and Microsoft doesn't support you hacking your registry in this case, you should think twice before doing it to your production server.

So, all of that to say this: MSDN was only half right. It's a little misleading to say that you have to completely reinstall SQL Server. The FDLAUNCHERLOG file is a log file that belongs only to the Full-Text Filter Daemon, so all you need to do is uninstall the Full-Text Filter Daemon and reinstall it. Provided you have already changed your default system directory, it will automatically install itself to that location. If you haven't changed the default directory then look at your SQL Services, right click the instance name, select properties, pick the Startup Parameters tab, and alter those parameters. Be careful. Copy the original values before you change them. If those are wrong, you won't start SQL until they are fixed.

EDIT: Even on the instance where the FDLAUNCHERLOG file moved, the default Data location was not changed. Why it installed into the correct directory while the default data directory was wrong is beyond me. On the other server with the same issue it did not act that way. In the end, I had to edit the registry using the above method to get this corrected.

So, step one is to uninstall it by going into your Control Panel and selecting Programs and Features. Find the Microsoft SQL Server entry and right-click it and choose "uninstall" (don't worry, you aren't uninstalling all of SQL Server). When given the option, choose to uninstall only the Full-Text Search.

After that completes, begin a new installation and choose the option "New installation or add features to an existing installation". From there, only add the Full-Text Search feature.

Once that completes, you're all set.

 

SQL Server FDLAUNCHERLOGFull Text Filter Daemonsql server

Post navigation

Previous post
Next post

Comment

  1. Kevin says:
    2024-04-11 at PM 03:30 GMT-0400

    Shouldn’t be that shy about editing the Registry. There are 3 sections under the instance key that link to the previous instance directories (I’m using SQL 2022).

    CPE
    [ErrorDumDir]
    Setup
    [SQLDataRoot]
    SQLAgent
    [WorkingDirectory]

    Modify the paths correctly, Verify path permissions (granting to NT Service\)

    Restart the FullText Filter Daemon and SQLAgent services.

    Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • Love Never Fails
  • FIXED! Left Audio Only on OBS with Behringer U-Phoria UMC204HD
  • Gnome Alt+Tab Window Switching; How to ungroup the windows
  • Pay or else
  • 1Password App Integration With Browser Extension on Kubuntu (or Debian Linux)

Recent Comments

  1. LOL on Major Federal Budget Cuts – do the math
  2. Writer #1 on Online Privacy In The United States
  3. More About Sortable Dates; Plus AutoHotKey Scripts! – benjf.com on Date/Time Formatting Can Unite The World
  4. AutoHotKey Tips – benjf.com on Date/Time Formatting Can Unite The World
  5. Kevin on Moving FDLAUNCHERLOG in SQL Server

Archives

  • May 2025
  • April 2025
  • March 2025
  • February 2025
  • January 2025
  • December 2024
  • November 2024
  • October 2024
  • September 2024
  • August 2024
  • July 2024
  • June 2024
  • April 2024
  • March 2024
  • November 2023
  • October 2023
  • September 2023
  • July 2023
  • June 2023
  • May 2023
  • October 2022
  • September 2022
  • August 2022
  • May 2022
  • December 2021
  • November 2021
  • September 2021
  • July 2021
  • June 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • July 2019
  • May 2019
  • April 2019
  • January 2019
  • December 2018
  • November 2018
  • May 2018
  • April 2018
  • February 2018
  • December 2017
  • September 2017
  • June 2017
  • May 2017
  • February 2017
  • January 2017
  • December 2016
  • August 2016
  • July 2016
  • May 2016
  • April 2016
  • March 2016
  • February 2016
  • December 2015
  • September 2015
  • August 2015
  • July 2015
  • June 2015
  • October 2013
  • September 2013
  • August 2013
  • June 2013
  • May 2013
  • April 2013
  • March 2013
  • February 2013
  • January 2013
  • December 2012
  • October 2012
  • September 2012
  • July 2012
  • April 2012
  • March 2012
  • February 2012
  • January 2012
  • December 2011
  • November 2011
  • October 2011
  • September 2011
  • August 2011
  • July 2011
  • June 2011
  • May 2011
  • April 2011
  • February 2011
  • January 2011
  • December 2010
  • November 2010
  • September 2010
  • August 2010
  • July 2010
  • June 2010
  • May 2010
  • April 2010
  • March 2010
  • February 2010
  • January 2010
  • December 2009
  • November 2009
  • October 2009

Categories

  • Ai
  • Android
  • C#
  • CSS
  • Desktop
  • EMail
  • Faith
  • For Fun
  • Health
  • HTML
  • Javascript
  • jQuery
  • Just Info
  • Linux
  • Movies
  • MS Access
  • Music
  • Opinion
  • PHP
  • Politics
  • Powershell
  • Privacy
  • Productivity
  • Programming
  • Random Awesomeness
  • Self Hosting
  • SQL
  • SQL Server
  • Technology
  • Uncategorized
  • WordPress
©2025 benjf.com | WordPress Theme by SuperbThemes