First configuration...crash during "adding filter section" (1 Viewer)

[hoborg]

That is a long time known MePo configuration crash problem. I reported it ~year ago with easy way how to reproduce it.
This is caused by error in registry when filter is not installed/uninstalled correctly.
If you have SAF installed, please send me your SAF logs.
To identify source of the problem - START - SAT - Tools - Filmerit.
Here click on "bug" icon - this will show only bugs. expand it fully and post screenshot here. I will then identify the source of the problem. And possibly add a registry fix in my SAF if such bug is detected.

 

[mm1352000]

That is a long time known MePo configuration crash problem. I reported it ~year ago with easy way how to reproduce it.

Ahhhh, sorry didn't know this - this was before I became "active" here.

This is caused by error in registry when filter is not installed/uninstalled correctly.

So the cause is that a filter doesn't exist in the file system in the location specified in the registry?

If you have SAF installed, please send me your SAF logs.
To identify source of the problem - START - SAT - Tools - Filmerit.
Here click on "bug" icon - this will show only bugs. expand it fully and post screenshot here. I will then identify the source of the problem. And possibly add a registry fix in my SAF if such bug is detected.

Personally I agree with tourettes - this is something that should be fixed in MP. If we can, please let's do that (before we apply a fix to jeremfg's system... otherwise I won't be able to fix the problem).

mm

 

[hoborg]

So the cause is that a filter doesn't exist in the file system in the location specified in the registry?

The problem i reported happend, when filter is registered but one part is missing.
Filters have two keys in registry, for example FFDshow on x86 - (04FE9017-F873-410E-871E-AB91661A4EF7):

HKEY_CLASSES_ROOT\CLSID\{04FE9017-F873-410E-871E-AB91661A4EF7}
and
HKEY_CLASSES_ROOT\CLSID\{083863F1-70DE-11d0-BD40-00A0C911CE86}\Instance\{04FE9017-F873-410E-871E-AB91661A4EF7}

If second one is missing, MePo config will crash while adding codecs.

EDIT:
It looks like it is some more complex.
If i delete second key from registry, it is still working.
Best way how to reproduce is add reg key i posted in bug report.

 

[mm1352000]

Thanks again hoborg
From jeremfg's system log I can see that a null reference exception was thrown so from my perspective I think it is just a matter of tracking down where this exception is thrown from and figuring out how to handle it properly. I'll see if I can reproduce the problem here but I want to be careful that I don't mess up my system.

 

[hoborg]

I'll see if I can reproduce the problem here but I want to be careful that I don't mess up my system.

Dont worry, there is nothing to mess. What Os do you have? If x86 you can just add my reg key to registry. To remove it, edit it and add "-" on begin, and apply it again. It will be removed.
On x64 reg file need to be modified - it is located in a different key.

 

[mm1352000]

I'm running XP. I'll give it a shot...

 

[hoborg]

Found what exactly is causing it.

To reproduce for FFDshow - open regedit and list "HKEY_CLASSES_ROOT\CLSID\{083863F1-70DE-11d0-BD40-00A0C911CE86}\Instance\{04FE9017-F873-410E-871E-AB91661A4EF7}" (x64 have different key)
Here is field "FriendlyName". Rename it to for example to "FriendlyName1". Now MePo config will crash now. Rename it back to "FriendlyName". It is working again

So it looks like MePo config will crash if "FriendlyName" key is missing.

 

[jeremfg]

No problem at all... I'm just glad you're here to help me out!

Well... It's probably my fault... but it's just getting worse and worse...

I can no longer run the Debug-Mode utility to retrieve log files... During the process, it crashes, about not finding the "MediaPortal.xml" file... I've checked, and it's true that I don't have it! Attached is a screenshot of this error I get.

What I noticed however, a mistake in the path... See the double back-slash in the path just before the file name!

I've also attached the Configuration log, wich might be the file you need the most!

Thanks again for your kind help

 

[jeremfg]

lol,.... a lot was said while I was trying the debuggin and log files...

If you have SAF installed, please send me your SAF logs.
To identify source of the problem - START - SAT - Tools - Filmerit.
Here click on "bug" icon - this will show only bugs. expand it fully and post screenshot here. I will then identify the source of the problem. And possibly add a registry fix in my SAF if such bug is detected.

I no longer have SAF installed, Do you want me to re-install it so I can try what you suggested?

Found what exactly is causing it.

To reproduce for FFDshow - open regedit and list "HKEY_CLASSES_ROOT\CLSID\{083863F1-70DE-11d0-BD40-00A0C911CE86}\Instance\{04FE9017-F873-410E-871E-AB91661A4EF7}" (x64 have different key)
Here is field "FriendlyName". Rename it to for example to "FriendlyName1". Now MePo config will crash now. Rename it back to "FriendlyName". It is working again

So it looks like MePo config will crash if "FriendlyName" key is missing.

Would love to check it's non-existence on my server. Any idea where it should be on x64?

Edit :
I've checked everything I have in "HKEY_CLASSES_ROOT\CLSID\{083863F1-70DE-11d0-BD40-00A0C911CE86}\Instance\" and they all have a FriendlyName key... However, one of them has a Friendly Name of "Null Renderer"...

I don't know much about filters and codecs, so I didn't know it this was normal.

 

[mm1352000]

Found what exactly is causing it.... So it looks like MePo config will crash if "FriendlyName" key is missing.

Confirmed.

I can no longer run the Debug-Mode utility to retrieve log files... During the process, it crashes, about not finding the "MediaPortal.xml" file... I've checked, and it's true that I don't have it!

This is a problem that *should* resolve itself if you were able to run MP config.

However, one of them has a Friendly Name of "Null Renderer"...

Not a problem - the problem on your system may be different. We'll see I guess.

Okay, so I was able to reproduce the problem easily using the FriendlyName trick. It took awhile to find all the places that needed to be patched since another problem seemed to popup every time I thought I had got them all. Try the attached Configuration.exe and see how you go...

mm