"Unable to Replace Image" [#9255]

[vsnmx]

Windows Edition: Windows Vista Home Premium
Processor: Intel Core 2 Quad CPU Q6600 @ 2.40 GHz 2.40 GHz
Memory (RAM): 4.00GB
System Type: 32-bit Operating System

MediaMonkey v4.0.3 Gold

I've been having this problem for a while now, and I was hoping with this new release the problem would be fixed. Not so. I've been using the debug version of MediaMonkey and each time this happens I send an error report which seems to go unnoticed by MediaMonkey.

Here is the problem:

Every time I try to open Media Monkey I get the error message "MediaMonkey has encountered a problem." The problem listed on the error report is "Unable to Replace Image."

As I mentioned, I then send in the error report, and always provide my email address hoping MM will contact me about the problem which has never happened.

After sending in the error report I get the message "The message was sent successfully" and then I click "OK."

Then a window comes up that says "Error during player initialization." I click "OK" and then the MediaMonkey program comes up and looks like this:

Then I have to open the task manager in order to close the program by terminating the process.

I've uninstalled and reinstalled the program several times yet nothing seems to help.

This is extremely frustrating and almost renders the program useless.

Please help!

[Lowlander]

Do you have the last.fm plugin installed?

[vsnmx]

Do you have the last.fm plugin installed?

No. Also, I have tried deleting and/or renaming any iphone and ipod dlls as I have read that those cause problems but it has made no difference in the problem I am having.

[BKKKPewsey]

Have you tried changing the skin?
You may be trying to use an incompatible/corrupted skin.

[vsnmx]

Have you tried changing the skin?
You may be trying to use an incompatible/corrupted skin.

Yes, I have tried that but it has made no difference.

[BKKKPewsey]

Try installing the latest version http://www.mediamonkey.com/sw/MediaMonk ... 3.1476.exe
in portable mode and see if that works.
That will give new separate install and will not try to read anything from your existing application folders.

[vsnmx]

Try installing the latest version http://www.mediamonkey.com/sw/MediaMonk ... 3.1476.exe
in portable mode and see if that works.
That will give new separate install and will not try to read anything from your existing application folders.

Thanks, I will try that, although to be honest, I'm not sure what portable mode is - do I have to uninstall the existing application first or do I just install it in portable mode alongside the existing program?

I hope that makes sense (I'm not very tech savvy)!

[Lowlander]

No, just select Portable Install during the installation and install into a separate folder not in Program Files.

[vsnmx]

No, just select Portable Install during the installation and install into a separate folder not in Program Files.

Okay, thank you!

[pderwael]

Hi all,

Just to let you know, I have exactly the same issue ("Error during player initialization") on 4.0.3.1476
I tried the portable installation, but it did not solve my issue...

I guess we will have to wait until a bug fix update is released...

[PetrCBR]

Can you PM me your mediamonkey.ini and your current skin ?

[vsnmx]

Can you PM me your mediamonkey.ini and your current skin ?

Done!

[vsnmx]

* I updated my Norton antivirus software to the latest version.

* I uninstalled and reinstalled iTunes and Quicktime.

* I turned ".off" iPhone/iPod dlls

* I am using the default MM skin.

* I removed MM from CCleaner.

* I uninstalled Spotify and Free Download Manager.

Despite this, the problem still exists. I am still getting the same error message when trying to open MM. Not sure what else to do.

[progcode]

I have exactly the same problem.

[vsnmx]

I have exactly the same problem.

I'm glad it's not just me!

I would suggest installing the debug version If you haven't already ( http://www.mediamonkey.com/sw/MediaMonkey_Debug.exe ) which will display an error message each time you encounter the problem and you can send in the error message to MM.

Also, submit a support ticket so they know what's going on. Although they haven't been able to figure out what's causing this yet, they have been very helpful!