Problem with upgrading from Mirrorsync 4 to Mirrorsync 6

[sfpx]

I started the process by doing an initial sync on a device using the current installation of Mirrorsync 4.

I then installed Mirrorsync 6 and configured it.

I returned to my device and tried to sync.

I first got an error about insufficient privileges which I fixed by adding the api privilege to the sync privilege set.

Now I get an error 104

Configuration: xxxHub: xxx.direct / xxx (FileMaker Server)

Spoke(s): Demouser IPHONE( username 'demouser', running Go_appSDK 1.524 on xxx.xxx.xxx.xx, ping time: 67 ms, machine name: 'iPhone' )

 

Error when attempting to execute script on FileMaker database: xxx.direct / xxx (FileMaker Server); An error 104 occurred.

It's supposed to sync using Mirrorsync 4 scripts since the app has not been updated but it can't seem to find them for a mysterious reason.

 

Edited November 10, 2021 by sfpx

[Jesse Barnum]

Error 104 is missing script. It sounds like you may need to edit the configuration in MirrorSync 6 and make sure that all of the steps have been followed there.

[sfpx]

I have edited the Mirrorsync 6 configuration and finished it.

Here is the detailed error in the mirrorsync log

URL: https://mydb.direct/fmi/data/v1/databases/mydb/layouts/MirrorSync/script/MirrorSync 6 worker?script.param=Let( [%24command%3D"serverSync"%3B %24%24MIRRORSYNC_URL%3D"http%3A%2F%2Flocalhost%2FMirrorSync%2F"%3B %24%24MIRRORSYNC_URL_EXTERNAL%3D"http%3A%2F%2Flocalhost%2FMirrorSync%2F"%3B %24%24MIRRORSYNC_CONFIG_NAME%3D"mydb"%3B %24%24addressToTryFirst%3D"internal"%3B %24%24MIRRORSYNC_USERTOKEN%3D"demouser demouser DEMOHOLDING "%3B %24%24detailedLogging%3D1%3B %24%24isServer%3D1%3B %24%24hub%3D1%3B %24%24MIRRORSYNC_SCRIPTNAME%3D"MirrorSync 6 (mydb)"%3B %24%24syncStartId%3D"ec353dc3-a88c-447d-b5d2-ba22ef564f30"%3B %24%24sessionId%3D"fef6df86-03fe-4439-943d-b895d3177dc9"%3B %24%24MIRRORSYNC_HANDSHAKE_ONLY%3D0]%3B true )
    at com.prosc.fmapi.ApiRequest.checkCode(ApiRequest.java:249)

[Jesse Barnum]

Do you have a script in your solution, executable by your syncing user, named 'MirrorSync 6 (mydb)' ?

Also, do you have a script named 'MirrorSync 6 worker' ?

[sfpx]

Yes

It was required to edit the name of the script in the first step of ms 6 configuration

It should be executable by my syncing user since I edited his privilege set to run all executable scripts

Attached is the privilege set of the user

I changed it on the server but not on the device (could it be the problem ?)

[Jesse Barnum]

It should be changed on both the server file and the offline copy, although the error you've posted is specific to the server file.

Do you also have a script named 'MirrorSync 6 worker' on the server?

[sfpx]

Those scripts are on the server

The redacted part is the name of the database as it appears in the log 

Also, I was asked to insert the url in the script that I was asked to rename.

This screen is no longer there when I edit the configuration

If guess that it means that it's configured correctly.

 

Edited November 10, 2021 by sfpx

[sfpx]

Any idea on what to check or to send you ?

I'm currently stuck with no idea what to do.

[Jesse Barnum]

All I can think of to do is see if I can reproduce the problem. Could you send me an empty clone of the database, with admin credentials, and I'll see if I can reproduce the problem? Email to [email protected]. Also file a problem report using the MirrorSync launch page, this will send me your log file and an export of the configuration.

 

[sfpx]

1 minute ago, Jesse Barnum said:

All I can think of to do is see if I can reproduce the problem. Could you send me an empty clone of the database, with admin credentials, and I'll see if I can reproduce the problem? Email to [email protected]. Also file a problem report using the MirrorSync launch page, this will send me your log file and an export of the configuration.

 

I already filed the problem (ticket 126311)

I will check if I can send you a file shortly 

[sfpx]

I tested an initial sync.

If I use the mirrorsync 4 script I will get an error 104

If I use the mirrorsync 6 script it works (I get a schema changed warning at the beginning though).

Initial sync with ms6 seems slower than ms 4.

Took 15 minutes while my ms 4 initial sync this morning took 3 minutes (unusually fast though)

P.S.

I noticed an error in the config import.

I have a table that uses 2 primary keys...only the second one was imported in the ms6 config.