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

Http 503 error

  • Filter
  • Time
  • Show
Clear All
new posts

  • Http 503 error

    I am running IIS Application server and about every day I get an HTTP 503 error, my website and my mobile application is down. After I reboot the server both works. Anyone else experiencing this?

  • #2
    Re: Http 503 error

    It would only a guess what might it be. Can you turn on the logging? At least then when the server goes down you'll have an error to track down.
    Mike Brown - Contact Me
    Programmatic Technologies, LLC
    Independent Developer & Consultant


    • #3
      Re: Http 503 error

      Here is the Failed Trace Log.failedtracelog.txt


      • #4
        Re: Http 503 error

        Yeah ...that's over 6000 lines.
        Mike Brown - Contact Me
        Programmatic Technologies, LLC
        Independent Developer & Consultant


        • #5
          Re: Http 503 error

          Alpha is saying it is a Denial Of Service Attack happening. I dont think it is, with a Denial Of Service Attack rebooting the server shouldnt fix the issue. Is Alpha saying they dont know how to fix their software?


          • #6
            Re: Http 503 error

            I thing the access log would tell much more what is happening in your site. There you can see if your server in under hammering or somebody using exceptional urls against your server.


            • #7
              Re: Http 503 error

              Where is the access log located at?


              • #8
                Re: Http 503 error



                • #9
                  Re: Http 503 error

                  So where is the access log located at?


                  • #10
                    Re: Http 503 error

                    The access logs (and you may find some other useful logs) are probably on the IIS server under something like:
                    C:\inetpub\logs (probably in the same general location as wwwroot)

                    Under logs, the access log should be found under: \LogFiles\W3SVC1

                    If it were an DoS and the attack brought the server down, whoever it was, probably stopped sending requests. So when you restart the server, it may restart without a lot of traffic and with no problem.


                    • #11
                      Re: Http 503 error

                      I dont see huge amounts of traffic in the log files under \Logfiles\W3SVC1. I have decent size server on AWS so I would think it would handle a good amount of traffic before crashing. Any other thoughts?


                      • #12
                        Re: Http 503 error

                        Do you rely on any free-tier service in the global architecture? For instance, you have a good sized, not free-tier EC2 instance for IIS and the app but the app calls for resources from a free-tiers S3 bucket?
                        Or maybe the AWS Route 53 service that is configured "incorrectly". For instance, the "health check" configuration used to switch to another server is the server starts to slow down is a bit too sensitive, and perhaps, has no configuration to send the requests to a 2nd server. But I don't know if Route 53 would answer with a 503 or 504.

                        So many possible root causes that even if I had direct access to the IIS server to look, it could take a little while to set up additional tracing to find the source of the problem.
                        But I do love those types of problems. Obsessively tracking them down until I find it are always personally the best methods for me to learn.

                        EDIT: Thinking now that an unavailable or throttled down S3 bucket, would cause more of a timeout situation (504) rather than 503. I think the 503 would indicate an unavailable web server or a status sent by a gateway "in front" of IIS rather than anything slowed down or unavailable "behind" the IIS server. If you can't find and 503 entries in the IIS logs then it is very likely an element of the architecture in front of IIS that is responding with that HTTP code.
                        Last edited by jgrannis; 03-25-2019, 03:09 PM.


                        • #13
                          Re: Http 503 error

                          The failedtracelog.txt concerns one request to:



                          That specific request in the failed trace log triggers off a 401 status code and then the IIS configuration is set up to send back a HTTP code of 302 (but not before wasting a few resources looking for that .asp in the appserver's file cache). I don't believe that failedtracelog.txt contains any requests involving a 503 response from the server.
                          It is probably unrelated but you would probably want to look into solutions that prevent .asp, .php, etc., etc. from even getting handled by IIS or least by that particular hosted app on IIS.