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

anyone seen this error before

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

  • anyone seen this error before

    anyone seen this error before
    Thanks
    Charlie Crimmel

  • #2
    Re: anyone seen this error before

    I could not make out the attached picture. What does the message say. ?

    Comment


    • #3
      Re: anyone seen this error before

      Originally posted by milesjg View Post
      I could not make out the attached picture. What does the message say. ?
      Using Firefox just magnify it one click and it reads:

      Internal error (exception caught) in function _rpc_resolve in C:\Dev\a5v9\src\engine\GENERIC\AU_PARSE.cpp on line 186 Please contact Alpha Software with a reproducible case of this error.

      And no, I have never seen the error.

      Ray

      Comment


      • #4
        _rpc_resolve Problem

        We have recently upgraded our application from Version 7 to Version 8, and we are seeing this error frequently. The error looks like this:

        Internal error (exception caught) in function _rpc_resolve in C:\dev\a5v8\src\engine\GENERIC\AU_PARSE.cpp on line 186Please contact Alpha Software with a reproducible case of this error
        .

        I also have a debugger image, but I can't figure out how to enclose it. The program seems to get hung when attempting to run a previously defined operation. When this happens, the program is really stuck. Only solution is to use Task Manager to end the application.

        Unfortunately, this problem is difficult to reproduce because it typically does not occur again (in the same place) when the program is restarted. Gradually the instances of the problem seem to subside, but when we merge in new application code to an existing application, we see frequent instances of the problem again.

        We are considering skipping Version 8 & going to Version 9. Has anyone seen this in Version 9?

        -- Dick James

        Comment


        • #5
          Re: anyone seen this error before

          Dick,
          Has anyone seen this in Version 9?
          This is the version 9 forum and Charlie's error also says so....so the answer is yes. Considering this error happens in both current versions suggests either a very long standing problem (don't think so) or you are simply having the same problem....time to figure out commonalities I think between your cause and Charlie's.
          Mike
          __________________________________________
          It is only when we forget all our learning that we begin to know.
          It's not what you look at that matters, it's what you see.
          Henry David Thoreau
          __________________________________________



          Comment


          • #6
            Re: anyone seen this error before

            I am using V9 and have just experienced this error for the first time. Mine is preceded with a little more info:

            "Error. Script: OnPush line:9
            topparent.commit()
            Internal error (exception caught) in function_rpc_resolve in C:\Dev\a5v9\src\engine\GENERIC\AU_PARSE.cpp on line 186Please contact Alpha Software with a reproducible case of this error"

            I was attempting to save an updated record at the time the error occurred. I still have ongoing issues with the "Unrecoverable error"/memory leakage problem. The above new error occurred on one of the two PC's which continually has the Unrecoverable errors. I have to conclude that until the problem is traced and eradicated, these two PC's cannot be used in conjunction with Alpha 5.

            Comment


            • #7
              Re: anyone seen this error before

              To All --

              I may have discovered a possible cause of my problem that may be useful to others.

              I had written an On Error condition that branched to a series of statements that were formatted essentially as follows:

              Code:
              lblerrorhandler:
              	err = error_code_get()
              	if err = 1000 	then resume lblendscript
              					end if
              	msg = error_text_get(err)
              	ui_msg_box("Error",msg)
              	resume next
              end 
              
              lblEndScript:
              end
              As I suspect most readers of this board know, A5 does not permit anything to follow the "then" except a carriage return. This is clearly a syntax error on my part.

              Version 7 seemed to ignore the problem. I'm not sure about the Version 9 behavior, but I think it also ignored the problem. In Version 8, when the line was being parsed, it evidently hung A5. (Processor usage went to 100%.) Debugger came up, but not on the offending statement. Stepping to another statement just brought back the debugger. Only way out was to end the application with Task Manager.

              I placed a carriage return after the "then" above, and the error message and problem have not recurred. As a point of interest, because I was having so much trouble with Version 8, I called Alpha support and was told that there is no problem skipping over Version 8 and going directly from Version 7 to Version 9.

              -- Dick James

              Comment

              Working...
              X