Start a new topic

explanation of errors in log

there is an explanation for the next two error in the log

Error one

2019-06-04 11:35:11.5063|ERROR|MyLogger|AlbumView:Unable to update track: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding. st:    bij MySql.Data.MySqlClient.Interceptors.ExceptionInterceptor.Throw(Exception exception)

Error two

2019-06-04 11:36:26.9071|ERROR|MyLogger|AlbumView:ExecuteNonQuery: Data too long for column 'AlbumSubtitle' at row 1 sql:UPDATE tblAlbums SET   TotalItems = 120,   TotalSize = 4131,   TotalLength = 21946,   AlbumArtist = 'Ramses Shaffy',   ReleaseType = 2,   TotalCDs = 8,   PartOfSeries = '',   ReleaseYear = 1980,   AlbumSortorder = 'Laat Mijn Liedjes Nu Maar Zwerven',   AlbumSubtitle = 'Ramses Ii (Reissue)/Zonder Bagage (Reissue)/Wij Zullen Doorgaan... Reissue//We Leven Nog (Reissue)/Dag En Nacht (Reissue)/Ramses Live (Reissue)/Sterven Van Geluk (Reissue)/Een Bloemenkrans En Een Nachtgewaad (Reissue)',   AlbumLabel = 'Universal',   ArtistSortOrder = 'Various artists',   AlbumPath = 'P:\\_Taggend\\Ba\\Ramses Shaffy\\Laat Mijn Liedjes Nu Maar Zwerven_Cd-8]\\Cd-8',   AlbumVersion = '',   RecYear = 2006,   AddedDate = tblAlbums.AddedDate,   IsVa = 0,   AlbumName = 'Laat Mijn Liedjes Nu Maar Zwerven',   ItemType=3 WHERE   (album_id=16673); st:    bij MySql.Data.MySqlClient.MySqlStream.ReadPacket()

This error stems from a collection box where the album is called "Laat Mijn Liedjes Nu Maar Zwerven" but all CDs in the box have a different AlbumSubtitle name:
Let My Songs Now Roam Ramses II (Reissue)
Let My Songs Now Roam Without Luggage (Reissue)
Let My Songs Now Roam We Will Continue ... Reissue
Let My Songs Now Roam We Are Still Living (Reissue)
Let My Songs Now Roam Day And Night (Reissue)
Let My Songs Now Roam Ramses Live (Reissue)

this puts this above the length / set in the database.
this means that albums with different CDs AlbumSubtitle cannot be put under an album name but as a standalone album Let My Songs Now Roam (Ramses Live (Reissue)) "in AlbumName.
can this problem be solved?

Good morning Mikael. Thanks for the explanation. on behalf of my dj's thank you.

This seem to be the same issue, incorrect classification. ERROR should be INFO, none of the listed lines are actual errors.

thanks Mikael voor de wijziging in de volgende nieuw update.

now the next error in the log.
when updating a folder the following message is the error log:

2019-06-04 15:45:07.2197|ERROR|MyLogger|UpdateLibraryRepository:AddRatings(Start)
2019-06-04 15:45:07.2277|ERROR|MyLogger|UpdateLibraryRepository:AddRatings(END)
2019-06-04 15:45:09.2759|ERROR|MyLogger|UpdateLibraryRepository:Adding new genres
2019-06-04 15:45:09.2828|ERROR|MyLogger|UpdateLibraryRepository:Mapping genres
2019-06-04 15:45:09.2828|ERROR|MyLogger|UpdateLibraryRepository:Create genres; 8705
2019-06-04 15:45:11.4381|ERROR|MyLogger|UpdateLibraryRepository:Create labels; 3978
2019-06-04 15:45:12.5572|ERROR|MyLogger|UpdateLibraryRepository:Creating artists: 0
2019-06-04 15:45:12.5572|ERROR|MyLogger|UpdateLibraryRepository:Get ids
2019-06-04 15:45:12.5702|ERROR|MyLogger|UpdateLibraryRepository:Bind to tblArtist_x_detail
2019-06-04 15:45:12.5702|ERROR|MyLogger|UpdateLibraryRepository:Clear new
2019-06-04 15:45:12.6231|ERROR|MyLogger|UpdateLibraryRepository:Created artists
UpdateArtistSummaryByArtistNameFromAdd sql: SELECT tblArtists.Artist_ID, tblArtists.ArtistName, tblArtists.ArtistSortorder, 0, Max(tblDetail.artistsortorder) AS MaxOfartistsortorder, Min(tblDetail.totalartists) AS MinOftotalartists, Count(tblDetail.Detail_ID) AS CountOfDetail_ID, Avg(tblRating.Rating) AS AvgOfRating, Max(tblDetail.totalartists) AS MinOftotalartists1, tblArtists.ArtistPicturePath, tblArtists.biography FROM (tblDetail INNER JOIN (tblArtists INNER JOIN tblArtist_x_Detail ON tblArtists.Artist_ID = tblArtist_x_Detail.Artist_ID) ON tblDetail.Detail_ID = tblArtist_x_Detail.Detail_ID) INNER JOIN tblRating ON tblDetail.Detail_ID = tblRating.Detail_ID WHERE (tblRating.User_ID = 1) GROUP BY tblArtists.Artist_ID, tblArtists.ArtistName, tblArtists.ArtistSortorder, tblArtists.ArtistPicturePath, tblArtists.biography
2019-06-04 15:45:12.6420|ERROR|MyLogger|UpdateLibraryRepository:BATCH1
2019-06-04 15:45:13.6798|ERROR|MyLogger|UpdateLibraryRepository:GET ALL ARTISTS
2019-06-04 15:45:13.7386|INFO|MyLogger|UpdateLibraryRepository:******Art4
2019-06-04 15:45:13.7386|ERROR|MyLogger|UpdateLibraryRepository:BATCH2: False
2019-06-04 15:45:13.7386|INFO|MyLogger|UpdateLibraryRepository:**************Art 4.1: 653
2019-06-04 15:45:13.7516|ERROR|MyLogger|UpdateLibraryRepository:UPDATING SUMMARY

