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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Windows Server 2003 vs. Windows Server 2008

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Windows Server 2003 vs. Windows Server 2008

    Application Server v10 build 4369_3712

    We just published our web application to a server running Windows Server 2008.

    The application was developed and tested on a server running Windows Server 2003.

    Now, under Server 2008, whenever we try to load the app in more than one browser tab (doesn't matter which browser) by opening a new tab and entering the app's URL, we get an error (below).

    1) So ... open browser, go to app URL, login, no problem.

    2) While the app is open in the old tab, open new tab, go to app URL ... error (below).

    2a) If we right-click on any internal link within the app and choose "Open in new tab", there is no problem ... the Alpha5 app link opens in a new tab.

    2b) If the URL entered includes the main app page that usually opens after logging in (mainpage.a5w), then the URL works fine. It's just when we use the base URL (i.e. http://www.example.com:8086/ or http://123.123.123.123:8086/) that the error happens.

    Here's the complete error:

    500 Internal Server Error
    "Script Error
    Error:Script: /index.a5w line:15
    ? ; ?x_login_screen.Output.Body.Login_Errors ;?;?crlf()
    Not found
    x_login_screen not found."

    (Binary placeholder icons display in the browser between the '?' and the ';' 2 icons each at char 2 and char 47.)

    The errors noted in the A5 log file are:

    [Tue Jul 26 13:26:50 2011] [Internal Server Error] (C:\A5Webroot\index.a5w) "Script Error: Error:Script: /index.a5w line:15 ? <td>; ?x_login_screen.Output.Body.Login_Errors ;?</td>;?crlf() Not found
    x_login_screen not found."
    [Tue Jul 26 13:26:50 2011] [Forbidden] Your security credentials do not allow access to this resource.<p>

    The default page within the app is the login page.

    This just started happening when we moved the app to the Windows Server 2008 machine. It does not happen when the app is running on the Windows Server 2003 machine. When it's under Server 2003, we can open as many new instances in new tabs by entering the URL as we want.

    It's definitely a validation error of some kind, probably because the script error prevents the file from being properly parsed. But I know so little about how Alpha5 validates logged in users, or where/why this might be happening under Server 2008 when it was not happening under Server 2003.

    Thoughts?
    Last edited by Stupidscript; 07-26-2011, 04:55 PM. Reason: added error from log
    Tags: None
    #2
    Re: Windows Server 2003 vs. Windows Server 2008

    After all of that, I figured it out. I'm leaving this for others who might experience it.

    It has nothing to do with the operating system.

    The problem is that the login page is set to be only accessible by people who are not already logged in. It's a permissions issue! Expanding our permissions to let even logged in users access the login page resolved the error.

    The error was masked because the bookmarks that were being used while the app was on Server 2003 included the subsequent page (http://www.example.com:8086/mainpage.a5w), so when the bookmark was clicked, if the user was not logged in, they redirected to the login page. If they were already logged in, they went right to the main page.

    After we moved the app, we updated all of the bookmarks ... but we removed the page reference, leaving only the base URL. In that scenario, when a logged in user went to the base URL in a new tab, their logged-in status was checked ... but the login widget could not be accessed until the permissions were expanded! So the credentials check failed, and the error occurred.

    So ... no problem. Either update your permissions so that logged in users can access the login mechanism, or simply maintain the redirect page in the bookmark URL. Either method will "resolve" this issue.

    Comment

    Previous template Next
    Working...
    X