WIN CE5.0 + ME 2.1 sp03 + MAM2.5 = PROBLEM

[Former Member]

Hello,

We've been using MAM 2.5 with Windows Mobile 2003SE for six months without any problems

Now we've bought several brand new PDAs with Windows Mobile 2005 and faced some issues:

1. The version of Creme JVM did not work on the new version of Windows Mobile.(After consulting with nsi's support team we've downloaded and installed CrEme326_ARM_CE50_PPC.CAB which fixed this issue)

2. After deploying MAM2.5 and all the nescessary upgrades on ME 2.1, MAM2.5 failes to star:

 NOT Found (404)
original request: /MAM25/start
Nor found request: /MAM25/start

Any comments would be at help

[/code]

Kind Regards,

Martin Radev

[Former Member]

Hello, Martin,

I've had exactly the same problem using WIN CE5.0 + ME 2.1 sp03 + MAM2.0.

using http:/localhost Iget the Error:500 message you posted.

Did you come to find a fix? I would appreciate if you could guive me a hand.

[Former Member]

No progress at all.. which a little bit embarrasses me, because i can not use MAM 2.5 with new Pocket PCs

Message was edited by: Martin Radev

[Former Member]

Hi All,

I am also getting the error below. I get it on a Windows Mobile 2003 SE device. It was working, but when I gave the PDA a softreset the error occurs. Does anyone know anything how to resolve this issue?

Some people refers to an xml file in the windows\its\nt folder or something, but this folder is not located on my device, and I don't know where I can download this XML file.

Can someone help me with this problem?

Thanks in advance,

Bart Elshout

[code]Error: 500

Location: /MAM25/home/home_mgmt.do

Internal Servlet Error:

javax.servlet.ServletException: cannot find message associated with key : dispatcher.forwardException

at org.apache.tomcat.facade.RequestDispatcherImpl.doForward()

at org.apache.tomcat.facade.RequestDispatcherImpl.forward()

at org.apache.jasper.runtime.PageContextImpl.forward()

at mam_0005fstart._jspService()

at org.apache.jasper.runtime.HttpJspBase.service()

at javax.servlet.http.HttpServlet.service()

at org.apache.tomcat.core.ServletWrapper.doService()

at org.apache.tomcat.core.Handler.service()

at org.apache.tomcat.core.ServletWrapper.service()

at org.apache.tomcat.core.ContextManager.internalService()

at org.apache.tomcat.core.ContextManager.service()

at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection()

at org.apache.tomcat.service.TcpWorkerThread.runIt()

at org.apache.tomcat.util.ThreadPool$ControlRunnable.run()

at java.lang.Thread.run()[/code]

[prashantha_hj]

It looks like, some resource bundles are missing. please can you check if you have resource bundle files in folder WEB-INF/classes directory of MAM.

You can find out actual error if you paste /home/home_mgmt.do at the end of the URL, you will get the actual error.

Regards,

Prashanth

[Former Member]

Hi Prashanth,

The resource bundles are still available. When I replace start for /home/home_mgmt.do I get the following error:

<b>Internal Servlet Error:</b>
java.lang.NoClassDefFoundError:
com/sap/mbs/tools/list
PageBuilder
  at
com.sap.mbs.mam.application.web.FrontServlet.init()
  at
.....

In the FrontServlet.init() there are two things done using the PageBuilder:

- com.sap.mbs.tools.list.PageBuilder.setDisplayBundle(prop);

- com.sap.mbs.tools.list.PageBuilder.setTextBundle(getResourceBundle());

So it can be a problem with the resource budles, but they are available in the WEB-INF/classes folder of MAM

My application was up and running on this PDA for 1 month, but suddenly this error occurs, without doing any special handlings.

Do you have more ideas what could be the problem? I hope you could help me.

Thanks in advance,

Bart Elshout

[Former Member]

hello bart,

