cancel
Showing results for 
Search instead for 
Did you mean: 

AWT Application on WM 5.0

Former Member
0 Kudos

hi all,

I had installed AWT Client on WM 5.0 OS. The client starts fine. now, i deployed the uploaded Application i developed to my MI Client. After a device restart, when i click on the Application, i dont' get my apps screen.

This is the <b>TRACE </b> file i got from my device.

[20060818 08:01:51:852] I [MI/API/Logging ] ***** LOG / TRACE SWITCHED ON

[20060818 08:01:51:852] I [MI/API/Logging ] ***** Mobile Engine version: MI 25 SP 13 Patch 00 Build 200507282032

[20060818 08:01:51:852] I [MI/API/Logging ] ***** Current timezone: IST

[20060818 08:01:53:023] W [MI/Core ] The SSL support feature is not available.

java.lang.NoClassDefFoundError: com/sun/net/ssl/internal/ssl/Provider

at com.sap.ip.me.core.SslSupportConfiguration.initialize()

at com.sap.ip.me.core.SslSupportConfiguration.<init>()

at java.lang.Class.newInstance()

at com.sap.ip.me.core.SecurityManager.initializeSslSupport()

at com.sap.ip.me.core.SecurityManager.<init>()

at com.sap.ip.me.core.SecurityManager.<clinit>()

at com.sap.ip.me.core.UserImpl.<init>()

at com.sap.ip.me.core.UserManagerImpl.<init>()

at com.sap.ip.me.core.UserManagerImpl.<clinit>()

at com.sap.ip.me.core.FrameworkInitializer.initSingletons()

at com.sap.ip.me.core.FrameworkInitializer.initializeFramework()

at com.sap.ip.me.core.FrameworkInitializer.main()

at com.sap.ip.me.core.Startup.main()

Can some one help me out?

Regards

Arun

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

hello arun,

it seems that you have enable SSL support but you don't

have the necessary libraries in your MI. try adding the

necessary libraries into your MI or disabling the SSL

support.

check on your MobileEngine.config file for MobileEngine.Security.*

entries like MobileEngine.Security.SSLSupport.

see <a href="http://help.sap.com/saphelp_nw04/helpdata/en/1c/7bef3d5e10af5ee10000000a114084/frameset.htm">Parameters for Secure Sockets Layer (SSL) Support</a>

for details.

regards

jo

Former Member
0 Kudos

hi Jo,

Thanks for your reply. I disabled SSL support explicitly in mobile engine.config file. now, the Trace file is empty when i synchronize/download a apps to my mi client or when i click on an application. btw what are the required libraries to enable SSL support on my mobile device?

now, after i get the application to my client, when i click on it, NOTHING happens... but when i deploy a tutorial application, it shows in my screen. but the custom built apps which i developed is not working in WM 5.0. (it works on win32 client).

here's a trace file of <b>APPLOG</b>

<i>[20060818 04:00:23:413] W [MI/Security ] Error while creating MIAUTH sync bo (no SyncBoDescriptor for MIAUTH available); contact SAP support

[20060818 04:00:23:447] W [MI/Security ] Cannot start authority query for user because SyncBoDescriptor for MIAUTH is not available

</i>

I saw your answers from the previous posts u wrote for Madhan Mohan. as you had said, there is no DATA directory or LAST SYNC directory. could you suggest a workaround? i tried reinstalling it 4 times so far on my WM 5.0 OS.

Regards

~Ak

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Ravi

For SP17 full build please refer to my reply in post

You can obtain a full build for AWT version as well.

Best Regards

Sivakumar

Former Member
0 Kudos

hi,

i installed SP17 as said. Still the same problem persists. though the trace shows a different error this time.

i'll post the trace. Forgive me for its lentgh..

<i>[20060822 12:26:57:476] I [MI/API/Logging ] ***** LOG / TRACE SWITCHED ON

[20060822 12:26:57:476] I [MI/API/Logging ] ***** Mobile Engine version: MI 25 SP 17 Patch 00 Build 200605152040

[20060822 12:26:57:476] I [MI/API/Logging ] ***** Current timezone: IST

[20060822 12:27:12:467] E [AppLog/MI/API/Services ] java.io.WriteAbortedException: Writing aborted by exception; java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle

