[Solved] Muso crashes when testing database connection....

Fixed bugs will be filed here.
DuLac
Posts: 213
Joined: Sun Feb 10, 2013 9:53 am

[Solved] Muso crashes when testing database connection....

Post by DuLac »

...when I tried to test the SQLite connection. I am running Win10 64 and my LMS database folder is exposed and properly linked.
To try and solve the problem I tried stoping the UAC, I then uninstalled Muso and installed the legacy version but always to no avail.
I then used Microsoft Win 10 built in Troubleshoot Compatibility tool and after fiddling with several options I manage to solve the problem when I chose that Muso was working fine under Win 7 (64 too)
I could not find a way to start Muso in debug mode. There is no such option now on my Win10 installation.
Therefore in order to try and get help in pinpointing the problem I transcribe hereunder the OS crash report.

Code: Select all

Version=1
EventType=InPageError
EventTime=131092514591480595
ReportType=2
Consent=1
UploadTime=131092514592478922
ReportIdentifier=ca6a0b18-27e5-11e6-bde2-f46d04719de8
IntegratorReportIdentifier=4839e968-9442-47b7-b043-ead590ed7d2e
NsAppName=Muso.exe
Response.BucketId=e1c177ee6da8d2bff64ce61dd3e053a9
Response.BucketTable=5
Response.LegacyBucketId=1710875
Response.Str=http:////oca.microsoft.com//resredir.aspx?SID=1163&iBucketTable=5&iBucket=1710875&BucketHash=e1c177ee6da8d2bff64ce61dd3e053a9
Sig[0].Name=Error Status Code
Sig[0].Value=c0000054
Sig[1].Name=Faulting Media Type
Sig[1].Value=00000000
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.10586.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=2057
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=60ec
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=60ecd51f63fa85a72d4494f3801e93c1
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=36c3
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=36c3045ecc3b16fa9268c84edfd69b6c
UI[2]=C:\Users\Luis\AppData\Local\Apps\2.0\5MTJLAQP.N1P\E0ENDPYO.RDP\muso..tion_0000000000000000_0002.0005_7bfef665f8e1ac89\Muso.exe
UI[3]=muso has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Users\Luis\AppData\Local\Apps\2.0\5MTJLAQP.N1P\E0ENDPYO.RDP\muso..tion_0000000000000000_0002.0005_7bfef665f8e1ac89\Muso.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\SYSTEM32\MSCOREE.DLL
LoadedModule[3]=C:\Windows\system32\KERNEL32.dll
LoadedModule[4]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[5]=C:\Windows\system32\apphelp.dll
LoadedModule[6]=C:\Windows\system32\ADVAPI32.dll
LoadedModule[7]=C:\Windows\system32\msvcrt.dll
LoadedModule[8]=C:\Windows\system32\sechost.dll
LoadedModule[9]=C:\Windows\system32\RPCRT4.dll
LoadedModule[10]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll
LoadedModule[11]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[12]=C:\Windows\system32\combase.dll
LoadedModule[13]=C:\Windows\system32\bcryptPrimitives.dll
LoadedModule[14]=C:\Windows\system32\GDI32.dll
LoadedModule[15]=C:\Windows\system32\USER32.dll
LoadedModule[16]=C:\Windows\system32\IMM32.DLL
LoadedModule[17]=C:\Windows\system32\kernel.appcore.dll
LoadedModule[18]=C:\Windows\SYSTEM32\VERSION.dll
LoadedModule[19]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
LoadedModule[20]=C:\Windows\SYSTEM32\MSVCR120_CLR0400.dll
LoadedModule[21]=C:\Windows\assembly\NativeImages_v4.0.30319_64\mscorlib\43226440664fdfb99f9ad60968b2a60c\mscorlib.ni.dll
LoadedModule[22]=C:\Windows\system32\ole32.dll
LoadedModule[23]=C:\Windows\system32\uxtheme.dll
LoadedModule[24]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clrjit.dll
LoadedModule[25]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[26]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System\43b8952c0d907f0a02958a98443699ba\System.ni.dll
LoadedModule[27]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Drawing\fdc9c3b678ad232cb22146073f71c998\System.Drawing.ni.dll
LoadedModule[28]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Windows.Forms\9b397cef9e862b789463f8fb670d66f7\System.Windows.Forms.ni.dll
LoadedModule[29]=C:\Windows\system32\shell32.dll
LoadedModule[30]=C:\Windows\system32\cfgmgr32.dll
LoadedModule[31]=C:\Windows\system32\windows.storage.dll
LoadedModule[32]=C:\Windows\system32\shcore.dll
LoadedModule[33]=C:\Windows\system32\powrprof.dll
LoadedModule[34]=C:\Windows\system32\profapi.dll
LoadedModule[35]=C:\Windows\SYSTEM32\urlmon.dll
LoadedModule[36]=C:\Windows\SYSTEM32\iertutil.dll
LoadedModule[37]=C:\Windows\SYSTEM32\SspiCli.dll
LoadedModule[38]=C:\Windows\SYSTEM32\CRYPTSP.dll
LoadedModule[39]=C:\Windows\system32\rsaenh.dll
LoadedModule[40]=C:\Windows\SYSTEM32\bcrypt.dll
LoadedModule[41]=C:\Windows\SYSTEM32\CRYPTBASE.dll
LoadedModule[42]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Core\8e325c9a2b96c925621b8214b5785cd7\System.Core.ni.dll
LoadedModule[43]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Configuration\af40f3c8414c2b75e6a9e9c7a79fed97\System.Configuration.ni.dll
LoadedModule[44]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xml\b6708e6e2b55466cc8c5ac0eed95468b\System.Xml.ni.dll
LoadedModule[45]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Data\8a7bad83799510e0390936d8319078f2\System.Data.ni.dll
LoadedModule[46]=C:\Windows\Microsoft.Net\assembly\GAC_64\System.Data\v4.0_4.0.0.0__b77a5c561934e089\System.Data.dll
LoadedModule[47]=C:\Windows\system32\WS2_32.dll
LoadedModule[48]=C:\Windows\system32\CRYPT32.dll
LoadedModule[49]=C:\Windows\system32\MSASN1.dll
LoadedModule[50]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Data7706cdc8#\5f64707a72be2a9b487c5a9e55d3b921\System.Data.DataSetExtensions.ni.dll
LoadedModule[51]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Numerics\16570a0ad0322c624bb862191cb59dee\System.Numerics.ni.dll
LoadedModule[52]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.10586.0_none_396e892957c7fb25\comctl32.dll
LoadedModule[53]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.10586.0_none_8c15ae12515e1c22\comctl32.dll
LoadedModule[54]=C:\Windows\system32\dwmapi.dll
LoadedModule[55]=C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.10586.20_none_db007f1392e69ef4\gdiplus.dll
LoadedModule[56]=C:\Windows\SYSTEM32\DWrite.dll
LoadedModule[57]=C:\Windows\system32\MSCTF.dll
LoadedModule[58]=C:\Windows\SYSTEM32\RichEd20.DLL
LoadedModule[59]=C:\Windows\SYSTEM32\USP10.dll
LoadedModule[60]=C:\Windows\SYSTEM32\msls31.dll
LoadedModule[61]=C:\Windows\SYSTEM32\WindowsCodecs.dll
LoadedModule[62]=C:\Windows\system32\clbcatq.dll
LoadedModule[63]=C:\Windows\System32\ieframe.dll
LoadedModule[64]=C:\Windows\SYSTEM32\sxs.dll
LoadedModule[65]=C:\Windows\system32\dataexchange.dll
LoadedModule[66]=C:\Windows\system32\d3d11.dll
LoadedModule[67]=C:\Windows\system32\dcomp.dll
LoadedModule[68]=C:\Windows\system32\dxgi.dll
LoadedModule[69]=C:\Windows\system32\twinapi.appcore.dll
LoadedModule[70]=C:\Windows\SYSTEM32\PROPSYS.dll
LoadedModule[71]=C:\Windows\System32\mshtml.dll
LoadedModule[72]=C:\Windows\SYSTEM32\srpapi.dll
LoadedModule[73]=C:\Windows\SYSTEM32\ieapfltr.dll
LoadedModule[74]=C:\Windows\SYSTEM32\WININET.dll
LoadedModule[75]=C:\Windows\system32\msimtf.dll
LoadedModule[76]=C:\Windows\SYSTEM32\d2d1.dll
LoadedModule[77]=C:\Windows\SYSTEM32\d3d10warp.dll
LoadedModule[78]=C:\Windows\SYSTEM32\Secur32.dll
LoadedModule[79]=C:\Windows\SYSTEM32\MLANG.dll
LoadedModule[80]=C:\Windows\SYSTEM32\ntmarta.dll
LoadedModule[81]=C:\Windows\SYSTEM32\efswrt.dll
LoadedModule[82]=C:\Windows\SYSTEM32\wintypes.dll
LoadedModule[83]=C:\Windows\SYSTEM32\edputil.dll
LoadedModule[84]=C:\Windows\System32\uiautomationcore.dll
LoadedModule[85]=C:\Windows\System32\USERENV.dll
LoadedModule[86]=C:\Windows\System32\jscript9.dll
LoadedModule[87]=C:\Windows\SYSTEM32\ondemandconnroutehelper.dll
LoadedModule[88]=C:\Windows\SYSTEM32\IPHLPAPI.DLL
LoadedModule[89]=C:\Windows\SYSTEM32\winhttp.dll
LoadedModule[90]=C:\Windows\system32\mswsock.dll
LoadedModule[91]=C:\Windows\system32\NSI.dll
LoadedModule[92]=C:\Windows\SYSTEM32\WINNSI.DLL
LoadedModule[93]=C:\Windows\SYSTEM32\DNSAPI.dll
LoadedModule[94]=C:\Program Files\Bonjour\mdnsNSP.dll
LoadedModule[95]=C:\Windows\System32\rasadhlp.dll
LoadedModule[96]=C:\Windows\SYSTEM32\T2EMBED.DLL
LoadedModule[97]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[98]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Servf73e6522#\9ba1c2bd555f165ef965de84ddf3537e\System.ServiceModel.Web.ni.dll
LoadedModule[99]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.ServiceModel\2419e7e2035a9e24bacf22c436b859a9\System.ServiceModel.ni.dll
LoadedModule[100]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Runteb92aa12#\cf0b85bb854847b9b92e5e45ab95b114\System.Runtime.Serialization.ni.dll
LoadedModule[101]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Net.Http\b0fcbf89ef94c54b8d47bd204373b27e\System.Net.Http.ni.dll
LoadedModule[102]=C:\Windows\SYSTEM32\httpapi.dll
LoadedModule[103]=C:\Windows\system32\psapi.dll
LoadedModule[104]=C:\Program Files\Common Files\microsoft shared\ink\tiptsf.dll
LoadedModule[105]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Transactions\e53c0db4190a4314aae2dc20342cb262\System.Transactions.ni.dll
LoadedModule[106]=C:\Windows\Microsoft.Net\assembly\GAC_64\System.Transactions\v4.0_4.0.0.0__b77a5c561934e089\System.Transactions.dll
LoadedModule[107]=C:\Users\Luis\AppData\Local\Apps\2.0\5MTJLAQP.N1P\E0ENDPYO.RDP\muso..tion_0000000000000000_0002.0005_7bfef665f8e1ac89\x64\SQLite.Interop.dll
LoadedModule[108]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\diasymreader.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=InPageError
AppName=muso
AppPath=C:\Users\Luis\AppData\Local\Apps\2.0\5MTJLAQP.N1P\E0ENDPYO.RDP\muso..tion_0000000000000000_0002.0005_7bfef665f8e1ac89\Muso.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=8F2C77FA7DB8293A6A860A073C71EAFA
Last edited by DuLac on Thu Jun 02, 2016 6:15 pm, edited 1 time in total.
musoware
Site Admin
Posts: 1847
Joined: Fri Sep 14, 2012 6:50 am

