Bug 12428 - Error during install: libFLAC_dynamic.dll was not found
: Error during install: libFLAC_dynamic.dll was not found
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Windows Installer
: 7.4.0
: PC Windows Vista
: -- normal (vote)
: 7.4.0
Assigned To: Dan Evans
http://forums.slimdevices.com/showthr...
: Support-Important
Depends on:
Blocks: 12429
  Show dependency treegraph
 
Reported: 2009-06-17 13:37 UTC by Dan Evans
Modified: 2009-10-05 14:28 UTC (History)
6 users (show)

See Also:
Category: Bug


Attachments
Crash error during server install (16.07 KB, image/jpeg)
2009-06-17 13:38 UTC, Dan Evans
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Evans 2009-06-17 13:37:45 UTC
While performing an auto-update today the installer appeared to uninstall SC first then do a full install.  (maybe to switch from SC to "SB Server"?)  At the end of the install SQUEEZ~1.EXE crashed with this error:

"This application has failed to start because libFLAC_dynamic.dll was not found.  Re-installing the application may fix this problem."

This is the second time I've seen this error in the last 2 weeks.  Sorry, not sure what version I was updating from or to.  It updated twice today so it's unclear.

System info: Win XP SP2
Comment 1 Dan Evans 2009-06-17 13:38:20 UTC
Created attachment 5343 [details]
Crash error during server install
Comment 2 Michael Herger 2009-06-17 23:56:02 UTC
Can you reliably reproduce this? On any Windows machine? What AV/Security suite?
Comment 3 Dan Evans 2009-06-18 12:17:20 UTC
I thought I'd do a clean install to be sure.  The error appeared during the UNinstall process.  Then I downloaded latest build, 27149, and reinstalled.  Error came up again preventing the CP from opening.

Tried manually opening CP and it failed with error 3 times then finally opened on the 4th try.

Originally when I saw this error a couple weeks ago I had no security software installed at all.  Currently I have Outpost Firewall installed to test the Troubleshooting tab in CP.
Comment 4 Michael Herger 2009-06-18 13:32:46 UTC
> Originally when I saw this error a couple weeks ago I had no security  
> software installed at all.

But can you reliably reproduce it on another machine? I don't believe this  
is a general issue, as we would have heard from our users. And I've never  
seen this myself, running tests on Windows 2k, XP, Vista, 2008, 7.
Comment 5 Michael Herger 2009-06-18 13:37:35 UTC
*** Bug 12429 has been marked as a duplicate of this bug. ***
Comment 6 Dominic Evans 2009-06-19 02:09:17 UTC
I am also seeing this, on vista 64sp2.

Not sure if this is relevant, but the new SC routine uninstall always failed (just hung). The only way i could install SBs was to manually uninstall the SBs from a couple of days ago, then uninstall SC, then delete both SC/SBs folders, then reinstall in that order. So its effectively a fresh install.

My scanner just loops now though.
Comment 7 Michael Herger 2009-06-19 02:18:59 UTC
This must be your family names :-).

Dominic - could you please make sure the scanner issue is documented in a separate bug report including scanner.log etc. Thanks.
Comment 8 Michael Herger 2009-06-23 00:20:34 UTC
Could you please check if you have any pdk* sub folders in any of your Windows temporary folder, especially in 

C:\Documents and Settings\*username*\Local settings\Temp

If so, then please shut down any SC related program (Tray icon, control panel, SC itself), wipe those folders and try again. Any change?

We seem to suffer from some regression here: while we added an option to clean up those folders, this doesn't always happen if something can't shut down properly. Leaving those folders behind can lead to messages as you've reported.

If this is the case, then this might be related to bug 12495
Comment 9 Dan Evans 2009-06-23 09:05:38 UTC
FYI, I had 176 PDK folders in the path you listed below, ranging in creation dates from 10/2007 to 6/2009.  I've deleted most of them but 1-2 I'm unable to delete.  Or more specifically, I can only delete them if I shut down SqueezeTray.  When I restart SqueezeTray 1-2 folders are created.

Is this what you expect?
Comment 10 Michael Herger 2009-06-23 09:17:08 UTC
> FYI, I had 176 PDK folders in the path you listed below, ranging in  
> creation dates from 10/2007 to 6/2009.

Wow :-).

