cancel
Showing results for 
Search instead for 
Did you mean: 

unable to synchronise the client with the server

Former Member
0 Kudos

Hi Everyone,

I get the folllowing error while trying to sync my MI client for the first time.

Synchronization started.

• Connection set up (without proxy) to: http://idesec7:50000/meSync/servlet/meSync?~sysid=ice&;

• Successfully connected with server.

• Processing of inbound data began.

• Internal server error; contact your system administrator.

any thoughts.....

Thanks in advance,

hima

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

After synchronising with the server i am not able to start the MIclient it gives the error as <b>"start failed"</b>. But before synchronising, MIclient was working fine.This error has occured when i tried to download and start the aplication as an end user.in the webconsole the status is displayed as <u>"delete with next synchronisation"</u>.will this status in the webconsole matter.

the detailed information is as follows:

DEPLID E7D34F0264E5F64BBD740CCECB688CE0

INSTALLATION_IMAGE NO

JAVA_VERSION 1.4.2_06

JVM_VENDOR Sun Microsystems Inc.

MI_FULLNAME MI 25 SP 09 Patch 00 Build 200409101427

OSARCHITECTURE x86

OSNAME Windows XP

OSVERSION 5.1

PROCESSOR pentium i486 i386

RUNTIME TOMCAT

USERS_ON_DEVICE MISYNC-00; TEST; MI_ADMIN; MI_USER

USER_TIMEZONE Asia/Calcutta

can anybody help me in this..

Former Member
0 Kudos

Hi Hima:

You are getting "start failed" because your conversation id is not correct.The easy fix to this is re-install the MI client.Synchronize atleast one to make sure your sync is working fine.Then assign the MI Application to to your device id(If the application is set to deploy in all devices then you should get this during your first sync).Re-SYnc to get the application.You should be fine.

Let me know if this fixes your problem.

Gisk

Former Member
0 Kudos

thank u stefan,

i have overcome this error.

Former Member
0 Kudos

Hi all,how did you overcome with this issue.I have a little different problem.MI sync url does not show anything to me.Our WAS (ABAP+JAVA) server is 'WEB',instance number is 00 and sid is EP0.

But this url "http://WEB:50000/meSync/servlet/meSync?~sysid=EP0&" does not show anything to me?Do you have any idea about what my problem is?

Best wishes..

Former Member
0 Kudos

Hi Sadettin

The url http://WEB:50000/meSync/servlet/meSync?~sysid=EP0&; won't show you anything. You have to write in information about username, password, client.....

Like this http://<Server>:<Port>/meSync/servlet/meSync?sysid=<SystemID>&login=<User

name>&password=<Password>&client=<Client>&language=<Language>&ackno

wledge=X&~test=true&

Morten

Former Member
0 Kudos

I see you , but "http://web:50000/meSync/servlet/meSync?sysid=ep0&login=MISYNC&password=MISYNC&client=000&language=en&acknowledge=X&~test=true& "

does not give any results either.

Former Member
0 Kudos

Ok

Have you created the property file?

Do you have the right authorizations?

Best Regards

Morten

Former Member
0 Kudos

Yes ,I created the property file in visual admin.Since our sistem id is ep0 we create ep0.props file and we write

ashost=web

sysnr=00 in the ep0.props file.

Afterwards I tried to run the snyc url with the user which I create in WAS ABAP with role MOBILE_SYNC-00. MOBILE_SYNC-00 role has S_RFC and S_ME_SYNC authorization objects.It that the correct one isnt it?

Former Member
0 Kudos

Hi Sadettin!

The authorization objects S_RFC and S_ME_SYNC are the correct ones.Also add S_TCODE to the role,you can set the values for S_TCODE per your requirement.

Also I suggest that you open a new topic describing your current problem.

Thanks

Gisk

Former Member
0 Kudos

Hi hima

I got the exact same error today, because I by mistake pointed the props file to the backbone and keyed in the ip of the backbone in the props file!

But from your own information your WAS system must then called Ep0 and the hostname is then web or maybe you made the same mistake?

BR

Rolf

stefan_schwing
Active Participant
0 Kudos

Hi,

check transaction st22 in the MI middleware, maybe a shortdump occured during synchronization.

Cheers, Stefan