Upgrading SQL 2019 to 2025 - Fulltext index issue

Yunus Emre Coşkun 0 Reputation points

When doing a SQL server upgrade from 2019 to 2025, im running into an issue when it is trying to finalize the Fulltext index part of the upgrade.

It seems like the upgrade locks itself out of the upgrade, by putting permissions on the Filterdatafolder, so it can no longer be accessed be the install process. When i try to check permissions on it with a local admin, i get access denied, ive even tried via psexec as SYSTEM but no luck.

The error im getting in the SQL Install is the following:

👁 User's image

anyone experienced this, and how do i fix it?

  1. Erland Sommarskog 134.7K Reputation points • MVP • Volunteer Moderator

    Do you actually have any data in that folder? That is, are you using fulltext filters?

    In the upgrade process there are different options for full-text, which one did you take?

    Am I right to assume that this is a named instance by the name MSSQLSERVER2?

  2. Yunus Emre Coşkun 0 Reputation points

    Yes, i am using fulltext filters and there is some files inside folder. There is 3 options when doing implace upgrade. Import, Rebuild and Remove. I tried Import and Remove both of gave me same error.

    In that host i have 3 instances and one of its name is MSSQLSERVER2, which is i am tring to upgrade. Other 2 instances successfully upgraded without any errors.

  3. Erland Sommarskog 134.7K Reputation points • MVP • Volunteer Moderator

    I always go with Rebuild, but I suspect that it does not matter. I suspect that you actually use filters plays in here. Do you have filters on the other two instances as well?

    As Deepesh says, if you can share summary.txt and details.txt, we might find some clues there. But please don't paste any file into a query window, but attach them.

Sign in to comment

Answer recommended by moderator

2 additional answers

  1. Deepesh Dhake 165 Reputation points

    The exact failure reason is written to the setup logs at "C:\Program Files\Microsoft SQL Server...\Setup Bootstrap\Log". You can open Summary.txt and search for the failed action. Are there any more details why it is failing?

    1. Deleted

      This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    2. Yunus Emre Coşkun 0 Reputation points

      In that host i have 3 instances and one of its name is MSSQLSERVER2, which is i am tring to upgrade. Other 2 instances successfully upgraded without any errors.

      In Summary.txt file there is no error lines about MSSQLSERVER2. Ofc i'm searching solution with couple of AI and its all propose firstly check logs too :)

    3. Deepesh Dhake 165 Reputation points

      Do you see any error information in Details file?

      C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log\

    Sign in to comment
  2. Senthil kumar 685 Reputation points

    Hi @Yunus Emre Coşkun

    While install or upgrade applications need a admin permission. and you provided permission to particular folder 'Filterdatafolder' I think. so please provide permission to 'SQL_DATA' folder might be chance to fix your issue.

    Thanks.

    1. Yunus Emre Coşkun 0 Reputation points

      Thanks for reply @Senthil kumar but its not exact solution, we tried it.

      Even though we granted full permissions from the parent directory, the issue persists as the update process breaks the permission chain. Is it possible that the user account utilized during the initial installation was subsequently modified, leaving the permissions in an orphan state?

    2. Senthil kumar 685 Reputation points

      Thanks @Yunus Emre Coşkun , may be try to provide permission to full drive. then try to install the same. suppose its failed try to install any other drive like. most probably try to install in C drive.

    3. Yunus Emre Coşkun 0 Reputation points

      Trying to grant permissions, attempting with local admin, or even trying to access the entire drive from the parent directory doesn't work because, as far as I understand, the SID information of the user used during the initial installation of the instance was later removed, and when attempting an implace upgrade, it tries to perform the operation with that removed SID. Since it can't find the user with that SID, it gives a permission error. So it seems like we have an orphaned account.

    4. Lakshmi Narayana Garikapati 1,330 Reputation points • Microsoft External Staff • Moderator

      Hi @Yunus Emre Coşkun ,

      Following up to confirm if the earlier responses addressed your query. If not, please share your questions and we'll assist further

      Thanks,

      Lakshmi

    5. Lakshmi Narayana Garikapati 1,330 Reputation points • Microsoft External Staff • Moderator

      Hi @Yunus Emre Coşkun ,

      Following up to confirm if the earlier responses addressed your query. If not, please share your questions and we'll assist further

      Thanks,

      Lakshmi

    Sign in to comment
Sign in to answer

Your answer