i think mam serializes some data into a file. if you can find those "corrupted" files

and try to delete them, this might fix the problem. one way is to compare a fresh

installation with an existing installation on which files were created later.

regards

jo

[prashantha_hj]

Hi Bart,

As "Jo" has mentioned, there are some User specific files that get created by MAM in data/$USER folder. can you delete those file and check. (please take the backup of these files before deleting.. )

If it does not solve the problem, please paste the complete error message.

Regards,

Prashantha

[Former Member]

Any other ideas?

[Former Member]

Hi Martin,

I tested MI sp13 client on WM2005 myself, and my problem is the same as you mentioned in your previous responses, the browser doesnt recognize the 127.0.0.1 and when i check the system messages i found that the looparound is not being installed and is throwing an error.

If you find a fix please let me know.

Thanks,

Wael Aoudi

[Former Member]

hi

To avoid this error, use the attached file control.zip as follows:

1. Download and extract the file control.zip.

2. Replace the old CONTROL.XML file during the installation:

If you use the Server Components CD, start the installation as described in the installation guide and cancel the installation exactly at the point, where the Welcome screen offers the ITS installation.

Then replace the old control.xml in your SAPinst_InstDir with the one you have downloaded and start the installation from command line with the command:

sapinst

If you have downloaded an ITS patch, just replace the old CONTROL.XML with the one you have downloaded. The file is located at:

On Windows: :\ITS\NT\

you could refer to this note <b>0188427</b>

regards

Arun

[Former Member]

HEllo Arun,

thanks for the responce, but unfortenately this is not our case. - the problem concerns Pocket PCs (pdas) with Windows Mobile 2005 operating system...

Greetings,

Martin

[Former Member]

Hi Martin,

MI is planning to support Windows Mobile 2005 with MI 2.5 SP16 and ME 2.1 SP03 PL10. For details please check the PAM of the specific release which will be available on service.sap.com. As of now, MI 2.5 SP 15 is the latest release which does not run on WM 2005.

Regards,

Rahul

[Former Member]

Thank you for the responce!

Is there any information when is expected ME 2.1 SP03 PL10 ? I couldn't find any in the Product Availabality Matrix.

Regards,

Martin

[Former Member]

Hi Martin,

Sorry, but I have no idea when ME 2.1 SP03 PL10 will be released. I currently using MI 2.5 SP14 PL02 and not keeping any track of ME components. I suggest you to enquire on service.sap.com for the same.

A Product Availabality Matrix describes which features are available with diff versions which are already released. So I guess it will help you little in knowing when what will be out. Anyways if you want it, you will definitely find on service.sap.com. Only thing is that you will not find it easily.

Regards,

Rahul

if this helps, don't forget to assign me some points

[Former Member]

hello martin,

just a confirmation.

is mam2.5 using MI 2.5 APIs? if it is, then it is likely

to fail coz there are some APIs in 2.5 that are not in 2.1

regards

jo

[Former Member]

hello Jo Gel Santiago,

Everything worked just fine on WindowsMobile 2003.

Is it possible the problem is that WM 2005 uses LOCALHOST instead of 127.0.0.1? (it doesn' recognize/resolve 127.0.0.1 at all)

[Former Member]

hello martin,

i don't have a WM2005 device thus i can't confirm this.

but this blog seems to talk about the same problem.

http://blogs.msdn.com/cenet/archive/2005/06/06/425799.aspx

In PPC2003, there's a workaround to for http://localhost

connection. Refer to the following link. Maybe it will

work with WM2005 as well. (The link should be in one line)

http://groups.google.com/group/microsoft.public.pocketpc.developer/msg/b43b2355b36d73bf?q=

(localhostOR127.0.0.1)+group:microsoft.public.pocketpc.developer.*&hl=en&lr=&ie=UTF-8&rnum=3

regards

jo

[Former Member]

Hello Jo Gel Santiago,

Everything you've written is true, but unfortenutely this is not a problem we have with WM 2005

This issue is still not solvet.

Regards,

Martin

[Former Member]

hello martin,

is your problem in wm2005 the number 2 issue?

>2. After deploying MAM2.5 and all the nescessary upgrades

>on ME 2.1, MAM2.5 failes to star:

>

> NOT Found (404)

>original request: /MAM25/start

>Nor found request: /MAM25/start

here can be some of the cause:

1) network connection problem

