ABAP sync service exception

[Former Member]

Hi,

After configuring the ABAP sync service (client and server side), I get the following synchronisation error in the client.

Synchronization Log

Synchronization Log

• Synchronization started

• Connection set up (without proxy) to: http://SODPSAPDKXXX.ODP.XXX.NET:50100/sap/bc/MJC/mi_host?~sysid=BAD&;

• Connection to server failed.

• Error: cannot connect (java.io.FileNotFoundException: http://SODPSAPDKXXX:50100/sap/bc/MJC/mi_host?_sysid=BAD&client=100&~language=EN&ACKNOWLEDGE=&)

Some parts of the host name has been replaced by XXX

For information, the service in SCIF has been activated and the .config file on the client has been modified with the two new parameters.

Regards

Jacob

[Former Member]

Hi Jacob,

Did you give the correct synchronization password in client.

Synchronization password should be the same as in the ABAP stack.

I hope you did not get the device id?

Cheers,

Karthick

[Former Member]

Hi Karthick

Yes this is correct. Previously, the sync. were using the JAVA stac but now after upgrade to SP 19 we want to use the ABAP stack. So passwords are working fine.

No device ID given :o(

regards Jacob

[Former Member]

Hi Jocab,

You can do this by following the steps below.

1. Start transaction SICF.

2. Enter MJC as the service name and choose Execute. The path default_host/sap/bc/MJC is opened.

3. Open the node MJC and right click the service mi_service, check whether it is activated. After this check for mi_host, whether it is activated.

Also, please check if the user has the authorization S_ME_SYNC.

Once above mentioned steps are done.click on Test Service and you will be asked a windows prompt to enter your middleware user name and password for authentication. Once you are authenticated, a text MISYNC along with some XML parse errors will be displayed in your browser. Ignore the XML error and what is important is the text MISYNC being displayed in the browser. Now ABAP Sync Service is configured and this should solve your problem during synchronization.

Cheers,

Karthick

[Former Member]

Hi Karthick,

This is already done. Found that the port were wrong - it is not the JAVA port anymore but the ABAP port (8001).

Thanks for your help

/Jacob