6 Replies Latest reply on Feb 20, 2015 9:16 PM by EdgarRamirez

    Perform Script on Server failed

    EdgarRamirez

      Title

      Perform Script on Server failed

      Your post

      Hello,

      When trying to Perform Script on Server I get the following error dialog box, on the client that triggered the script:

          "The account name and password you entered does not match those for any Filemaker account"

      Only the 'Guest' user can Perform a Script on Server.

      As a test, I setup a Server-Side Script with the same Full Access credentials as the user trying to run the PSOS. This Server-Side Script executed successfully.

      Also, there is no problems logging into the database, for any of the users.

       

      Setup

      1 single database on

      FMS 13.0.5 on Mac OS X Yosemite (not OS X Server)

      FMP 13.0.5 client on Windows 7

       

      I need to have the users log in with their credentials and PSOS.

      Any help is greatly appreciated.

       

      Thank you

        • 1. Re: Perform Script on Server failed

          Edgar Ramirez: 

           

          Thank you for the post.

           

          "As a test, I setup a Server-Side Script with the same Full Access credentials as the user trying to run the PSOS. This Server-Side Script executed successfully."

           

          If the [FULL ACCESS] account works, but a managed account does not, then is the script set to "Run script with full access privileges" or does the managed account have permission to execute scripts? (See screenshot below.)

           

          TSFalcon

          FileMaker, Inc

          • 2. Re: Perform Script on Server failed
            EdgarRamirez

            Hello,

            Thanks for your response.

            When Performing Script on Server, the "Admin" [Full Access] account, actually does not work.

            Only the "Guest" [Read-Only Access] executes PSoS successfully.

            Let me give you a bit more details of my procedure.

            Since I saw this behavior in my project, I am testing all this in a brand new database with the default Admin and Guest accounts, 1 table and 1 field. There has not been any modification to Manage --> Security. All Privilege Sets are untouched.

            Here are the scripts I am using:

            Script Name: "PSOS Call"
            Run script with full access privileges On
            •Perform Script on Server [ “PSOS script” ] [ Wait for completion ]
            •Exit Script [ ]

            Script Name: "PSOS script"
            Run script with full access privileges On
            •Go to Layout [ “yut” ]
            •Show All Records
            •Go to Record/Request/Page [ First ]
            •Set Field [ yut::opa; Get ( ScriptName ) ]

            I have take a screenshot (below) of the failed massage on FMP, along with the Status and Log messages in FMS when the script fails when run by "Admin" [Full Access]. You can compare this to the Log messages when the script succeeds, when run by "Guest" [Read-Only Access], also in the screenshot.

            Maybe there is something there, that can shed some light.

            I can upload the database file if you deem necessary. It is less than 200k

            Thanks

             

            • 3. Re: Perform Script on Server failed

              Edgar Ramirez: 

               

              Thank you for the reply.

               

              I am unable to replicate. To attempt to replicate, I performed the following steps:

               

              1. File > New Database > "PSOS.fmp12"

              2. Created a single text field called "Text"

              3. Enabled the Guest account

              4. Created a blank record

              5. Created two scripts:

               

              "PSOS Call"
              Run script with full access privileges On
              Perform Script on Server [ “PSOS script” ] [ Wait for completion ]

               

              ----

               

              "PSOS script"
              Run script with full access privileges On
              Go to Layout [ “PSOS” ]
              Show All Records
              Go to Record/Request/Page [ First ]
              Set Field [ table::text; Get ( ScriptName ) ]

               

              6. Confirmed "PSOS script" works locally.

              7. Uploaded "PSOS.fmp12" to FileMaker Server 13.0v5

              8. As Admin, ran "PSOS script"

                  Actual Result: "PSOS script" placed in the text field.

              9. Cleared the value in the text field.

              10. As Admin, ran "PSOS call"

                  Actual Result: "PSOS script" placed in the text field.

              11. Closed the file, logged in as Guest

              12. As Guest, ran "PSOS script"

                  Actual Result: "PSOS script" placed in the text field.

              13. Logged in as Admin, cleared the value in the text field. 

              14. Logged in as Guest, ran "PSOS call"

                  Actual Result: "PSOS script" placed in the text field.

               

              Perhaps, I am missing a step to replicate?

               

              TSFalcon

              FileMaker, Inc.

              • 4. Re: Perform Script on Server failed
                EdgarRamirez

                Hello TSFalcon,

                Thanks for getting back.

                You will not be able to replicate this by changing the file, because the problem is not in the file, but in the Server.

                I installed this file in a Windows FM Server and PSoS executed successfully with all users. Therefore my assumption is that the authentication of ALL users, but the 'Guest', only fails on this server

                Mac OS X Yosemite 10.10.1 (no OS X Server)

                Filemaker Server 13.0.5

                Please review the screenshot with the messages from the Filemaker Server I posted above.

                 

                I do have a suspicion of what FMS might be doing:

                On the Mac Mini, previous to Yosemite with no OS X Server, this machine was running Mountain Lion WITH OS X Server.

                The machine was upgraded to Yosemite, to accommodate FMS 13. Because no services of the OS X Server 1.5.0 were ever used with Mountain Lion, OS X Server 4.0 was not installed with Yosemite. But I still can see the OS X Server icon in the dock, and Server.app is still in the Applications folder.

                Another feature that is currently not working from FMS 13 is email. email can not go out of the FMS 13 admin console. This is also a Server machine problem, because emails are sent successfully from FMP 13.

                I wonder if there might be some functionality for which FMS 13 is still looking for OS X Server or the machine is still redirecting these functionality through the OS X Server, which is still present, but not active in Yosemite.

                Could this be an issue?

                 

                If not, any other troubleshooting suggestions?

                 

                Thanks

                • 5. Re: Perform Script on Server failed

                  Edgar Ramirez: 

                   

                  Thank you for the reply.

                   

                  "the OS X Server, which is still present, but not active in Yosemite."

                   

                  FileMaker Server 13 is not compatible with the Server.app on Mac OS X 10.10 Yosemite, so if not in use, then the recommendation would be to remove the application. 

                   

                  "You will not be able to replicate this by changing the file, because the problem is not in the file, but in the Server."

                   

                  Help me to understand this part better. If the issue is specific to FileMaker Server 13, but not related to the database file, then uninstall and reinstall FileMaker Server 13.0v5 after removing the Server.app. 

                   

                  If the issue does not occur on a different machine (and removing and reinstalling does not resolve the issue), then this points to something in the specific computer environment.

                   

                  If another 10.10 computer is available, then is the issue reproducible on that machine?

                   

                  If the issue cannot be replicated in a new database file, then the file may be corrupt and I would suggest running recovery. 

                   

                  Additionally, I would recommend updating to Mac OS X 10.10.2.

                   

                  Please keep me updated with any progress. 

                   

                  TSFalcon

                  FileMaker, Inc.

                  • 6. Re: Perform Script on Server failed
                    EdgarRamirez

                    I clean installed the OS and FMS and PSoS works as expected now.

                    I really can not tell what the culprit was, but I can tell you that a clean install fixed this issue in my case.

                     

                    Thanks TSFalcon for responding