MI Client Installation Problems

[Former Member]

Hi,

I have installed

MI Version & SP Level -- MI 25 SP 13 (JSP )

- installation file type: -- setup.exe

- platform OS -- Windows XP

- JDK info -- j2sdk 1.4.2 08.

After installation i made an Entry into "MobileEngine.config"

MobileEngine.Sync.Gateway.Port=Server-Port

MobileEngine.Sync.Gateway.System=System-id

MobileEngine.Sync.Gateway.Host=Host-Name

then i started server using command Prompt startup.bat. I am able to see server running with the following Message

D:\MIJSP>startup

D:\MIJSP>set ME_HOME=D:\MIJSP

D:\MIJSP>set JAVA_OPTIONS=

D:\MIJSP>set JAVA_EXE=C:\j2sdk1.4.2_08\bin\java.exe

D:\MIJSP>set JAVA_HOME=C:\j2sdk1.4.2_08

D:\MIJSP>set bootstrapjars=;

D:\MIJSP>REM set bootstrapjars=D:\MIJSP\lib\system\crimson.jar;D:\MIJSP\lib\sy

stem\jaxp.jar;D:\MIJSP\lib\system\xalan.jar;

D:\MIJSP>REM SET JAVA_HOME=

D:\MIJSP>REM SET ME_HOME=

D:\MIJSP>REM SET JAVA_EXE=

D:\MIJSP>REM SET JAVA_OPTIONS=-mx256m

D:\MIJSP>SET _OLDCP=

D:\MIJSP>set _MEJARS=

D:\MIJSP>copy /b "D:\MIJSP\SetMejar.txt" + "D:\MIJSP\listOfJars.txt" "D:\MIJSP\s

etMeJar.bat"

D:\MIJSP\SetMejar.txt

D:\MIJSP\listOfJars.txt

1 file(s) copied.

D:\MIJSP>call "D:\MIJSP\setMeJar.bat"

D:\MIJSP>SET _MEJARS=D:\MIJSP\lib\crimson.jar;D:\MIJSP\lib\jasper.jar;D:\MIJSP\l

ib\jaxp.jar;D:\MIJSP\lib\MEg.jar;D:\MIJSP\lib\pinstall.jar;D:\MIJSP\lib\servlet.

jar;D:\MIJSP\lib\webserver.jar;D:\MIJSP\lib\xalan.jar;

D:\MIJSP>set _SSLJARS=

D:\MIJSP>if exist "D:\MIJSP\lib\jsse.jar" set _SSLJARS=D:\MIJSP\lib\jsse.jar

D:\MIJSP>if exist "D:\MIJSP\lib\jcert.jar" set _SSLJARS=;D:\MIJSP\lib\jcert.jar

D:\MIJSP>if exist "D:\MIJSP\lib\jnet.jar" set _SSLJARS=;D:\MIJSP\lib\jnet.jar

D:\MIJSP>set CLASSPATH=D:\MIJSP\lib\crimson.jar;D:\MIJSP\lib\jasper.jar;D:\MIJSP

\lib\jaxp.jar;D:\MIJSP\lib\MEg.jar;D:\MIJSP\lib\pinstall.jar;D:\MIJSP\lib\servle

t.jar;D:\MIJSP\lib\webserver.jar;D:\MIJSP\lib\xalan.jar;;;;;C:\j2sdk1.4.2_08\lib

\tools.jar

D:\MIJSP>echo Using CLASSPATH: D:\MIJSP\lib\crimson.jar;D:\MIJSP\lib\jasper.jar;

D:\MIJSP\lib\jaxp.jar;D:\MIJSP\lib\MEg.jar;D:\MIJSP\lib\pinstall.jar;D:\MIJSP\li

b\servlet.jar;D:\MIJSP\lib\webserver.jar;D:\MIJSP\lib\xalan.jar;;;;;C:\j2sdk1.4.

2_08\lib\tools.jar

Using CLASSPATH: D:\MIJSP\lib\crimson.jar;D:\MIJSP\lib\jasper.jar;D:\MIJSP\lib\j

axp.jar;D:\MIJSP\lib\MEg.jar;D:\MIJSP\lib\pinstall.jar;D:\MIJSP\lib\servlet.jar;

D:\MIJSP\lib\webserver.jar;D:\MIJSP\lib\xalan.jar;;;;;C:\j2sdk1.4.2_08\lib\tools

.jar