-> the http://localhost sometimes cause the PIE to

search for external hosts and not to that device itself.

this seems related to the connection manager of the

device. (i can't confirm this though as i don't have

a wm2005 unit).

try putting your device in the cradle and access

http://localhost:4444

2) missing descriptor entry

-> do you have a mapping for the /start url in the

web descriptor?

3) Inconsistent WAR archive file name

-> the WAR archive file name will be the context of your

application. and this should be consistent with the MCD

and the returned String for the method getApplicationName().

regards

jo

[Former Member]

Hello Jo,

So.. i`ve editted the MobileEngine.config file and changed:

[code]MobileEngine.Runtime.Host=127.0.0.1[/code]

to

[code]MobileEngine.Runtime.Host=localhost[/code]

.... now the error message which appeares is:

[code]

Error: 500

Location: /MAM25/home/home_mgmt.do

Internal Servlet Error:

javax.servlet.ServletException: cannot find message associated with key : dispatcher.forwardException

at org.apache.tomcat.facade.RequestDispatcherImpl.doForward()

at org.apache.tomcat.facade.RequestDispatcherImpl.forward()

at org.apache.jasper.runtime.PageContextImpl.forward()

at mam_0005fstart._jspService()

at org.apache.jasper.runtime.HttpJspBase.service()

at javax.servlet.http.HttpServlet.service()

at org.apache.tomcat.core.ServletWrapper.doService()

at org.apache.tomcat.core.Handler.service()

at org.apache.tomcat.core.ServletWrapper.service()

at org.apache.tomcat.core.ContextManager.internalService()

at org.apache.tomcat.core.ContextManager.service()

at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection()

at org.apache.tomcat.service.TcpWorkerThread.runIt()

at org.apache.tomcat.util.ThreadPool$ControlRunnable.run()

at java.lang.Thread.run()

[/code]

any comments would be at help

Regards,

Martin

[Former Member]

MI and ME do not support Windows Mobile 2005 yet.

[Former Member]

Hi,

1. Are you still using the same exact MAM war file as before?

2. Try and manually add mam_start.jsp from the source war file to the root of the war file being deployed.

3. If the MAM is custom app, then are the JSP compiled?

What is happening that the Creme is not being able to compile or find the classes for the JSP files. Try step 2.

[Former Member]

Hello,

1. I am using exactly the same settings as before

2. Adding mam_start.jsp did not help

3. MAM is not custom app

here is the jscpout.txt file:

NSIcom Ltd., CrEme(tm) Evaluation Version
CrEme J2ME(tm)
CrEme V3.27 B095.040628 12-September-2005
  MemoryLimit=29120Kb
EBCI(TM) Interpreter V1.00,
Copyright 1998-2002 by Bytecodes, Inc.
Do not use the MobileEngine classloader
FrameworkInitializer()
------------ Initialize framework ...
   Configuration initialized. Installation Base = /me21
   Path settings adjusted
   Trace initialized. Log is not switched on.
   Framework singletons initialized.
   Gzip data compression configuration initialized.
   Registry initialized.
    MI OS installer lib (/me21/bin/NATSTART.DLL) loaded successfully.
   Dlls loaded.
   Timed Sync initialized.
   Persistence initialized.
   Smart Sync initialized.
   Communication server initialized.
------------ Framework initialized
Use normal startup: true
Starting tomcat. Check logs/tomcat.log for error messages 

Kind Regards,

Martin Radev