Re: Muso stops working....

Post by musoware »

The latest version of muso has an option to turn debug on via a little bug icon top right, this should allow you to capture the problem in a muso2.log.

What has changed in your environment since the last time database access was working?

I do not quite understand "I manage to solve the problem when I chose that Muso was working fine under Win 7 (64 too)".
DuLac
Posts: 213
Joined: Sun Feb 10, 2013 9:53 am

Re: Muso stops working....

Post by DuLac »

Unfortunatelly the solution was temporary. That is if there has been a solution at all, something I now very much doubt. I did not change a thing from my previous report here but I am now back to square one. Everytime I try to test the SQLite connection the program crashes.
Here is the content of muso2.log

Code: Select all

+----+--------------+---------+--------------------------------------------------------------------------------------------------------------------------------------------------------
| Th |    Timestamp |  Timing | Log Message
+----+--------------+---------+--------------------------------------------------------------------------------------------------------------------------------------------------------
| 01 | 02:23:44.857 |         | muso version 2.5.18
| 01 | 02:23:44.857 |         | 01 June 2016 14:23:44
| 01 | 02:23:44.857 |         | Diagnostics turned on
| 01 | 02:24:05.244 | 020.388 | showOptions
| 01 | 02:24:05.244 |         | Options
| 01 | 02:24:05.532 |   0.291 | Build Fonts
| 01 | 02:24:05.714 |   0.179 | GetThemes
| 01 | 02:24:05.729 |    .008 | GetPreferences
| 01 | 02:24:05.745 |    .019 | checkTags
| 01 | 02:24:05.745 |    .007 | GetThemeWallpaper
| 01 | 02:24:05.745 |         | bind watch folders
| 01 | 02:24:05.745 |         | checkTags
| 01 | 02:24:05.745 |         | ctr done
| 01 | 02:24:05.745 |         | ShowTabNo
| 01 | 02:24:05.778 |    .019 | InitOptions
| 01 | 02:24:05.798 |    .029 | InitOptions done
| 01 | 02:24:09.978 | 004.173 | SaveMusicDB start
| 01 | 02:24:10.001 |    .034 | . no changes
| 01 | 02:24:10.032 |    .019 | SaveMusicDB end
| 01 | 02:24:11.088 | 001.064 | SLIMSERVERAPI 192.168.1.27 9090
| 01 | 02:24:11.088 |         | SS:SSAPI start
| 01 | 02:24:11.088 |         | SS:sEP 192.168.1.27,9090
| 01 | 02:24:11.088 |         | SS:addr=192.168.1.27
| 01 | 02:24:11.088 |         | SS:ip=192.168.1.27
| 01 | 02:24:11.088 |         | SS:ep=192.168.1.27:9090
| 01 | 02:24:11.088 |         | SS:SSAPI end
| 01 | 02:24:11.088 |         | SS:Connect
| 13 | 02:24:11.088 |         | SS:TELNET CONNECTION SUBTHREAD
| 13 | 02:24:11.088 |         | SS:socket connection 192.168.1.27:9090
| 13 | 02:24:11.105 |    .008 | SS:. connected True
| 01 | 02:24:11.106 |         | SS:. connected True
| 01 | 02:24:11.126 |    .020 | SS:Disconnect 
| 01 | 02:24:12.301 | 001.175 | SqueezeCenterSQLite.TestConnection
Native library pre-loader is trying to load native SQLite library "C:\Program Files (x86)\klarita.net\muso2\x64\SQLite.Interop.dll"...
| 01 | 02:24:12.372 |    .072 | . TestConnection: Connecting to data source=\\\\192.168.1.27\\squeezebox_db\\library.db;version=3;read only=False;default timeout=3;failifmissing=True;legacy format=True;journal mode=Wal
DuLac
Posts: 213
Joined: Sun Feb 10, 2013 9:53 am

