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

500 Internal Server Error when saving dialog

  • Filter
  • Time
  • Show
Clear All
new posts

  • 500 Internal Server Error when saving dialog

    I just got this error and wanted to know if anyone else has seen it. I have no idea what it is. The working preview worked fine - I was able to submit data.

    500 Internal Error.jpg
    Attached Files
    Last edited by josevelez; 01-12-2012, 10:25 PM. Reason: changed image

  • #2
    Re: 500 Internal Server Error when saving dialog

    Can anyone tell me why I am getting this error on my dialog? Please help!!


    • #3
      Re: 500 Internal Server Error when saving dialog

      Can anyone tell me if this is a bug or if I am doing something wrong?

      I am using the 'Submit-Reset' buttons under the 'Defined Controls' for a new dialog. I have the dialog called when a user clicks on a button from a grid (edit button). Everything fines in working preview, but when I try to edit and submit data in the browser I get this error.

      I have no idea what it means and did not see any posts related to it. Since I added a screenshot I'll add the text as well so it is searchable in the forums:

      XHTTPRequest Error:

      500 Internal Server Error
      Script ErrorError:Script:"/__a5RunDialog.a5w"
      x_out = a5_ajax_dialog2(tmpl)
      Property not found

      e._state._parentGridId subelement not found.

      Alpha Five Application Server/11.0 Build/2327-3852 at Server 1 Port 80

      Someone PLEASE help me!!! :)


      • #4
        Re: 500 Internal Server Error when saving dialog

        Is it not a pre-release you are running ??


        • #5
          Re: 500 Internal Server Error when saving dialog

          Hi Jim,

          Yes, I forgot that I am on a pre-release. I also just noticed that my builds are not matching (AGAIN!!). I dont understand, I have not made any updates or changes so how did they get mismatched? This may be what the problem is.Developer Build.jpgServer Build.jpg


          • #6
            Re: 500 Internal Server Error when saving dialog

            Did fixing your builds to match resolve this issue?


            • #7
              Re: 500 Internal Server Error when saving dialog

              I was getting the same issue with the 27 Feb pre-release build and the 29 Feb full release.

              It affected the majority of my data input. It occurred whenever I did an ajax call-back of any kind.

              As I work to deadlines I could not live with this and the only solution was to roll back to the 4 Feb build which does not have the issue.

              Both my developer and server versions were in sync.


              • #8
                Re: 500 Internal Server Error when saving dialog

                Thanks Lance for your input. I have wasted days on this and am also behind in deadlines now and have some very frustrated people.

                Mine is also happening with ajax callbacks and I just can't pin it down.

                I think I will try your suggestion and rollback to feb 4th build.

                Thanks! Kim


                • #9
                  Re: 500 Internal Server Error when saving dialog

                  To save Kim and anyone else the time, this bug is still there in the latest release (7th March 2487-3884)


                  • #10
                    Re: 500 Internal Server Error when saving dialog

                    Thank you for the update Lance. I could not find the Feb 4th release as you mentioned; it must have been a beta and I could not find the links.
                    After reviewing the release notes for the Feb 29th release, I decided I had better stick it out as rolling back looked like it would cause other problems for me.

                    Doing the "Bulk Operations" In the "Web Projects Control Panel", under the "Edit" tab seemed to help me resolve the 500 Internal Server Error [that is, as long as I do not uncover it elsewhere, which seems to be the issue many are having!]

                    Before I did the "Global Replace of Component Styles" (in Bulk Operations), I went into the Project Properties and edited the Project Profile, making my custom CSS Profile compatible with V11 so it was no longer considered a "legacy" style. This also resolved some issues I was having.

                    However, I'm still getting that darn $(ele).style.display error that I have never gotten before, in code that was working properly.
                    I thought I had it fixed several times, even posted that I had it resolved, only to find that it is still popping up, just very inconsistently (like every 3rd or 4th record that is pulled, whereas before it happened religeously on every 2nd record that was pulled).

                    Here is the link to that issue:


                    • #11
                      Re: 500 Internal Server Error when saving dialog

                      Filled with hope I checked my CSS and I only use grblue and mobblue so that should not be an issue.

                      I then did the 'bulk operation' 'update compiled files for ajax grids', this found an error in an unused grid, but didn't change the error. As this means I have to unload and reload a grid after each ajax callback it makes processing data very time consuming. Therefore it is back to earlier working version again.

                      I think I will try and find time to submit this as a bug report, maybe at the weekend, because I really like the hide a container on a dialog feature that has recently been added.


                      • #12
                        Re: 500 Internal Server Error when saving dialog

                        Which version did you roll back to? And is it working for you?

                        I think I will have to try rolling back as well. I wanted to avoid that, but have now wasted well over a week trying to resolve this and am at a deadend.

                        Surely others must be having this problem??


                        • #13
                          Re: 500 Internal Server Error when saving dialog

                          The version I rolled back to is a pre-release version 2404-3868, which works for me. I save all the different versions I download for just this situation (probably should clear some of the older ones from the beta testing out as I think we are beyond that now).

                          I know you should not run different developer and server versions, but I might give it a go so that I can use the feature packs. I have added some of the features to my grids when in the newer version then rolled back and they still work. Therefore I will try developing in the latest version and running on the server in 'safe' version.


                          • #14
                            Re: 500 Internal Server Error when saving dialog

                            Let me know how this works for you, and maybe I can find the links online to those same versions.

                            Though I purchased V11 in August before it was realeased, I only just made the upgrade from v10.5 1 1/2 weeks ago, thus all the new problems.
                            Which is why I don't have links to any of the "prereleases".
                            I had hoped that waiting so long I would not have too many issues.


                            • #15
                              Re: 500 Internal Server Error when saving dialog

                              Running the developer and server versions did not work at all, Dialog2 components do not show any of the repeating section data. Rolling back to my trusted version again