> I've deleted most of them but 1-2 I'm unable to
> delete.  Or more specifically, I can only delete them if I shut down
> SqueezeTray.  When I restart SqueezeTray 1-2 folders are created.
> Is this what you expect?

Yes, this sounds pretty much correct: you can't delete them as long as one  
of our apps is still using them. And every app will create a new folder  
when it's started. Obviously the cleaning up once the app is stopped  
doesn't always work. If eg. the scanner crashes -> one folder left behind.  
Recently the control panel crashed on every start -> one folder per start.  
etc.

I've added code to the tray icon and control panel to do regular cleanups  
of unused folders. Let's see how this behaves.
Comment 11 John Keeling 2009-06-23 17:32:44 UTC
SC 7.3.3 and earlier 7.3.3 nightly builds, Win XP SP3

Message "The procedure entry point Perl_newXS_flags could not be located in the dll perl58.dll" 

I occasionally get this message several times on startup and SC 7.3.3 does not start, the tray icon just sits there blinking.
Workaround is right clicking the tray icon and exit, then from the Start menu run SC and it usually fixes it. However if that doesn't, then a server shutdown and restart always has.

I searched for PDK folders and deleted 30 or 40 of them.
Comment 12 James Richardson 2009-06-25 13:22:59 UTC
*** Bug 12522 has been marked as a duplicate of this bug. ***
Comment 13 Michael Herger 2009-07-01 23:19:26 UTC
Dan - could you please update your people to follow the "delete pdk* folders" route whenever SC is complaining about missing DLLs or similar? Bug 12586 is mostly a dupe of this, and it seems LaRon took a rather laborious way trying to solve this issue...
Comment 14 Michael Herger 2009-07-01 23:19:58 UTC
*** Bug 12586 has been marked as a duplicate of this bug. ***
Comment 15 Michael Herger 2009-07-02 06:05:21 UTC
change 27392 - I backported part of what I've added from 7.4 to 7.3.4. The tray icon should now clean up the mess crashing apps left behind. This will not work in 100% of all cases, but should help reduce the probability of hitting that issue.
Comment 16 Michael Herger 2009-07-02 06:56:31 UTC
Please update to the latest 7.3.4 build. This should take care of the cleanup work. Successfully wiped about 100 of those folders on my test system
Comment 17 Walker LaRon 2009-07-02 13:33:16 UTC
Hello All,

For Vista, the path the the PDK folders are as follows:

C:\Users\<username>\AppData\Local\Temp


Thanks,

LaRon
Comment 18 James Richardson 2009-08-06 07:25:15 UTC
*** Bug 13255 has been marked as a duplicate of this bug. ***
Comment 19 James Richardson 2009-08-06 08:18:21 UTC
This issue has come back, and I am able to replicate it.  Even if I remove the PDK files, I'm still unable to install.

This happens when upgrading from 27954 to 28076
Comment 20 Andy Grundman 2009-08-06 08:54:09 UTC
This was never broken, marking fixed.
Comment 21 Walker LaRon 2009-08-25 17:11:44 UTC
(In reply to comment #19)
> This issue has come back, and I am able to replicate it.  Even if I remove the
> PDK files, I'm still unable to install.
> 
> This happens when upgrading from 27954 to 28076

Hey James,

I have a customer with the same issue.

SC 7.3.4
Windows XP
No anti-virus or security software

Had delete 5 PDK folders:

4 pdk folders under the C:\Documents and Settings\USERNAME\Local Settings\Temp

and

1 in c:\windows\temp

Upon ending the squeezesvc the pdk folder in c:\windows\temp automatically was removed, but he still had to remove the 4 PDK folders from C:\Documents and Settings\USERNAME\Local Settings\Temp

Upon Reboot, the PDK folders came back in the above stated directories

Deleted them again, and SqueezeCenter still would not start.

Found a file named WGAErrLog.txt in c:\windows\temp, deleted it then the service started.

I hope this information helps.

Thanks,

LaRon
Comment 22 Michael Herger 2009-08-26 02:39:57 UTC
Please note that is an issue we can't fix once and for all time. It will always happen on some installations, but shouldn't be something you see every day.

It not only depends on our code, but on PDK too, and potentially other installed applications on the user's computer.

Feel free to re-target this to a release if this should become a daily issue again.

> Windows XP
> No anti-virus or security software

He better should :-)

> Upon ending the squeezesvc 

Did it end automatically or did you shut it down? 

