Announcement

Collapse
No announcement yet.

Serial Number Authentication Checker

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

  • Serial Number Authentication Checker

    Hi Ulrich,

    My checker is working great and thanks for the help a while back. I get a couple of errors and maybe you will know how the customer can solve it.

    "Could not open request"
    The firewall fixed was to add the Falcon 50 install file, "FLYSIMWARE_FALCON_50_V2.0b.exe", to the firewall "Allowed apps and features" table.

    This is a fix for the first error. Maybe you know why they had to add an exception? Or can they just click the reset defaults for the firewall?


    “HTTP”

    Unkown

    This is not because they have no internet. If they can't find google we have the installer got to our OFFLINE MODE.


  • #2
    Do you see this with only one user/customer?

    Ulrich

    Comment


    • #3
      No. 3 customers for the HTTP and maybe 5 for the Could not open request.

      Comment


      • #4
        Ok, so not all of them, and this is good, because otherwise this could indicate an issue with the PHP on the server. It might be a good idea to change the screens / script slightly then, to allow a "retry" operation. I imagine that, if the firewall blocks the access to the internet on the first attempt, and the default timeout for any socket operation is 20 seconds in Windows, it might happen that the user does not grant the access through the firewall in the required time. So, instead of proceeding to the "offline" screen after the first attempt to validate the serial fails, it might make sense to offer a "retry" option. I hope this makes sense.

        As for the HTTP error... perhaps some additional debugging with HTTP.GetHTTPErrorInfo() could explain a little more what might be happening. At this time, I cannot offer any advice without knowing more.


        Ulrich

        Comment


        • #5
          Our offline mode works when you first start the installer and it fails to find google. The error "Could not open request" only happens when the handshade to the server is happening. So its odd how only a few people have to make an exception.

          I am not sure how to make a redirect from this error as it pops up a window message that we did not create. How can we redirect from that popup message? I can try that.

          For the the other error i am not sure how to check this as neither of these errors i can simulate. They are just rare.

          Comment


          • #6
            Can you post a capture of the sceen where this message box pops up? I checked my current script here, and from what I can see, the "Verify Serial Number" is not supposed to show any dialogs, unless the debug code was uncommented.

            Ulrich

            Comment


            • #7
              I can't reproduce these errors. They are rare and very odd. But when they do appear they do show as a popup window. And they either say "Could not open request" or "http error". So i figure these come from the main program and not what we programmed. And so that is why i ask for help. I am not interested in preventing the popups but more want to tell the customer why it happens. And so far the "Could not open request" a customer had to make a firewall exception. So that is the only clue we have so far.

              Comment


              • #8
                I looked through our on next code for the verify serial number and there was this in the code. This is the actual second message that appears. "HTTP.Submit"
                The other one i have no clue where its coming from. I forget how to check run a error. So maybe you can remind me or tell me what this error means below.

                error = Application.GetLastError();
                if (reply == "" or error ~= 0) then
                Dialog.Message("HTTP.Submit", _tblErrorMessages[error], MB_OK, MB_ICONEXCLAMATION);
                else

                Comment


                • #9
                  Please see here the code below. I would leave the dialog commented out - it is certainly useful during debugging, but once the mechanism is tested and working, it is better to deactivate this part out of the script:

                  Click image for larger version

Name:	SCRN-2020-09-18-01.png
Views:	68
Size:	28.6 KB
ID:	305483

                  Here is where I show how you could implement some retries, and attempt to log some additional information about the error.

                  Click image for larger version

Name:	SCRN-2020-09-18-02.png
Views:	56
Size:	37.6 KB
ID:	305484

                  Ulrich

                  Comment


                  • #10
                    I noticed your sample reply = HTTP.Submit is not what we use. We use reply = HTTP.SubmitSecure
                    Could this be why only a few customers have issues?

                    Comment


                    • #11
                      If your web server is reachable via HTTPS, and your URL starts witrh "https://", then of course use the "secure" version of that action. I only showed the original code which comes with my custom screen.

                      Ulrich
                      Last edited by Ulrich; 09-19-2020, 06:25 AM.

                      Comment


                      • #12
                        Where does the log file get created? Nothing happened?

                        Comment


                        • #13
                          The destination of the log file is defined in the project settings.

                          Click image for larger version

Name:	SCRN-2020-09-19-01.png
Views:	69
Size:	18.7 KB
ID:	305505

                          Ulrich

                          Comment


                          • #14
                            Thanks for that info. I will try to see if i can get a customer who has this issue to test using our test installer and then take the log info and share it with you. Will update you soon.

                            Comment

                            Working...
                            X