- March 26, 2007
- 3,715
- 180
- Home Country
-
Germany
When using a thin network client where the SQL lite database files are located on a remote server the mediaportal.log and error.log log files are riddled with all sorts of SQL errors.
This happens when...
client suspends htpc.
client resumes htpc.
The db connections needs to be properly disposed/disconnected when located on remote servers, since the network drive(s) will disconnect once the user suspends.
when resuming the HTPC the database connection is now invalid.
Ideally the suspend-resume sequence should be:
user requests standby/hiber. (hits power butto on remote control)
all database connections are properly disposed.
MP signals to OS that its ready to suspend.
windows suspends.
user now resumes the HTPC.
all database connections are properly reopened.
Singleseat users should not be affected by this.
No dispose/reopen sequence needed there.
http://mantis.team-mediaportal.com/view.php?id=2569
Open the issue in Mantis...
This happens when...
client suspends htpc.
client resumes htpc.
The db connections needs to be properly disposed/disconnected when located on remote servers, since the network drive(s) will disconnect once the user suspends.
when resuming the HTPC the database connection is now invalid.
Ideally the suspend-resume sequence should be:
user requests standby/hiber. (hits power butto on remote control)
all database connections are properly disposed.
MP signals to OS that its ready to suspend.
windows suspends.
user now resumes the HTPC.
all database connections are properly reopened.
Singleseat users should not be affected by this.
No dispose/reopen sequence needed there.
http://mantis.team-mediaportal.com/view.php?id=2569
Open the issue in Mantis...