on 03-27-2006 4:56 PM
We've been using ME 2.1 and MAM 2.0 in PPC 2003 for almost a year without any problems.
But now, we are trying to user new PDas with Windows Mobile 5, but are having problems in using them:
We made the download of the adequate JVM from NSIcom, and tried to install the application.
It seems that WM5 does not resolve //127.0.0.1/ to activate the ME.
We've tried using //localhost/ in Pocket IE and it seems to work, allowing us to install the applications (MAM).
However, we still have problems: Wen we try to access MAM we get the message:
[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]
this seems to be a result of the inability of WM5 to resolve //127.0.0.1/
We've found the following article for PPC 2003 (in spanish), that shows how to make PPC2003 resolve "localhost" correctly:
<a href="http://www.microsoft.com/spanish/msdn/articulos/archivo/261104/voices/migration_developers_faq.asp">http://www.microsoft.com/spanish/msdn/articulos/archivo/261104/voices/migration_developers_faq.asp</a>
Does any one know of a similar fix for Window Mobile 5?
(the full text is shoewn below in this message)
What is necessary for PPC2003 to resolve 'locahost' correctly?
If you are having problems using Pocket PC's HTTP server or when connecting to a "localhost" with a PPC 2003 based device, you may need to configure tour device in the following way:
Create an acrchive named _setup.xml with the following content:
[code]<wap-provisioningdoc>
<characteristic type="CM_Mappings">
<characteristic type="536870911">
<parm name="Pattern" value="://localhost/" />
<parm name="Network" value="{e8e89f5a-d3bb-4c58-9b4e-08279d31044e}" />
</characteristic>
</characteristic>
<characteristic type="Registry">
<characteristic
type="HKLM\Software\Microsoft\ConnMgr\Providers\{EF097F4C-DC4B-4c98-8FF6-AEF
805DC0E8E}\localhost-null">
<parm name="DestId"
value="{e8e89f5a-d3bb-4c58-9b4e-08279d31044e}" datatype="string" />
<parm name="Type" value="0" datatype="integer" />
<parm name="Enable" value="1" datatype="integer" />
</characteristic>
</characteristic>
<characteristic type="CM_Mappings">
<characteristic type="536870911">
<parm name="Pattern" value="://127.0.0.1/" />
<parm name="Network" value="{e8e89f5a-d3bb-4c58-9b4e-08279d31044e}" />
</characteristic>
</characteristic>
<characteristic type="Registry">
<characteristic type="HKLM\Software\Microsoft\ConnMgr\Providers\{EF097F4C-DC4B-4c98-8FF6-AEF805DC0E8E}\localhost-null">
<parm name="DestId" value="{e8e89f5a-d3bb-4c58-9b4e-08279d31044e}" datatype="string" />
<parm name="Type" value="0" datatype="integer" />
<parm name="Enable" value="1" datatype="integer" />
</characteristic>
</characteristic>
</wap-provisioningdoc>[/code]
Create a cab file with this info
place it in the device and activate it
hello rogerio,
i don't have a WM5 device thus i cannot test this.
could you try:
using a registry editor, (get one for windows CE or use the
one from the embeddedTools utilities)
1)create a key HKEY_LOCAL_MACHINE\Comm\Tcpip\Hosts\localhost
and under this key,
2)create a multistring value of name <i>aliases</i> having no value
3)create a binary value of name <i>ipaddr</i> and specify a value of <i>7F 00 00 01</i>.
then restart your device...
i hope that this work.
regards
jo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you, Jo,
Unfortunately, it doesn't seem to work.
I made the changes you suggested (more complicated than anticipated:
WM5 denies access to registry changes: needed to use an application to crack it - EnableRApi
WM5 discards registry changes if we use the sofReset button: only using software softReset makes these changes usable
...but the problem remains. It seems, however, that you are in the right track. Too bad I don't have enough WM5 knowledge to pursue it further.
More suggestions?
B Regards,
Rogério
Hello Rogério.
I heard that there is no fix available at the moment and that Microsoft will ship a fix with the next major release.
Here are two links to find more information:
http://blogs.msdn.com/cenet/archive/2005/06/06/425799.aspx
Regards,
Sascha
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.