I can see it connecting, and the connection appears successful (simply because I don't see an error and the processing continues), but I see a couple things that concern me regarding the credentials. Highlighted:
2020-06-04 16:52:07 . 52 - Common.SaveMediaInfo - The store path is on a remote server.
2020-06-04 16:52:07 . 52 - Common.SaveMediaInfo - Server is 'Tigger'
2020-06-04 16:52:07 . 52 - Common.SaveMediaInfo - Share path is 'Canada\Wolf of Wall Street'
2020-06-04 16:52:07 . 52 - Common.SaveMediaInfo - Share has subfolder
2020-06-04 16:52:07 . 52 - Common.SaveMediaInfo - Credentials found
2020-06-04 16:52:07 . 52 - Common.AddExternalCredentials - '\\Tigger\Canada'
2020-06-04 16:52:07 . 52 - Common.AddExternalCredentials - Credentials already exists for the share path '\\Tigger\Canada', but with different casing '\\tigger\Canada'. Confirming that the username and password have not been changed.
2020-06-04 16:52:07 . 52 - Common.AddExternalCredentials - The credentials are the same, username 'Thomas'. Returning True.
2020-06-04 16:52:07 . 52 - Common.SaveMediaInfo - Checking if directory exists '\\Tigger\Canada\Wolf of Wall Street'.
2020-06-04 16:52:07 . 53 - Common.SaveMediaInfo - Checking directory '\\Tigger\Canada\Wolf of Wall Street'.
Everything I highlighted yellow has an uppercase first character. I went round and round with Binnerup about this, that there seems to be an issue with capitalizing the first character of both NAS server names and usernames with My Movies. When logging into a NAS, My Movies will use the Server Name as the domain. For Linux logins (and your NAS most likely runs Linux), both usernames and domains need to be lowercase first char. It would be easier if My Movies simply lowercased them, but it will copy the servername as-is and try to log you into the server as \\Tigger\Thomas or Thomas@Tigger.
So even though I don't see an error, and I may be off base, I find that capitalized usernames and servernames/domains as problematic with My Movies.
The next bit that caught my eye is a few lines later, these two gems:
2020-06-04 16:52:07 . 67 - Common.SaveTitleMediaInfo - Checking content for element '\\Tigger\Canada\Wolf of Wall Street\VIDEO_TS\VTS_12_0.IFO'.
2020-06-04 16:52:07 . 67 - Common.SaveTitleMediaInfo - Content of folder have not changed since last storage and read version is the same leaving existing information, and updating update check date.
This seems to suggest to me that My Movies decided what's in the folder is already good, and is skipping the writing of any metadata. This, again, is a common problem for My Movies. We typically solve it by doing the full MM Metadata Clean step I have documented in the Getting Started guides. I know I wrote the other day that I didn't think you needed to do the clean, but that might be the only way to convince MM it needs to write data.
But I might be mis-interpreting what is happening there. This might be reading the IFO file in the directory, and seeing it hasn't changed so it isn't updating the MM DB. Their logs aren't super clear for us end users, so only they know exactly what that means.
I see this line posted a few times, which might have something to do with you not being able to manage external server credentials:
Code: Select all
2020-06-04 16:52:07 . 80 - Common.Database.OpenConn - Current Unclosed Connection: NotConfiguredExternalCredentialsExists
But I also see this, which suggests that write access on your NAS is working:
Code: Select all
2020-06-04 16:52:09 . 90 - Common.PerformTitleInfoStorage - Trying to create mymovies.ign file at '\\Tigger\Canada\Wolf of Wall Street\mymovies.ign'
2020-06-04 16:52:09 . 90 - Common.PerformTitleInfoStorage - mymovies.ign file created
By the way, the mymovies.ign file is an "IGNore" flag file, which MM places in folders temporarily while it is working in them, and then deletes automatically when it is done. It prevents the app from doing some processing at the wrong time.
Code: Select all
2020-06-04 16:52:10 . 17 - Common.PerformTitleInfoStorage - Deleting mymovies.ign file.
In general, I see it checking all the various media handlers (i.e. Dune, XBMC, Zappiti, TViXetc.) and none are enabled so it doesn't export any metadata for them, as expected. I also see where it teases about generating XML data for export, but I never see it being written.
So my main suggestion is to do the MMCM Metadata Clean. That's the one thing that has worked for all my other users, and while I thought we were beyond those days it seems this might still be a requirement for discless movie users like yourself.