|
Mobile and Handheld Application Development and Deployment
|
||||||||
|
|||||||||
|
|||||||||
Knowledge Base - Middleware and Operating System IssuesContents:Middleware IssuesMW001. Configure AppServer as State-Reset or Stateless to work with Tunnel Broker. MW002. Configure WebSpeed or AppServer with a DOMAIN user to access shared networked folders. MW003. Reboot Windows or restart IIS to use new jsihttp.ini values in Tunnel Broker messenger. MW004. Configure WebSpeed for Development mode to use web utilities such as ping.p. MW005. Getting Socket Errors on PocketPC when doing many host requests. MW006. Tunnel Broker configuration in IIS6/Windows 2003. MW007. How to install and configure Version 10 AppServer. MW008. ActiveSync 4.0 USB Connection Problems. MW009. Problems Running Progress on Windows 2003. MW010. Microsoft RemoteDSP Installation Problems. MW011. How to remove the "Generated by WebSpeed" message. MW012. Correcting data errors caused by HTTP 1.1 chunking under Apache. MW013. Problems Installing PHP on Windows 2003. Operating System Issues OS001. Add loopback service on standalone WinXP laptop to access it from a cradled PocketPC . OS002. Add new MIME type on Windows 2003 to enable downloads of ".ini" files. OS003. Modify URLScan config file on Windows NT/2000 to enable downloads of ".ini" files. OS004. Does Jargon ReaderX support Firefox/Mozilla/Netscape7? Middleware IssuesMW001. Configure AppServer as State-Reset or Stateless to work with Tunnel Broker.Problem: Don't know how to configure AppServer to work with Tunnel Broker. Solution: Configure AppServer to run in State-Reset or Stateless mode. MW002. Configure WebSpeed or AppServer with a DOMAIN user to access shared networked folders. Problem: Cannot create or write to remote shared network directories from 4GL programs on a Win2000 server. Solution: If your 4GL programs will need to create or write to remote shared network directories on a Win2000 server, note that the WebSpeed broker should be configured using a DOMAIN/account with a valid userid and password. See Progress Knowledge Base Solution ID# P26491, Title: Error 98 with errno = 13 writing a file on a network resource using Webspeed. MW003. Reboot Windows or restart IIS to use new jsihttp.ini values in Tunnel Broker messenger. Problem: Tunnel Broker messenger process (jsihttp.dll) does not recognize new jsihttp.ini values on a WIndows server. Solution: Reboot Windows NT/2000/2003 to clear any copy of the old jsihttp.dll that may have been cached in memory by Windows. Stopping and restarting the IIS service itself may also do this on some versions of Windows, however stopping and starting an individual web site within IIS will NOT do so. MW004. Configure WebSpeed for Development mode to use web utilities such as ping.p Problem: Webspeed request for "webutil/ping.p" returns a blank page and the error “ Unable to find web object file 'ping.p' “ Solution: The WebSpeed broker was probably set in Production mode, change it to Development mode. MW005. Getting Socket Errors on PocketPC when doing many host requests. Problem: We have found that any system that has ActiveSync 3.7 will run hundreds of host requests without a single error. But with ActiveSync 3.7.1 it will fail after 65-75 times and require a warm reboot to be able to do any further host requests. We have seen a number of complaints from other developers about ActiveSync 3.7.1 causing other connection problems. Solution: We recommend that if you have this problem, uninstall ActiveSync 3.7.1 and then do a clean install of the older 3.7 version. http://www.microsoft.com/downloads/details.aspx?familyid=67e9e87c-ca96-48b4-b5d4-f3e047ca5108&displaylang=en MW006. Tunnel Broker configuration in IIS6/Windows 2003. Problem: Cannot access the jsihttp.dll (tunnel broker DLL) on Windows 2003 Server. Get a "404 File not Found" error message. Also when this is fixed, jsihttp.ini values not loading. Reason: When you install IIS 6.0, it is locked down, only request handling for static Web pages is enabled, and only the World Wide Web Publishing Service (WWW service) is installed. None of the features that sit on top of IIS are turned on by default, including ASP pages and third-party DLL files. Also, the default folder where IIS looks for ".ini" files has changed. Solution:
MW007. How to install and configure Version 10 AppServer. Problem: How to install and configure Version 10 AppServer. Solution: See this help page. MW008. ActiveSync 4.0 USB Connection Problems. Problem: In some specific cases, Windows Mobile device connectivity to a Windows PC running Microsoft ActiveSync 4.0 may experience connection problems. For example, the connection is never established between the PC and the mobile device, or the connection is dropped during data transfer or synchronization, or only partially completes, etc. This appears to be a problem only with the 4.x versions of ActiveSync, not the 3.x versions. Solution: Connection problems can be caused by desktop firewall applications or applications that manage network traffic. These applications can conflict with the TCP traffic between a Device and the PC. Firewalls that may cause problems include Norton, McAfee, Trend Micro, Sygate and Zone Alarm. For detailed instructions on how to configure these firewalls or other applications to allow ActiveSync traffic, see the Microsoft help page at: http://www.microsoft.com/windowsmobile/help/activesync/default.mspx MW009. Problems Running Progress on Windows 2003 Problem: After installing Progress Version 9.1C or older versions on a Windows 2003 server, the Name Server or other products do not start or operate correctly. Solution: According to the Progress Software support web site, the following versions are supported on Windows Server 2003:
MW010. Microsoft RemoteDSP Installation Problems. Problem: If you have an SD Card, then the Windows Mobile installer gives you the option to install on the SD Card or on the Device. Other apps install and work fine except for Microsoft's MS-Remote DSP. If you attempt to install it on the SD Card, then it never gets installed and does not show up in the "programs" folder. Solution: Install MS-RemoteDSP on the device (not on the SD Card). MW011. How to remove the "Generated by WebSpeed" message. Problem: The Progress WebSpeed middleware prefixes each response with an HTML comment that reads "Generated by WebSpeed - http://www.webspeed.com/". The message is contained inside HTML comment delimiters, and is followed by two newlines. This comment is ignored by the Jargon Reader sys.ProcessInstructions(http.GetResponseData()) method, but it can cause problems if the response buffer is being processed directly by other script functions, for instance if it contains data that does not consist of Jargon CIO commands. Solution: This message is generated by the Progress WebSpeed source file src/web/methods/cgiutils.i at lines 516-520. To remove this comment, edit the cgiutils.i file and remove or comment out this Progress statement. Then recompile all Jargon host programs that contain "jsi" includes. Also recompile the WebSpeed src/web/object/web-util.p program. MW012. Correcting data errors caused by HTTP 1.1 chunking under Apache. Problem: The HTTP 1.1 specification allows responses to be broken up into two or more "chunks" of data. When these chunks are recombined in the client receive buffer, some additional characters (which contain the chunk sizes) remain in the buffer, mingled in with the data. Jargon Reader does not handle this correctly in versions 3.3.32 and older. Solution: Until a new version of Jargon Reader is available that corrects this problem, a workaround under the Apache web server (the only web server where this problem has been reported) is as follows. Add the following line to Apache's httpd.conf file, then restart Apache. BrowserMatch "Jargon" downgrade-1.0
This forces Apache to send an HTTP 1.0 response anytime it receives a request from Jargon Reader.
Chunking isn't part of the HTTP 1.0 specification, so it avoids the problem.
Second, read the "User contributed notes" section in the PHP installation instructions for Windows on the php.org web site. A common cause of this 404 error is that the installer puts short file names in 8.3 format in the php extension settings in the IIS Admin Manager settings, and IIS can't handle them correctly. Change these to the full long filename format. For example, if you installed php in the default location of C:\Program Files\PHP: Start->Control Panel->Administrative Tools->Internet Information Services->(select web site) ->Properties->Home Directory->Configuration->Mapping
Then change the Executable Path for .php files from the short names like "C:\Program~\PHP\php5is~1.DLL" (or whatever crazy path) to the full long names like "C:\Program Files\PHP\php5isapi.dll". Use the browse button to navigate to and select the correct file to avoid typing errors.
Operating System issuesOS001. Add loopback service on standalone WinXP laptop to access it from a cradled PocketPC. Problem: Cannot connect to web server (Apache) on a standalone laptop running WinXP and Apache from a cradled PocketPC. Jargon Reader error message is "Error #5774 Socket error - 10061". Solution: By default, WinXP does not provide a "localhost" loopback service, so localhost and 127.0.0.1 do not work as hostnames. Also, when not connected to a network, WinXP does not recognize manually assigned IP addresses. To manually add a loopback IP address that can be referenced by Jargon Reader from a PocketPC, do these steps:
OS002. Add new MIME type on Windows 2003 to enable downloads of ".ini" files. Problem: Jargon Reader client cannot access ".ini" files from a Windows 2003 server. Solution: By default, security settings on Windows 2003 server only allow access to files with certain predefined extensions (such as ".html", ".xml", ".jpg" etc.). To allow Jargon Reader to download ".ini" files, do these steps using the IIS Manager:
OS003. Modify URLScan config file on Windows NT/2000 to enable downloads of ".ini" files. Problem: Jargon Reader client cannot access ".ini" files from a Windows NT/2000 server. Solution: For IIS4/5 on Windows NT/2000, the problem may be due to a Windows feature called "URLScan." This is an optional Microsoft tool (part of the "IIS Lockdown" downloadable tool), that enables IIS to allow or deny access to various file types. If you have URLScan installed, edit this file: c:\winnt\system32\inetsrv\urlscan\urlscan.ini and if access is denied for ".ini" files, comment out the line, save and reboot. OS004. Does Jargon ReaderX support Firefox/Mozilla/Netscape7?. Problem: Does Jargon ReaderX (Enterprise Edition) support Firefox/Mozilla/Netscape7? Solution: The index.html in the latest ReaderX install zip file has a new auto-install feature for the "xpi" install file for Mozilla-based browsers including Firefox and Netscape. We have tested it and it seems to work ok. So the answer is yes, if you update your install html pages. However, firefox by default will block any software installation unless the site it comes from is set up as a trusted site. So before accessing the login, Firefox users must:
|
| Home | Products | Demos | Download | Support | Partners | News | About Us |
|
Copyright© 2000-2007 Jargon Software Inc.
| Privacy Policy
| Terms of Use
|