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

WAS server 3944_3012 not allowing login using FireFox

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

    #16
    Lenny-

    With SSl off FireFox still cannot work but now i get an error.. see screenshot.

    FYI-IE still works fine getting past the login.

    The error occure after pressing submit button of the login control.

    Comment


      #17
      If you enter that error msg in google, you get lots of hits by other developers, or gamers really. A quick search had suggestions like to clear the cache, "ipconfig /flushdns" (a dos command), and here's a longer quote:
      -----------------
      If you get this annoying "the document contains no data" message in firefox (caused when you have ad blocking enabled somewhere, I think...), then do this:

      in address bar, type:

      about:config

      find the setting called "browser.xul.error_pages.enabled" and set it to true.

      the annoying message will then go away.
      Steve Wood
      See my profile on IADN

      Comment


        #18
        Thanks Steve -

        That would make since were this an issue that occured in other areas using FireFox. In my case, I only get this error trying to access my database through the normal login script which FireFox did just fine with immediatly prior to updating the WAS server. I can comment out the login requirments and FireFox does just fine getting to the target page. I can login to other sites that require it like this forum and FireFox does just fine.

        I guess I will try to rebuild and republish the login componets of my database based using the new Alpha5 release and see if that helps.

        Chuck

        Comment


          #19
          If you wanted to send your login dialog & a5w page (privately), I would post them on my server and see if they fire. Also, I could then compare your script to what I have in case there is some difference. That would at least eliminate the login method as cause.
          Steve Wood
          See my profile on IADN

          Comment


            #20
            Lenny-

            Any issues I should know about before attempting to revert back to the previous release of the WAS. This FireFox problem is not getting solved for me. Will the older release just install over the newer release? Can I continue to develop using the newer realease and have the older WAS serve what I develop. It would seem that the changes in the development side would not have impacted the WAS despite the WAS only version having the same upgrade release numbers as the full development version of A5V7.

            Thanks,

            Chuck

            Comment


              #21
              Chuck, can you send me your application so I can try to duplicate the problem here? I'd really like to get this resolved for you.

              I don't know for sure if reverting will make cause any problems - you will need to review the release notes and see what changes were made to web components (which is not really my area so I'm not familiar with everything done in the last release). When the components are updated, there is a small potential for version conflicts. If there is one, you may have to recreate your component in the older development environment to be able to run it on the older server again.

              Originally posted by Hansolo
              Lenny-

              Any issues I should know about before attempting to revert back to the previous release of the WAS. This FireFox problem is not getting solved for me. Will the older release just install over the newer release? Can I continue to develop using the newer realease and have the older WAS serve what I develop. It would seem that the changes in the development side would not have impacted the WAS despite the WAS only version having the same upgrade release numbers as the full development version of A5V7.

              Thanks,

              Chuck

              Lenny Forziati
              Vice President, Internet Products and Technical Services
              Alpha Software Corporation

              Comment


                #22
                Because I was concentrating on this FireFox problem I did not pick up on another problem which all of my clients have informed me of.

                It seems no one can save or update data on my WAS served databases now. This also coinsides with the upgrade. I'm a little screwed here :-)!

                Maybe it is my server system itself but i have not changed anything on it and have not allowed automatic updating of the Windows Server 2003 soefware.

                Anyone else haveing problems of this sort?

                Chuck

                Comment


                  #23
                  Chuck, do you have error logging enabled on the server? If not, you should turn it on. Review the error log for any problems such as connection resets, etc., or send it to me and I will review it.

                  Originally posted by Hansolo
                  Because I was concentrating on this FireFox problem I did not pick up on another problem which all of my clients have informed me of.

                  It seems no one can save or update data on my WAS served databases now. This also coinsides with the upgrade. I'm a little screwed here :-)!

                  Maybe it is my server system itself but i have not changed anything on it and have not allowed automatic updating of the Windows Server 2003 soefware.

                  Anyone else haveing problems of this sort?

                  Chuck

                  Lenny Forziati
                  Vice President, Internet Products and Technical Services
                  Alpha Software Corporation

                  Comment


                    #24
                    Chuck,

                    I have a windows 2003 server,. Just tested, and with IE it is properly saving data, sending email, logging in etc.

                    However, I find that now I cannot log in using Firefox. (I have ssl, but have not yet entered the "chain" value, if that makes a difference).

                    https://support.attorneystrust.com

                    In my case, I will just put up a notice on the login page to not use Firefox (my stats show nill us of Firefox), but I'll have to resolve at some point.

                    Do what Lenny says and turn on logging, including "raw" logging. It will give some clue to what is happening.
                    Steve Wood
                    See my profile on IADN

                    Comment


                      #25
                      Originally posted by Lenny Forziati
                      Chuck, do you have error logging enabled on the server? If not, you should turn it on. Review the error log for any problems such as connection resets, etc., or send it to me and I will review it.

                      Lenny- I have error logging on of course. It shows timeout and page not found errors when folks try to Add or Update a record. However further testing shows this is only happening with grids with many fields. I have not narrowed dow how many before the problem occure. For example in the same database I can update a table with 4 fields and another with 3 fields but have not been able to update tables with up to 7 fields or more including tabbed grids.

                      By the way this occurs in Live Preview on my local development system as well so it is not just the WAS on my server.

                      The attachment is not zipped. I just put the .zip extension on because .log is not a valid file to upload to this forum which is strange.

                      Chuck

                      Comment


                        #26
                        Originally posted by Steve Wood
                        Chuck,

                        However, I find that now I cannot log in using Firefox. (I have ssl, but have not yet entered the "chain" value, if that makes a difference).

                        Well that is some comformation anyway. Thanks for the reply. Did you happen to update grids will more than 7 fields?

                        Chuck

                        Comment


                          #27
                          Chuck, one of the missing files that is being complained about is a5_url.js. This is an important part of navigation components and it not being found will cause all sorts of strange problems. You should clear your publishing history and republish the whole project to get this and any other missing files onto the server. This may or may not resolve the login problems, but it is something that needs to be done anyway and it just may help out here too.

                          Originally posted by Hansolo
                          Lenny- I have error logging on of course. It shows timeout and page not found errors when folks try to Add or Update a record. However further testing shows this is only happening with grids with many fields. I have not narrowed dow how many before the problem occure. For example in the same database I can update a table with 4 fields and another with 3 fields but have not been able to update tables with up to 7 fields or more including tabbed grids.

                          By the way this occurs in Live Preview on my local development system as well so it is not just the WAS on my server.

                          The attachment is not zipped. I just put the .zip extension on because .log is not a valid file to upload to this forum which is strange.

                          Chuck

                          Lenny Forziati
                          Vice President, Internet Products and Technical Services
                          Alpha Software Corporation

                          Comment


                            #28
                            Sorry to say that clearing the publishing Hx and republishing all files did not help either problem.
                            I think many of the files listed as not found in the log were being complained a few days back because of my turning off SSL per your suggestion eariler. I did not realize that this would invalidate the https links. After realizing this I was then having to type the absolute paths in the browser to test the pages without SSL.

                            Chuck

                            Originally posted by Lenny Forziati
                            Chuck, one of the missing files that is being complained about is a5_url.js. This is an important part of navigation components and it not being found will cause all sorts of strange problems. You should clear your publishing history and republish the whole project to get this and any other missing files onto the server. This may or may not resolve the login problems, but it is something that needs to be done anyway and it just may help out here too.

                            Comment


                              #29
                              If you have links hard-coded at https://server/page.a5w then yes, turning off SSL will make them no longer work. However if you instead use a relative URL, such as just page.a5w, then the links will work regardless of your SSL setting.

                              Originally posted by Hansolo
                              Sorry to say that clearing the publishing Hx and republishing all files did not help either problem.
                              I think many of the files listed as not found in the log were being complained a few days back because of my turning off SSL per your suggestion eariler. I did not realize that this would invalidate the https links. After realizing this I was then having to type the absolute paths in the browser to test the pages without SSL.

                              Chuck

                              Lenny Forziati
                              Vice President, Internet Products and Technical Services
                              Alpha Software Corporation

                              Comment


                                #30
                                I only hard code the link on the initial index page (my jumping point to A5 and other things) in InetPub\wwwroot that jumps from the Win2003 Web Server on port 80 to the A5 index.a5w page in A5webroot on port 443. When I turned off SSL and tried to make the jump the server recorded the invalid page index.htm in the log. At least that seems like what happened. Other instances seem to coinside with my typing the wrong page into the browser. Not sure where "url /robots.txt" came from though in the log? I did not type that and I have no link to a text file by that name?

                                Chuck

                                Originally posted by Lenny Forziati
                                If you have links hard-coded at https://server/page.a5w then yes, turning off SSL will make them no longer work. However if you instead use a relative URL, such as just page.a5w, then the links will work regardless of your SSL setting.

                                Comment

                                Working...
                                X