D:\MIJSP>"C:\j2sdk1.4.2_08\bin\java.exe" -DSERVER_IMPL="com.sap.tc.webdynpro.se

rverimpl.me.MEServerImplementation" -Duse.repository=noDB com.sap.ip.me.core.Sta

rtup "-home:D:\MIJSP"

Use the MobileEngine classloader

Collect jar: D:\MIJSP\lib\crimson.jar

Collect jar: D:\MIJSP\lib\jasper.jar

Collect jar: D:\MIJSP\lib\jaxp.jar

Collect jar: D:\MIJSP\lib\MEg.jar

Collect jar: D:\MIJSP\lib\pinstall.jar

Collect jar: D:\MIJSP\lib\servlet.jar

Collect jar: D:\MIJSP\lib\webserver.jar

Collect jar: D:\MIJSP\lib\xalan.jar

-

---

Initialize framework ...

Configuration initialized. Installation Base = D:\MIJSP

Path settings adjusted

Timezone initialized; use timezone id 'Europe/Berlin'

Trace initialized. Log is switched on.

Framework singletons initialized.

Gzip data compression configuration initialized.

Registry initialized.

MI OS installer lib (D:\MIJSP\bin\NATSTART.DLL) loaded successfully.

Dlls loaded.

Timed Sync initialized.

Persistence initialized.

Smart Sync initialized.

CCMS initialized.

Agents initialized.

Communication server initialized.

-

---

Framework initialized.

-

---

Check if running inside installation server.

Installation toolkit parameters D:\MIJSP/itool.properties not detected

Use normal startup: true

Starting tomcat. Check logs/tomcat.log for error messages

after that ,i started MI Client or double clicked MobileEngine.exe . I am getting Page Cannot be Displayed Error.

Please let me know ,am i missing any configuration settings.

Thanks a Lot

Madhan

[Former Member · Accepted solution]

Hi Madhan

The reason for the page not found error is that you are trying to run two instances of the MI at the same time i.e by executing startup.bat and MobileEngine.exe which is prevented by Tomcat server. Once you start MI using the Startup.bat file, you shouldnt execute MobileEngine.exe file. Instead you should open a browser window and execute http://localhost:4444/index.html.

Or execute MobileEngine.exe file without executing Startup.bat file

Hope this solves your problem

Best Regards

Sivakumar

[Former Member · Accepted solution]

Hello,

What should we do even if http://localhost:4444/index.html shows page can not display error message?

[Former Member · Accepted solution]

Hi

Thats strange!!! http://localhost:4444/index.html will only show a page not found error if MI has not started. Please open the DOS prompt and execute startup.bat file and check whether you get any errors or not. Ideally you should not. Sometimes you may get a classpath error which occurs when some class files fail to load. In such case please check you entries in listOfJars.txt file.

Hope this helps

Best Regards

Sivakumar

[Former Member · Accepted solution]

Yes,I run startup.bat using command line.It shows ".DLL) loaded successfully.

Dlls loaded.

Timed Sync initialized.

Persistence initialized.

Smart Sync initialized.

Error while initialize the framework: null

java.lang.NullPointerException

at com.sap.ip.me.services.os.Startup.runApps(Startup.java:109)

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

Initializer.java:258)

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

a:123)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

C:\Program Files\SAP Mobile Infrastructure>SET CLASSPATH=

How can I solve "Error while initialize the framework: null" problem?

Do you have any solution?

Also listofjars.txt contain ,

C:\Program Files\SAP Mobile Infrastructure\lib\crimson.jar;C:\Program Files\SAP Mobile Infrastructure\lib\jasper.jar;C:\Program Files\SAP Mobile Infrastructure\lib\jaxp.jar;C:\Program Files\SAP Mobile Infrastructure\lib\MEg.jar;C:\Program Files\SAP Mobile Infrastructure\lib\pinstall.jar;C:\Program Files\SAP Mobile Infrastructure\lib\servlet.jar;C:\Program Files\SAP Mobile Infrastructure\lib\webserver.jar;C:\Program Files\SAP Mobile Infrastructure\lib\xalan.jar;C:\Program Files\SAP Mobile Infrastructure\lib\db2ejdbc.jar;

I think it is OK?

[Former Member · Accepted solution]

Hi

This seems to be a bug. Can you please check if there exists a file called agents.properties under your settings folder. Also can you please paste the contents of the trace file(trace.txt)

Best Regards

Sivakumar

[Former Member · Accepted solution]

