Problem during synchronization

[Former Member]

HI

iam using MI 7.0 sp 15 patch 1 ,windows mobile 6.0 and when iam synchronizing for the first time,

iam getting an error message in the emulator

Problem during Synchronization:Format of the synchronization inbound file is not supported;Check sync gateway

can any one tell me how to resolve this issue.

Thanks and regards

Manohar

Edited by: Gouri Manohar Gadhamsetty on Jan 7, 2009 2:03 PM

[Former Member · Accepted solution]

Hello Gauri,

Would you please provide the trace file for analysis?

However at prima-facie it appears like a Network issue (check sync gateway- This is at the application layer of the Network)

Please check the MI Client Settings and sync again.

Take the trace and paste it.

Please award points if the suggestions are useful.

Thanks

Himanshu Limaye

[Former Member]

Hi Gauri,

Please attach the trace file so that we may analyse.

[Former Member]

[20081226 14:18:20:000] I [MI/API/Logging ] ***** LOG / TRACE SWITCHED ON

[20081226 14:18:20:000] I [MI/API/Logging ] ***** Mobile Infrastructure version: MI 70 SP 15 Patch 1 Build 200806121101

[20081226 14:18:20:000] I [MI/API/Logging ] ***** Current timezone: PST[20081226 14:18:20:000] I [MI/API/Logging ] ***** Current Trace Level: 50

[20081226 14:18:25:196] E [AppLog/MI/Sync ] Container can not be written to the outbound file

java.io.FileNotFoundException: /MI/sync/(SHARED)/out/a000012w.sync

at java.io.FileOutputStream.<init>()

at java.io.FileOutputStream.<init>()

at com.sap.ip.me.sync.out.SyncOutboundContainer.writeOutboundContainer()

at com.sap.ip.me.sync.out.SyncOutboundContainer.close()

at com.sap.ip.me.sync.out.ContainerFactory.createAcknowledgeContainer()

at com.sap.ip.me.sync.SyncManagerImpl.processSingleContainer()

at com.sap.ip.me.sync.SyncManagerMerger.processInboundContainers()

at com.sap.ip.me.sync.SyncManagerImpl.processSyncCycle()

at com.sap.ip.me.sync.SyncManagerImpl.syncForUser()

at com.sap.ip.me.sync.SyncManagerImpl.processSynchronization()

at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()

at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()

at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend()

at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run()

at java.lang.Thread.run()

[20081226 14:18:27:478] E [AppLog/MI/Sync ] Container can not be written to the outbound file

java.io.FileNotFoundException: /MI/sync/(SHARED)/out/a000012x.sync

at java.io.FileOutputStream.<init>()

at java.io.FileOutputStream.<init>()

at com.sap.ip.me.sync.out.SyncOutboundContainer.writeOutboundContainer()

at com.sap.ip.me.sync.out.SyncOutboundContainer.close()

at com.sap.ip.me.sync.out.ContainerFactory.createAcknowledgeContainer()

at com.sap.ip.me.sync.SyncManagerImpl.processSingleContainer()

at com.sap.ip.me.sync.SyncManagerMerger.processInboundContainers()

at com.sap.ip.me.sync.SyncManagerImpl.processSyncCycle()

at com.sap.ip.me.sync.SyncManagerImpl.syncForUser()

at com.sap.ip.me.sync.SyncManagerImpl.processSynchronization()

at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()

at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()

at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend()

at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run()

at java.lang.Thread.run()

[20081226 14:18:29:511] E [AppLog/MI/Sync ] Container can not be written to the outbound file

java.io.FileNotFoundException: /MI/sync/(SHARED)/out/a000012y.sync

at java.io.FileOutputStream.<init>()

at java.io.FileOutputStream.<init>()

at com.sap.ip.me.sync.out.SyncOutboundContainer.writeOutboundContainer()

at com.sap.ip.me.sync.out.SyncOutboundContainer.close()

at com.sap.ip.me.sync.out.ContainerFactory.createAcknowledgeContainer()

at com.sap.ip.me.sync.SyncManagerImpl.processSingleContainer()

at com.sap.ip.me.sync.SyncManagerMerger.processInboundContainers()

at com.sap.ip.me.sync.SyncManagerImpl.processSyncCycle()

at com.sap.ip.me.sync.SyncManagerImpl.syncForUser()

at com.sap.ip.me.sync.SyncManagerImpl.processSynchronization()

at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()

at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()

at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend()

at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run()

at java.lang.Thread.run()

[20081226 14:18:31:880] E [AppLog/MI/Sync ] Container can not be written to the outbound file

java.io.FileNotFoundException: /MI/sync/(SHARED)/out/a000012z.sync

at java.io.FileOutputStream.<init>()

at java.io.FileOutputStream.<init>()

at com.sap.ip.me.sync.out.SyncOutboundContainer.writeOutboundContainer()

at com.sap.ip.me.sync.out.SyncOutboundContainer.close()

at com.sap.ip.me.sync.out.ContainerFactory.createAcknowledgeContainer()

at com.sap.ip.me.sync.SyncManagerImpl.processSingleContainer()

at com.sap.ip.me.sync.SyncManagerMerger.processInboundContainers()

at com.sap.ip.me.sync.SyncManagerImpl.processSyncCycle()

at com.sap.ip.me.sync.SyncManagerImpl.syncForUser()

at com.sap.ip.me.sync.SyncManagerImpl.processSynchronization()

at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()

at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()

at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend()

at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run()

at java.lang.Thread.run()

[20081226 14:18:35:000] E [AppLog/MI/Sync ] Container can not be written to the outbound file

