Maria,

Are these clients as in "business clients" or clients as in "workstation clients"? I guess I'm wondering if you have easy access to the machines that are giving you these errors. You mentioned that you have read other postings but that doesn't tell us what you have already tried. Here are some issues to look for:

1. Failure to execute START32 during the current session

2. Failure to execute STOP32 during the last session

3. Multiple OIPI32 processes in memory

4. Executing a Set_Printer command which is no longer support

5. No default printer defined for the workstation

6. No printers at all defined for the workstation

7. Registry settings never being set due to restricted access

We developed a tool that we would use to launch our OIPI sessions. It would do the following:

1. Attempt a normal INIT.

2. If that failed then it would attempt to close the OIPI/STOP32 and then START32 again with another INIT.

3. If that failed then we would search for all running processes of OIPI32 and terminate them (i.e. the equivalent of End Tasking them from the Task Manager) and then START32/INIT one more time.

This resolved our INIT problem 99.9% of the time. Fortunately this utility is not really needed with 7.x so upgrading may be the best solution for you. However, if you are unable to upgrade and you cannot resolve the problem then drop us a line regarding our utility.

[email protected]

SRP Computer Solutions, Inc.

Thank you, and I will review this information with the development manager. It is happening on client workstations. We have not attempted anything except for a reboot of the workstation, which seems to clear the problem temporarily. Thanks again!

View this thread on the Works forum...