I have no files as agent.properties. When I want to start SAP Mobile Client it says Time out 61. Can not connect to server.

And here is the trace file.

[20060620 13:02:28:218] I [MI/API/Logging ] ***** LOG / TRACE SWITCHED ON

[20060620 13:02:28:218] I [MI/API/Logging ] ***** Mobile Engine version: MI 25 SP 15 Patch 00 Build 200512142038

[20060620 13:02:28:218] I [MI/API/Logging ] ***** Current timezone: Europe/Istanbul

[20060620 13:02:28:280] A [MI/Persistence ] com.sap.ip.me.core.PersistedDataUpgradeComponent miSyncDataVersionBeforeConversion is 251300

[20060620 13:02:28:280] A [MI/Persistence ] No upgrade necessary for com.sap.ip.me.core.PersistedDataUpgradeComponent because MI.Sync.DataVersion is 251300

[20060620 13:02:28:781] I [MI/Core ] The https protocol is able to run with the currently used java version: 1.4.2_08

[20060620 13:02:28:796] D [MI/Core ] System property javax.net.ssl.keyStore has value: C:\Program Files\SAP Mobile Infrastructure\settings\keystore

[20060620 13:02:28:796] D [MI/Core ] System property javax.net.ssl.trustStore has value: C:\Program Files\SAP Mobile Infrastructure\settings\truststore

[20060620 13:02:28:796] D [MI/Core ] SecurityManager: The following security providers are available:

[20060620 13:02:28:796] D [MI/Core ] Name: SUN, preference order: 1, info: SUN (DSA key/parameter generation; DSA signing; SHA-1, MD5 digests; SecureRandom; X.509 certificates; JKS keystore; PKIX CertPathValidator; PKIX CertPathBuilder; LDAP, Collection CertStores), version: 1.42.

[20060620 13:02:28:812] D [MI/Core ] Name: SunJSSE, preference order: 2, info: Sun JSSE provider(implements RSA Signatures, PKCS12, SunX509 key/trust factories, SSLv3, TLSv1), version: 1.42.

[20060620 13:02:28:812] D [MI/Core ] Name: SunRsaSign, preference order: 3, info: SUN's provider for RSA signatures, version: 1.42.

[20060620 13:02:28:812] D [MI/Core ] Name: SunJCE, preference order: 4, info: SunJCE Provider (implements DES, Triple DES, AES, Blowfish, PBE, Diffie-Hellman, HMAC-MD5, HMAC-SHA1), version: 1.42.

[20060620 13:02:28:812] D [MI/Core ] Name: SunJGSS, preference order: 5, info: Sun (Kerberos v5), version: 1.

[20060620 13:02:28:812] D [MI/Core ] SecurityManager: The following message digest algorithm was instantiated: SHA-1 Message Digest from SUN, <initialized>

[20060620 13:02:28:812] D [MI/Core ] SecurityManager: Selected synchronization password handling option: AtSync

[20060620 13:02:28:812] D [MI/API/Configuration ] null (root cause: null [java.lang.NumberFormatException])

[20060620 13:02:28:843] D [MI/Core ] New UserManager SINGLETON created : com.sap.ip.me.core.UserManagerImpl@15a8767

[20060620 13:02:28:859] P [MI/Core ] Set current application to 'Framework'

[20060620 13:02:28:968] D [MI/Core ] load conversation id 176EB66BA658CD47B23668F9ACD46510

[20060620 13:02:28:984] D [MI/Core ] load conversation id 03E9B5EB17196145B9B19E0993E1BEF1

[20060620 13:02:29:000] D [MI/Core ] load conversation id 19E00AF9B0B020409F1B04A15E51FCF6

[20060620 13:02:29:031] D [MI/Core ] load conversation id 4FE8C3EB9BA8CD4CBA0177B6B9427141

[20060620 13:02:29:031] D [MI/Core ] load conversation id D4A0AA68D9E1EF4BB32BE1417BE43DC5

[20060620 13:02:29:031] D [MI/Core ] load conversation id 863106AB9593D34C842657C72A0EE240

[20060620 13:02:29:046] D [MI/Core ] load conversation id 20C28975ABA38840ACD50BF27B0CDE2C

[20060620 13:02:29:046] D [MI/Core ] load conversation id MI2853484152454429

[20060620 13:02:29:046] D [MI/Core ] load conversation id MI50454c494e

[20060620 13:02:29:062] D [MI/Core ] load conversation id MI43524d524643

