prowin32.exe error 1

[Scottlem]

Hello i have a network of 6 machines. All win2k. One of the machine allow us to gain access to a progress database on Sco unixware 7.1.1 5 machines will come up with the prowin.exe error any ideas.

All machines are running progress 8.3d and win2k. The prgress

 

[stanhubble]

what exactly is the error that prowin is displaying?
is it a progress error message or a w2k error message?

stan

 

[Scottlem]

PROWIN32 caused an invalid page fault in module PROWIN32.EXE at 0157:00509d87.

Tried it on a Win 95 machine. Same sort of error. As above.

 

[stanhubble]

check out the following knowledgebase entry

http://www.progress.com/services/su...id=18221&keywords=prowin.exe&wintype=kbwindow

stan

 

[Guest_imported]

we suddenly started getting this error on a windows 98 system then it wont let ya connect to the network drive and ya have to reboot if anyone has an answer to this please let me know!


PROWIN32 caused an invalid page fault in
module KERNEL32.DLL at 0177:bff876d2.
Registers:
EAX=c00309c8 CS=0177 EIP=bff876d2 EFLGS=00010212
EBX=00000000 SS=017f ESP=005aff08 EBP=005b0014
ECX=8178c8dc DS=017f ESI=1042f5ac FS=2cd7
EDX=bffc9490 ES=017f EDI=00000000 GS=0000
Bytes at CS:EIP:
53 56 a1 10 9d fc bf 57 8b 71 40 66 c7 45 fc 00
Stack dump:

 

[stanhubble]

Just to clarify:

POSSIBLE CAUSES:

1) A corrupted Progress executable (PROGRESS.EXE or PROWIN.EXE) --
To fix that, either re-install Progress or restore from
backup. (Note that in Progress 8.2 and later you must first
uninstall Progress and then install again as new.)

2) A corrupted Dynamic Link Library file (.DLL) or a needed
.DLL file that was replaced when installing a piece of software
produced by a company other than Progress -- It is not unusual to
install Progress and have it running properly and then
installing a new program made by someone else will cause
problems within Progress. Another cause of corrupted .DLL
files is any abnormal power loss or any lockup of the system
that forces a Control-Alt-Delete sequence or a power off/reset.
Corrupted or erroneous .DLL files are difficult to troubleshoot
as there are many, many .DLL files within Windows. Simply
re-installing Progress will fix the problem, however, as the
installation will copy all the .DLL files needed by Progress
back to the hard disk.

3) Memory problems

4) Device driver problems -- Make sure that you are using the device
drivers provided by the manufacturers of your video board,
network card, sound card or any other unique hardware you may
have. The manufacturer-supplied device drivers will almost always
work better than the generic drivers supplied by Microsoft and
will generally operate faster than Microsoft's drivers. Video
drivers seem to be the cause of many GPF errors. In many cases,
downloading and installing the latest drivers from the video
board manufacturer's Web site will solve the problem.

 

[Guest_imported]

I am having a prowin32.exe error and I read the posts about re-installing the progress software. Well I am not real sure how to do that, can someone help me?

 

[Scottlem]

Ok i have solved my problem. I can now access our progress database. All i needed to make sure of is that all machines had a c:\temp directory.

Try it you never know. This work for me but its a problem with version 8.3

 

[ROJDI]

i'am installing progress with all componement , when i open
appbuilder to locate file , a message of error occured ,this
message is : activex error or file .ocx missplaced ,
error 6087

 

[stanhubble]

The progress knowledgebase is a great source of information:

http://www.progress.com/services/support/cgi-bin/techweb-kbase.cgi/webkb.p

Kbase Id:
20660

Title:
Error 6087 When Opening a File in AppBuilder

Creation:
09-Mar-2001

Modified:
09-Mar-2001



SUMMARY:

This solution discusses the following error you might encounter when
you try to open any file from the Progress AppBuilder:

Specified ActiveX control is not registered or the .ocx file was
moved from where it was registered.
Error occurred in procedure: <procedure name> (6087)

SOLUTION:

The problem might be with the listview control that is used to display
the available files. The .ocx files that contains listview might need
to be registered.

To register it, run the following:

regsvr32 <Progress Install>\bin\system\comctl32.ocx