Tag update problem after update

[redged]

Hello

I have just updated to 272 on my Synology NAS and minimserver can longer locate my tagUpdate text file. This is still located in my appdata folder but after the update will no longer rescan as says cannot locate. I have tried changing the name of the file but still no joy.

Any help would be great as I am currently operating without my customised sorting.

Thanks in advance for any help given.

[simoncn]

There are no changes in update 272 that could cause this. Are you sure you have the folder name spelt correctly (appData, not appdata)?

[redged]

Thanks for replying Simon.

I updated, then the icon turned red and it had red writing stating something about the tagUpdate not being in the correct location. I deleted the tagUpdate reference in properties and the icon turned green.

Now when I try to reinstate I get the following

   

   

[simoncn]

It looks like there is an ownership or permissions problem with the sort.txt file. Please do the following:

1) Right-click the sort.txt file and select Properties
2) Take a screenshot of the Properties pop-up
3) In the Properties pop-up, select the Permission tab and take another screenshot
4) Attach both screenshots to a post here

Edit: Have you recently updated from DSM 6 to DSM 7? I am asking this because DSM 7 changed the way file permissions are handled for MinimServer.

[redged]

Hello Simon, as always thanks in advance for your help. Info as requested.

Still on DSM 6

   

   

[simoncn]

Thanks for this information. I don't see anything unusual in these screenshots.

I am surprised that this is happening on DSM 6, as MinimServer runs as root on DSM 6 and should be able to open and read all files. Is it possible that some other program has the sort.txt file open and this is blocking MinimServer from opening it for reading? For example, is this file being accessed from some other device on the network?

I checked the code that produces the "file not found" message. This message is misleading because it can also be produced when the file exists but cannot be opened for some reason. This misleading message will be corrected in the next MinimServer update.

[Klaus57]

(03-03-2026 08:03)redged Wrote:  Thanks for replying Simon.

I updated, then the icon turned red and it had red writing stating something about the tagUpdate not being in the correct location. I deleted the tagUpdate reference in properties and the icon turned green.

Now when I try to reinstate I get the following

Hi redged,

This probably doesn't mean anything - but in the File Station screenshot, the file "sort.txt" has a different icon than all the others. Could it be that the file wasn't saved as a true text file—perhaps during editing? Best regards;

[simoncn]

(04-03-2026 08:43)Klaus57 Wrote:  This probably doesn't mean anything - but in the File Station screenshot, the file "sort.txt" has a different icon than all the others. Could it be that the file wasn't saved as a true text file—perhaps during editing? Best regards;

I had the same thought, so I set up a test using the same filename (sort.txt). The different icon is displayed by Synology File Station for a file with a .txt extension but has no other significance. For me, the sort.txt file was accepted for the tagUpdate setting with no error message.

[simoncn]

Please try uploading a new copy of the tag update file to the appData folder using Synology File Station, using a different name (for example, sort2.txt). After doing this, change the tagUpdate property to sort2.txt and restart MinimServer.

[redged]

Quick update and thanks to everyone for your help, its much appreciated.

I have no idea why this happened, but I have stopped and restarted the app and that has worked.

Apologies to everyone, I thought I had already tried this as its something I always do when anything won't work (try a restart). I got dragged in as it happened as soon as I updated.

Thanks again.