> the pdk folder in c:\windows\temp automatically was
> removed, but he still had to remove the 4 PDK folders from C:\Documents and
> Settings\USERNAME\Local Settings\Temp

Make sure _all_ of our executables are stopped (server, scanner, tray icon, control panel) before deleting anything. 

> Upon Reboot, the PDK folders came back in the above stated directories

As soon as one of our applications (or even some other Perl app) starts it will create those folders. There's nothing wrong with that.

Keep in mind these folders are nothing evil, but necessary for our application to run. If you pull them while an app is running, it will crash. Most likely with that very message about the missing file.

> Found a file named WGAErrLog.txt in c:\windows\temp, deleted it then the
> service started.

This has nothing to do with SC. If the service afterwards started, then this was pure conincidence. The service would have started with that file in place. It just needed the time you spent caring about that file :-)
Comment 23 Walker LaRon 2009-08-26 11:29:38 UTC
Hello Michael,

Thanks for the update, information and guidance.

LaRon
Comment 24 bphilp 2009-08-31 19:03:50 UTC
Michael, while my solution to wipe the temp dirs of pdk folders is very unorthodox it does work... I've not had a crash since making the change.

A note of interest is that when I do the nightly reboot I do not gracefully end the squeezesvc but instead simple issue this forceful reboot command "C:\WINDOWS\system32\shutdown.exe -r -f"
Comment 25 Michael Herger 2009-09-01 00:18:09 UTC
> Michael, while my solution to wipe the temp dirs of pdk folders is very
> unorthodox it does work... I've not had a crash since making the change.

That's ok. It's just not safe to remove the temp folder at any time.

BTW: what we're doing in 7.3.4 and later is wipe all pdk* folders which  
don't match a process ID (the number in the folder name refers to the  
process which created it).
Comment 26 bphilp 2009-09-04 19:31:37 UTC
Just a quick update to let you know that my squeezesvc crashed today after a reboot.  So my script of clearing the pdk folders didn't fix the problem.  Might be useful to look elsewhere to fix this problem??
Comment 27 James Richardson 2009-09-14 09:17:34 UTC
Verify that TS has adequate FAQ for customers that run into this issue.

We have done as much as we can to fix the issue, however some instances of PDK files may still exist that can cause the issue to appear.
Comment 28 bphilp 2009-09-14 09:25:14 UTC
As a follow up I've stopped deleting the PDK folders as previously posted and have altered my reboot to do a gentle shutdown of the Squeezesvc using a CLI script to issue the shutdown command prior to taking down the OS.  

Will post back if this resolves the issue.  So far so good.
Comment 29 bphilp 2009-09-15 03:55:30 UTC
Gentle shutdown didn't help... decided to switch from using a Service to a manual run of squeezecenter.exe in the START menu at boot time.  Works fine for now and I've noticed a huge performance improvement since it runs in an active window on the taskbar (higher priority I suppose).  Will post an update later.
Comment 30 bphilp 2009-09-16 17:46:17 UTC
As an alternate means of running squeezecenter.exe at startup time I learned the following trick which works, has great performance AND is stable... 20 reboots with no crashes!

Create a new XP service with the simple DOS commands...
sc create "SqueezeStart" binPath="C:\Progra~8\SqueezeCenter\server\squeezecenter.exe"
Comment 31 bphilp 2009-09-16 17:47:57 UTC
As an alternate means of running squeezecenter.exe at startup time I learned the following trick which works, has great performance AND is stable... 20 reboots with no crashes!

Create a new XP service with the simple DOS commands...
sc create "SqueezeStart" binPath="C:\Progra~8\SqueezeCenter\server\squeezecenter.exe"
Comment 32 Michael Herger 2009-09-17 00:17:02 UTC
> As an alternate means of running squeezecenter.exe at startup time I learned
> the following trick which works, has great performance AND is stable... 20
> reboots with no crashes!

Ahm.... that's why we've added this as an option in 7 something. In 7.3 there's the startup configuration tool in the start menu, in 7.4 it's part of the control panel (accessible through the tray icon). No need to fiddle with the command line.
Comment 33 James Richardson 2009-10-05 14:28:36 UTC
This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server!
    * SqueezeCenter: 28672
    * Squeezebox 2 and 3: 130
    * Transporter: 80
    * Receiver: 65
    * Boom: 50
    * Controller: 7790
    * Radio: 7790  

Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes

If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.