Error 959 During Configuration Process

August 16, 201213 yr

Hi,

During the process of attempting to configure Mirror Sync, when we attempt to choose the database name, we receive an error 959, Unknown error. This error tells us it is unable to load the database names and we cannot proceed.

We have confirmed the following:

1) XML is enabled on FMS

2) The FM account we are attempting to access has XML enabled

3) We have re-started the FMS machine and the status shows XML is activated.

Any ideas on how to troubleshoot this issue?

Thanks,

Paul

October 18, 201213 yr

Newbies

was getting the same error.... had to uninstall MirrorSync... then config FM Server for web pub. properly. then reinstall MirrorSync.

May 21, 20196 yr

Also running MirrorSync and today all of the sudden got this 959 error. Uninstalling MS and reconfiguring the FMS 16 server did not work. I had to uninstall everything and reinstall from scratch.

May 21, 20196 yr

The 959 error is coming from FileMaker when MirrorSync makes a request to FileMaker Server via XML. When FileMaker responds with 959, that means the Custom Web Publishing technology has been disabled. On FileMaker Server 16, you still have the ability to redeploy the FileMaker Server. FMS < 16 we recommend redeploying before totally uninstalling everything. FMS 17 if CWP is unresponsive then one of your only choices is to uninstall > reinstall. The only reason why you need to reinstall MirrorSync is to put the port re-write in place from port 42424 to port 80. You shouldn't have to uninstall though. You can just run the installer again. Hope this helps!

Joshua

360Works

May 21, 20196 yr

Redeploying FMS 16 (via the Edit Deployment) did not work for me, had to do a complete uninstall and re-install of FMS 16. Then reinstall MS. Specifically the following was done in this order.

1 - Reboot - still did not respond giving 959.

2 - Try Redeploy - still did not respond giving 959.

3 - Reboot after Redeploy - still did not respond to giving 959.

4 - Uninstall MS, reboot then redeploy, - still did not respond to giving 959.

5 - Uninstall FMS, reboot, then re-install FMS and then MS - success, no more 959!

To be clear this was not an MS specific issue, as it was the FileMaker XML engine basically broke randomly (after months of working fine), but thought it would be useful to post here as this was one of the top Google hits for the 959 error.

Daniel