N-Track Won't Launch

I attempted to Start my N-Track 5 today, and the application will not launch. I reinstalled the latest version from the web site and still no go. I haven’t altered anything on my PC since I last used N-Track about 2 weeks ago.

Has this happened to anyone else? If so, how did you remedy the problem?

I’m in a pinch to finish a recording for a friend.

Thanks - TJ

Hi TJ,

What actually happens when you try to start n-Track? Nothing? An error? A crash? A splash screen? A lock-up?

It’s probably worth deleting (renaming?) the n-track config files. I don’t have the software on this PC so can’t remember exactly where they are. Perhaps someone else can help…

n-track2.cfg
n-TrackConfiguration2.xml

Hi phoo :cool:

This happened to me too BTW, that’s why I know. Deleting these files did nothing.
Had to do the old uninstall/reinstall dance for the first time ever.

Yeah, that’s the ones, thanks teryeah.

The files are here btw:

C:\Documents and Settings<em>your_user_name_here\Application Data
-Track Studio5

Rename and re-start n-track. It will re-create the files.

Thanks, all.

I was able to correct the problem by uninstalling N-Track from the Control Panel rather than the from the N-Track install prompt.

For future reference, when I clicked on the icon, I would get a quick hourglass icon, then nothing.

Regards,

TJ

Quote: (tommyj55 @ Apr. 03 2008, 7:54 PM)

Thanks, all.

I was able to correct the problem by uninstalling N-Track from the Control Panel rather than the from the N-Track install prompt.

For future reference, when I clicked on the icon, I would get a quick hourglass icon, then nothing.

Regards,

TJ

Glad you got it sorted and thanks for reporting back.

Happy tracking!

From my experience when I start a program with this characteristic it means it is already running. Firefox was like this. You need to go to the task manager and see if it is listed under processes and if so select it and hit end process.

Mine’s a little different than that. I’m running vista, and N v.5. About 2 days ago, it quit working.

I fire N up and it reads, “N-Track Studio has stopped working Windows is checking for a solution to the problem”. Then it goes away. I’ve tried deleting the two files mentioned above, and uninstalling N, and reinstalling it. Same thing happens.

I go into Event Viewer, and the error reads, "Faulting application ntrack.exe, version 5.1.1.2313, time stamp 0x4724e006, faulting module SYSFER.DLL_unloaded, version 0.0.0.0, time stamp 0x46e22b3d, exception code 0xc0000005, fault offset 0x6f025682, process id 0xa8c, application start time 0x01c898607022fa50."

Oh, and one other thing. In the right hand column, it tells me that DEP has attempted to save my day, by not allowing the $%^&* application to run. Funny thing, though – I’ve excluded N from DEP and set DEP to only do Windows Services. Incredibly frustrating.

Any thoughts?

I believe SYSFER.DLL is a Symantec dll. You wouldn’t happen to be running Symantec Endpoint Protection would you? I’ve heard of problems in that DLL after a Symantec upgrade.

Phoo:

Thanks for the reply. Yes, I’m running Endpoint Protection. Are you suggesting that N-track and Symantec are now mutually exclusive, or is there some type of workaround?

Similar thing here
My issue was black ice (resonia destop protection) it did blok for n-track start up
Had to disable the black ice

Quote:

Are you suggesting that N-track and Symantec are now mutually exclusive, or is there some type of workaround?


No, I'm suggesting that there's at least an issue with an upgrade to Symantec. Search the internet. There's quite a few posts about it and a few different fixes and workarounds. I searched using the dll that crashed and found a lot of things that looked similar. n-Tracks may simply be the victim.

n-Tracks has a feature to check for updates. Disable that so it doesn't ping the internet when it runs. That might not be related, but it couldn't hurt to get it out of the way in your case.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SysPlant]
“Start”=dword:00000004
Reboot after editing the registry.

This was the fix for me. Just in case anyone else might need it.

Thanks for all the help!