java.io.WriteAbortedException: Writing aborted by exception; java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle

at java.io.ObjectInputStream.readObject()

at java.io.ObjectInputStream.defaultReadObject()

at java.io.ObjectInputStream.inputObject()

at java.io.ObjectInputStream.readObject()

at java.io.ObjectInputStream.readObject()

at com.sap.ip.me.api.services.IOUtils.readSerializedObjectFromFile()

at com.sap.ip.me.api.services.IOUtils.readHashtableFromDirectory()

at com.sap.ip.me.sync.InboundProcessorRegistryImpl.<init>()

at java.lang.Class.newInstance()

at com.sap.ip.me.api.conf.Configuration.createInstanceForType()

at com.sap.ip.me.api.conf.Configuration.getSingletonInstanceForType()

at com.sap.ip.me.api.sync.InboundProcessorRegistry.<clinit>()

at com.sap.ip.me.smartsync.core.SmartSyncRuntimeManager.initializeSmartSyncFramework()

at com.sap.ip.me.core.FrameworkInitializer.initSmartSync()

at com.sap.ip.me.core.FrameworkInitializer.initializeFramework()

at com.sap.ip.me.core.FrameworkInitializer.main()

at com.sap.ip.me.core.Startup.main()

[20060822 12:27:40:120] E [AppLog/MI/API/Services ] Problems while saving /MI/sync/inboundProcessors/1.value

java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

at java.io.ObjectOutputStream.defaultWriteObject()

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

at com.sap.ip.me.api.services.IOUtils.serializeObjectToFile()

at com.sap.ip.me.api.services.IOUtils.saveHashtableToDirectory()

at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register()

at com.sap.ip.me.core.ApplicationManager.registerInboundProcessors()

at com.sap.ip.me.core.FrameworkInitializer.initializeFramework()

at com.sap.ip.me.core.FrameworkInitializer.main()

at com.sap.ip.me.core.Startup.main()

[20060822 12:27:43:055] E [AppLog/MI/API/Services ] Problems while saving /MI/sync/inboundProcessors/1.value

java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

at java.io.ObjectOutputStream.defaultWriteObject()

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

at com.sap.ip.me.api.services.IOUtils.serializeObjectToFile()

at com.sap.ip.me.api.services.IOUtils.saveHashtableToDirectory()

at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register()

at com.sap.ip.me.core.ApplicationManager.registerInboundProcessors()

at com.sap.ip.me.core.FrameworkInitializer.initializeFramework()

at com.sap.ip.me.core.FrameworkInitializer.main()

at com.sap.ip.me.core.Startup.main()

[20060822 12:27:45:105] E [AppLog/MI/API/Services ] Problems while saving /MI/sync/inboundProcessors/1.value

java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

at java.io.ObjectOutputStream.defaultWriteObject()

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

at com.sap.ip.me.api.services.IOUtils.serializeObjectToFile()

at com.sap.ip.me.api.services.IOUtils.saveHashtableToDirectory()

at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register()

at com.sap.ip.me.core.FrameworkInitializer.initializeFramework()

at com.sap.ip.me.core.FrameworkInitializer.main()

at com.sap.ip.me.core.Startup.main()

[20060822 12:29:42:049] E [AppLog/MI/API/Services ] Problems while saving /MI/sync/inboundProcessors/1.value

java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

at java.io.ObjectOutputStream.defaultWriteObject()

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

at com.sap.ip.me.api.services.IOUtils.serializeObjectToFile()

at com.sap.ip.me.api.services.IOUtils.saveHashtableToDirectory()

at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register()

at com.sap.ip.mi.systemnews.NewsImpl.create()

at com.sap.ip.mi.systemnews.StartListener.userLoggedOn()

at com.sap.ip.me.core.UserManagerImpl.fireLogon()

at com.sap.ip.me.core.UserManagerImpl.logOnUser()

at com.sap.ip.me.core.UserManagerImpl.logOnUser()

at com.sap.ip.me.awtapps.home.LoginDialog.actionOk()

at com.sap.ip.me.awtapps.home.LoginDialog.action()

at java.awt.Component.handleEvent()

at com.sap.ip.me.awtapps.home.AWTDialog.handleEvent()

at java.awt.Window.postEvent()

at java.awt.Component.postEvent()

