|
Middleware Issues
MW001. 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.
MW014. No internet access with ActiveSync Guest partnership.
MW017. User set up problems in SQL Server 2005 installation on Windows 2003.
MW013. Problems Installing PHP on Windows 2003.
MW015. Problems Installing PHP 5.2.9-2 with IIS ISAPI.
MW016. Problems Installing/Running PHP Mail on Windows 2003.
MW018. PHP installation using IIS and FastCGI.
MW019. PEAR installation with PHP5.3
MW020. PEAR MAIL installation
MW021. PEAR MAIL_MIME Installation (advanced email features like cc: and attachments)
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?
Firewall Issues
FW001. Window firewall blocks passive FTP traffic on server.
Web Server Issues
WS001. How to get IIS6 to allow download of .exe files
ODBC Driver Issues
ODBC001. PSC ODBC driver via PHP under IIS6 blows up when retrieving large sets of records
ODBC002. Enabling write access for PSC ODBC driver
ODBC003. Configuring non Administrator access for PSC ODBC driver
Middleware Issues
MW001. 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:
- Copy the jsihttp.ini file to the C:\Windows\system32\inetsrv folder (not the system32 folder
used in other versions of Windows).
- Run IIS Manager
- In the tree at left, under the local computer node, click on the "Web Service Extensions" node.
- Select "Add a new Web Service Extension" in the tasks links. (if not shown, right-click the
above node to select this from a popup menu)
- For the "Extension name", enter "Tunnel Broker DLL"
- Click the "Add" button next to "Required Files", click the "Browse" button in the "Add file"
window, and navigate to and select the jsihttp.dll file. It will be something like
"C:\Inetpub\wwwroot\scripts\jsihttp.dll". Click "OK" to accept this and close the "Add file" window.
- Check the "Set extension status to allowed" checkbox.
- Click OK to add the extension.
- In the tree at the left, right click on the
Scripts directory where jsihttp.dll is installed and select "Properties".
- Change the "Execute Permissions:" value to "Scripts and Executables" (instead of just "Scripts").
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:
- OpenEdge 10.0A and later
- Progress 9.1E
- Progress 9.1D06 and later
- WebSpeed 3.1D06 and later
For other operating system and supported versions information, see the
Knowledge Base entry P34824 on the Progress web site.
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.
MW013. Problems Installing/Running PHP on Windows 2003.
Problem:
After installing PHP on Windows 2003, attempts to run php pages return a "404 page not found"
error message.
Solution:
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.
Another suggestion is to use: c:\php as the install directory for PHP
REMEMBER to move an updated php.ini to \windows folder.
MW014. No internet access with ActiveSync Guest partnership.
Problem:
Device cannot access the internet while cradled and connected via Active Sync as a guest
vs a standard partnership.
Solution:
Guest partnerships may not have the same Internet access privileges as a standard partnership.
This may depend on the ActiveSync version, OS version and handheld model. The problem was seen
on a SoMo650 cradled via USB using ActiveSync 4.5 on Windows XP.
First, try to remove the guest partnership and set up a standard partnership for the device.
If you cannot, then simply uncradle the device, uninstall ActiveSync, reboot, and reinstall
ActiveSync. Then, create a standard partnership for the device, and it should work.
MW015. Problems Installing PHP 5.2.9-2 with IIS ISAPI.
Problem:
PHP 5.2.9-2 windows installer does not provide an installation choice of IIS ISAPI.
Solution:
Install using FastCGI instead of ISAPI. See MW018
MW016. Problems Installing/Running PHP Mail on Windows 2003.
Problem:
Email generation in PHP scripts fails.
Solution:
1. You must install PEAR extension to PHP when either installing PHP or modifying it's installation via Control Panel -> Add/Remove Programs.
2. If you install the PEAR extension, you will see a PEAR folder in the PHP folder.
3. run the go-pear.bat in PHP folder. This will install the PEAR system.
Verify PEAR is installed correctly by using a DOS command from the PEAR sub-folder:
pear version
Finally, be sure to copy the php.ini from the PHP folder to the c:\windows folder. This will have a modified include_path set to include the PEAR sub folder.
4. Find the PHP PEAR Mail package at http://pear.php.net/package/Mail. Download the .gz file to the PEAR sub folder.
From a DOS command prompt in the PEAR sub-folder, enter the following to install the PEAR Mail package into PHP:
pear install -a MailPackageName <--- do not include the .gz file extension.
the -a option installs all dependant PEAR packages needed for Mail to work (important to use this option)
REMEMBER to move an updated php.ini to \windows folder.
MW017. User setup problems in SQL Server 2005 installation on Windows 2003
Problem:
ODBC authentication problems for user and password embedded in SQL db
Solution:
1. You must set SQL server security to use both SQL Server and Windows authentication modes. To do this: Use SQL Server management studio. Go to security properties of the SQL server, i.e. properties of the top most node, then choose security settings. Set the server authentication mode to use both SQL server and Windows authentication.
2. A user must also be defined in the Databases -> security --> users portion of the SQL server studio. This use must also be a valid windows user. The password is derived from the windows password for the same user. That win user must also be in the SQL server user group (verify this using Admin tools -> computer management console)
MW018. PHP installation using IIS and FastCGI.
Problem:
IIS ISAPI has stability issues with PHP so PHP dropped IIS ISAPI support. Recommended to use FastCGI.
Solution:
1. Enable IIS to handle FastCGI by installing the FASTCGI Extension for IIS (v6.0) prior to the PHP install.
2. Review and follow the instructions for "Quick Installation on IIS" on the primer on PHP and FastCGI.
Notes on "Quick Installation on IIS":
a. See PHP windows release files for the latest windows PHP code.
Select VC9 Thread Safe code.
b. In "Quick Installation on IIS" - step #5. For registry entries, change AppPath to be:
AppPath = c:\php\php-cgi.exe
c. Suggest using c:\php as install location for PHP. Saves hassles later, see MW013.
d. Be sure to copy php5ts.dll and php.ini from PHP folder to c:\WINDOWS
e. Be sure that the Anonymous HTTP user can read,write, and execute c:\php\isapi_FCGI.dll
MW019. PEAR installation with PHP5.3
Problem:
Some users have reported that the windows builds of PHP 5.3 are not able to open the shipped go-pear.phar file, i.e. running "go-pear.bat" does not work.
Solution:
Run the distributed phar with: php -d phar.require_hash=0 go-pear.phar
or download and use the http://pear.php.net/go-pear non-pharred version.
MW020. PEAR MAIL Installation
Problem:
How to install PEAR Mail
Solution:
Via command prompt in PHP folder:
pear install -a Mail-1.2.0b
or check for latest version at http://pear.php.net/package/Mail
MW021. PEAR MAIL_MIME Installation
Problem:
How to install PEAR MAIL_MIME for advanced email functions like cc: and attachments.
Solution:
Via command prompt in PHP folder: pear install -a Mail_Mime-1.5.2
or check for latest version at
http://pear.php.net/package/Mail_Mime
Operating System issues
OS001. 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:
- Open Control panel
- Select "Add New Hardware"
- Select "manual install"
- Select "Network Adapters "
- Select "Microsoft"
- Select the loopback adapter as if it were another network card.
- XP will assign the loopback adapter on reboot (not 127.0.0.1) or you can assign one
manually. The default is 169.254.25.129
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:
- Select the web server node
- Click "Properties"
- Select "Mime Types"
- Add a new MIME type to serve files with the extension ".ini" (for V3 apps).
- Extension: ".ini"
- MIME Type: "text/plain"
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:
- Select Tools-->Options
- Select "Web Features" in lefthand menubar
- Check "Allow web sites to install software"
- Click "Allowed sites" button to the right of that checkbox
- Enter your web server site name or IP address
- Click "allow" button
- Click "ok" button to close allowed site window
- Click "ok" button to close options window
- Go to startup page and it should ask to install ReaderX
after saying Jargonsoft is not a certified site.
Firewall Issues
FW001. Window firewall blocks passive FTP traffic on server.
Problem:
Windows firewall prevents passive FTP use on the server.
Solution:
Create a .bat file from the following and run it. This will make the adjustments necessary in the windows firewall configuration.
Echo OFF
ECHO ADDING PORT RANGE TO IIS
C:\Inetpub\AdminScripts\adsutil.vbs set /MSFTPSVC/PassivePortRange "5500-5550"
ECHO OPENING FIREWALL PORTS
FOR /L %%I IN (5500,1,5550) DO NETSH FIREWALL ADD PORTOPENING TCP %%I FTPPort%%I
iisreset
ECHO FINISHED
Pause
Web Server Issues
WS001. How to get IIS6 to allow download of .exe files.
Problem:
Sometimes IIS does not allow downloading .exe files.
Solution:
1. On web site properties in IIS manager, Home Directory tab, make sure execute permissions is set to "scripts only".
2. On web site properties in IIS manager, HTTP Headers tab, be sure to define .exe as a valid MIME type.
3. Be sure to stop and restart the IIS Service (via Services)
ODBC Driver Issues
ODBC001. PSC ODBC Driver via PHP under IIS6 blows up when retrieving large sets of records.
Problem:
PSC ODBC driver randomly blows up on large datasets when called using PHP under IIS6
Solution: From PSC tech support kbase entry:
See PSC tech support kbase entry P149377.
(reproduced below if the link above is broken)
ID: P149377
Title: "PHP, running under IIS6, error log shows ODBC errors when the SQL-92 query retrieves a large sets of records from the progress/OpenEdge database"
|
| Created: 07/10/2009 |
Last Modified: 07/10/2009 |
Status: Unverified
|
| |
Symptoms:
PHP, running under IIS6, error log shows ODBC errors when the SQL-92 query retrieves a large sets of records from the progress/OpenEdge database
PHP Warning: odbc_exec() [<a href='function.odbc-exec'>function.odbc-exec</a>]: SQL error: [DataDirect-Technologies][ODBC PROGRESS driver]Cannot open file 'C:\WINDOWS\SYSTEM32\INETSRV\'., SQL state S1000 in SQLExecDirect in C:\Inetpub\wwwroot\Jargon_TT\select.php on line 55
The ODBC trace log is intermittently generated but when it works shows the following errors
DIAG [S1000] [DataDirect-Technologies][ODBC PROGRESS driver]Cannot open file 'C:\WINDOWS\SYSTEM32\INETSRV\'. (30040)
DIAG [S1000] [DataDirect-Technologies][ODBC PROGRESS driver]Cannot delete file: 'C:\WINDOWS\SYSTEM32\INETSRV\'. (1502)
DIAG [01S02] [DataDirect-Technologies][ODBC PROGRESS driver]Option value changed. (0) |
Facts:
Allowing full control to IUSR_MACHINE-NAME user or everyone to 'C:\WINDOWS\SYSTEM32\INETSRV folder did not resolve the issue
When retrieving small sets or results, everything works fine
Other 3rd party ODBC tools, such as WinSQL, works fine regardless of the size of the record set provided that the database is started with some SQL tuning parameters
The JDBC also works fine
Running the same PHP script from DOS prompt works fine, and the ODBC trace log also gets created every time as well
Changing the anonymous user of IIS from IUSR_Machine-name to a user with administrator rights resolved the issue
PHP 5.2.x or 5.3.x
IIS 6 on Windows 2003
Windows
Progress 9.x
OpenEdge 10.x |
| |
Cause:
This is an IIS issue with IIS user privileges. IIS user uses IUSR_MACHINE-NAME user with very limited rights on different folders outside of wwwroot folder. On the other hand ODBC driver tries to create a temp file to cache the records after a certain records set. Since IIS user is trying to run the query against ODBC driver, it lacks privileges to create temporary file by Progress/OpenEdge SQL-92 ODBC driver. Therefore, the errors are apparent. |
Fixes:
Change the anonymous user (IUSR_MACHINE-NAME) of IIS to a local system user with some local security policies added under Anonymous access and authentication control on the the directory security tab of the Web sites properties |
Notes:
You can further research with FileMon or process monitor utility from Microsoft TechNet web site to determine what other directories the IIS user needs read, write and modify privileges if the anonymous user can not be changed for business reasons.
http://technet.microsoft.com/en-us/sysinternals/bb896642.aspx
http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx |
ODBC002. Enabling write access for PSC ODBC Driver.
Problem:
By default, the PSC ODBC driver has read only access.
Solution:
1. Set default isolation level in ODBC driver properties (Advanced tab) to "READ COMMITTED". Note that "READ UNCOMMITTED" (default state) implies read only.
2. In PSC SQL explorer, connect via Administrator credentials and issue the following SQL statement (one for each db table desired):
GRANT ALL ON PUB.tablename TO Administrator;
...
COMMIT;
Note: Be sure to prefix the table name with "PUB".
ODBC003. Configuring non Administrator access for PSC ODBC driver.
Problem:
By default, the PSC database has only one user, Administrator (assuming it was installed using Administrator). This can cause security issues by having Administrator credentials in clear text form on server.
Solution:
1. Using PSC SQL Explorer, connect via Administrator, then create at least one SQL Admin user as follows:
CREATE USER 'SQLAdmin', 'SQLAdmin'; (This creates a SQL user SQLAdmin with pw: SQLAdmin)
COMMIT;
2. Grant dba authority to the user as follows:
GRANT DBA to SQLAdmin;
COMMIT;
This Admin user can access all tables in any fashion as desired.
If desired, create other dba and non dba SQL users. For non dba users, explicit permission must be granted to read or write tables, as follows:
GRANT ALL ON PUB.tablename TO Username;
...
COMMIT;
|
