View Issue Details

IDProjectCategoryView StatusLast Update
0011868MMW v4Install/Configpublic2014-09-23 13:37
Reporterlowlander Assigned To 
PriorityimmediateSeveritymajorReproducibilitysometimes
Status closedResolutionfixed 
Product Version4.1 
Target Version4.1.5Fixed in Version4.1.5 
Summary0011868: Error Code 5 on upgrade
DescriptionMany users encounter an error code 5 during upgrade. It isn't always sufficient to have MediaMonkey closed, sometimes it requires a reboot.
Additional InformationNCZ-964557, ZFO-152665, FUD-265594, IPG-959080, GJJ-100049, QDC-442336, CUR-307211, UTJ-123772, ZJP-751822, GGD-470-57946, EHH-184-94378, URC-868-72507, OWL-689-36258, KBZ-241-85088, KBP-998-80866
http://www.mediamonkey.com/forum/viewtopic.php?f=1&t=75479
http://www.mediamonkey.com/forum/viewtopic.php?f=1&t=73728&p=374528#p374528
http://www.mediamonkey.com/forum/viewtopic.php?f=1&t=71726&p=367630#p367630
http://www.mediamonkey.com/forum/viewtopic.php?f=1&t=71591&p=367339#p367339
http://www.mediamonkey.com/forum/viewtopic.php?f=1&t=75553
http://www.mediamonkey.com/forum/viewtopic.php?f=1&t=76954
http://www.mediamonkey.com/forum/viewtopic.php?f=1&t=77187
TagsNo tags attached.
Fixed in build1712

Relationships

related to 0000388 closedLudek MMW 5 MMHelper.dll sometimes prevents uninstallation/installation (regression in MM5) 

Activities

Ludek

2014-02-14 21:24

developer   ~0039615

Last edited: 2014-02-14 21:33

From the ticket id NCZ-964557:

C:\Program Files (x86)\MediaMonkey\MediaMonkey.exe
An error occurred while trying to replace the existing file:
DeleteFile failed; code 5. Access is denied.

It sounds as if the installer has not enough privileges to replace the file, asking more via the ticket/forums

But generally it can happen when user:
- installed MM 4.0.7 as administrator
- he installs 4.1 as normal user and/or he doesn't accept UAC prompt of the MM 4.1 installer

Anyhow solution could be to install MM 4.1 to different folder or to uninstall MM 4.0.7 as admin at first.

Peke could you take over and check whether we have this covered by KB articles? If not, could you create new KB article?

lowlander

2014-02-14 21:48

developer   ~0039616

I see this with nearly every release on win2003 doing Portable Installs. I've also seen it a couple times on Win8. Generally it is MMHelper.dll that is the culprit for me.

peke

2014-02-15 00:18

developer   ~0039617

The only case where this can happen if MMW is not closed correctly or taskbar player is recently used and still locked by windows.

I added http://www.mediamonkey.com/support/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=171

lowlander

2014-02-15 02:06

developer   ~0039618

Neither is the case for me. Also for most users with this problem MediaMonkey is the only program exhibiting this.

Ludek

2014-02-17 10:24

developer   ~0039629

Lowlander, your case sounds more like: 0000388

lowlander

2014-02-18 03:22

developer   ~0039644

Yes, I do believe it normally is MMHelper. However I believe that MediaMonkey 4.1 warns user that MediaMonkey is running (or does that only work from 4.1 to 4.1 upgrades?) so users shouldn't see this happening.

peke

2014-02-18 20:01

developer   ~0039655

Install check for MediaMonkey app not MMHelper.dll which is in most cases locked by Explorer.exe and thus user get error 5.

Maybe it could be good that before actual install happen an installation package tries to delete MMHelper.dll or even best do the the following:

1. Rename MMHelper.dll to MMHelper.Dll.off
1a. if MMHelper.Dll.off exists try to delete it and than rename existing MMHelper.Dll
2. Copy MMHelper.dll.off to MMHelper.dll
3. Try to Delete MMHelper.dll.off
4. proceed with installation

Also in Uninstall script we should add check for existence of "MMHelper.dll.off" and delete it so that there was no leftovers.

That should at least fix that issue.

peke

2014-02-24 22:50

developer   ~0039721

Can you triage?

peke

2014-08-26 19:47

developer   ~0040424

More reports rising the priority.

Ludek

2014-09-10 14:57

developer   ~0040496

Last edited: 2014-09-10 15:12

Because MMHelper.dll has not been changed for years than I suppose that it's rewrite can be just skipped in case the DLL already exists and there are any access problems, but my understanding was that the broadcast solution from 0000388:0019698 helped, but based on LL feedback it apparently does not.

Fixed in 1712.

peke

2014-09-23 13:37

developer   ~0040536

Verified 1714