TCC Startup Error

Nov 12, 2009
7
0
Just installed Take Command 12.11. Getting an error on startup 0xc0000005.

Reviewed for any apps/services that may be problematic. The only item I would maybe suspect is Acronis True Image 2012. Anti Virus disable was no help.

Tried MS Process Exp. The only odd handle I could see was Acronis.

Sys Info:

WIN7 ULT X64 i7 970 12GB RAM

Any ideas? Thanks in advance!
 

rconn

Administrator
Staff member
May 14, 2008
12,556
167
> Just installed Take Command 12.11. Getting an error on startup 0xc0000005.

If the crash is in TCMD, you'll have a TCMD.GPF file which has a stack trace
and register details. (It's usually in the same location as your TCMD.INI
file, which varies depending on the version of Windows and your startup
options.)

Is this an upgrade or new installation? Are you running any plugins?
 
Nov 12, 2009
7
0
If the crash is in TCMD, you'll have a TCMD.GPF file which has a stack trace
and register details. (It's usually in the same location as your TCMD.INI
file, which varies depending on the version of Windows and your startup
options.)

Is this an upgrade or new installation? Are you running any plugins?

Thanks for the fast response.

The ini dir is "C:\Users\username\AppData\Local\JPSoft". No crash file only the ini file.

Fresh install via upgrade license and no plugins. The program won't start.

Thanks.
 

rconn

Administrator
Staff member
May 14, 2008
12,556
167
> The ini dir is "C:\Users\username\AppData\Local\JPSoft". No crash file
only

> the ini file.
>
> Fresh install via upgrade license and no plugins. The program won't start.

Then it's unlikely that the crash is actually in TCMD.EXE. Are you trying
to start from a shortcut, Explorer, or the command line? Can you run
TCC.EXE and IDE.EXE?

Are you starting with a fresh TCMD.INI or importing one from a previous
version?
 
Nov 12, 2009
7
0
only



Then it's unlikely that the crash is actually in TCMD.EXE. Are you trying
to start from a shortcut, Explorer, or the command line? Can you run
TCC.EXE and IDE.EXE?

Are you starting with a fresh TCMD.INI or importing one from a previous
version?

OK. Tried starting via desktop, start menu shortcuts created during install. Failed. Same result if I attempt to start via double clicking the EXEs tcc or tcmd. However, IDE.exe is just fine. It starts.

The INI is the freshly installed one.

This is a fresh "upgrade" install. Is it looking for a previous version that is not there?

Otherwise would it be possible for you to suggest what I need to look for say via Process Explorer?

Thanks for all the help.
 
Nov 12, 2009
7
0
only



Then it's unlikely that the crash is actually in TCMD.EXE. Are you trying
to start from a shortcut, Explorer, or the command line? Can you run
TCC.EXE and IDE.EXE?

Are you starting with a fresh TCMD.INI or importing one from a previous
version?

Additional note: I just noticed that the INI file installed during setup is a zero byte file. It's empty.

Is this normal?
 
Nov 12, 2009
7
0
only



Then it's unlikely that the crash is actually in TCMD.EXE. Are you trying
to start from a shortcut, Explorer, or the command line? Can you run
TCC.EXE and IDE.EXE?

Are you starting with a fresh TCMD.INI or importing one from a previous
version?

Issue resolved. Thanks for the help.

The system had a Theme installed that replaced/MOD certain key windows files. Removed the theme and Take Command runs fine.
 

rconn

Administrator
Staff member
May 14, 2008
12,556
167
> Additional note: I just noticed that the INI file installed during setup
is a

> zero byte file. It's empty.
>
> Is this normal?

TCMD doesn't install an .INI file (this is deliberate, to avoid overwriting
an existing one when upgrading). TCMD will create one when it needs to save
any configuration changes.
 

rconn

Administrator
Staff member
May 14, 2008
12,556
167
Issue resolved. Thanks for the help.

The system had a Theme installed that replaced/MOD certain key windows files. Removed the theme and Take Command runs fine.

Glad you got it working.

I'd like to know the theme & developer, so I can contact them about fixing it, and add it to our list of problem apps. (Screen managers are particularly troublesome, though they're thankfully becoming less common.)
 

Similar threads