at java.awt.Component.postEvent()

at java.awt.Component.dispatchEventImpl()

at java.awt.Component.dispatchEvent()

at java.awt.EventDispatchThread.run()

c.core.SmartSyncRuntimeManager.initializeSmartSyncFramework()

at com.sap.ip.me.core.FrameworkInitializer.initSmartSync()

at com.sap.ip.me.core.FrameworkInitializer.initializeFramework()

at com.sap.ip.me.core.FrameworkInitializer.main()

at com.sap.ip.me.core.Startup.main()

[20060822 12:28:53:197] E [MI/ComServer ] Exception while running communication server:

java.io.IOException: SysCall : bind() failed

at java.net.PlainSocketImpl.bind()

at java.net.ServerSocket.<init>()

at java.net.ServerSocket.<init>()

at com.sap.ip.me.core.CommunicationServer.run()

at java.lang.Thread.run()

[20060822 12:28:58:549] E [AppLog/MI/API/Services ] Problems while saving /MI/sync/inboundProcessors/1.value

java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

at java.io.ObjectOutputStream.defaultWriteObject()

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

at com.sap.ip.me.api.services.IOUtils.serializeObjectToFile()

at com.sap.ip.me.api.services.IOUtils.saveHashtableToDirectory()

at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register()

at com.sap.ip.me.core.ApplicationManager.registerInboundProcessors()

at com.sap.ip.me.core.FrameworkInitializer.initializeFramework()

at com.sap.ip.me.core.FrameworkInitializer.main()

at com.sap.ip.me.core.Startup.main()

[20060822 12:29:02:046] E [AppLog/MI/API/Services ] Problems while saving /MI/sync/inboundProcessors/1.value

java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

at java.io.ObjectOutputStream.defaultWriteObject()

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

at com.sap.ip.me.api.services.IOUtils.serializeObjectToFile()

at com.sap.ip.me.api.services.IOUtils.saveHashtableToDirectory()

at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register()

at com.sap.ip.me.core.ApplicationManager.registerInboundProcessors()

at com.sap.ip.me.core.FrameworkInitializer.initializeFramework()

at com.sap.ip.me.core.FrameworkInitializer.main()

at com.sap.ip.me.core.Startup.main()

[20060822 12:29:04:710] E [AppLog/MI/API/Services ] Problems while saving /MI/sync/inboundProcessors/1.value

java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

at java.io.ObjectOutputStream.defaultWriteObject()

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

at com.sap.ip.me.api.services.IOUtils.serializeObjectToFile()

at com.sap.ip.me.api.services.IOUtils.saveHashtableToDirectory()

at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register()

at com.sap.ip.me.core.FrameworkInitializer.initializeFramework()

at com.sap.ip.me.core.FrameworkInitializer.main()

at com.sap.ip.me.core.Startup.main()

[20060822 12:31:17:047] E [AppLog/MI/API/Services ] Problems while saving /MI/sync/inboundProcessors/1.value

java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

at java.io.ObjectOutputStream.defaultWriteObject()

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

at com.sap.ip.me.api.services.IOUtils.serializeObjectToFile()

at com.sap.ip.me.api.services.IOUtils.saveHashtableToDirectory()

at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register()

at com.sap.ip.mi.systemnews.NewsImpl.create()

at com.sap.ip.mi.systemnews.StartListener.userLoggedOn()

at com.sap.ip.me.core.UserManagerImpl.fireLogon()

at com.sap.ip.me.core.UserManagerImpl.logOnUser()

at com.sap.ip.me.core.UserManagerImpl.logOnUser()

at com.sap.ip.me.awtapps.home.LoginDialog.actionOk()

at com.sap.ip.me.awtapps.home.LoginDialog.action()

at java.awt.Component.handleEvent()

at com.sap.ip.me.awtapps.home.AWTDialog.handleEvent()

at java.awt.Window.postEvent()

at java.awt.Component.postEvent()

at java.awt.Component.postEvent()

at java.awt.Component.dispatchEventImpl()

at java.awt.Component.dispatchEvent()

at java.awt.EventDispatchThread.run()

</i>

Applog Trace

<i>[20060822 12:26:58:893] W [MI/Core ] The SSL support feature is not properly configured. Https is not available.

