temp folder conflict between multiple instances of WAS? " cannot find the file specified"

[RichCPT]

How do I make absolutely sure each instance of AA WAS (Ver 12.3 Build 2689) uses its own folder for temporary files and not mess with any other instances' temporary folders or files?

I have configured every path I can find in the .XML file for each of the four instances of AA to use separate folders like:

TraceLogFolder = "C:\ProgramData\Alpha Software\Alpha Anywhere Application Server Version 12\Installations\LogFilesInst3"

But, I can find no such setting for where the instances create their temporary files. All four instances are creating temporary folders under the following folder:

C:\Users\Administrator\AppData\Local\Temp\AlphaAnywhere

While it looks like each instance is properly creating its own unique folder, I do not trust that the instances are not somehow interfering with each other because as I look at the "A5XbasicErrorStackLog.txt" files I see they are all littered with errors like the following:

Thu Sep 29 05:10:48 2016
 The system cannot find the file specified.
 C:\Users\ADMINI~1\AppData\Local\Temp\AlphaAnywhere\p_2712\$$9B3C.DDD
Execution Stack:
0#1 evaluate_shared_private(           
0#37 OOhttpdServerClientMIME(ptemp,"AppServerMain")
0#2 A5WCallResult = evaluate_a5w_to_response(page_contents,Response,quote(" " + eval_settings.global.Request.ScriptName),eval_settings,EVALUATE_A5W_TIMEOUT,RequestBundle.RequestInfo.Filename.Path)
0#465 _htmlReportContent = a5w_report_html_saveAs(reportName, filter,order,phtml,global_variables(),printOptions,args,options)
Thu Sep 29 05:10:48 2016
 The system cannot find the file specified.
 C:\Users\ADMINI~1\AppData\Local\Temp\AlphaAnywhere\p_2712\$$9B3C.DDD
Execution Stack:
0#1 evaluate_shared_private(           
0#37 OOhttpdServerClientMIME(ptemp,"AppServerMain")
0#2 A5WCallResult = evaluate_a5w_to_response(page_contents,Response,quote(" " + eval_settings.global.Request.ScriptName),eval_settings,EVALUATE_A5W_TIMEOUT,RequestBundle.RequestInfo.Filename.Path)
0#465 _htmlReportContent = a5w_report_html_saveAs(reportName, filter,order,phtml,global_variables(),printOptions,args,options)
==========================================================

If the above error is not a conflict between multiple AA WAS instances then what is causing this?

[JerryBrightbill]

Re: temp folder conflict between multiple instances of WAS? " cannot find the file specified"

There were issues on some machines where programs such as cleanup programs would delete all temp folders as part of a cleanup process. If Alpha Anywhere was running at that time, the temp folders for the system were deleted. In older builds, the temp folder was created on startup, and assumed to always exist. If it was deleted for some reason, you will get the file not found message as the system can't write to the folder as it no longer exists

The newest pre-release builds include a method that checks if the folder was deleted and recreates it before saving anything to the folder. This change in not in the last release build

[RichCPT]

Re: temp folder conflict between multiple instances of WAS? " cannot find the file specified"

Looking deeper into the problem, I see the above error is being triggered when a user tries to save a report as PDF.
I have started a new thread here about it.

[Lenny Forziati]

Re: temp folder conflict between multiple instances of WAS? " cannot find the file specified"

Looking deeper into the problem, I see the above error is being triggered when a user tries to save a report as PDF.
I have started a new thread here about it.

Jerry's explanation fits this perfectly. Do you have a recent prerelease, or an official release?

[RichCPT]

Re: temp folder conflict between multiple instances of WAS? " cannot find the file specified"

Lenny,
No, I do not think this is related to what Jerry said, I don't see how my dev computer and the production computer could be suffering from same problem when things go wrong immediately when trying to save a report to PDF; I would think any cleanup tool would let a file sit for a lot longer before deleting it.

The production server (and one of many copies of AA on my development box) are version 12.3 Build 2689.

I just now tested under 12.4 Build 3670 on my development box and a separate testing server and everything works okay (in regards to Save to PDF).

At one time the production server had been updated to a newer build than 2689, but I had my hosting service provider put it back to build 2689 because there was something that did not work. It is quite possible that saving to PDF has been broken ever since the rollback. I do not know how the rollback was done. At this point I am going to assume the problem has to do with a later build installation of AA clobbering some shared code for printing to PDF which makes rolling back difficult unless a complete un-install is done. I do remember some mention of Amyuni print driver changes, sometime back.

I was planning on moving forward with Build 3670 for production which looks like it would solve the problem, but build 3670 has a problem saving web security group information from a checkbox control on a UX. Which means we cannot setup logins for new users! I will have to isolate it and send you guys a bug report on that one.