Hi,

I have a nightly scheduled script running on a Mac FMP 9 Server. There is no External Authentication set up.

In FMP's Accounts & Privileges there is an account, "admin", that I need to change the password for. The problem: every time I change this password, the nightly script throws this error in the Logs and Email notifications:

-authentication failed on database "XYZ.fp7" using "admin".

Any idea how to stop this so I can change the password?

Many thanks,

Pat

Do you have more than one file in this system?

All your files need the same account name and passwords.

I noticed you said the "admin" account, normally the default full access account is "Admin". User names and passwords are case sensitive.

There are two files - Interface and Data. They have exactly matching user/pwd accounts.

I inherited this system, so am not sure why "admin" is lower-case. I have another full-access account I use instead of admin, but unfortunately FMP Server seems to be both using the admin account and staying stuck on the old password.

Thanks for the reply. Any other thoughts?

Please post the script and any sub-scripts, or better still post clones of your files.

IdealData,

Thanks for the offer of further help. Unfortunately I don't have permission to post the scripts. They're pretty standard stuff however.

P

OK, let's first clarify a couple of items. Passwords are case-sensitive. Account names are not, but it's a good idea to treat them as if they were.

Now, a few questions to help solve this issue:

1. Are you using the "Change Password" script step, or are you using the "Reset Account Password" step?

2. What Account did you tell FileMaker Server to use to run the script, and does that Account's privileges allow for changing passwords?

3. Finally, why are you doing this in the fashion you describe, as a server side script? That seems to me a bit unusual. But there may be a good reason for it.

Steven

Thanks Steven.

-All Accounts/PWDs match, including case.

-Not using "Change Password" or "Reset Account Password" script steps

-You ask: "What Account did you tell FileMaker Server to use to run the script?" I suspect this is the problem. Where do I set this preference?

-The script is a nightly maintenance script that archives off old records and creates certain new ones as required. It did have to be a scheduled script.

Regards,

Patrick

Select the scheduled script in FM Server (Scheduled Scripts). When you do you will notice below your login requirements for it.

LaRetta, that's the answer. Thank you!

Just to clarify for anyone else with this issue: I selected the Scheduled Script in FMP Server then chose to Edit the selected script option. The option to change the usr/pwd is right there in the first panel.

Thanks to all three of you for your help on this!

-Not using "Change Password" or "Reset Account Password" script steps

How are you proposing to change the password then, as you said you wanted to do?

Steven

The option to change the usr/pwd is right there in the first panel.

No, no, no. [color:red]That is not what that option is there to do. Its purpose is to supply an Account under which server will run the selected script server side. It does not change any passwords.

Steven

but unfortunately FMP Server seems to be both using the admin account and staying stuck on the old password.

I understood him to say he HAD changed the file password and the schedule script then began throwing errors. I thought I was clear that the schedule script must match ONE of the proper account/passwords in the file and THAT is what we were changing with my suggestion. :wink2:

Edited November 30, 200817 yr by Guest
Added quote

Hi All and sorry for any confusion!

LaRetta got me right.

I had changed the pwd on the "admin" account in both the db files and it was as a consequence of this that the server side scheduled script stopped working. It stopped working because the pwd in the field LaRetta pointed me to no longer matched the FMP User Account pwds.

Regards,

Patrick

I thought I was clear that the schedule script must match ONE of the proper account/passwords in the file and THAT is what we were changing with my suggestion

This is still not correct. The Account name under which the server runs the script server side must be matched to one in the file [color:red]whose privileges allow for the proper execution of the script, not just to any valid Account.

Glad that it appears to be working correctly now.

Steven

I understand, Stephen - I said it must be one of the PROPER accounts and Pat understood me perfectly.

OF COURSE it must be an account authorized to run the script ... that is true with ALL scripts. Anyone who uses privileges with scripts understands that. :wink2: