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



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

Web Security on remote server not working

  • Filter
  • Time
  • Show
Clear All
new posts

  • Web Security on remote server not working

    I have an application that works fine on a local AA WAS server but when I publish to another system and include the security tables (I'm using DBF tables) I get to the login screen and when trying to login I get "Incorrect Login Information." I've tried republishing the security tables several times using both the security components option as well as selecting publish security data in the Publish profile. It appears to be some problem with the encryption of the security data. If I turn off the security framework on the remote server I can access my tabbed ui with no problem. My security component is a stand-alone component on my index.a5w page which redirects to my tabbed ui after a successful login.

    Brad Weaver, President
    ComputerAid International
    Ottawa ON Canada
    Versailles KY USA

  • #2
    Re: Web Security on remote server not working

    Okay, here's what I ran into. Even though the security framework is using DBF tables I am running my SQL Server on different system than I installed the WAS server. It turns out that I had to disable the Private Profile of the advanced firewall on the SQL Server host in order to allow the connection from the Alpha WAS host on port 1433. Once I cleared that up the security system in Alpha also began working properly and I could once again log in to my application. Weird since I didn't think the security framework would care at all about my SQL connections.

    Before I hear the screams of security issues in disabling the Private Profile of the Advanced Firewall, I added both inbound and outbound rules allowing port 1433 to no avail. I also added a program exception for SQLSERVER.EXE to allow all connections, again to no avail. This might be an issue with Windows 8 as I've never had a problem with Windows 7 or any Windows Server 2008 or earlier that I've done this on. The SQL Server is currently hosted on my Windows 8 system while the Application Server for Alpha is on a Windows 7 machine (this is a development test environment).
    Brad Weaver, President
    ComputerAid International
    Ottawa ON Canada
    Versailles KY USA


    • #3
      Re: Web Security on remote server not working

      Further resolution. While opening port 1433 on TCP is all that is required in the firewall to allow Alpha connections, if you want to use SQL Server Management Studio from a remote machine you also need to make sure that the SQL Browser service is running and that you open UDP port 1434 inbound. Everything is now working as it should with the firewall fully enabled.
      Brad Weaver, President
      ComputerAid International
      Ottawa ON Canada
      Versailles KY USA


      • #4
        Re: Web Security on remote server not working


        You may be on to this already but I would only open up port 1433 for known ip addresses, ie the ones you are accessing from. I have just started administering a mail server on a VPS for our company and over half of the packets dropped by the firewall are attempts to reach 1433.


        PS Grew up in Belleville, Ont and my wife is born and grew up in TO (Bloor West Village)
        Tim Kiebert
        Eagle Creek Citrus
        A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.


        • #5
          Re: Web Security on remote server not working

          Thanks Tim and good point. I do close down 1433 to all but known IPs for exactly the same reason you mentioned. There's an amazing amount of sniffing for open port 1433's out there. In this case I was already running the SQL Server behind a NAT router and not port forwarding from the public interface so I knew it wouldn't matter if I opened the port completely on the Windows 8 host but I'm glad you added your suggestion for others who might follow this thread in the future.

          I'm in west Etobicoke very close to Bloor West Village (the Ukrainian festival is coming up there in three weeks.)
          Brad Weaver, President
          ComputerAid International
          Ottawa ON Canada
          Versailles KY USA