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

Reports Stopped Working

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

    Reports Stopped Working

    All of my reports stopped working this morning (about 70). When a report is started, it just sits on the "working" message with the little circle spinning
    There are no errors in the A5 error logs and there's nothing in the MS Event viewer that could be related to this.
    I have 7 websites/ 7 WAS running and all of them have this problem

    Build V11 3381_4096
    Windows Server 2008 r8
    SQL Server 2008

    The only thing that has happened is we did a server reboot around 2am

    Does anyone have any idea what might cause this, and more importantly how to fix it ?????????????????

    #2
    Re: Reports Stopped Working

    Dave,

    I can only state the obvious which you have probably already tried:

    1. reboot the WAS
    2. reboot the server
    Peter
    AlphaBase Solutions, LLC

    [email protected]
    https://www.alphabasesolutions.com


    Comment


      #3
      Re: Reports Stopped Working

      Hi Peter
      Due to heavy traffic, I didn't want to reboot until later tonight, but my hand was forced at 1:00pm EDT when all of my websites/WAS stopped working. No error messages in the A5 logs and nothing related in the server event logs. I rebooted the server and everything returned to normal.

      The initial problem with not being able to run any reports must have been a warning shot over the bow, and then the ship sank a few hours later.

      I cannot even begin to describe how angry my customers are. To top it off, I'm very concerned something like this can happen and I have no idea what caused it and there's nothing in the logs. I don't even have information to send to Alpha Support

      Comment


        #4
        Re: Reports Stopped Working

        Very likely server overload or the memory got maxed and Alpha could not recover. That's not just a thought, I have seen it happen at several sites. The A5 Report Server runs on a separate CPU if available, but if you are running a bunch of reports at once, or even one that takes significant cycles, then it can lock up everything else. You could also have hacking attempts. If you have seven websites on the same server, then you have seven attack points. Hackers can be trying to hack your RDP or Windows login. Easy to spot in the logs if true.

        You have to observe your CPU/Memory during the day, or set a performance monitor to track. See if it fluctuates close to the max.

        I suggest you use AlwaysUp to automatically reboot every early morning when server not generally used.
        Steve Wood
        See my profile on IADN

        Comment


          #5
          Re: Reports Stopped Working

          Another possibility for this behaviour i encountered more than once is that some user creates a pdf report an no default printer is set on the server or the default printer is set to your local printer, which can happen when you enter your server through rdp and have set rdp to access your local printers.
          Ger Kurvers
          Alpha Anywhere / V4.6.1.9- Build 6488 (production) / V4.6.5.1 - 8722-5683(testing)
          Development: Mysql, windows 10 64 Applicationserver: standard on Windows server 2019

          Comment


            #6
            Re: Reports Stopped Working

            Steve and Ger, thank you for your input and to let you know more

            The problem escalated to the point where the sites stopped rsponding about 4 hours after the initial problem with the reports. We re-booted and everything has been fine ever since
            1) Server is a single core, so the "report server" enhancement is not applicable
            2) All reports are well tuned and run in less than 7 seconds (tight edit checks on user parameters to prevent humongous reports from being generated)
            3) When users began reporting the initial problem, I did a system health check. Available memory, CPU and bandwidth were all fine. MS event viewer was clean, firewall was clean, etc. Also, there were no errors in the Alpha logs
            4) Ger, the default printer on the server is fine, and the problem happened to the web users (rules out a RDP mishap)
            5) My biggest web app has been in production for almost 2 years with 600+ users who operate 24x7. They run reports frequently and I've never had this problem in the past

            It concerns me that Alpha does not log anything regarding the error that must have been occurring

            Regarding AlwaysUp, I refuse to use it
            IMO, this is a poor way of managing an unstable product. I work hard to develop error free code and performance check everything before it is installed on the production server. I also pay Alpha $1,200 every year for their product and expect them to provide the stability they promise. The WAS "memory leak" or whatever it is that gradually consumes memory needs to be fixed by Alpha, it's been a problem for a long time.

            I do a daily health check on the server and have a planned server re-boot once every 2 weeks to release the memory that the WAS accumulates over time, and, to install MS updates. If the system became so unstable that I had to re-boot daily, or, install an attendant like AlwaysUp, I'm sure I would abandon Alpha Five and switch to another tool

            Comment

            Working...
            X