TVServer fails to locate database (1 Viewer)

[dale77]

MediaPortal Version: 1.0.2
MediaPortal Skin: bluewide
Windows Version: Vista Premium 32bit SP2
CPU Type: AMD 4850e 2.5Ghz X2
HDD: WD10EARS
Memory: 2Gb DDR800
Motherboard: GA-MA78GPM-UD2H F3
Video Card: Sapphire 4670 1Gb
Video Card Driver: Catalyst 9.11
Sound Card: Realtek ALC889a
Sound Card AC3:
Sound Card Driver: 6.0.1.5780
1. TV Card: Hauppage HVR-2200
1. TV Card Type: Dual DVB-T, analog hybrid
1. TV Card Driver: 7.6.1.27086
2. TV Card:
2. TV Card Type:
2. TV Card Driver:
3. TV Card:
3. TV Card Type:
3. TV Card Driver:
4. TV Card:
4. TV Card Type:
4. TV Card Driver:
MPEG2 Video Codec: MPC MPEG-2 Gabest
MPEG2 Audio Codec: AC3 Filter
h.264 Video Codec: PCM H.264/AVC Decoder
Satelite/CableTV Provider:
HTPC Case: Antec Fusion 430 v2
Cooling:
Power Supply: Antec 430W
Remote: Logitech Harmony 525
TV: Samsung LA40B530 1080p
TV - HTPC Connection: HDMI

Hello, since moving my windows installation to a new disk, occasionally Mediaportal TVServer will fail to start up. The event shows it is unable to login to the database. When this happens, I can then go into windows Services and manually start the TVServer service, and all is well.

It looks like TVServer is not waiting for the SQLServer database service to come up properly or something. Any suggestions as to how to avoid this? It is a bit hard to tell the kids "Go into control panel, System Maintenance, Administrative Tools, Open Services, Locate the TVService service and click start, then you can watch Batman".

 

[aidbish]

See the following thread about delaying the startup of the tv service
may help
https://forum.team-mediaportal.com/mediaportal-1-talk-45/urgent-serious-problem-tvserver-not-starting-boot-76701/

 

[dale77]

Thanks, this How to delay loading of specific services may help also.

 

[dale77]

Problem was caused by upgrading to a new advanced format drive, copying over my system image to the new drive.

This causes a partition alignment problem and associated performance problems with the disk.

Solution was to run the WD Align utility on the misaligned drive. Haven't seen any errors since.