ViP causing constant "Illegal Operation" errors on workstation (ViP Specific)
At 04 NOV 1997 01:57:37PM Ken Wachs wrote:
Dear ViP support:
I have a user on a Dell Dimension XP5 computer who is getting constant errors. The error message is:
"This program has performed an illegal operation and will be shut down. If the problem persists, contact the program vendor."Have other users experienced this? Can you suggest any ways to troubleshoot the problem?
Thanks,
Ken Wachs
At 05 NOV 1997 01:57PM Stephen Bellefontaine Revelation wrote:
Hello Ken,
"This program has performed an illegal operation and will be shut down … is a windows error message generated most often because of corruption, or memory conflicts between your operating system and the application.
Before I can offer any ways to troubleshoot the problem it would be helpful if I knew a little more as to what causes the problem …
- What module causes the GPF? (select details when the error occurs, ex. ViP.exe, or Kernel32.dll)
- does this happen in the ViP Designer or Runtime?
- if it is the Runtime, then what is the user doing at the time of the crash (ex. ExecuteQuery)
- is the software installed locally or on the network?
and finally what version of ViP are you using?
Any additional information you could provide would be beneficial.
Hope this helps,
ViP Tech Support
At 13 NOV 1997 12:24PM Ken Wachs wrote:
Steve:
I e-mailed you a copy of the error message from one of the other computers in the company. It did not have web access, so I could not post directly to the web site.
Please post your response here when you get it. I'll just check the site periodically.
Thanks,
Ken Wachs
At 17 NOV 1997 10:00AM Stephen Bellefontaine Revelation wrote:
Hello Ken,
Based on our records, you are currently developing with ViP 2.2. Therefore, any applications compiled and/or saved with the 2.2 designer need to be executed with the 2.2 runtime.
In your previous post you mentioned you are using the ViP 2.0 runtime. I would uninstall this version and install ViP 2.2 runtime, as several dll files have changed since that version.
Hope this helps,
ViP Tech Support