Configurator crashes (1 Viewer)

[mts1]

MediaPortal Version: 1.1.0
MediaPortal Skin:
Windows Version: WIn 2003 x64
CPU Type: AMD
HDD: Seagate 3x750GB RAID-5
Memory: 2x2GB
Motherboard: ASUS M3N78 PRO
Video Card: Nvidia 8300
Video Card Driver: Always latest
Sound Card: Raltek
Sound Card AC3:
Sound Card Driver:
MPEG2 Video Codec:
MPEG2 Audio Codec:
h.264 Video Codec:
Satelite/CableTV Provider:
HTPC Case:
Cooling:
Power Supply:
Remote: PS3 BD
TV: LG 50PCD3
TV - HTPC Connection: HDMI

Well. I've installed latest RC1 and didn't work for me.
Actually the MP works fine. What doesn't work is the Configuratior. It starts, waits for a few seconds and quietly closes.
Yes, I know my configuration breaks two rules - it's 2003 and it's x64, but previous version worked without any problems. So, I hope some could help me and reveal the actual reason for the crash.
Maybe some manual changes in my system will make it work again.

Thanks

 

[Paglioni]

I have problems too
i was running not client and tvserver 1.0.2 (and many older version before that) without a glitch, on my 2003 R2 x86 server.
now i've unistalled those and installed the 1.1.0 rc1, and is a no go.
MEdiaportal can't start without a configuration, so it launch the configurator
Configurator.exe asks me if i want normal or expert mode, and after i choose (both with same result), the configurator.exe disapper from my task manager. I'll attach log from the configurator.

TvServer seems fine, the service is running, but launching it's configurator does nothing for a while, then a window appear with an error.

 

[mts1]

If this problem is not some side effect of another bug, then most likely it won't be fixed.
So we are stuck with the old version.

 

[tourettes]

Well, without logs I'm quite sure that it wont get fixed It could be some corrupted registry entry.

 

[mts1]

The logs are for the MP main program only. You can't produce them for configuration program.

 

[tourettes]

The logs are for the MP main program only. You can't produce them for configuration program.

Are you sure? Configuration.log

 

[mts1]

The logs usually don't start by themselves. You have to activate this feature one way or another. I didn't find this trigger.

 

[rekenaar]

The logs DO start by themselves.
It is the logscollector that does not start by itself, but no need for that here.

Like tourettes said, just get the configuration.log and attach here.

 

[mts1]

Finally I've got some time to install RC1 and to try it again.
The log is attached.

 

[chemelli]

2010-04-13 11:05:43.515625 [Debug][Config Main(1)]: Startup: Argument did request Wizard mode - /wizard

Simone