Posted by Tom Fulton on November 22, 2016 at 07:09:43:
In Reply to: Lost TMP posted by Grant Foraker on November 21, 2016 at 11:01:05:
Many end-users do not want to dedicate a PC to CometAnywhere hosting or running of Scheduled Tasks. If they do, an operator will shut down Comet or otherwise get in the way. So for the most part, a license is reserved for use on the server desktop for hosting CometAnywhere and for Scheduled Tasks ( upload data to our Order-Track website ). TMP folder has been driving me crazy, particularly when CometAnywhere users print pdf forms for our document-imaging. So I looked in to the issue. When RDP is established for use it defaults a setting called "PerSessionTemp" to On ( 1, True ). What this does is modify the Windows Temp folder to use a sub-folder keyed to the session number. This is what creates the C:\.....\Temp\2 or 3 or 4. This causes havoc with TMP when other things occur such as server reboot with automatice startup of Comet or a third party IT services provider connects up with RDP. Changing the "PerSessionTemp" to Off ( 0, False ) eliminates this issue. Everything Windows TEMP-oriented stays in C:\....\Temp. Comet is happy, Comet PDF is happy. It's a registry entry, rumor has it that it can be maintained in RDP configuration. I highly recommend changing this setting to eliminate TMP issues.
Post a Followup
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.