Problem description / Issue description

What can I do if I start the service of the SmartConsole, or even trying to start the SC as an application and it hangs up and doesn't start properly? 

Symptoms

The SmartConsole seems to start but then hangs up on the first screen without any error. 

Step 1

Stop the SmartConsole Service (or close it if you started it as an application).

After doing this, you MUST verify with the TaskManager (checking the option to "Show processes for all users") that there are no SmartConsole.exe nor SmartConsoleService.exe processes still running. If they are still up kill them. 

Tip: You may start a DOS command line and execute the command: 

  • Taskkill /F /IM SmartConsole.exe
  • Taskkill /F /IM SmartConsoleService.exe

Step 2

Explore the SmartConsole installation directory, and delete the T4Trace.log file. After this, just start the SmartConsole service or the application. If it starts it's fixed and the problem was that for some reason there were zombies processes hung up. If the problem persists, keep going to Step 3

Step 3

Into the SmartConsole installation directory search for the files:

  • SC_DB_DATA.db
  • SC_DB_DATA.db.ind

And rename, delete or move them to another directory.

WARNING: This will make you lose all your changes made to the SmartConsole from the last time the SC stored the changes into its own database. 

At this point, start the SmartConsole service or the application. If it starts, it's fixed and the problem was that for some reason the SmartConsole wasn't able to store all the configuration into its own configuration database therefore it started to store all the information into a temporary file called SC_DB_DATA.db. Unfortunately, in version 7.5.1 (and older) of the SmartConsole this was bug. If the problem persists, keep going to Step 4.

Step 4

Look for the file T$Trace.log into the SmartConsole installation directory and open it with Notepad and try to find out if there's any permission problem, Database connection problem, etc. Probably the best thing to do is to zip the t4trace.log file and report it. 


Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: October 18, 2018