MP TV/SQL Error (1 Viewer)

[clarkey2r]

Hi All

Basically on friday my media portal stopped working, it starts but crashes about 5 mins in with an SQL - time out error (not attemptig to watch TV).
I have tried to open up the MP TV configuration but get the 2 attacthed errors, I think the problem looks like an SQL issue but I dont really know where to start with it, I have tried to manually restart the SQL service in SQL Config Manager but I get another "service did not respond in a timley fashion" error!

Any ideas?


TV-Server Version: 1.0
MediaPortal Version: 1.0
MediaPortal Skin: Monchrome2.6
Windows Version: XP SP3
CPU Type: AMD
HDD: Not sure
Memory: 1.5GB
Motherboard: MSI K8N
Video Card: x1300 Series Radeon
1. TV Card: WinTV Nova HD s2
1. TV Card Type: PCI
1. TV Card Driver: Latest

 

[Marvman]

Hi Clarkey,

did you installed somthing new, like Firewall etc...?

If not, try to access your MS SQL Server with the SQL Administrator (or something like that), and check your DB for errors.

 

[clarkey2r]

Hi Clarkey,

did you installed somthing new, like Firewall etc...?

If not, try to access your MS SQL Server with the SQL Administrator (or something like that), and check your DB for errors.

Hello

I haven't installed anything new!
I'm not sure how to access SQL as Administrator, my logon account has SQL admin rights??

 

[Marvman]

Hi Clarkey,

i meant with SQL Administrator the MSSQL Admin Tool, i don't know the exact name of it, cause i use MySQL.

Similiar tools can you find at MS SQL Tools - MSSQL Admin Tools - SQL Server Tools - MSDE Tools by SQL Maestro Group

But i don't know if you can repair your DB with this tools, with MySQL you can

Maybe you can attach logs?

The easy way would be, to delete your DB and re-install MP, BUT its not a guaranty that MP works after this.

 

[clarkey2r]

I will try that when I get home!

I have a feeling its more to do with the server rather than the database?

Can anyone else offer any help?

 

[fromaron]

I will try that when I get home!

I have a feeling its more to do with the server rather than the database?

Can anyone else offer any help?

Seeing you have Win XP SP3 machine you can try to check what is installed from the Add/Remove Programs tool. If you see you have MSXML6 SP2 installed, try to get a Windows Installation Cleanup utility (because I am afraid remove program won't help you) and uninstall the MSXML6 SP2 pack.
Some MS updates are driving me crazy ....

 

[clarkey2r]

I will try that when I get home!

I have a feeling its more to do with the server rather than the database?

Can anyone else offer any help?

Seeing you have Win XP SP3 machine you can try to check what is installed from the Add/Remove Programs tool. If you see you have MSXML6 SP2 installed, try to get a Windows Installation Cleanup utility (because I am afraid remove program won't help you) and uninstall the MSXML6 SP2 pack.
Some MS updates are driving me crazy ....

You sound like you have had this issue yourself?
Would you recommend using the M$ cleanup util?

 

[fromaron]

You sound like you have had this issue yourself?
Would you recommend using the M$ cleanup util?

I had a bit different issue when I couldn't install SQL at all after getting SP3 and the MXML6. SP3 has a bug with MSXML6 pack, overprotecting it, resulting in the database failures as I understand.
People reported issues uninstalling the MSXML6 pack this is why I recomend using MS Installation Cleanup utility.
Check if you have the MSXML first and if yes, remove it - it didn't do any harm to me.

 

[clarkey2r]

Just checked now and its not installed, thanks tho!

Any more ideas?

 

[fromaron]

Just checked now and its not installed, thanks tho!

Any more ideas?

In the case it is just SQL issue and you need SQL people to help you. I had once issue with the SQL database and luckily had a friend who is Database Admin .
I can't remember now what was the issue and what did we do to fix it, but remember we had to analise ogs created by SQL and then tried to manually update the database records etc. At the end we found something in the configuration which was not 100% right.