this is a small overview in the appendix total overview

this error keeps coming again, the folder is deleted and scanned again


Hi Geer,

The above lines are actually not errors, despite that the logging output says so.

It seems more like an incorrect classification of the outputted lines (they should be INFO and only logged when advanced logging is active).

We will correct it for an upcoming release, thanks for reporting it.

Thank you Mikael

"The first error indicates that you because of some reason have lost your connection to your MySql server. Is this constantly occuring when you perform a specific  task (if so, which) or does it just happen from and to? "

this error occurs when updating the folder

I think error one is resolved by adding the following lines in my.ini:
skip_name_resolve = 1
query_cache_size = 0

Fixed error two
the AlbumSubtitle table in the database has been adjusted to resolve 128 to 255 issue

I am not there yet Mikael when starting Helium the following lines appear in the log:

2019-06-04 14:17:56.5121|ERROR|MyLogger|:Starting
2019-06-04 14:17:56.5281|ERROR|MyLogger|:1
2019-06-04 14:17:56.5560|ERROR|MyLogger|:2
2019-06-04 14:17:56.5560|ERROR|MyLogger|:3
2019-06-04 14:17:56.6737|ERROR|MyLogger|:4
2019-06-04 14:17:56.9474|ERROR|MyLogger|UpdateDetailRepository:5
2019-06-04 14:17:56.9604|ERROR|MyLogger|UpdateDetailRepository:6
2019-06-04 14:17:56.9604|ERROR|MyLogger|UpdateDetailRepository:C:\ProgramData\Imploded Software\Helium 14\languages\Translation.resx
2019-06-04 14:17:56.9604|ERROR|MyLogger|UpdateDetailRepository:C:\ProgramData\Imploded Software\Helium 14\languages\
2019-06-04 14:17:56.9604|ERROR|MyLogger|UpdateDetailRepository:x1
2019-06-04 14:17:56.9784|ERROR|MyLogger|UpdateDetailRepository:x3
2019-06-04 14:17:56.9784|ERROR|MyLogger|UpdateDetailRepository:x5
2019-06-04 14:17:56.9864|ERROR|MyLogger|UpdateDetailRepository:x6
2019-06-04 14:17:56.9864|ERROR|MyLogger|UpdateDetailRepository:Set culture: Translation.resx
2019-06-04 14:17:56.9864|ERROR|MyLogger|UpdateDetailRepository:Version: 14.1.16160.0
2019-06-04 14:17:57.1230|INFO|MyLogger|UpdateDetailRepository:Active culture: Nederlands (Nederland)
2019-06-04 14:17:57.1270|ERROR|MyLogger|UpdateDetailRepository:7

Changing the language in option and adjusting user rights does not resolve this error.

Do you have option for this eror mikael.

Hi Geer,

The first error indicates that you because of some reason have lost your connection to your MySql server. Is this constantly occuring when you perform a specific  task (if so, which) or does it just happen from and to?

For the second issue, I assume it happens after tagging?

The fields in the database size limits and for this specific case it seems like the length exceeds the maximul allowed length.

Generally it will result in that the data will be truncated. If you need larger max-sizes, you can manually adjust the field sizes for your MySql database.

Login or Signup to post a comment