Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

NAV 5 eating diskspace!

NAV 5 eating diskspace!

NAV 5 eating diskspace!

We are still using NAV v5.02 for NT server/workstation. The NAVNT directory is constantly growing and looking in that folder i find a lot of (>10000) files namned TM??????.exe and TM??????.dll. I guess the problem is related to the virus definitions updates, we're using NSC and the Central LiveUpdate. Anyone else experienced this? What are these files, where did they come from, can I delete them and how can I prevent them from re-occurring?

RE: NAV 5 eating diskspace!

I'm finally glad to find a document or somebody that has the same problem! Hope we can find a solution to this.

In my case, I have a LOT (500Mb) of TM??????.DLL and TM??????.HTM files that have accumulated over time (2 years) in the C:\Program Files\Navnt directory, and I'm not sure if I can erase them.

So far, I have only been able to find ONE document on Internet (in Symantec's site) relating to this problem. Although not exactly in the same context (I will try to relocate this document and email it to you), it said that NAV had to extract files from compressed files in order to scan them for viruses. They should normally be erased when done but might have been left there in the Navnt directory, creating all these TM*.* files.

If this is true, then we should be able to erase them without causing any problem. I will try to get a confirmation of this before doing so. Let me know if you find out anything new on this.



RE: NAV 5 eating diskspace!


You’re right, I also found that document regarding scanning inside compressed files some time ago.
I disabled scanning inside compressed files for a couple of days to verify that I didn’t get any more TM*.* files. Then I applied the patch, deleted all of the TM*.* files and enabled scanning compressed files again.
Everything seems to work fine and i haven’t seen any of those files since.

Here’s the link to the Symantec knowledge base article:

Hope this will help you!

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close