Re: Muso stops working....

Post by DuLac »

Just in case it may be of help here is the content of my smb.conf

Code: Select all

"[global]
workgroup = JAZZY
server string = VortexBox Media Server
security = user
map to guest = Bad User
public = yes
obey pam restrictions = Yes
pam password change = Yes
dns proxy = No
usershare allow guests = Yes
log level = 3
log file = /var/log/samba/samba.log
unix extensions = no
wide links = yes
printcap name = /etc/printcap
load printers = no
socket options = IPTOS_LOWDELAY TCP_NODELAY SO_KEEPALIVE
write cache size = 2097152
use sendfile = true
getwd cache = yes
oplocks = no
netbios name = VORTEXBOX

[files]
comment = Read/Write file share
path = /storage
browsable = Yes
guest ok = Yes
read only = No
create mask = 0755
directory mask = 0755
force user = root
force group = root

[music_readonly]
comment = Read Only music share
path = /storage/music
browsable = Yes
guest ok = Yes
read only = Yes
create mask = 0755
directory mask = 0755
force user = root
force group = root

[pictures_readonly]
comment = Read Only pictures share
path = /storage/pictures
browsable = Yes
guest ok = Yes
read only = Yes
create mask = 0755
directory mask = 0755
force user = root
force group = root

[movies_readonly]
comment = Read Only movies share
path = /storage/movies
browsable = Yes
guest ok = Yes
read only = Yes
create mask = 0755
directory mask = 0755
force user = root
force group = root

