Jargon Software - Knowledge Base

Knowledge Base

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

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;