Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[klauss]

I upgraded from MC21 to MC23 and server sync is not working anymore. For instance, a show that I watch from a connected client (running the same MC23) will not save its position or won't delete files. When I delete a file from a client, it disappears from the list of available shows, but it will show up the next time when I start the client and I can (of course) see that the file(s) are not deleted from the server's disk. Deleting files using MC 23 on the server works just fine. I turned on authentication and also selected the checkbox 'auto sync with server'. No luck. Any way I can figure out why this is not working?

[JimH]

Authentication is required.  Try restarting both sides.

[klauss]

I turned on authentication on both sides. I did restart both sides more than once. No luck. What I am finding a little 'odd' is that I can re/enter my credentials on the server as many times as I want, but the client only offers me to re/enter 'read only' creds. I was only able to enter read / write creds after initial installation of the client.

[klauss]

I have un-installed the client and the server, rebooted both machines, re-installed both machines. Same result. I want to note that the behavior on the client is very odd when I delete a recording in the standard UI. The file that I 'deleted' will NOT disappear from the list of recordings, however, the selection jumps to another line. Deleting on the server works just fine. One additional thing to note is that both machines recently received the Windows 10 Falls Creators Update - I want to mention that since it could be related. I really would appreciate help on how to figure out what happened.

[klauss]

I also deleted my library on the server and re-created it. I turned on logging to see if there is some hint as to why this is not working - no luck. The client does not even store the last position where I stopped watching a show. I would really appreciate some help here to figure out why this is not working.

[fitbrit]

Sounds like you could be running different libraries on server and client. Did you uninstall MC21? It sounds as if you are still connected to the MC21 library server to me, if you did not.

[klauss]

I uninstalled MC21 and MC23 on both the client and the server. Rebooted both boxes. Then I re-installed MC23 on both machines and restored a library backup (including settings) on the server. Shared my library on the server and created a media authentication password (read / write) on the server. I then deleted the (restored) library on the server completely and re-added my directories - waited for the library to be ready (took about 10 min).

Then I started the client and connected to the server using the access key and entered the username / password (My client does not have a local library - it only uses the server). Tried to delete a file from the client - does not delete the file on the server (this used to work). The odd thing is that when I delete a file (from the client) from theater view, the file actually disappears. When I delete a file in standard view, the file does NOT disappear. Deleting files on the server in any view always works.

Again, I would like to mention that I also installed the Windows Fall Creator's Update. This update introduced some bugs for IIS and powershell. Of course, I don't know if there is a correlation, but I want to point that out.

[~OHM~]

error

[klauss]

I believe it's configured the way it should be. The option 'auto sync with server' is selected and I also have an 'authentication' username and password set. Both of these are set on the server and the client. Anything else I should do?

[tzr916]

What exactly is the purpose of "Authentication (must be on to use Library Server Sync)" ?
And what exactly is "Library Server Sync" ?

I've never enabled Authentication, just have "Auto sync with server" checked... and deleting files/tagging files from clients has always worked fine.

[RoderickGI]

Klauss, a firewall on your Server or Client or both is blocking MC transactions between the Server and the Client. You need to investigate your firewalls and explicitly allow MC programs to operate. There is a small chance a Virus Scanner is the actual culprit if yours uses heuristics or similar, but I would look to the firewall first.

This explains perfectly the scenario of deleting a file on the Client, having it disappear on the Client View, but then reappearing when the Client is closed and reopened. i.e.
Delete file in Client.
The local copy of Server Library is updated with the deletion, removing the file from the view. This is immediately apparent in Theatre View, but requires a refresh of the View in Standard View, possibly.
Firewall blocks the deletion from being executed on the Server and also blocks the update of the Server Library. Probably the Server Firewall, but could be the Client Firewall.
The Client is closed.
The Client is reopened and a new, fresh copy of the Server Library is downloaded, which includes the "deleted" file.
Frustration and confusion ensue.  ?


When you upgraded from MC21 to MC23 all the executables changed, so a firewall would want to be told those executables were okay to Allow again. If you have notifications turned on in your Firewall it should have generated messages asking whether you want to allow the programs access the first time you used MC23. Typically there are several notifications, for different parts of MC. I usually get two or three when I install a new major version, at times like initial connection to the Server, first playback of video, audio, etc. which require access to the internet to download madVR, LAV, codecs, etc. I'm using Norton 360 on all my Windows PCs and do not have it set to Silent Mode specifically so that I can see when the firewall needs to Allow access to something.

Check which MC21 programs are Allowed in your Firewall, and make sure that the equivalent MC23 programs are also Allowed. on your Server and Client.

[klauss]

Bingo. Your analysis was spot on. It turns out that it's the webroot firewall / av on the client side. I turned the client side webroot off (still running on the server side) and that actually did the trick. With webroot turned off everything is working. Since I have the root cause I will be able to configure a firewall exception. Nicely analyzed. I truly appreciate your help. The next round is on me.

THANK YOU!!! 

[RoderickGI]

You are welcome.

I'm not sure when I will be in your neck of the woods to collect that round, but I appreciate the thought.