TC Application Error

obirek

New member
Anybody knows how to fix this error:

oo73.jpg
 
I had this for a long time in TRS2006, and got rid of it somehow ... Now it is back, when I save a route, after the route saves, it comes up with this error, but other than that it causes no problems, with running and saving a route.

It may me because of some, or several, faulty content, or something like that ?
 
Check that your Visual C++ libraries are up-to-date. I did a quick check on Bing and this seems to be where these errors are pointing.

John
 
You would have to check via Control Panel > Add/Remove Programs or Programs and Features. The usual version that is required is the Visual C++ 2005 redistributable.

Shane
 
I still am unsure what "Up to Date" means ... Do you need the 2005 vrsion as well, even if you have 2008, and 2010 ?
 
Last edited:
Check that your Visual C++ libraries are up-to-date. I did a quick check on Bing and this seems to be where these errors are pointing.

John
Thanks for this tip. I am not totally convinced that these error are caused by outdated C++ libraries.

The problem seems to be caused by referencing a memory location which cannot be accessed. If this location cannot be accessed there are two possible reasons for this:

1/ The memory has been allocated, then released, but the reference hasn't been set to the null pointer. So, the program still thinks that it can read from this location and boom! It throws an exception.

2/ The memory has not been allocated correctly in the first place, i.e. the reference returned by the function allocating memory was not read or stored correctly, or it was swapped with another reference, or so like.

Both cases are clear programming error. I don't think that any library update is going to fix it.

The first error occurs on my laptop running Windows XP 32-bit. This is my production installation of TC. I have many erroneous assets, zombie routes, etc there. The second error occurs on a PC running Windows 8. This is a clean installation, error free, used for Driver only. The separation of Surveyor and Driver between two physical machines is my solution to much grief documented on this forum. Still, it is far from perfect.
 
Thanks for this tip. I am not totally convinced that these error are caused by outdated C++ libraries.

The problem seems to be caused by referencing a memory location which cannot be accessed. If this location cannot be accessed there are two possible reasons for this:

1/ The memory has been allocated, then released, but the reference hasn't been set to the null pointer. So, the program still thinks that it can read from this location and boom! It throws an exception.

2/ The memory has not been allocated correctly in the first place, i.e. the reference returned by the function allocating memory was not read or stored correctly, or it was swapped with another reference, or so like.

Both cases are clear programming error. I don't think that any library update is going to fix it.

The first error occurs on my laptop running Windows XP 32-bit. This is my production installation of TC. I have many erroneous assets, zombie routes, etc there. The second error occurs on a PC running Windows 8. This is a clean installation, error free, used for Driver only. The separation of Surveyor and Driver between two physical machines is my solution to much grief documented on this forum. Still, it is far from perfect.

I wouldn't doubt there are program errors. Try updating the VC++ libraries, especially on the Windows 8 machine. That will also resolve the side-by-side errors you'll see in the Event Viewer so this won't hurt. I went by the error message and a look-up on Microsoft's MSDN website.

John
 
Microsoft has patches for the currently installed versions. They are called service packs. I installed both the x86 and x64 versions. This took care of the side-by-side errors we've seen in the Event Viewer.

John
 
I wouldn't doubt there are program errors. Try updating the VC++ libraries, especially on the Windows 8 machine. That will also resolve the side-by-side errors you'll see in the Event Viewer so this won't hurt. I went by the error message and a look-up on Microsoft's MSDN website.

John
But C++ is a compiled language!

That means that the libraries must have been linked at the time of compilation of the program. This was done already before burning TC executable on a CD. Updating libraries would only have effect if I built the whole program on my machine from the source code. But nobody has the source code.
 
Not necessarily. Whilst the code is pre-compiled, it still references third-party library files (especially with .NET Framework applications) in order to handle certain things that it's own code cannot handle.

Shane
 
Back
Top