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

Alpha Web Server Crashes Every Night at approximately 9:00pm!

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

    Alpha Web Server Crashes Every Night at approximately 9:00pm!

    I recently updated my Alpha Five App Server to the latest build (dated March 22, 2013).
    Ever since the update, my Alpha driven website crashes every night at around 9:00pm.. users receive "Host Unreachable Error in Browser".

    I run the AlwaysUp app so Alpha is running as a service. When I open AlwaysUp it shows that Alpha is still running!?
    So, I restart Alpha and it works again until the next evening when I again have to manually restart Alpha.

    In the Windows event log viewer for Application I find the following log recorded:
    The description for Event ID 0 from source Alpha Five Application Server cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

    If the event originated on another computer, the display information had to be saved with the event.

    The following information was included with the event:

    The server has shutdown


    Any ideas? Before applying the latest patch from Alpha I did not experience this issue.

    Cheers,
    Steve Hood

    #2
    Re: Alpha Web Server Crashes Every Night at approximately 9:00pm!

    Steve,

    I'm getting these errors as well now. But the build my client's running is still at 3036_4040 (it's a very large application and I haven't had the time to run tests in a development environment to make sure there wouldn't be any new bugs that would bring the entire thing down with the latest patches). My client started getting random 404 errors on grids and dialogs when they're using fields that are set up as either Edit-Combo or Auto-Suggest boxes:

    404 Error.png

    I've been trying to figure out where the problem is initiating for the last two days. Today, my client's IT guy sent me a summary of the Event Log from the Windows server that runs the application and apparently these EventID 0 errors have been happening since 4/8/2013!? No idea what triggered it. The only updates I made were to some individual components and their corresponding A5w pages which I'd copied over on 4/7, but the errors are popping up throughout the entire application, not just on the components that I updated. I'm going to attempt to re-install that existing patch (3036_4040) and republish the entire website tonight and see if it clears it up.

    The IT person did update their Trend Micro antivirus software on that Windows server, but I don't know if that is in any way connected yet.


    EDIT: I should clarify that my error's not entirely the same. I'm also using Always Up V8. But in my case the WAS is functioning and doesn't require a restart. The particular problem I'm running into is the 404 errors that popup within the web application and the EventID 0 below:

    EventID 0 Msg.JPG


    Regards,
    Melissa
    Last edited by Melissa Smith; 04-12-2013, 12:42 PM. Reason: Clarify Details
    Melissa Smith
    Triskelion Consulting, LLC

    Comment


      #3
      Re: Alpha Web Server Crashes Every Night at approximately 9:00pm!

      Hi Melissa, Steve,

      Make sure you turn on the AWS log files for the server, specially the Access Log, Error Log, Raw HTTP Traffic and the Xbasic Error Stack logs. For that you will have to turn off the AWS first, then once you start getting the errors you can look at the logs to try to figure out what may be wrong.

      Be aware that turning all these logging options, will slow down the server performance a bit.
      Edhy Rijo
      Progytech
      (Computer Consultants)
      The makers of CardTracking.Net
      www.progytech.com

      Comment


        #4
        Re: Alpha Web Server Crashes Every Night at approximately 9:00pm!

        Just wondering if you use the upload feature or SSL?
        Reed Brown
        ITOT Solutions, Inc.
        Alpha v12

        Comment


          #5
          Re: Alpha Web Server Crashes Every Night at approximately 9:00pm!

          Just a thought, since it happens at the same time every night, are you running a nightly scheduled backup or something at that time that might not be playing nice with a change in the new build?
          Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V

          Comment


            #6
            Re: Alpha Web Server Crashes Every Night at approximately 9:00pm!

            Or some late night partying at the office.

            Steve - since I am familiar with your application and V11, I can remote in to the server after you collect a day or so of logs. The most important are the "stack" and Raw logs.

            I know when I updated to latest I had to make sure I updated every TabbedUI (but I don't think you are using any). The error log should have some activity near the same time the Windows event log shows the error and you get shut down.

            Because you advertise and have lots of ads, you are also susceptible to being hit by search engines or other crawlers looking at your product list. Perhaps this is happening around that time. This might render your application "hung" even though the server is still running. Lately I have seen thousands of hacking hits on my servers and had to deal with them through blocking.
            Steve Wood
            See my profile on IADN

            Comment

            Working...
            X