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

Failed to Save Document / Failed to Open Document

  • Filter
  • Time
  • Show
Clear All
new posts

  • Failed to Save Document / Failed to Open Document


    I'm somewhat new to Alpha and I've been noticing some error messages that occur sporadically that I can't seem to identify the source.

    We have a Windows server 2003 box with about 40 scheduled task that will run various scripts throughout the day. Every now and then the the task will start and immediately an error message of "Failed to Save Document" is thrown or "Failed to Open Document". I've done my research and I know that this is usually caused by an incorrect path or the network connection to that path was lost. The problem with that is everything is saved to the local hard drives and not on the network. I've double and triple checked the paths and they are all correct.

    The weird thing about this is, when the "Failed to Save Document" error is thrown I'll press OK and the script will run without any issues. Also, this problem is very sporadic and there isn't a rhyme or reason as to why the error has occured. Lastly, if I don't press OK and subsequent Alpha scheduled jobs will either give the "Failed to Save Document" or "Failed to Open Document" error.

    Any input would be greatly appreciated.

    Thank you,

    Kyle Nelson

  • #2
    Re: Failed to Save Document / Failed to Open Document

    I've done my research and I know that this is usually caused by an incorrect path or the network connection to that path was lost.
    Or a windows permissions issue.

    The weird thing about this is, when the "Failed to Save Document" error is thrown I'll press OK and the script will run without any issues.
    Why weird (?), the connection has probably been restored.
    There can be only one.


    • #3
      Re: Failed to Save Document / Failed to Open Document

      I'm fairly sure that it isn't a windows permission issue because I can re-run the script after a failure and it runs without any issues.

      I'm starting to wonder if it is a problem with our NAS. The database resides on a NAS and I suppose it could be possible that the server lost the connection to the NAS temporarily. Have you ran into this issue before by chance?


      • #4
        Re: Failed to Save Document / Failed to Open Document

        Not personally but some who work in our office use laptops with wireless connections. They encounter the same message occasionally due to dropped connections.
        There can be only one.


        • #5
          Re: Failed to Save Document / Failed to Open Document

          Using a v9 desktop application on a 5 user lan with a windows server I have seen the "failed to save document" message ten or more times in the last few years. The users are using the runtime under windows 7 with no shadowing. Closing the app and restarting usually cleared the message. But once I was actually running the a5v9 on the server using the full development a5v9 itself and got the error. On that occasion I closed the database but reopening it gave the same error. I then opened an old copy of the same database (a backup a few days old) and did not get an error. I closed the old DB and opened the production DB again with no error. I would also like to understand this. But since I was working on the server I do not think it was a connection error. Some how I think it has something to do with the .RMUF file or .MUF (tracking multi-user count) but I am just guessing. Does anybody know what file the error message is referring to?


          • #6
            Re: Failed to Save Document / Failed to Open Document

            Well for any users in the future that come across this problem here is what the resolution was for this issue. I ended up changing the start times of the scheduled tasks. After some logging and many headaches, I found a pattern that when multiple Alpha 5 instances start at the exact same time it can throw these error messages. Changing the start time of the scheduled task ensured that there wasn't multiple instances of Alpha 5 starting at the exact same time.


            • #7
              Re: Failed to Save Document / Failed to Open Document

              We get this error when a user launches the application, the login dialogue displays and the user does not login right away, then subsequent users that attempt to login get the "Failed to save document" error. This usually is more common in the mornings, when everyone is trying to login to the application around the same time. It is just a warning though, if one click "OK", the application starts without problems.
              This is my experience with this issue; I have several clients that are using the Runtime Client with many users, and we see situation in both places.