• State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 63 subscribers
  • Views 1609 views
  • Users 0 members are here
Options
Related

Lots of "rogue" files accumulating under Passolo's Documents and Settings Temp area

Mark Owens

Hi

The C: drive on my Windows 2003 server running Passolo 2011 keeps filling up.  This server runs Passolo several times a day, creating a pseudo translation for 2 projects.

I've traced the problem to this folder:

C:\Documents and Settings\<USER>\Local Settings\Temp\PASSOLO

It contained 40GB of data!!!

I deleted everything in this folder yesterday, but since then it's starting to accumulate folders/files again.

A typical example of what's being left is:

- a file called "RSC9185.tmp"

- 2 x folders for each Passolo session, called: "psl386d" and "psl4436". There's approximately 36MB in each folder. The majority of the disk space is taken up with a bunch of files with names like "035e213a.bin" immediately under each of these folder names.

I can understand this Temp folder being used whilst Passolo is being run but can someone explain why these files are being left on the system?

Best Regards
Mark
Rate translation
×
Suggest better translation
×
Parents
  • 0
    Hi again,
    It seems the problem was with the script that was driving Passolo.

    Deep in the log files were entries indicating Passolo was crashing with an unhandled exception "External component has thrown an exception". By crashing, it was leaving all those temporary files on disk.

    It looks like a network latency problem when talking to the Licence Server that I run.

    The script was running separate consecutive Passolo sessions, each one needing to talk to the Licence Server - which looks like it couldn't keep up.

    I've fixed the problem by using the "/script" batch option which only needs to communicate with the Licence Server on startup even though it's running several Passolo commands. All round, a much better solution, and it's taking significantly less time to run the same set of Passolo commands.

    Best Regards
    Mark
Reply
  • 0
    Hi again,
    It seems the problem was with the script that was driving Passolo.

    Deep in the log files were entries indicating Passolo was crashing with an unhandled exception "External component has thrown an exception". By crashing, it was leaving all those temporary files on disk.

    It looks like a network latency problem when talking to the Licence Server that I run.

    The script was running separate consecutive Passolo sessions, each one needing to talk to the Licence Server - which looks like it couldn't keep up.

    I've fixed the problem by using the "/script" batch option which only needs to communicate with the Licence Server on startup even though it's running several Passolo commands. All round, a much better solution, and it's taking significantly less time to run the same set of Passolo commands.

    Best Regards
    Mark
Children