[u][b]Skins were the problem.[/b][/u]
In my case, the error cropped up when I was installing skins and rearraging the different components around on screen. I accidentally moved some components off-screen and couldn't get them back. I quit mediamonkey (should have end processed it) in hopes of resetting the layout but it started freezing.
So I deleted the [b][u]Skins [/u][/b]folder in [b][i]C:\Program files\Mediamonkey[/i][/b], and voilà, after deleting the folder I could start mediamonkey, though it started with system themes and I guess I would have to download and install them again (actually I didn't as I liked the system theme but you can).

Hope this helps, let me know if it does.

[url=http://www.ventismedia.com/mantis/view.php?id=5181]Mantis 5181[/url] has been set as Can't / Won't fix.

One possible cause is a corrupted Quick Time install on your system. Removing and re-installing Quick Time will repair a corrupted install.

[quote="grillmeister7"]I do not have an iPhone or Apple mobile device; my MP3 player is a Sansa e260.[/quote]
Thanks.
As a workaround, until a full fix is available, you can:
- Exit MM
- Rename the ...Program Files\MediaMonkey\Plugins\d_iPhone.dll to e.g. d_iPhone.dll.off.
- Restart MM

This workaround will have to be re-applied after each install

I do not have an iPhone or Apple mobile device; my MP3 player is a Sansa e260.

[url=http://www.ventismedia.com/mantis/view.php?id=5181]Mantis 5181[/url]

00000214	47.92975235	[5152] 2524 DB open SQL: SELECT * FROM Devices WHERE PluginName='d_iPhone.dll' 	
00000215	47.93055725	[5152] 2524 DB lock finished, took 2033843.	
00000216	48.00640106	[5152] iPhone: Loading library: C:\Program Files\Common Files\Apple\Mobile Device Support\bin\iTunesMobileDevice.dll	
00000217	93.56959534	[5748] d:\7.0\build\071021\cross\util\rierror.cpp(462): [177c] Error: Unable to find specified item (SETUP\language).	
00000218	93.56959534	[5748]  (536870989)	
00000219	93.56997681	[5748] d:\7.0\build\071021\cross\util\rierror.cpp(462): [177c] Error: Unable to find specified item (PROVIDERINFO\server).	
00000220	93.56997681	[5748]  (536870989)	
00000221	93.57061005	[5748] d:\7.0\build\071021\cross\util\rierror.cpp(462): [177c] Error: Unable to find specified item (PROVIDERINFO\serverbaseurl).	
00000222	93.57061005	[5748]  (536870989)	
00000223	93.69863892	[5748] d:\7.0\build\071021\cross\util\rierror.cpp(462): [177c] Error: Unable to find specified item (PROVIDERINFO\msisourcedir).	
00000224	93.69863892	[5748]  (536870989)	
00000225	93.69970703	[5748] d:\7.0\build\071021\cross\util\rierror.cpp(462): [177c] Error: Unable to find specified item (PROVIDERINFO\productcode).	
00000226	93.69970703	[5748]  (536870989)	
00000227	93.71292877	[5748] d:\7.0\build\071021\cross\util\rierror.cpp(462): [177c] Error: Unable to find specified item (PROVIDERINFO\msisourcedir).	
00000228	93.71292877	[5748]  (536870989)	
00000229	93.71405029	[5748] d:\7.0\build\071021\cross\util\rierror.cpp(462): [177c] Error: Unable to find specified item (PROVIDERINFO\productcode).	
00000230	93.71405029	[5748]  (536870989)	

Got the debug log from 1209. Everything is fine until the end.
[code]00000214 47.92975235 [5152] 2524 DB open SQL: SELECT * FROM Devices WHERE PluginName='d_iPhone.dll'
00000215 47.93055725 [5152] 2524 DB lock finished, took 2033843.
00000216 48.00640106 [5152] iPhone: Loading library: C:\Program Files\Common Files\Apple\Mobile Device Support\bin\iTunesMobileDevice.dll
00000217 93.56959534 [5748] d:\7.0\build\071021\cross\util\rierror.cpp(462): [177c] Error: Unable to find specified item (SETUP\language).
00000218 93.56959534 [5748] (536870989)
00000219 93.56997681 [5748] d:\7.0\build\071021\cross\util\rierror.cpp(462): [177c] Error: Unable to find specified item (PROVIDERINFO\server).
00000220 93.56997681 [5748] (536870989)
00000221 93.57061005 [5748] d:\7.0\build\071021\cross\util\rierror.cpp(462): [177c] Error: Unable to find specified item (PROVIDERINFO\serverbaseurl).
00000222 93.57061005 [5748] (536870989)
00000223 93.69863892 [5748] d:\7.0\build\071021\cross\util\rierror.cpp(462): [177c] Error: Unable to find specified item (PROVIDERINFO\msisourcedir).
00000224 93.69863892 [5748] (536870989)
00000225 93.69970703 [5748] d:\7.0\build\071021\cross\util\rierror.cpp(462): [177c] Error: Unable to find specified item (PROVIDERINFO\productcode).
00000226 93.69970703 [5748] (536870989)
00000227 93.71292877 [5748] d:\7.0\build\071021\cross\util\rierror.cpp(462): [177c] Error: Unable to find specified item (PROVIDERINFO\msisourcedir).
00000228 93.71292877 [5748] (536870989)
00000229 93.71405029 [5748] d:\7.0\build\071021\cross\util\rierror.cpp(462): [177c] Error: Unable to find specified item (PROVIDERINFO\productcode).
00000230 93.71405029 [5748] (536870989)
[/code]

Do you have an iphone or other Apple mobile device?

Start DebugView before trying to start MM. If MM starts OK, then just close DebugView. If it fails to start then DebugView will be either idle or reporting a lot of new messages (in a loop of some sort). In either case use DebugView -> File -> Save As to create a debug log. At that point you can close DebugView.

If the debug log is large you can email a zipped copy to (owyn dot mm at gmail dot com).

[quote] Send us a debug log to help us pinpoint the problem (you need to be using a debug build to do so e.g. MediaMonkey_xxxx_debug.exe):

a) For crashes and error conditions MediaMonkey will automatically prompt you to send a debug log / error report. If this doesn't occur, you can generate the debug log by clicking <right-CTRL><left-SHIFT><TAB>.

b) For functional problems (i.e. no crash or error) or if you can't generate a debug log as described above, you can manually generate a debug log as described below:
- Install a debug version of MediaMonkey (if necessary) on top of the current beta. Debug versions of MediaMonkey are usually posted within each Alpha/Beta/RC announcement. Make certain that the debug version# matches the beta version#. Note that Alpha builds are always debug builds (i.e. no special download is required.
- Download the DbgView application from: http://www.microsoft.com/technet/sysinternals/utilities/debugview.mspx
- Execute DbgView.
- If you know that the bug triggers a system freeze, configure DbgView to save the log to a file automatically via File > Log to File...
- Execute MediaMonkey_Debug.exe and try to reproduce the bug with a small set of Tracks.
- You'll see logs being generated in DbgView. Save the log messages from DbgView to a file if necessary.[/quote]
http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=341

You can include most debug logs in a forum post if you enclose the log in BBCode "Code" tags.

I moved on to 1207 and this happened again. How do I generate/find the debug log to send?

Can you get a debug log of the startup.
Thanks.

I shut down 1202 normally then started it up a few minutes only to see a slew of 'application seems to be frozen' popup messages. I filled out some of them and hit send.

This was happening to me with 1203 and 1204 so I reverted to 1202 which seemed to be better for me.