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 Server DMP files

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

    Alpha Server DMP files

    I'm running AA Server Build 8368 and it just started to generate some DMP files. There are a number of messages in the A5XbasicErrorStackLog file but the one that seems to be triggering the dump is "filefind.first(filename) Argument is incorrect data type". I've searched through all my source files and have found only a couple of places where filefind.first is used, but the curious thing is that the file is generated early in the morning, after the server has been restarted and when no one (I've checked) is using any applications.

    Has anyone encountered this specific error? It can be generated a few times a day. Funny thing is we experienced similar problems about a year ago, but then it stopped and has just reared its ugly head again only recently.

    Thanks for any ideas.



    #2
    You can turn on the Raw HTTP log and then by matching the time stamps figure out what component is giving you that error.
    Mike Brown - Contact Me
    Programmatic Technologies, LLC
    Programmatic-Technologies.com
    Independent Developer & Consultant​​

    Comment


      #3
      OK, I'll investigate. Strange thing is, that one error occurs every day at the exact same time (mod seconds): 3:04 AM ET. There is no one who works that early, and certainly not each day at the exact same time. Of course SOMETHING is causing it, and I'm sure, should I be lucky enough to find out what, that in retrospect it will be obvious. But that doesn't help me now. :(

      Thank you for the suggestion.


      Comment


        #4
        I'm not sure what mikeallenbrown is suggesting, but it sounds like solid advice.

        If that doesn't work:
        Try searching for, (below image), then see if you can run an Ajax callback to update a new table called "ErrorDebug" or something. Add fields like Date, Time, and Error. Then have that Ajax update the table after each instance of filefind.first(filename) is called, (Go through and make the error send back "This UX" or something that makes sense to you).

        Also, ensure that the field is a character field, and that the control's type is character.

        image.png

        Comment


          #5
          Well, as I say, the thing that's dominating my thinking right now is this repeatability: Every day, like clockwork, @3:04AM ET, this error is thrown. Now unless the timestamp in the A5XbasicErrorStackLog file does not reflect the actual occurrence of the error, I should be able to look at the RAW log and see what, if anything, is going on. Right now, before the fact, it doesn't look like it's app related since, as I mentioned, no one is on the app at that hour plus even if they were it wouldn't be timed to the minute. Maybe something or someone is polling the server machine or AA Server. IF the error was thrown randomly, perhaps on some days and not others, I could see that being an app issue. Not this way.

          Again, I could be totally off-base here, but we'll see.

          Thanks for chiming in.

          Comment


            #6
            As a followup: After doing some testing it appears that error is thrown when the AA Server starts (or restarts). I have two instances running, applications are different on each, but it's the same error when either instance starts up. RawHTTP log shows a request about a minute after startup (seems to be for the login page) but the error does NOT repeat when a request is made from a browser for the login page.

            I'm not quite sure where to go with this but I will keep trying.

            Thanks again for the assistance.

            Comment


              #7
              The best inference I can draw is that the 8368 version of the AA Server simply does not play nice with my Host's version of Windows Server. I downloaded two newer versions of AA Server and started, in turn, all three from the command line. The two newer versions did NOT throw the error, 8368 did. Where the logger is getting filefind.first I do not know, but I'm afraid I am going to have to go where I don't want to and tell my client he has to upgrade his server version. For kicks I might try this on another host account I have, but I'm not really expecting anything different.

              Comment

              Working...
              X