[20060620 13:02:29:062] D [MI/Core ] load conversation id 0C0D21BD9FC56F4BB292DD05716B64A5

[20060620 13:02:29:078] D [MI/Core ] load conversation id AA171B4F6252D54A96D9D499ACA05E29

[20060620 13:02:29:125] D [MI/API/Services ] Read Hashtable from directory C:\Program Files\SAP Mobile Infrastructure\sync\eventListeners

[20060620 13:02:29:265] D [MI/Core ] GzipDataCompressionConfiguration: GzipDataCompression is switched on.

[20060620 13:02:29:297] I [MI/Core ] MI OS installer lib (C:\Program Files\SAP Mobile Infrastructure\bin\NATSTART.DLL) loaded successfully

[20060620 13:02:29:297] I [MI/Core ] Libraries are loaded

[20060620 13:02:29:297] I [MI/API/Persistence ] Determined PersistenceImplementation (implementation / config paramter value): DB2E / DB2E

[20060620 13:02:29:406] D [MI/Core ] DB2e DLLs loaded

[20060620 13:02:29:531] D [MI/API/Services ] Read Hashtable from directory C:\Program Files\SAP Mobile Infrastructure\sync\inboundProcessors

[20060620 13:02:29:969] D [MI/API/Services ] Read Hashtable from directory C:\Program Files\SAP Mobile Infrastructure\sync\registeredMethods

[20060620 13:02:30:047] D [MI/Sync ] Start dumping of registered inbound processors (inboundProcessors)

[20060620 13:02:30:047] D [MI/Sync ] "WAF_INSTALLATION_LOG" --> com.sap.ip.me.core.InstallationLog

[20060620 13:02:30:047] D [MI/Sync ] "WAF_REGISTRY" --> com.sapmarkets.web.liTS.util.reg.RegistrySyncInboundProcessing

[20060620 13:02:30:047] D [MI/Sync ] "CLIENT_ALERT" --> com.sap.ip.me.ccms.AlertInboundProcessor

[20060620 13:02:30:047] D [MI/Sync ] "SYSTEMNEWS" --> com.sap.ip.mi.systemnews.InboundListener

[20060620 13:02:30:047] D [MI/Sync ] "CRMHH_SYNC_PLAYBACK" --> com.sap.crm.handheld.core.sync.response.UpSyncProcessor

[20060620 13:02:30:047] D [MI/Sync ] "DEVICEINFO" --> com.sap.ip.me.core.DeviceAttributeInboundProcessor

[20060620 13:02:30:047] D [MI/Sync ] "MI_SET_CLIENTTRACE" --> com.sap.ip.me.ccms.remotetracing.RemoteTracingInboundProcessor

[20060620 13:02:30:047] D [MI/Sync ] "AGENT_PARAMETERS" --> com.sap.ip.me.services.os.AgentManager$AgentInboundProcessor

[20060620 13:02:30:047] D [MI/Sync ] "SMARTSYNC" --> com.sap.ip.me.smartsync.core.SyncAdapter

[20060620 13:02:30:047] D [MI/Sync ] "CRMHH_SYNC" --> com.sap.crm.handheld.core.sync.response.DownSyncProcessor

[20060620 13:02:30:047] D [MI/Sync ] "CENTRAL_TRACING" --> com.sap.ip.me.sync.LogSenderInboundProcessor

[20060620 13:02:30:047] D [MI/Sync ] End of dump of registered inbound processors (inboundProcessors)

[20060620 13:02:30:047] D [MI/Sync ] Register inbound processor com.sap.ip.me.smartsync.core.SyncAdapter for method SMARTSYNC

[20060620 13:02:30:063] D [MI/API/Sync ] Do not register SyncEventListener com.sap.ip.me.smartsync.core.SyncAdapter@18d9850 for ConvId 176EB66BA658CD47B23668F9ACD46510

[20060620 13:02:30:063] D [MI/API/Sync ] Do not register SyncEventListener com.sap.ip.me.smartsync.core.SyncAdapter@18d9850 for ConvId 03E9B5EB17196145B9B19E0993E1BEF1

[20060620 13:02:30:063] D [MI/API/Sync ] Do not register SyncEventListener com.sap.ip.me.smartsync.core.SyncAdapter@18d9850 for ConvId 19E00AF9B0B020409F1B04A15E51FCF6

