Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

PWE errors on win2003 TS/psql200i sp4/macola 7.6.100a

Status
Not open for further replies.

MacolaHelp

Instructor
Mar 19, 2003
659
US
Since moving from win2k TS to win2003 TS we get these errors immediately after logging into the server via remote desktop: PWE encountered an error and needed to close. Error signature is not helpful (all zeroes). Files referenced on error report contents do not exist (pwe.exe mdp & appcompat.txt). We get the error repeated as many times as users have logged off the TS since the current user last logged off. So, if I log off at 4pm, then 5 others log off, then I log back on at 6pm, I get the message 5 times with different time stamps. Using std progression doesn't create this condition. I've tried turning off logging for pwe on the TS. No dice. Only turning off all logging will eliminate the error. Remember, I get the error before I launch anything! I've double checked before log off to be sure vbmacexe is closing & it does indeed. We must use pwe as we use ICRs, many compiled reports on tabs, etc. Macola says send it in to microsoft, but if anyone else has ideas, I'm ready to try anything. I also got an internet explorer error twice today, so it is happening with other apps from time to time.
 
What happens if you log in as the Administrator to TS? And what do you mean by turning off all logging? Which logging are you referring to?

Scott Travis
infoSpring, LLC.
 
Logging: in my computer, advanced tab, error reporting. You can shut off all logging, or only for selected apps. I have shut off pwe.exe, macexe.exe, macola32.exe, vbmacexe.exe. If I disable error logging except fro critical errors, I don't get the messages. All users get these messages when logging in to terminal.
 
I would suggest following Macola's advice. The only thing that I can think to try is to make sure your client is using no more than 256 colors, my understanding is that Windows 2003 terminal services supports more colors now and this may be what's causing the problem. I've had a great deal of problems with the PWE splash screen in the past and bad graphics adapters. This is a complete shot in the dark.

Scott Travis
infoSpring, LLC.
 
Some progress of note: I had turned off only pwe.exe, in addition I have now turned off the other 3 exes in my previous post. Now, when I log onto terminal from my WS, I only get a few errors, but if I log on as me, I get many errors. Starting to think it is something stored on the local workstation invoking the remote desktop session. Some ini or something, maybe? Also a shot in the dark. No info back from microsoft from the network "gurus" as yet.
 
This might be stupid, but what about installing the Macola files on your TS? It got rid of most of our errors on our W2K TS.

Christine
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top