Bugzilla – Bug 7272
Win 2K: SC 7.0 over 6.3: SC does not start at all.
Last modified: 2009-09-08 09:25:54 UTC
System Info: Gateway, P4, 2.0 GHz, 1.25 GB of RAM, Win 2K SP4 ENU SC Version: Nightly of 2008-02-21. Steps to Reproduce: 1. Install this nightly onto Win 2K. 2. Try to start it from SlimTray or bouble click the desktop icon. 3. Notice SlimTray keeps flashing and flashing. After 10 minutes, SC still would not start. Is this build the same as the 2008-02-19 nightly? It worked.
Actually, 6.3 was installed and uninstalled on this PC before 7.0 was installed on it. Here is the event error log: The description for Event ID ( 0 ) in Source ( Application ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: Database error: Can't create table '.\slimserver\metainformation.frm' (errno: 121) at /<D:\PROGRA~1\SQUEEZ~1\server\SQUEEZ~1.EXE>DBIx/Migration.pm line 115. . Here is the error message from SqueezeCenter.exe: [08-02-21 16:28:24.1093] Slim::Schema::init (151) Warning: Creating new database - empty database or database from 6.3.x found [08-02-21 16:28:24.1799] Slim::Utils::Misc::msg (1241) Warning: [16:28:24.1795] Database error: Can't create table '.\slimserver\metainformation.frm' (errno: 121) at /<D:\Program Files\SqueezeCenter\server\squeezecenter.exe>DBIx/Migration.pm line 115. [08-02-21 16:28:24.1812] Slim::Schema::forceCommit (1363) Warning: Trying to commit transactions before DB is initialized!
This is related to 7237. Except that happened on a MAc. This is on Win 2K. Looks like Michael Herger has put in some changes for that bug today. This bug may be fixed also. Will check again tomorrow.
Andy: is this the same bug?
Probably, but this log doesn't have a mention of SQLite. Let's see if Wallace can reproduce with today's build.
Working on it right now.
Good news. Initial tests found this to be fixed. Please set this bug to fixed. I am going to verify the fix several more times, and perform regression tests.
Oops, on second and third attempts, it did not work. Still the same error. [08-02-22 07:59:05.7812] Slim::Schema::init (151) Warning: Creating new database - empty database or database from 6.3.x found [08-02-22 07:59:05.8626] Slim::Utils::Misc::msg (1241) Warning: [07:59:05.8623] Database error: Can't create table '.\slimserver\metainformation.frm' (errno: 121) at /<D:\Program Files\SqueezeCenter\server\squeezecenter.exe>DBIx/Migration.pm line 115. [08-02-22 07:59:05.8638] Slim::Schema::forceCommit (1363) Warning: Trying to commit transactions before DB is initialized! However, I may have found a work around. Work Around Steps: 1. Uninstall 6.3 first. Delete the SlimServer folder manually. 2. Install SC 7.0. 3. Uninstall SC 7.0. 5. Reboot. 6. Delete the SC folder manually. (For some reason, this folder is not removed completely by uninstaller.) 7. Install SC 7.0 again. 8. Now it works. These steps need to be verified more several more times.
Verified that these steps of work around do work.
Here are the log info of database.mysql, database.sql, server, and server.timers when starting of SC fails: [08-02-22 10:44:06.0474] Slim::Utils::MySQLHelper::createConfig (182) createConfig() Creating config from file: [D:\Program Files\SqueezeCenter\server\MySQL\my.tt] -> [D:\Documents and Settings\All Users\Application Data\SqueezeCenter\Cache\my.cnf]. [08-02-22 10:44:06.2986] Slim::Utils::MySQLHelper::init (108) Creating system tables.. [08-02-22 10:44:06.3007] Slim::Utils::MySQLHelper::startServer (247) About to start MySQL as a process with command: [D:\PROGRA~1\SQUEEZ~1\server\Bin\MSWIN3~1\mysqld.exe --defaults-file=D:\DOCUME~1\ALLUSE~1\APPLIC~1\SQUEEZ~1\Cache\my.cnf] [08-02-22 10:44:09.0167] Slim::Utils::MySQLHelper::stopServer (344) Running shutdown. [08-02-22 10:44:13.1100] Slim::Utils::MySQLHelper::startServer (247) About to start MySQL as a service with command: [D:\PROGRA~1\SQUEEZ~1\server\Bin\MSWIN3~1\mysqld.exe --defaults-file=D:\DOCUME~1\ALLUSE~1\APPLIC~1\SQUEEZ~1\Cache\my.cnf] [08-02-22 10:44:14.2349] Slim::Schema::init (151) Warning: Creating new database - empty database or database from 6.3.x found [08-02-22 10:44:24.4693] main::checkDataSource (870) Warning: Schema updated or tracks in the database, initiating scan.
Check the Services tree for Windows. SqueezeMySQL started automatically.
Wallace to work with chris to isolate this
Ok, tried this myself on a pretty virgin W2K: - installed, run, scanned SS 6.3.1 - downloaded and installed SC7: during installation I get an error message; installer can't uninstall previous SS6.3 - SC7 installs fine, starts without any problem - reboot: SC7 starts fine As SS6.3 didn't get uninstalled automatically there's still SlimTry running along with SqueezeTray. If SS6.3 was set to start automatically "At Logon", this might lead to problems running SC7, as one or the other would start faster and use ports needed by both. Manually uninstalling SS6.3 should fix this issue. Conclusion: - works for me. Caveats: - you might need to uninstall SS6.3 manually
Here are the log message from --logging dstart: [08-02-25 07:32:11.4225] Slim::Schema::init (151) Warning: Creating new database - empty database or database from 6.3.x found [08-02-25 07:32:11.4873] Slim::Utils::Misc::msg (1241) Warning: [07:32:11.4864] Database error: Can't create table '.\slimserver\metainformation.frm' (errno: 121) at /<D:\Program Files\SqueezeCenter\server\squeezecenter.exe>DBIx/Migration.pm line 115. [08-02-25 07:32:11.4889] Slim::Schema::forceCommit (1363) Warning: Trying to commit transactions before DB is initialized! Hi, Michael, In my steps, SlimServer 6.3 was manually unisntalled and left over folder deleted before SC7.0 was installed. SlimServer 6.3 was set to start automatically at logon. On Win 2K, SC7.0 is not set to start at logon by default(Bug# 7242). In my system, uninstalling 6.3 manually first does bnot take care of this problem.
This is Chris: I'm looking at this on Wallace's system right now, and I do see the crash he's talking about. The log fragments he posted are the only things that appear when running from the commandline. No ERROR is shown there. The only error visible is in the event log, as he posted in the first half of comment #1. It doesn't seem like it's quite enough information to figure out what remnant of 6.3 is still hanging on to cause this problem. A much simpler workaround is to delete the "\Documents and Settings\All Users\Application Data\Squeezecenter" directory, then restart Squeezecenter. If more users see this problem please let us know.
Chris: did you want to keep this open to 7.0? I thought we were going to push this off since it appears to be unique to Wallace's system.
The work around steps found by Chris are very simple to use. With that, the risk of changing code in 7.0 is not worth taking. Marking as "VERIFIED".
Closing.
As expected, this bug was found on 7.0.1, build 17830 also. Should this be fixed.
But can you reproduce it on a _really_ new Windows 2000 install, too? Or only on your testmachine? I haven't seen any "real-world" report of this issue, nor can I reproduce it.
The work around is reasonable enough that this can be looked at in the future.