Prowin32 Errors after upgrading to 4.0


(system) #1
This workstation is the only one we have problems with.

-CLay

-----Original Message-----
From: Troy Funte [mailto:tfunte@...]
Sent: Monday, July 31, 2000 3:29 PM
To: vantage@egroups.com
Subject: Re: [Vantage] Prowin32 Errors after upgrading to 4.0


Clay,
By the way, most of the errors had to do with old versions of .dll files
on certain workstations. Does the error happen on the same workstation all
the time, or on different ones?

Troy

Subject: RE: [Vantage] Prowin32 Errors after upgrading to 4.0


I tried this, but it didn't work. We still get this error about once or
twice a day, and usually when trying to print an invoice. The error says:
"Runtime Error Program: V:\Progress\Bin\Prowin32.exe abnormal program
termination." Then after Vantage crashes, it says "invalid page fault in
module prowin32.dll."

-Clay Buchanan
Kams, Inc., Oklahoma City, OK
www.kamsinc.com




[Non-text portions of this message have been removed]




We no longer allow attachments to files. To access/share Report Files,
please go to the following link: http://www.egroups.com/files/vantage/
(Note: If this link does not work for you the first time you try it, go to
www.egroups.com, login and be sure to save your password, choose My Groups,
choose Vantage, then choose Files. If you save the password, the link above
will work the next time you try it.)

(system) #2
Here's a tip that might save users some grief when upgrading from Vantage
3.xx to version 4.0. If you use the same local working directory in version
4 as you did in version 3, ie: "c:\vntgwork" - make sure you delete all the
files out of the old Vantage working directory before installing the 4.0
client software. We did not do this, and we experienced intermittant
"Prowin32 errors" on several clients after upgrading to version 4 -- usually
while printing reports. Deleting all files in "c:\vntgwork" made these
problems go away.


[Non-text portions of this message have been removed]

(system) #3
I tried this, but it didn't work. We still get this error about once or
twice a day, and usually when trying to print an invoice. The error says:
"Runtime Error Program: V:\Progress\Bin\Prowin32.exe abnormal program
termination." Then after Vantage crashes, it says "invalid page fault in
module prowin32.dll."

-Clay Buchanan
Kams, Inc., Oklahoma City, OK
www.kamsinc.com


>-----Original Message-----
>From: Jerry M Nettik [mailto:jnettik@...]
>Sent: Friday, July 28, 2000 10:57 AM
>To: vantage@egroups.com
>Subject: [Vantage] Prowin32 Errors after upgrading to 4.0
>
>Here's a tip that might save users some grief when upgrading from Vantage
>3.xx to version 4.0. If you use the same local working directory in
version
>4 as you did in version 3, ie: "c:\vntgwork" - make sure you delete all
the
>files out of the old Vantage working directory before installing the 4.0
>client software. We did not do this, and we experienced intermittant
>"Prowin32 errors" on several clients after upgrading to version 4 --
usually
>while printing reports. Deleting all files in "c:\vntgwork" made these
>problems go away.

(system) #4
We've had some Prowin32 errors in 3.0, and Vantage tech support has been able to pretty much track them all down. (P.S. The latest one had to do with a user who would double click where he should single click, thereby opening two processes at the same time and making a conflict. But Tech support was able to track that down too.) Don't hesitate to call them on this one. They've probably got a few pages of fixes to send you.

Troy
----- Original Message -----
From: Kams
To: vantage@egroups.com
Sent: Monday, July 31, 2000 1:07 PM
Subject: RE: [Vantage] Prowin32 Errors after upgrading to 4.0


I tried this, but it didn't work. We still get this error about once or
twice a day, and usually when trying to print an invoice. The error says:
"Runtime Error Program: V:\Progress\Bin\Prowin32.exe abnormal program
termination." Then after Vantage crashes, it says "invalid page fault in
module prowin32.dll."

-Clay Buchanan
Kams, Inc., Oklahoma City, OK
www.kamsinc.com


>-----Original Message-----
>From: Jerry M Nettik [mailto:jnettik@...]
>Sent: Friday, July 28, 2000 10:57 AM
>To: vantage@egroups.com
>Subject: [Vantage] Prowin32 Errors after upgrading to 4.0
>
>Here's a tip that might save users some grief when upgrading from Vantage
>3.xx to version 4.0. If you use the same local working directory in
version
>4 as you did in version 3, ie: "c:\vntgwork" - make sure you delete all
the
>files out of the old Vantage working directory before installing the 4.0
>client software. We did not do this, and we experienced intermittant
>"Prowin32 errors" on several clients after upgrading to version 4 --
usually
>while printing reports. Deleting all files in "c:\vntgwork" made these
>problems go away.


------------------------------------------------------------------------------



------------------------------------------------------------------------------
We no longer allow attachments to files. To access/share Report Files, please go to the following link: http://www.egroups.com/files/vantage/
(Note: If this link does not work for you the first time you try it, go to www.egroups.com, login and be sure to save your password, choose My Groups, choose Vantage, then choose Files. If you save the password, the link above will work the next time you try it.)



[Non-text portions of this message have been removed]

(system) #5
Clay,
By the way, most of the errors had to do with old versions of .dll files on certain workstations. Does the error happen on the same workstation all the time, or on different ones?

Troy

Subject: RE: [Vantage] Prowin32 Errors after upgrading to 4.0


I tried this, but it didn't work. We still get this error about once or
twice a day, and usually when trying to print an invoice. The error says:
"Runtime Error Program: V:\Progress\Bin\Prowin32.exe abnormal program
termination." Then after Vantage crashes, it says "invalid page fault in
module prowin32.dll."

-Clay Buchanan
Kams, Inc., Oklahoma City, OK
www.kamsinc.com




[Non-text portions of this message have been removed]