Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

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

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

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

    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:

    Code:
    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?

  • #2
    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

    Comment


    • #3
      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.

      Comment


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

        Originally posted by RichCPT View Post
        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?

        Lenny Forziati
        Vice President, Internet Products and Technical Services
        Alpha Software Corporation

        Comment


        • #5
          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.
          Last edited by RichCPT; 09-29-2016, 07:39 PM. Reason: added "in regards to Save to PDF"

          Comment

          Working...
          X