#[keepout]
#path = /
#browsable = Yes
#guest ok = Yes
#read only = No
#create mask = 0755
#directory mask = 0755
#force user = root
#force group = root

[squeezebox_db]
path = /var/lib/squeezeboxserver/cache
browsable = Yes
guest ok = Yes
read only = No
create mask = 0755
directory mask = 0755
force user = squeezeboxserver
force group = squeezeboxserver

musoware
Site Admin
Posts: 1847
Joined: Fri Sep 14, 2012 6:50 am

Re: Muso stops working....

Post by musoware »

My question was concerning what had changed in your environment since database access last worked. Or is this a brand new environment where database access has never worked?

The smb.conf looks OK to me. What version of LMS ? Is it on a Vortexbox or similar?
DuLac
Posts: 213
Joined: Sun Feb 10, 2013 9:53 am

Re: Muso stops working....

Post by DuLac »

I run Logitech Media Server Version: 7.8.0 on a Vortexbox 32b.
I installed Win10 from scratch very recently. I am not sure if I had this issue before as as I believe Muso works without a connection to the DB and the problem could have gone unnoticed. However, I had noticed then (in W7) and continue to notice it now on W10 that if I add music files to the storage directory on my Vortexbox and add these songs files to Muso I am not able to play them until a LMS scan is performed. It was that behaviour that made me check the Db connection. I am led to believe that the problem was there before I installed W10.
Trying to figure out what has been changed I remebered that some 2 months ago I tried to install VB24 just to learn that my VB machine is unable to run a 64b envirnoment. I should have read the instructions a little more carefully. So I went back and installed VB23 again. The problem may be on this new VB install.
DuLac
Posts: 213
Joined: Sun Feb 10, 2013 9:53 am

