Caught exception trying to convert extra data attribute 'originallyAvailableAt'

Server Version#: 1.24.4.5081
Player Version#: 4.63.0

Caught exception trying to convert extra data attribute ‘originallyAvailableAt’ with type 1 and value ‘2019-04-05’ ~ bad lexical cast: source type value could not be interpreted as target

Thoughts?

1 Like

I’m also seeing the same and its only started in past 3 days on random files.

Oct 03, 2021 19:13:45.269 WARN Caught exception trying to convert extra data attribute ‘originallyAvailableAt’ with type 1 and value ‘2021-10-01’ ~ bad lexical cast: source type value could not be interpreted as target

Appears to be related to music albums.

Inside the SQLite database I found originally_available_at on the metadata_items table with a value of ‘1-01-01 00:00:00’.

I was able to confirm this within the Plex music library with albums where filtered by Album Decade is 0s and I identified a number of albums.

I have selected them all and bulk edit them, wiping out the value in Originally Available.
I’ll continue to monitor to see if the error presents itself in the log again.

Another possibility is the Plex Music agent is polling data from AllMusic and MusicBrainz and getting an unexpected response. Then throwing an exception with encountering data that doesn’t parse into its data type.

I have this on video as well, but seems to affect my Samsung only:
Oct 09, 2021 07:16:19.452 [0x7f9f00ad5b38] WARN - Caught exception trying to convert extra data attribute ‘originallyAvailableAt’ with type 1 and value ‘1970-01-24’ ~ bad lexical cast: source type value could not be interpreted as target
and then this which I am unsure whether it is related:
Oct 09, 2021 07:17:08.350 [0x7f9f00b60b38] ERROR - Unknown metadata type: folder
Oct 09, 2021 07:17:08.672 [0x7f9f00ad5b38] WARN - LPE: falling back to slow path evaluation: /library/collections/38349/children
Oct 09, 2021 07:17:17.631 [0x7f9efdbb7b38] WARN - SLOW QUERY: It took 280.000000 ms to retrieve 16 items.

I’m glad there seems to be an easy solution. Although I don’t understand the steps to the solution. If you could explain it again I would appreciate it.

1 Like

For anyone else who needs clearer instruction:

Enter the ‘Music Library’, go to the ‘Library’ section, in the top right replace ‘All’ with ‘Advanced Filters’. The first criteria under ‘Match all of the Following’ should be set to ‘Album Decade’ and on the decade input there will apparently be a ‘0s’ option. Which you can now bulk edit to remove the warning/error.

I didn’t have any such values so this was not the solution for me, I posted this to clarify what was said by nathanstorms.

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.