Config wizard stops responding in Thunderblade Release
When trying to open the config wizard in Thunderblade I get the message it has stopped.
Description: Stopped working Problem signature: Problem Event Name: CLR20r3 Problem Signature 01: configurator.exe Problem Signature 02: 2.2.2.0 Problem Signature 03: 4b82dd50 Problem Signature 04: WindowsBase Problem Signature 05: 3.0.0.0 Problem Signature 06: 4a174f32 Problem Signature 07: 368 Problem Signature 08: 19 Problem Signature 09: System.ComponentModel.Win32 OS Version: 6.1.7600.2.0.0.768.3 Locale ID: 2057
It worked for me the 1st time, enough for me to setup my media folders and add a few podcasts. I think the problem is with setting permissions, although I allowed MB to set permissions initially it appears not to have worked. I cannot allow a second time as the box is greyed out. see pic
I am seeing this to on my Vista 32 bit install.
Working ok on my Win 7 64bit install.
Error log gives this –
Description:
Stopped working
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: configurator.exe
Problem Signature 02: 2.2.2.0
Problem Signature 03: 4b82dd50
Problem Signature 04: PresentationCore
Problem Signature 05: 3.0.0.0
Problem Signature 06: 48fef619
Problem Signature 07: 4e2b
Problem Signature 08: 6
Problem Signature 09: System.IO.FileFormatException
OS Version: 6.0.6000.2.0.0.256.1
Locale ID: 2057
Will quickly test this, in case its a vista regression
Unfortunately I am seeing the same thing on my Vista 32 setup.
Will eagerly await Sam’s findings…
Unlike Groove I am running W7 32 bit.
Yes it does work but it is asking each time to set folder permissions.
Sam, for me – I cannot start Configurator at all.
If I rename ‘Plugins’ folder to ‘Plugins1’ – the Configurator simply crashes again with the above errors and it recreates the ‘Plugins’ folder.
MB appears to be running fine, however I can’t install any plugins because Configurator will not run.
edit: i have .NET SP1 installed
I was having that issue, it actually would crash my configurator. I fixed it by changing the permissions of my c:\programdata\mediabrowser folder to full read/write access. I am on win 7 32bit by the way.
Tried all sorts last night, updating .dotnet’s , patching , reinstalling , everything i could think of, to no avail….but ill try the permissions thing that Bemaserra posted shortly and post back.
After a new install it looks like it is going to fire up as the splash screen stays on for ages before failing out. Subsequent retries it crashes almost immediately.
On the verge of re-building the htcp with win7 today , but ill see if i can get to the bottom of it beforehand if it helps to find the cause of the problem
Changing permissions and renaming the plugins folder didnt work for me.
After renaming the plugins folder and launching the configurator a new plugins directory is created then it crashes out.
strange
For me the configurator won’t open. Windows says it has stopped working as soon as I open it and then it shuts down.
Have you guys added different sources (urls) for plugin sources?
Hi,
I got the same crash on vista 32.
Description: Stopped working
Problem signature: Problem Event Name: CLR20r3 Problem Signature 01: configurator.exe Problem Signature 02: 2.2.2.0 Problem Signature 03: 4b82dd50 Problem Signature 04: PresentationCore Problem Signature 05: 3.0.0.0 Problem Signature 06: 4858c628 Problem Signature 07: 4e2b Problem Signature 08: 6 Problem Signature 09: System.IO.FileFormatException OS Version: 6.0.6001.2.1.0.256.1 Locale ID: 1037
I got the vannila and chocolate source xml and the MB source url in the plugin section.
Thanks, Tempo
I think this may clear up with the permissions setting fix I just put in…
Im also having this issue. Anyone get it working in vista 32 yet?
There is a new configurator now:
I am still having the same issues with the new configurator
Vista 32 still having the same problem.
I would start anew topic with say “New configurator still not working in Vista 32”
This basically doesn’t apply any longer. I believe all configurator issues have been resolved with the Pegasus release.
Im marking it as fixed, since it appears to be the first report …
This was duplicated quite a few times