[20060822 12:27:12:436] E [MI/API/Services ] java.io.WriteAbortedException: Writing aborted by exception; java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle

[20060822 12:27:40:000] E [MI/API/Services ] Problems while saving /MI/sync/inboundProcessors/1.value (root cause: com.sap.ip.me.api.services.MEResourceBundle [java.io.NotSerializableException])

[20060822 12:27:43:000] E [MI/API/Services ] Problems while saving /MI/sync/inboundProcessors/1.value (root cause: com.sap.ip.me.api.services.MEResourceBundle [java.io.NotSerializableException])

[20060822 12:27:45:069] E [MI/API/Services ] Problems while saving /MI/sync/inboundProcessors/1.value (root cause: com.sap.ip.me.api.services.MEResourceBundle [java.io.NotSerializableException])

[20060822 12:29:42:000] E [MI/API/Services ] Problems while saving /MI/sync/inboundProcessors/1.value (root cause: com.sap.ip.me.api.services.MEResourceBundle [java.io.NotSerializableException])

[20060822 12:29:46:048] W [MI/Security ] Error while creating MIAUTH sync bo (no SyncBoDescriptor for MIAUTH available); contact SAP support

[20060822 12:29:46:114] W [MI/Security ] Cannot start authority query for user because SyncBoDescriptor for MIAUTH is not available

erializableException])

[20060822 12:29:02:000] E [MI/API/Services ] Problems while saving /MI/sync/inboundProcessors/1.value (root cause: com.sap.ip.me.api.services.MEResourceBundle [java.io.NotSerializableException])

[20060822 12:29:04:669] E [MI/API/Services ] Problems while saving /MI/sync/inboundProcessors/1.value (root cause: com.sap.ip.me.api.services.MEResourceBundle [java.io.NotSerializableException])

[20060822 12:31:17:000] E [MI/API/Services ] Problems while saving /MI/sync/inboundProcessors/1.value (root cause: com.sap.ip.me.api.services.MEResourceBundle [java.io.NotSerializableException])

[20060822 12:31:21:000] W [MI/Security ] Error while creating MIAUTH sync bo (no SyncBoDescriptor for MIAUTH available); contact SAP support

[20060822 12:31:21:040] W [MI/Security ] Cannot start authority query for user because SyncBoDescriptor for MIAUTH is not available

</i>

Regards

Arunkumar Ravi

Former Member
0 Kudos

Any body with any ideas on this?

Thanks

~Ak

prashantha_hj
Employee
Employee
0 Kudos

Hi Arunkumar,

It looks like MIAUTH syncbodescripto is not deployed by default for some reason in the Client. To check whether the Descriptor is deployed or not. go to the data

folder of your installation and check the folder "MI2853484152454429". It should contain dat files with name meta_topRow.dat, meta_childRow.dat, meta_field.dat and PROPERTIES.dat. These files are created when you first use the MI.

Please check whether you get any message like:

"Skipping deployment of AuthSyncBo because it is not enabled. ". in the trace file during first usage of MI. Please switch on the trace to level all before using MI by providing these parameters in the MobileEngine.config file with MobileEngine.Trace.Level = 1000. If you post the resulting trace file, I could help you further.

Regards,

Prashanth

Former Member
0 Kudos

Hi Ravi

I see that you are currently using SP13 of MI Client. Please use SP17 AWT Client for running MI on WM 5.0. Also make sure that the Creme version being usied on PDA is only Creme 3.27A and not older versions since they do not support WM5.0.

For SSL support you need install the cab file JSSE1-0-3_01.CAB present in SAP-MI-SSL-PACK.zip and the same can be downloaded from SAP serveice market place. If you are not able to download the same, add the following jar files in the \Windows\Creme\bin\ext folder - jcert.jar; jnet.jar; jsse.jar. These jar files can be download from the net. I will get back to you regarding the MIAUTH issue. Hope this helps.

Best Regards

Sivakumar

Former Member
0 Kudos

hi Sivakumar

> I see that you are currently using SP13 of MI

> MI Client. Please use SP17 AWT Client for running MI

> on WM 5.0.

Is SP17 a full version like SP 13 or is it an add on patching component?

And my CrEme version is 3.27A. i'll look for the SSL suppor files on service market place.

Thanks again.

~Arun.