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

Last Build that worked was 2715-3938

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

    Last Build that worked was 2715-3938

    Still having lots of App server slow downs and or freezes with any build past 2715-3938. The last one 2743-3945 only let the App server run for a few hours. Rolled back to 2715-3938, no problems.
    Reed Brown
    ITOT Solutions, Inc.
    Alpha v12
    Tags: None
    #2
    Re: Last Build that worked was 2715-3938

    Reed - What does Alpha say about your slow downs and freezes? Have you reported the problem to them?
    Carol King
    Developer of Custom Homebuilders' Solutions (CHS)
    http://www.CHSBuilderSoftware.com

    Comment

      #3
      Re: Last Build that worked was 2715-3938

      The user has not submitted any issues to us or sent in any log files.
      Not much we can say under these circumstances.

      Comment

        #4
        Re: Last Build that worked was 2715-3938

        Originally posted by kingcarol View Post
        Reed - What does Alpha say about your slow downs and freezes? Have you reported the problem to them?
        Yes, Lenny has been trying to solve this for months. The problem is I cannot turn on the logs because it slows down my server so much and fills up the hard drive. The server can run for a few days before it freezes so the logs would be too large. Also several times when I was luckily enough to have them on when it froze, it did not record any problem so that did not help.
        Reed Brown
        ITOT Solutions, Inc.
        Alpha v12

        Comment

          #5
          Re: Last Build that worked was 2715-3938

          This does not compute. How could he have been trying to solve a problem for "months" when the problem started (you say) in build 2715 (which is a pre-release test build that was made available on June 6 - less than 2 weeks ago).
          If the problem has been going on for 'months' then you are saying that there is a problem with the current official release, but no one else has reported a problem with the current official release.

          Comment

            #6
            Re: Last Build that worked was 2715-3938

            I've been having this problem for months and months. What I mean was that build 2715 worked great. Many builds before that did not and the builds after that did not work for my server either. Once I roll back to 2715, no problem. Sorry for the confusion.
            Reed Brown
            ITOT Solutions, Inc.
            Alpha v12

            Comment

              #7
              Re: Last Build that worked was 2715-3938

              If you set the logs to rotate by date or size, the files don't get very large and the performance impact is very small. Smaller logs also make troubleshooting problems that occur infrequently much easier. Without server logs, it is almost impossible to track down problems that are not tied to specific actions.

              Log rotation can be turned on from the Advanced tab in the server configuration.

              Comment

                #8
                Re: Last Build that worked was 2715-3938

                Maybe an option could be added to the server configuration to deletelogs over X days old to help keep space down Jerry?

                Comment

                  #9
                  Re: Last Build that worked was 2715-3938

                  Which logs are you using and why have the logs turned on?

                  I usually only use the logs when I'm having a problem, then turn off when it is fixed. But if the logs are the problem, I probably wouldn't use them.

                  If Lenny has been working on this for months, was this directed to him, or are you asking the rest of us for help? Are you having an issue with a grid or a page? Maybe we could help you with that so you won't need the logs.
                  Pat Bremkamp
                  MindKicks Consulting

                  Comment

                    #10
                    Re: Last Build that worked was 2715-3938

                    I will give it a try, thanks
                    Reed Brown
                    ITOT Solutions, Inc.
                    Alpha v12

                    Comment

                      #11
                      Re: Last Build that worked was 2715-3938

                      No it is the App server program itself. Alpha has been great trying to fix this but it is very hard to pin down. We use my program for the medical industry so I cannot have it down for any reason. The App server program will run for days then it will freeze over and over again. My server is hosted and has been checked out and given a clean bill of health. As the builds come and go, some of them do not have this problem "for me" but I keep trying the new ones. I end up rolling back to 2715.
                      Reed Brown
                      ITOT Solutions, Inc.
                      Alpha v12

                      Comment

                        #12
                        Re: Last Build that worked was 2715-3938

                        Try restarting the appserver everyday at say 3 am It will run much healthier. If you use always up this is very easy to do.
                        Chad Brown

                        Comment

                          #13
                          Re: Last Build that worked was 2715-3938

                          Been there done that. Thanks however.
                          Reed Brown
                          ITOT Solutions, Inc.
                          Alpha v12

                          Comment

                            #14
                            Re: Last Build that worked was 2715-3938

                            Originally posted by chadbrown View Post
                            Try restarting the appserver everyday at say 3 am It will run much healthier. If you use always up this is very easy to do.
                            To my understanding this was fixed in V10 but we have to restart the WAS for best performance dialy? mmmm..........

                            Comment

                              #15
                              Re: Last Build that worked was 2715-3938

                              Just received this email from Alpha. Good news !

                              I have tracked down a crash in the server that might be the culprit -
                              tommorrows pre-release should have the changes,
                              Reed Brown
                              ITOT Solutions, Inc.
                              Alpha v12

                              Comment

                              Previous 1 2 template Next
                              Working...
                              X