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

Solved: Different behavior on App server from Dev: UX and Grid

  • Filter
  • Time
  • Show
Clear All
new posts

  • #31
    Re: Different behavior on App server from Dev: UX and Grid

    I would delete all project files on the server, including the directory of the project. Then, republish as new. I remember a scenario similar to yours a while back and I had to start totally fresh. There is no problem with using Windows Server 2012, from what I can recall. Your error msg saying the URL can't be found, seems to indicate that a fully qualified path is required, and you aren't supplying that.


    • #32
      Re: Different behavior on App server from Dev: UX and Grid

      Thanks, Stephen,

      That was actually one of my first guesses. I opened up the security to "always" or "login" for everything.

      Capture.PNGCapture 1.PNGCapture 2.PNGCapture 3.PNG


      • #33
        Re: Different behavior on App server from Dev: UX and Grid


        I was thinking that too. So I wiped it out and republished. No change.



        • #34
          Re: Different behavior on App server from Dev: UX and Grid

          I would try DELETING all files, including the app folder, from the server. Then have Alpha Anywhere recreate it from scratch. I know this may not be possible in your situation, but if it is I would try it and see if it helps. I've had to do this before and it resolved the issue.


          • #35
            Re: Different behavior on App server from Dev: UX and Grid


            Good thought. I have been working on this for a while, it could have some accumulated detritus in there.

            So I did delete it, entirely, including the folder. Republished from scratch.

            No change.



            • #36
              Re: Different behavior on App server from Dev: UX and Grid

              What turns out to be happening is that for some reason, the App server is returning HTML wrapped code on an ajax callback.

              I looked at server settings and can't find a setting for this. Does anyone know where that is? Or is it something in the profile setting from when I publish?

              Last edited by Vincent; 08-14-2019, 08:41 AM. Reason: For clarity.


              • #37
                Re: Different behavior on App server from Dev: UX and Grid

                SOLVED: It was running on a server managed by Sophos server management software.

                The filters for form hardening and code injection were causing the issue.

                They were wrapping html around the Ajax callback. Once they were changed, the problem resolved.


                • #38
                  Re: Solved: Different behavior on App server from Dev: UX and Grid

                  Makes sense. Once you were made aware of the server returns being wrapped in HTML... and then combine that with the fact that you're working with your own server... the trouble shooting path becomes clear.


                  • #39
                    Re: Solved: Different behavior on App server from Dev: UX and Grid

                    I would remove the forward slash from the following line:
                    requestUSER = "window.location = '/req_sent.a5w';"

                    So it reads,
                    requestUSER = "window.location = 'req_sent.a5w';"