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

Publishing problems and other errors

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

    Publishing problems and other errors

    I posted this in the V11 forum and thought I should post it here as it involves V12 too. I'm really stumped on this and I can't move forward so if anyone can give some advice I'd appreciate it. Thanks.



    Hi everyone,

    V11. This has been working forever and all of a sudden I am getting a 500 Internal Server Error. I have no clue what this means. I ran the program in live preview, it was not loaded on a browser. This has been working for a while and I've made no changes to the screen/grid being called. (Edit: I just ran it in Working Preview and it works - Live preview does not)

    I recently did these things and maybe this caused the problem?

    I decided to move to AA V12 so I backed up the V11 version and unzipped it into a completely different directory under V12.
    Opened the version in the V12 directory
    Worked on that version (in the V12 directory) - Everything works fine in V12
    Live Preview in V12 works fine.

    Now, I'd prefer, at this point, to keep it in V12, however, whenever I try to publish it to my test site (where I already have the V11 version) it does not publish properly. I get 403 and 404 errors. I suspect I am not setting up the profile correctly but I've pretty much copied it from the V11 version which works.

    So, if anyone can help me with just publishing the V12 version to my test site I'd be extremely grateful. I can then at least move forward with V12.

    If that's not possible, can anyone help me with why I can't run my V11 anymore. I'd like to get one of them working so I can let users test again.

    Thanks much

    -John
    Attached Files

    #2
    Re: Publishing problems and other errors

    Your test site has Alpha WAS V11 and Alpha WAS V12 installed? It's a bit confusing as to what's installed where.

    You can't publish V12 stuff to a V11 site... which it sounds as if you're doing. If so, then by publishing V12 stuff to your V11 site, you've wrecked your V11 site.

    Comment


      #3
      Re: Publishing problems and other errors

      Hi David,

      Thanks for the reply.

      Sorry for it being confusing. It's *really* confusing to me and harder to try and 'splain it.

      Yes, the test site has both WAS V11 and V12 but only one running at a time.

      Online, if I shutdown V12 WAS and start V11 WAS the V11 files that were published with V11 work. That's good. What's bad is that on my local development PC I get that 500 error when using V11, so I now cannot publish anything.

      That's why I then installed the V12 WAS to the site and republished the V12 version files online, loaded V12 WAS and tried logging in, but it doesn't work. 403 and 404 errors.

      On my development PC (desktop), I also have both V11 and V12 (Developer and WAS) and have used both in live preview with no problems before, it's just recently (last week) that I now cannot run the V11 developer of my database, I get that 500 error message. I even restored backup versions of the dialog that seems to be having the problem, with no success.

      To make it more confusing I originally had ONLY V12 on the test site but I could never get it to work, I would get the 403 and 404 messages, hence I had no choice but to take that off and put V11 on there and it worked. Further, if I shutdown the WAS on my test site and run the V11 WAS it works.

      I have to move to V12 at some point, this seems like a good time to do it. Heck, I've been paying to keep V12 software current for years and never moved from V11. Time to bit the bullet :)

      Do you have any advice?

      Thanks

      -John

      Comment


        #4
        Re: Publishing problems and other errors

        Your using Alpha WAS, not IIS, is that right? On your Server, V11 and V12 are installed to separate folders, and you're publishing to those specific folder from Dev. Sorry... have to ask.

        What build of Alpha V12 are you using?
        Are you working with SQL or DBF?

        You are publishing to A5V12/A5Webroot. Does your BaseURL point to that folder structure? If not... that's probably your main issue.

        Your data files folder is showing as A5V11/Data. Are you publishing V11 and V12 data files to the same folder?

        Comment


          #5
          Re: Publishing problems and other errors

          Hi David,

          Don't be sorry! lol ask away, I'll attempt to be as clear as I can. I am pleased as punch to get some help!

          -Yes, using Alpha WAS (11 and 12).
          -Yes, installed in separate folders.
          -Build = 5254 on Desktop and Server.
          -Working with Access backend.
          -A5V12\A5Webroot ok, this is where I start getting confused. Yes, I'm publishing it there because I thought I'd keep it separate from A5V11. I'm not sure where It should be going to. BaseURL is pointing to http://my.org, again, that's what I thought should be in there.
          -Yes. Datafiles being published to A5V11\Data because I'm using the same profile as I used for the A5V11 version. The data files are the same files.

          I hope that clears things up a little.

          Thanks for the help David.

          -John

          Forgot to show the layout on the server.
          Attached Files
          Last edited by Jberry; 04-07-2019, 05:08 PM. Reason: Forgot file

          Comment


            #6
            Re: Publishing problems and other errors

            In your WAS Configuration for V11 and V12, in the General Tab, what is the Document Root for each?

            5254 is the Addins build #. The full build # is 5667_5254, but generally, referring to Alpha build 5667 will be enough.

            Comment


              #7
              Re: Publishing problems and other errors

              Hi David,

              For the V12 WAS it is C:\A5Webroot (Build 5667)

              For the V11 WAS it is C:\A5V11\A5Webroot (Build 3788)

              Comment


                #8
                Re: Publishing problems and other errors

                Hi David,

                Now I'm getting somewhere. I changed my profile setting for Folder to A5Webroot. The login screen displays and when I sign-in I get this message "WebSecurity: The security data tables for this application are missing or incomplete". I can see the security files are in the A5Webroot though.

                Comment


                  #9
                  Re: Publishing problems and other errors

                  I republished the security files and now I can get online. The next issue is that the screens do not use the CSS original style (grGray), they're all just transparent.

                  Comment


                    #10
                    Re: Publishing problems and other errors

                    Hi David,

                    So two problems (at least) still remain. I'm looking for answers on the board but not finding anything I can use as of yet.

                    1) It looks like the CSS is not working. I have my screens set to GrGray and everything is transparent. No icons show. No dropdowns work.
                    2) I get an Error opening Grid table/View: Internal error - Can't find named connection string...

                    NamedGridError.jpg
                    Last edited by Jberry; 04-08-2019, 10:50 AM. Reason: Edit: I also changed the CSS to MobBlue but it had no affect

                    Comment


                      #11
                      Re: Publishing problems and other errors

                      I believe the Profile Folder should be A5Webroot, as you now have it. But your server Document Root should be C:\a5v12\A5Webroot. This is where your published files exist. Confirm this by creating a new UX, or saving an existing UX under development... and then publish that one component. Then check your server folder with explorer to confirm you're seeing that file.

                      This could be part of your CSS and connection string issues.


                      EDIT: Fixed my Document Root error.
                      Last edited by Davidk; 04-08-2019, 01:22 PM.

                      Comment


                        #12
                        Re: Publishing problems and other errors

                        Hi David,

                        I manually publish the files because A5 publishing does not work, meaning, if I set the FTP Program in the Web Projects Profiles to Internal and publish, it looks like it is doing something but nothing actually gets published. I confirmed this by doing as you suggested, creating a new UX, doing a publish, then going to the server and searching the whole drive for that UX and it is nowhere to be found, hence, I've been using External.

                        I went to the online WAS and changed it FROM C:\A5Webroot TO C\A5V12\Webroot. It said the directory didn't exist so I let it create one.

                        WAS_SettingsNewDK.jpg

                        My desktop profile is:

                        ProfileV12.jpg

                        Comment


                          #13
                          Re: Publishing problems and other errors

                          Sorry, John, that's my fault. I wrote C:\a5v12\Webroot and it should have been C:\a5v12\A5Webroot which does exist in your server.

                          Change your Document Root again and try it.

                          Comment


                            #14
                            Re: Publishing problems and other errors

                            Hi David,

                            No worries. Let me ask you this, if I'm publishing the files manually:

                            -I let A5 do its thing.

                            -It gives me a directory on my desktop PC where the files to be published are.

                            -I use my FTP file transfer program to copy those files to? Where should they go on the server?

                            Here's a screen shot of the directory on my server.

                            C_on_Server2.jpg

                            Comment


                              #15
                              Re: Publishing problems and other errors

                              They should go in c:\A5V12\A5Webroot.

                              That you have files in c:\A5Webroot is most likely due to all the different publishing scenarios you've gone through. Check the date and time on those files... see how current they are.

                              Comment

                              Working...
                              X