Hi,

when upgrading vom Mirrorsync 5.x to 6.03 the installation failed.

This was on a Windows Server 2016 Datacenter, FMS 17

When I try to start the 360Works Admin Console on the server the Error as in Image 2 occurs.

(I think this is just because the installation did not work.)

Does anybody have a tipp for me ?

Kind regards

Carsten

Hi Carsten,

 

We have had a few others report this issue this morning. I am trying to reproduce it as we speak. I will bump this thread as soon as I have more information or a fix

 

Hi Carsten,

Please use this build and let us know if you have any issues getting it installed.

Thx a lot, it worked.

What confuses me right now a bit, is that the SQL sync now uses the data api and I don't know if the usage will be a higher than our limit is there ...

MS 6 does use the data API but the amount used is negligible. Actual data transfer is done via the native script step Insert from URL on the FMS side and the SQL database JDBC driver on the SQL side so using MS 6 will not really have any impact to your yearly data allocation.