lozman

Thank you, Nay, this pointed me in the correct direction to solve the (silly) issue. Over the previous times I've built TC I've kept notes, snippets of code, commands, SQL, etc, that I used to make it easier in the future. Seems that the cmake command I had saved had an option specified (CSCRIPTS=1) that presumably was correct (or at least not problematic) at one point for one of the versions in the past (as I said interestingly when I tried rolling back to tag TDB 6.03 everything worked fine) but not for the current build. I noticed on checking the documentation carefully again that this is now a default option (defaulting to CSCRIPTS="static") and so I removed the incorrect parameter from my command line. Everything is now built and working as expected. Thank you, both, for replying. Regards, Lozman.

Ok, I deleted the build directory and recreated it. reran CMAKE, recompiled and installed. I still get the same issue. I dropped my entire databases and had them repopulate again but still the same. I can just blitz the entire installation folders, re-pull/clone the repo and start entirely fresh if you think that should make a difference, but I did that right at the start when I set the new server up, so I'm confused :/

I had a server crash and so am reinstalling my TrinityCore server on which I run both 3.3.5a and 6.x. I've done this a few times before successfully so while not an expert I'm not new to it either. I've got 3.3.5a working entirely again from scratch but though I can get 6.x setup, compiled and started ok my console commands do not work so I cannot among other things, create an account. I am using: Linux: Debian 8.3.0 TrinityCore: commit from April 25, 2016 Commit: 926c1ac9a064780241f0a22fd6cab45d10e16f89 MySQL: Ver 14.14 Distrib 5.5.47, for debian-linux-gnu (x86_64) using readline 6.3 GCC: (Debian 4.9.2-10) 4.9.2 CMake: version 3.0.2 OpenSSL: 1.0.1k 8 Jan 2015 I do not believe this to be a compilation or dependency issue, because the core starts up, the extractor work correctly, the DB installs without warnings or errors and as suggested below, if I checkout the 6.03 tag and compile that instead everything works fine. This is a brand new install (DBs entirely empty) with an automatic DB setup from downloaded TDB 6.04 (TDB_full_6.04_2016_04_11.7z) plus automatic updates on core startup to current required SQL/DB revisions. The core starts up but when I try to execute any CLI/console commands, the first time I issue one (anything at all; account, help, etc) I get the following spewed output. TC> account ---snip--- Table `command` contains a non-existing command 'deserter', skipped. Table `command` contains a non-existing command 'deserter', skipped. Table `command` contains a non-existing command 'list', skipped. Table `command` contains a non-existing command 'account', skipped. Table `command` contains a non-existing command 'arena', skipped. Table `command` contains a non-existing command 'reload', skipped. Table `command` contains a non-existing command 'account', skipped. Table `command` contains a non-existing command 'account', skipped. Table `command` contains a non-existing command 'ahbot', skipped. Table `command` contains a non-existing command 'ahbot', skipped. Table `command` contains a non-existing command 'guild', skipped. Table `command` contains a non-existing command 'instance', skipped. Table `command` contains a non-existing command 'instance', skipped. Table `command` contains a non-existing command 'go', skipped. Table `command` contains a non-existing command 'debug', skipped. Table `command` contains a non-existing command 'debug', skipped. ---snip--- After the first attempt at a command, any subsequent command just gives me; TC> account TC>There is no such command TC> I've also tried from the milestone/tag release for 6.04 (TDB 6.04 - 2016/04/11 - a1f59c9d8d9351bd4373e1e4355eee09369c589f) and a bunch of other commits between that one and the one above over the last several days always with the same issue. Then I tried a fresh install of the milestone/tag release for 6.03 (TDB 6.03 - 2015/11/08 - 271390753d63ea34e498e45f5e00a758f6997fbc). Same sort of installation procedure; fresh pull, compile, drop all the DBs and install them fresh from the 6.03 release of TDB with auto-population and updates on startup. This works fine, and my console commands work as expected. After I had that working I did a new pull to the origin master head revision and updated everything to TrinityCore rev. 926c1ac9a064 again (so back up to TDB 6.04 plus updates) and again the problems started and no commands work. I'm surprised I can't find anything on the forum or the google about this for searches such as "Table contains a non-existing command" so I have to expect this is something specific to me, but like I said, I've tried a bunch of times with the same effect. Any pointers or suggestions appreciated. Thanks, Lozman.