Re: Muso stops working....

Post by DuLac »

After trying several situations I am now almost certain that the problem reported only happens immediately after copying a file or files to the VB storage folder and adding them to the Muso db. Prior to that and after that after an undetermined but more or less long period of time, the testing of the connection performs OK.
It could perhaps help me to try and determine the offending action if you could let me know what sort of connection test is performed within Muso. I could then try and replicate it from outside your program to see if I could get some clues as to what is happening.
musoware
Site Admin
Posts: 1847
Joined: Fri Sep 14, 2012 6:50 am

Re: Muso stops working....

Post by musoware »

That's interesting. I imagine LMS may be "busy" scanning the new files and adding it to it's database, therefore refusing an external connection. However this is not a situation I've ever encountered. The line at the bottom of the muso2.log file tells you how Muso is trying to connect:

data source=\\\\192.168.1.27\\squeezebox_db\\library.db;version=3;read only=False;default timeout=3;failifmissing=True;legacy format=True;journal mode=Wal
musoware
Site Admin
Posts: 1847
Joined: Fri Sep 14, 2012 6:50 am

Re: Muso stops working....

Post by musoware »

Actually I've just reproduced this by forcing LMS to rescan and then trying the Test button - it seems LMS only allows Muso to access its database when it's not scanning. So you may have to wait until after it scans before you import into Muso.

Alternatively - and this is what I generally do which explains why I haven't encountered this issue - import into muso first via a file/folder import. If you always use Muso as your front-end it's database becomes the master - and when you play new albums it forces them to be pushed and registered in LMS's database also.
DuLac
Posts: 213
Joined: Sun Feb 10, 2013 9:53 am

Re: Muso stops working....

Post by DuLac »

After this message of yours I am now pretty sure I got the culprit! Some time ago I added a plugin named AutoRescan which is supposed to quietly monitor the music library and to add new tracks as soon as they are dropped into the music folder.
Et voilá! I have not tried to reproduce the problem without the said plugin yet but I am sure that is what is causing the crash. It is only too logical. Thanks for all your support, Jeremy!
http://www.hickinbottom.com/page/autore ... can-plugin
-----------------
After disabling the plugin I confirm the problem is now solved.
Post Reply