java.io.FileNotFoundException: /MI/sync/(SHARED)/out/a0000130.sync

at java.io.FileOutputStream.<init>()

at java.io.FileOutputStream.<init>()

at com.sap.ip.me.sync.out.SyncOutboundContainer.writeOutboundContainer()

at com.sap.ip.me.sync.out.SyncOutboundContainer.close()

at com.sap.ip.me.sync.out.ContainerFactory.createAcknowledgeContainer()

at com.sap.ip.me.sync.SyncManagerImpl.processSingleContainer()

at com.sap.ip.me.sync.SyncManagerMerger.processInboundContainers()

at com.sap.ip.me.sync.SyncManagerImpl.processSyncCycle()

at com.sap.ip.me.sync.SyncManagerImpl.syncForUser()

at com.sap.ip.me.sync.SyncManagerImpl.processSynchronization()

at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()

at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()

at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend()

at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run()

at java.lang.Thread.run()

[Former Member]

Dear Manohar,

1. Since you are synchronizing through emulator, you shoul make sure that your emulator is cradled and connected to Activesync via DMA mode.

2. If you have already taken care of my first point, are you connecting to the sever via host name or IP?

3. If you are accessing through hostname, then you should be able to ping to the server using hostname from your PC for it to be accessible to the emulator.

Regards,

Veera

P.S.: Accessing servers not on network domains through host names may require host entries in host file under WinDrive:\system32\drivers\etc.

[Former Member]

HI

we are accessing through the host name and we have assigned the IP address to the Middle ware URL in host.

but still we are facing the problem.

Regards

Manohar

[Former Member]

Dear Manohar,

Did you check the transaction merep_mon? Is your device visible? The best way to check would be to try starting a new sync from PDA and check the server with initial time as current time.

Also make sure that two instances of creme.exe are not running in your emulator. This is because the container is not able to right to outbound file, may be there is a lock on that file which can arise out of multiple instances. You can check the same using a freeware task manager for windows mobile (www.dotfred.net)

You have not replied about your activesync connection, I hope that your firewall policy is not blocking any activesync port.

Regards,

Veera

[Former Member]

HI,

i have checked with MEREP_MON it is saying that no work list found.

Actually tow instances of creme.exe are running and i have removed both the creme.exe and installed creme3.72a still iam getting the same error message.

and regarding active sync it is connected.

thanks in advance

regards

Manohar

[Former Member]

Dear Manohar,

Make sure that only one instance of creme.exe is running while you try to sync (the single running instance of CrEme should have around 23-27 threads - dont worry if there are more threads). I feel it is a problem of lock on the files since you are note able to write to them. You can try soft resetting the emulator. Also you can go and check in \Windows\Startup folder in emulator for the number of MI related shortcuts. There should be one shortcut related to MI according to your installation (for reference: it is MobileEngine.lnk for 2.5 and MI Server.lnk for 7.0)

Regards,

Veeraraagavan

[Former Member]

hi veeraragavan,

Can you explain in brief

manohar

[Former Member]

Dear Manohar,

Threads:

I mean the number of threads (at least around 20 in number) you see against the creme.exe in Task Manager.

Lock concept I am trying to explain:

When MI's runtime is started, the MI services lock down the files in the MI directory. So if two instance of MI exist, there exists a lock clash between them and hence one instance may not be able to write on to files locked by other instance (Note: here creme.exe is like javaw.exe / java.exe in windows which is used to lauch the tomcat).

Regards,

Veera

[Former Member]

Hi veeraragavan,

Even when iam using the single instance of CrEme even i could not able to get the item table informations and does it is mandatory to install MaxDb in the emulator to resolve this issue or is there any other alternative for this.

Regards

Manohar

[Former Member]

Dear Manohar,

You must install DB2e 8.2.4 (MI2.5 < SP21/ NW7.0 <14) and DB2e9.x for higher SPs.

For Mobile 7.1 you should use either DB2e9.x/Min DB (for PDA) / MaxDB 7.6 (desktop).

Please be informed that you must use a related DB instance compulsorily for the Mobile Offline Smart Sync/Generic Sync app to work properly.

Regards,

Veera

[Former Member]

Hi,

so it is implied that i have to install MaxDB2 in the windows emulator.And actually i have followed this link

so can you please explain this senario.

Thanks and Regards

Manohar

[Former Member]

Dear Manohar,

Please understand that Max DB and IBM's DB2 Everyplace (DB2e) are different databases.

Yup, that thread gives you the general overview. Just take care of the versions according to your server/client SP level.

Check the following note for proper versions of DB2e:

1. For 2.5/7.0: 677476

2. For 7.1: 1121247

Regards,

Veera

P.S.

Additional info:

For NetWeaver Mobile 7.1 with Data Orchestration Engine we can use either the default MaxDB 7.6(Desktop)/MinDB(PDA) or DB2e9.x

[Former Member]

HI veera

does the file which i am going to download with the help of the purticular note will it give me a .cab file so that i can install it in my emulator

and as i already gave you a link which helped me to download SAP_DB2_SDK has gave me a .zip file which i could not able to install neither in desktop nor in emulator

thanks and regards

Manohar

Edited by: Gouri Manohar Gadhamsetty on Jan 13, 2009 2:04 PM

[Former Member]

Dear Manohar,

You have to deploy the zip file to your MI server as Add On component and assign it to the device. Please note that only framework must be there before assigning DB2e to the device - No Generic Sync or Smart Sync application should be there. After DB2e deployment, any Mobile application can be assigned to the device.

Regards,

Veera