iiX Online Support - ExpressNet

Support Home • ExpressNet • Express for Browsers • Express for Windows • MVR Information • A-Plus™, Credit, UDI/UDV • Criminal History

Search

Error Message after Communications: "Error 36 - File I/O Error"

Error Message after Communications: "Error 36 - File I/O Error"

Problem:

Express for Browsers is installed on a Windows® 98 peer-to-peer network. One workstation and the server could communicate successfully. The 3rd workstation would not dial and ultimately would end communications with the error - "Error 36 - File I/O Error". Also, the last line of the very short communications log read:

" CFileException caught during communications, cause=2"

Solution:

Because the other workstations were able to access their modems, and because they were able to receive files successfully, we assumed there was not a problem with the network installation of EfB.

It appeared from the communications log, and from talking to our programmers, that the non-working system was somehow failing to create a either a communications logfile or an MTSTATUS file.

Since this sounded like a possible rights issue, we used the login i.d.'s from the working systems to log in on the non-working one. That did not resolve the problem.

Next, we examined the way the drives were mapped and made sure that the drive could be seen from the DOS level - by using the NET USE command. It could. For that reason, we assumed that the mapping was OK.

Actually, the final resolution was a workaround.

We completely uninstalled EfB from that one machine and then reinstalled it as a Standalone application. Then we tested communications to see if they would work. They did.

We then went into Control Panel and opened the ODBC 32-bit option. We then redirected the driver for Express for Browsers from C: to the network drive. Instructions follow:

Open Control Panel
Double click ODBC 32-bit
On the USER DSN tab, select Express Plus 32, then click <Configure>.
On the next screen, click <Select>.
The next box looks like a standard Windows Browse window. Locate the database file that is on the network drive and click OK on that screen.
You will need to click OK twice more to exit this function.

After redirecting the local copy of EfB to the network database, we again attempted communications. They were successful.

The drawback to this type of solution is that someone has to remember that it was done this way and remember to install any updates in the same way.

This page has been viewed 13445 times | Document Rating is -- / 5.00 | Last Updated on 4/28/2004 7:08:24 AM