[20060620 13:02:30:078] D [MI/API/Sync ] Do not register SyncEventListener com.sap.ip.me.smartsync.core.SyncAdapter@18d9850 for ConvId 863106AB9593D34C842657C72A0EE240

[20060620 13:02:30:078] D [MI/API/Sync ] Do not register SyncEventListener com.sap.ip.me.smartsync.core.SyncAdapter@18d9850 for ConvId 20C28975ABA38840ACD50BF27B0CDE2C

[20060620 13:02:30:078] D [MI/API/Sync ] Do not register SyncEventListener com.sap.ip.me.smartsync.core.SyncAdapter@18d9850 for ConvId 4FE8C3EB9BA8CD4CBA0177B6B9427141

[20060620 13:02:30:078] D [MI/API/Sync ] Do not register SyncEventListener com.sap.ip.me.smartsync.core.SyncAdapter@18d9850 for ConvId D4A0AA68D9E1EF4BB32BE1417BE43DC5

[20060620 13:02:30:110] D [MI/API/Sync ] SyncEventListener com.sap.ip.me.smartsync.core.SyncAdapter@18d9850 was registered for key com.sap.ip.me.smartsync.core.SyncAdapter/MI2853484152454429

[20060620 13:02:30:110] D [MI/API/Sync ] Do not register SyncEventListener com.sap.ip.me.smartsync.core.SyncAdapter@18d9850 for ConvId MI50454c494e

[20060620 13:02:30:110] D [MI/API/Sync ] Do not register SyncEventListener com.sap.ip.me.smartsync.core.SyncAdapter@18d9850 for ConvId MI43524d524643

[20060620 13:02:30:141] D [MI/API/Sync ] SyncEventListener com.sap.ip.me.smartsync.core.SyncAdapter@18d9850 was registered for key com.sap.ip.me.smartsync.core.SyncAdapter/0C0D21BD9FC56F4BB292DD05716B64A5

[20060620 13:02:30:188] D [MI/API/Sync ] SyncEventListener com.sap.ip.me.smartsync.core.SyncAdapter@18d9850 was registered for key com.sap.ip.me.smartsync.core.SyncAdapter/AA171B4F6252D54A96D9D499ACA05E29

[20060620 13:02:30:188] D [MI/Smartsync ] Smart Sync Framework successfully initialzed.

[20060620 13:02:30:235] D [MI/API/Sync ] SyncEventListener com.sap.ip.me.ccms.AlertManagerImpl@b5dac4 was registered for key com.sap.ip.me.ccms.AlertManagerImpl/MI2853484152454429

[20060620 13:02:30:235] D [MI/Sync ] Register inbound processor com.sap.ip.me.ccms.AlertInboundProcessor for method CLIENT_ALERT

[20060620 13:02:30:313] D [MI/API/Sync ] SyncEventListener com.sap.ip.me.ccms.LastSuccessfulSyncAlert@1ff0dde was registered for key com.sap.ip.me.ccms.LastSuccessfulSyncAlert/MI2853484152454429

[20060620 13:02:30:391] I [MI/Services/Os ] Error:.java.lang.NullPointerException

[Former Member · Accepted solution]

Hi Pg

I too had the same problem and the same problem

along with that request Time out 61 it will also give u

one file name <b>some .msi file</b> missing .

If you have another client then please check for the file in that client and copy that file put the file in the same location of ur defective client and then restart the MI client this should work

or else u just need to reinstall the client

bye

sid

[prashantha_hj]

Hi Madhan,

It looks like you have a "startup.properties" file

in %MI_HOME%/settings folder. But you do not have any

startup properties in the file. If you are not using any

startup application, delete this file and start the MI.

Otherwise specify proper startup property.

I reproduced the error you have mentioned in the Topic but in some other SP.

Persistence initialized.

Smart Sync initialized.

Error while initialize the framework: null

java.lang.NullPointerException

at com.sap.ip.me.services.os.Startup.runApps(Startup.java:110)

at com.sap.ip.me.core.FrameworkInitializer.initializeFramework(FrameworkInitializer.java:376)

at com.sap.ip.me.core.FrameworkInitializer.main(FrameworkInitializer.java:128)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

Regards,

Prashanth

[Former Member]

Dear Madan

I see that ur tring to change these

MobileEngine.Sync.Gateway.Port=Server-Port

MobileEngine.Sync.Gateway.System=System-id

MobileEngine.Sync.Gateway.Host=Host-Name

U can directly give these entries in the settings

why do u need to change these in setup can u please let me know

bye

sid