home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
Installation, configuration support
New motherboard, now tuner configuration does not work
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="fe31nz" data-source="post: 1036657" data-attributes="member: 78528"><p>I have been doing some debugging to try to track down this problem. I got the zip of the Mediaportal 1.5.0 source code and set it up in Vistual Studio, then set a breakpoint at the place where the exception is happening and stepped from there. It turns out that the exception is being triggered when the value for the "dvbt10Country" setting is read from the database. Its value is "NOTFOUND", which is of course not an integer, so when Int32.Parse is called with that value, the exception results. So it seems that somehow my database had bad values for the "dvbt%" settings. Here is the result of the SQL query "select * from setting where tag like 'dvbt%' order by tag;" on my database:</p><p></p><p><span style="font-family: 'Courier New'">+-----------+------------------------+----------+</span></p><p><span style="font-family: 'Courier New'">| idSetting | tag | value |</span></p><p><span style="font-family: 'Courier New'">+-----------+------------------------+----------+</span></p><p><span style="font-family: 'Courier New'">| 535 | dvbt10Country | NOTFOUND |</span></p><p><span style="font-family: 'Courier New'">| 536 | dvbt10creategroups | NOTFOUND |</span></p><p><span style="font-family: 'Courier New'">| 568 | dvbt11Country | NOTFOUND |</span></p><p><span style="font-family: 'Courier New'">| 569 | dvbt11creategroups | NOTFOUND |</span></p><p><span style="font-family: 'Courier New'">| 601 | dvbt12Country | NOTFOUND |</span></p><p><span style="font-family: 'Courier New'">| 602 | dvbt12creategroups | NOTFOUND |</span></p><p><span style="font-family: 'Courier New'">| 38 | dvbt2Bandwidth | 8 |</span></p><p><span style="font-family: 'Courier New'">| 35 | dvbt2Country | 23 |</span></p><p><span style="font-family: 'Courier New'">| 39 | dvbt2creategroups | false |</span></p><p><span style="font-family: 'Courier New'">| 40 | dvbt2createsignalgroup | false |</span></p><p><span style="font-family: 'Courier New'">| 37 | dvbt2Freq | 306000 |</span></p><p><span style="font-family: 'Courier New'">| 36 | dvbt2Region | 11 |</span></p><p><span style="font-family: 'Courier New'">| 44 | dvbt3Bandwidth | 8 |</span></p><p><span style="font-family: 'Courier New'">| 41 | dvbt3Country | 23 |</span></p><p><span style="font-family: 'Courier New'">| 45 | dvbt3creategroups | false |</span></p><p><span style="font-family: 'Courier New'">| 46 | dvbt3createsignalgroup | false |</span></p><p><span style="font-family: 'Courier New'">| 43 | dvbt3Freq | 306000 |</span></p><p><span style="font-family: 'Courier New'">| 42 | dvbt3Region | 11 |</span></p><p><span style="font-family: 'Courier New'">| 385 | dvbt4Country | NOTFOUND |</span></p><p><span style="font-family: 'Courier New'">| 386 | dvbt4creategroups | NOTFOUND |</span></p><p><span style="font-family: 'Courier New'">| 418 | dvbt5Country | NOTFOUND |</span></p><p><span style="font-family: 'Courier New'">| 419 | dvbt5creategroups | NOTFOUND |</span></p><p><span style="font-family: 'Courier New'">| 352 | dvbt6Country | NOTFOUND |</span></p><p><span style="font-family: 'Courier New'">| 353 | dvbt6creategroups | NOTFOUND |</span></p><p><span style="font-family: 'Courier New'">| 227 | dvbt7Bandwidth | 8 |</span></p><p><span style="font-family: 'Courier New'">| 224 | dvbt7Country | 23 |</span></p><p><span style="font-family: 'Courier New'">| 228 | dvbt7creategroups | false |</span></p><p><span style="font-family: 'Courier New'">| 229 | dvbt7createsignalgroup | false |</span></p><p><span style="font-family: 'Courier New'">| 226 | dvbt7Freq | 306000 |</span></p><p><span style="font-family: 'Courier New'">| 225 | dvbt7Region | 11 |</span></p><p><span style="font-family: 'Courier New'">| 634 | dvbt8Country | NOTFOUND |</span></p><p><span style="font-family: 'Courier New'">| 635 | dvbt8creategroups | NOTFOUND |</span></p><p><span style="font-family: 'Courier New'">| 667 | dvbt9Country | NOTFOUND |</span></p><p><span style="font-family: 'Courier New'">| 668 | dvbt9creategroups | NOTFOUND |</span></p><p><span style="font-family: 'Courier New'">+-----------+------------------------+----------+</span></p><p><span style="font-family: 'Courier New'">34 rows in set (0.00 sec)</span></p><p></p><p>To prevent the exception from happening, I have now manually changed all the NOTFOUND values to 23 (for dvbt<n>Country) or false (for dvbt<n>creategroups). After that, SetupTV is now able to run normally and I have been able to scan for channels and get the tuners working again.</p><p></p><p>I wonder what other problems might be lurking in my database also, if those values were wrong? What exactly are those dvbt% settings used for? What are the correct vlues for those settings? What will the bad data or my manual changes do to things - will they cause any other problems? And how did the bad data happen?</p></blockquote><p></p>
[QUOTE="fe31nz, post: 1036657, member: 78528"] I have been doing some debugging to try to track down this problem. I got the zip of the Mediaportal 1.5.0 source code and set it up in Vistual Studio, then set a breakpoint at the place where the exception is happening and stepped from there. It turns out that the exception is being triggered when the value for the "dvbt10Country" setting is read from the database. Its value is "NOTFOUND", which is of course not an integer, so when Int32.Parse is called with that value, the exception results. So it seems that somehow my database had bad values for the "dvbt%" settings. Here is the result of the SQL query "select * from setting where tag like 'dvbt%' order by tag;" on my database: [FONT=Courier New]+-----------+------------------------+----------+ | idSetting | tag | value | +-----------+------------------------+----------+ | 535 | dvbt10Country | NOTFOUND | | 536 | dvbt10creategroups | NOTFOUND | | 568 | dvbt11Country | NOTFOUND | | 569 | dvbt11creategroups | NOTFOUND | | 601 | dvbt12Country | NOTFOUND | | 602 | dvbt12creategroups | NOTFOUND | | 38 | dvbt2Bandwidth | 8 | | 35 | dvbt2Country | 23 | | 39 | dvbt2creategroups | false | | 40 | dvbt2createsignalgroup | false | | 37 | dvbt2Freq | 306000 | | 36 | dvbt2Region | 11 | | 44 | dvbt3Bandwidth | 8 | | 41 | dvbt3Country | 23 | | 45 | dvbt3creategroups | false | | 46 | dvbt3createsignalgroup | false | | 43 | dvbt3Freq | 306000 | | 42 | dvbt3Region | 11 | | 385 | dvbt4Country | NOTFOUND | | 386 | dvbt4creategroups | NOTFOUND | | 418 | dvbt5Country | NOTFOUND | | 419 | dvbt5creategroups | NOTFOUND | | 352 | dvbt6Country | NOTFOUND | | 353 | dvbt6creategroups | NOTFOUND | | 227 | dvbt7Bandwidth | 8 | | 224 | dvbt7Country | 23 | | 228 | dvbt7creategroups | false | | 229 | dvbt7createsignalgroup | false | | 226 | dvbt7Freq | 306000 | | 225 | dvbt7Region | 11 | | 634 | dvbt8Country | NOTFOUND | | 635 | dvbt8creategroups | NOTFOUND | | 667 | dvbt9Country | NOTFOUND | | 668 | dvbt9creategroups | NOTFOUND | +-----------+------------------------+----------+ 34 rows in set (0.00 sec)[/FONT] To prevent the exception from happening, I have now manually changed all the NOTFOUND values to 23 (for dvbt<n>Country) or false (for dvbt<n>creategroups). After that, SetupTV is now able to run normally and I have been able to scan for channels and get the tuners working again. I wonder what other problems might be lurking in my database also, if those values were wrong? What exactly are those dvbt% settings used for? What are the correct vlues for those settings? What will the bad data or my manual changes do to things - will they cause any other problems? And how did the bad data happen? [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Installation, configuration support
New motherboard, now tuner configuration does not work
Contact us
RSS
Top
Bottom