Community Discussions and Support
IErendrer upgrade crash Pmail

Thank for taking the time, Joerg . It is additional evidence the issue is specific to one W7 configuration conflicting with V2.6.3.6

 

<p>Thank for taking the time, Joerg . It is additional evidence the issue is specific to one W7 configuration conflicting with V2.6.3.6</p><p> </p>

My installation  is currently on a W2012 server share. Over the years this was migrated from Novell to a succession of Windows servers and may have accumulated unwanted files 

 
I need to upgrade IErenderer V.2.50 to V 2.636 but it crashes one of 1 of 3 PC, reverting to V2.5 restores sanity. On a W10 and a W7 Pmail starts fine whilst on another W7 Pmail freezes.
User1 use the W10 and user2 uses one of the W7 PC. (never at the same tie)
 
Pmail starts to load, the menu and panes are present but all panes are empty, the hourglass times out with a "not responding"
 
Any ideas how to investigate and fix this please. 
 
 
WinPMail version: Version 4.73.639, Mar 30 2018, build ID 639
Language resources: Standard UK English resource set
Extension Manager version: 1.14
Operating mode: Standalone
User name and ID: Pierre, 0
Windows version: 6.1
Windows flag word: 0
WINPMAIL.EXE directory: \\Valais\Martigny\PTT\PEGASUS
Home mailbox location: \\Valais\Martigny\PTT\PIERRE
New mailbox location: \\VALAIS\MARTIGNY\PTT\Pierre
TMP environment variable: F:\Temp
TEMP environment variable: F:\Temp
LAN-based SMTP support: N, N, N
NetWare MHS support: N, N, N
Built-in TCP/IP support: Enabled
  - WINSOCK version: WinSock 2.0
  - WINSOCK path: WSOCK32.DLL
Commandline: -I Pierre -id Apelec
Active -Z options: 32768
PMR variable: (None)
PML variable: (None)
MAI variable: (None)
NB variable: (None)
Autofiltering folders: 0 (0 active, 0 inactive)
Last new mail count: 26
Message size soft limit: 0 bytes
Message size hard limit: 0 bytes
Attachment size soft limit: 0 bytes
Attachment size hard limit: 0 bytes
 
 
 Many thanks
<div>My installation  is currently on a W2012 server share. Over the years this was migrated from Novell to a succession of Windows servers and may have accumulated unwanted files </div><div> </div><div> </div><div>I need to upgrade IErenderer V.2.50 to V 2.636 but it crashes one of 1 of 3 PC, reverting to V2.5 restores sanity. On a W10 and a W7 Pmail starts fine whilst on another W7 Pmail freezes.</div><div>User1 use the W10 and user2 uses one of the W7 PC. (never at the same tie)</div><div> </div><div>Pmail starts to load, the menu and panes are present but all panes are empty, the hourglass times out with a "not responding"</div><div> </div><div><span style="font-size: 10pt;">Any ideas how to investigate and fix this please. </span></div><div><span style="font-size: 10pt;"> </span></div><div> </div><div><span style="font-size: 13.3333px;">WinPMail version: Version 4.73.639, Mar 30 2018, build ID 639</span></div><div><span style="font-size: 13.3333px;">Language resources: Standard UK English resource set</span></div><div><span style="font-size: 13.3333px;">Extension Manager version: 1.14</span></div><div><span style="font-size: 13.3333px;">Operating mode: Standalone</span></div><div><span style="font-size: 13.3333px;">User name and ID: Pierre, 0</span></div><div><span style="font-size: 13.3333px;">Windows version: 6.1</span></div><div><span style="font-size: 13.3333px;">Windows flag word: 0</span></div><div><span style="font-size: 13.3333px;">WINPMAIL.EXE directory: \\Valais\Martigny\PTT\PEGASUS</span></div><div><span style="font-size: 13.3333px;">Home mailbox location: \\Valais\Martigny\PTT\PIERRE</span></div><div><span style="font-size: 13.3333px;">New mailbox location: \\VALAIS\MARTIGNY\PTT\Pierre</span></div><div><span style="font-size: 13.3333px;">TMP environment variable: F:\Temp</span></div><div><span style="font-size: 13.3333px;">TEMP environment variable: F:\Temp</span></div><div><span style="font-size: 13.3333px;">LAN-based SMTP support: N, N, N</span></div><div><span style="font-size: 13.3333px;">NetWare MHS support: N, N, N</span></div><div><span style="font-size: 13.3333px;">Built-in TCP/IP support: Enabled</span></div><div><span style="font-size: 13.3333px;">  - WINSOCK version: WinSock 2.0</span></div><div><span style="font-size: 13.3333px;">  - WINSOCK path: WSOCK32.DLL</span></div><div><span style="font-size: 13.3333px;">Commandline: -I Pierre -id Apelec</span></div><div><span style="font-size: 13.3333px;">Active -Z options: 32768</span></div><div><span style="font-size: 13.3333px;">PMR variable: (None)</span></div><div><span style="font-size: 13.3333px;">PML variable: (None)</span></div><div><span style="font-size: 13.3333px;">MAI variable: (None)</span></div><div><span style="font-size: 13.3333px;">NB variable: (None)</span></div><div><span style="font-size: 13.3333px;">Autofiltering folders: 0 (0 active, 0 inactive)</span></div><div><span style="font-size: 13.3333px;">Last new mail count: 26</span></div><div><span style="font-size: 13.3333px;">Message size soft limit: 0 bytes</span></div><div><span style="font-size: 13.3333px;">Message size hard limit: 0 bytes</span></div><div><span style="font-size: 13.3333px;">Attachment size soft limit: 0 bytes</span></div><div><span style="font-size: 13.3333px;">Attachment size hard limit: 0 bytes</span></div><div> </div><div> </div><div> Many thanks</div>

[quote user="Pierre"]Any ideas how to investigate and fix this please. [/quote]

How exactly did you do the upgrade?

<p>[quote user="Pierre"]<span style="font-size: 10pt;">Any ideas how to investigate and fix this please. </span>[/quote]</p><p>How exactly did you do the upgrade? </p>

			Michael

--
PGP Key ID (RSA 2048): 0xC45D831B
IERenderer's Home: https://www.pmpgp.de/renderer/History.htm
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

Was on PM 4.72, downloaded IERenderer2636.zip  and run IERendererSetup.exe withing the zip from the PC with the issue.

It discovered the correct path and I let it run.

 The two working PC reported V2636

Reverted to V2.50 in the same way.

 

Then upgraded PM to V4.73 and repeated above.

 

As all three PC load PM from the same shared folder, my thinking it that the procedure is correct. What do you think?

 

thank you for your assistance. 

<p>Was on PM 4.72, downloaded IERenderer2636.zip  and run IERendererSetup.exe withing the zip from the PC with the issue.</p><p>It discovered the correct path and I let it run.</p><p> The two working PC reported V2636</p><p><span style="font-size: 10pt;">Reverted to V2.50 in the same way.</span></p><p> </p><p><span style="font-size: 10pt;">Then upgraded PM to V4.73 and repeated above.</span></p><p> </p><p><span style="font-size: 10pt;">As all three PC load PM from the same shared folder, my thinking it that the procedure is correct. What do you think?</span></p><p> </p><p>thank you for your assistance. </p>

[quote user="Pierre"]As all three PC load PM from the same shared folder, my thinking it that the procedure is correct. What do you think?[/quote]

Well, my problem is that I have absolutely no experiences with shares and networks and especially not if Windows 10 comes into play with its access rights and anti virus issues etc. etc., Brian Fluet might be of a lot more help with regard to this stuff. My question would be whether it wouldn't be an idea to rather run upgrades and installs from the server than a client machine, but it's only a guess ...

<p>[quote user="Pierre"]<span style="font-size: 10pt;">As all three PC load PM from the same shared folder, my thinking it that the procedure is correct. What do you think?</span>[/quote]</p><p>Well, my problem is that I have absolutely no experiences with shares and networks and especially not if Windows 10 comes into play with its access rights and anti virus issues etc. etc., <a href="http://community.pmail.com/user/Profile.aspx?UserID=27894">Brian Fluet</a> might be of a lot more help with regard to this stuff. My question would be whether it wouldn't be an idea to rather run upgrades and installs from the server than a client machine, but it's only a guess ... </p>

			Michael

--
PGP Key ID (RSA 2048): 0xC45D831B
IERenderer's Home: https://www.pmpgp.de/renderer/History.htm
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

Hi Pierre,

Please note the following thread http://community.pmail.com/forums/thread/51071.aspx.  I experienced also problems when using the standard IER setup for our multi user environment where Pmail resides at a server. It seems it's a problem with VIEWER.PM. In the meantime I do not further use the official IER setup but extract the single files from the IER setup archive and replace the dll only. This works.

It's important that you always make a copmplete copy (backup) of the current Pmail directory at the server before updating anything, so that you are able to return to the former version!

<p>Hi Pierre,</p><p>Please note the following thread <a mce_href="/forums/thread/51071.aspx" title="http://community.pmail.com/forums/thread/51071.aspx" href="/forums/thread/51071.aspx">http://community.pmail.com/forums/thread/51071.aspx.</a>  I experienced also problems when using the standard IER setup for our multi user environment where Pmail resides at a server. It seems it's a problem with VIEWER.PM. In the meantime I do not further use the official IER setup but extract the single files from the IER setup archive and replace the dll only. This works.</p><p>It's important that you always make a copmplete copy (backup) of the current Pmail directory at the server before updating anything, so that you are able to return to the former version! </p>

[quote user="Joerg"]In the meantime I do not further use the official IER setup but extract the single files from the IER setup archive and replace the dll only. This works.[/quote]

Well, this won't be quite enough, there are some more files that need to be updated. They only get modified once in a while but it's important to keep track of them nevertheless since they provide the resource strings used for providing IER's user interface (i.e. menu entries, dialogs and help text): These files are the HTML files named BearHlpIE-En.htm etc. Their names are referencing the first Pegasus Mail HTML renderer replacement created by Martin Ireland (BearHtml), IER's rendering machine (IE) and the languages being used as far as there've been volunteers for translating them in the past (i.e. the French and Italian versions aren't quite complete anymore). For hints about unpacking the IER setup file see here.

<p>[quote user="Joerg"]In the meantime I do not further use the official IER setup but extract the single files from the IER setup archive and replace the dll only. This works.[/quote]</p><p>Well, this won't be quite enough, there are some more files that need to be updated. They only get modified once in a while but it's important to keep track of them nevertheless since they provide the resource strings used for providing IER's user interface (i.e. menu entries, dialogs and help text): These files are the HTML files named BearHlpIE-En.htm etc. Their names are referencing the first Pegasus Mail HTML renderer replacement created by Martin Ireland (BearHtml), IER's rendering machine (IE) and the languages being used as far as there've been volunteers for translating them in the past (i.e. the French and Italian versions aren't quite complete anymore). For hints about unpacking the IER setup file see <a mce_href="/files/folders/community_add-ons_for_pegasus_mail/entry24145.aspx#HowToUnpack" target="_blank" href="/files/folders/community_add-ons_for_pegasus_mail/entry24145.aspx#HowToUnpack">here</a>. </p>

			Michael

--
PGP Key ID (RSA 2048): 0xC45D831B
IERenderer's Home: https://www.pmpgp.de/renderer/History.htm
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

You are right, but, when I remember correctly, these files have not been changed the last time of IER update. But of course, checking and comparing the creation dates of all contained files in the setup with the current installation is recommended, but I didn't change the viewer.pm anyhow.

You are right, but, when I remember correctly, these files have not been changed the last time of IER update. But of course, checking and comparing the creation dates of all contained files in the setup with the current installation is recommended, but I didn't change the viewer.pm anyhow.

Thank you for the comment. I tried as you suggested and copied IERenderer.dll only (the other files appear to be same size same date). I am afraid this has not made any difference.

 W10 PC loads PM IErenderer V2.636 and all is fine.

 W7 PC start to load PM and hangs "not responding"

 

It would appear to be something in IERenderer.dll or perhaps LibTidy5.dll interfere with this one machine only.


I noticed in install_script.iss that V2.6 has two extra lines over V2.5

 line23  - Source: "{app}\IERenderer\LibTidy5.dll"; DestDir: "{app}\IERenderer"; Flags: promptifolder

 line51 - Type: files; Name: "{app}\LibTidy5.dll"; 

 

Clutching at straw here :( 


<p>Thank you for the comment. I tried as you suggested and copied IERenderer.dll only (the other files appear to be same size same date). I am afraid this has not made any difference.</p><p> W10 PC loads PM IErenderer V2.636 and all is fine.</p><p> W7 PC start to load PM and hangs "not responding"</p><p> </p><p><span style="font-size: 10pt;">It would appear to be something in </span><span style="font-size: 13.3333px;">IERenderer.dll or perhaps LibTidy5.dll interfere with this one machine only.</span></p><p> </p><p>I noticed in install_script.iss that V2.6 has two extra lines over V2.5</p><p> line23  - Source: "{app}\IERenderer\LibTidy5.dll"; DestDir: "{app}\IERenderer"; Flags: promptifolder</p><p> line51 - Type: files; Name: "{app}\LibTidy5.dll"; </p><p> </p><p><span style="font-size: 10pt;">Clutching at straw here :( </span></p><p> </p>

I do not believe the issue is related to a shared installation, after all PM was design, all those years ago, for Novell Network and it has worked for me for the last 20+ years. In this case W10 is not relevant as it is working perfectly well with V2.6

 

Would the event log give a clue?  (sorry about the long post)

 

Error #1 

The program winpm-32.exe version 4.7.3.639 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.

Process ID: 186c

 Start Time: 01d6494758c302a8

 Termination Time: 12

 Application Path: \\Valais\Martigny\PTT\PEGASUS\winpm-32.exe

 Report Id: bf4f5419-b53a-11ea-ae5e-00241daed5d1

 

Nothing relevant in the Action Center 

 

Error #2

Fault bucket , type 0

Event Name: AppHangB1

Response: Not available

Cab Id: 0


Problem signature:

P1: winpm-32.exe

P2: 4.7.3.639

P3: 5ac43ebf

P4: bb1e

P5: 0

P6: 

P7: 

P8: 

P9: 

P10: 


Attached files:

F:\Temp\WER516D.tmp.appcompat.txt

F:\Temp\WER519D.tmp.WERInternalMetadata.xml


These files may be available here:

C:\Users\pierre.ONSLOW\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppHang_winpm-32.exe_10a784b7f540dbf2106fead21af92e4959a3a5c_21fa5489


Analysis symbol: 

Rechecking for solution: 0

Report Id: bf4f5419-b53a-11ea-ae5e-00241daed5d1

Report Status: 1 

 


Content of WER

please note the two lines I marked >>>>>>>  is that correct?

 

Version=1

EventType=AppHangB1

EventTime=132373810521679192

ReportType=3

Consent=1

UploadTime=132373810543179192

ReportIdentifier=bf4f5418-b53a-11ea-ae5e-00241daed5d1

IntegratorReportIdentifier=bf4f5419-b53a-11ea-ae5e-00241daed5d1

WOW64=1

Response.type=4

Sig[0].Name=Application Name

Sig[0].Value=winpm-32.exe

Sig[1].Name=Application Version

Sig[1].Value=4.7.3.639

Sig[2].Name=Application Timestamp

Sig[2].Value=5ac43ebf

Sig[3].Name=Hang Signature

Sig[3].Value=bb1e

Sig[4].Name=Hang Type

Sig[4].Value=0

DynamicSig[1].Name=OS Version

DynamicSig[1].Value=6.1.7601.2.1.0.256.1

DynamicSig[2].Name=Locale ID

DynamicSig[2].Value=2057

DynamicSig[22].Name=Additional Hang Signature 1

DynamicSig[22].Value=bb1ee84150af6aaaabadf5b9a6d27840

DynamicSig[23].Name=Additional Hang Signature 2

DynamicSig[23].Value=1410

DynamicSig[24].Name=Additional Hang Signature 3

DynamicSig[24].Value=14103faed19411a71f153e16e2f49fe3

DynamicSig[25].Name=Additional Hang Signature 4

DynamicSig[25].Value=bb1e

DynamicSig[26].Name=Additional Hang Signature 5

DynamicSig[26].Value=bb1ee84150af6aaaabadf5b9a6d27840

DynamicSig[27].Name=Additional Hang Signature 6

DynamicSig[27].Value=1410

DynamicSig[28].Name=Additional Hang Signature 7

DynamicSig[28].Value=14103faed19411a71f153e16e2f49fe3

UI[3]=Pegasus Mail for Windows is not responding

UI[4]=If you close the program, you might lose information.

UI[5]=Close the program

UI[6]=Close the program

UI[7]=Close the program

LoadedModule[0]=\\Valais\Martigny\PTT\PEGASUS\winpm-32.exe

LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll

LoadedModule[2]=C:\Windows\syswow64\kernel32.dll

LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll

LoadedModule[4]=\\Valais\Martigny\PTT\PEGASUS\TER32.dll

LoadedModule[5]=C:\Windows\syswow64\ole32.dll

LoadedModule[6]=C:\Windows\syswow64\msvcrt.dll

LoadedModule[7]=C:\Windows\syswow64\GDI32.dll

LoadedModule[8]=C:\Windows\syswow64\USER32.dll

LoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dll

LoadedModule[10]=C:\Windows\SysWOW64\sechost.dll

LoadedModule[11]=C:\Windows\syswow64\RPCRT4.dll

LoadedModule[12]=C:\Windows\syswow64\SspiCli.dll

LoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dll

LoadedModule[14]=C:\Windows\syswow64\LPK.dll

LoadedModule[15]=C:\Windows\syswow64\USP10.dll

LoadedModule[16]=C:\Windows\syswow64\SHELL32.dll

LoadedModule[17]=C:\Windows\syswow64\SHLWAPI.dll

LoadedModule[18]=C:\Windows\syswow64\COMDLG32.dll

LoadedModule[19]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18837_none_41e855142bd5705d\COMCTL32.dll

LoadedModule[20]=C:\Windows\system32\WINSPOOL.DRV

LoadedModule[21]=C:\Windows\syswow64\IMM32.dll

LoadedModule[22]=C:\Windows\syswow64\MSCTF.dll

LoadedModule[23]=C:\Windows\syswow64\OLEAUT32.dll

LoadedModule[24]=\\Valais\Martigny\PTT\PEGASUS\HTS32.dll

LoadedModule[25]=\\Valais\Martigny\PTT\PEGASUS\PMHelp.dll

LoadedModule[26]=\\Valais\Martigny\PTT\PEGASUS\TextEdit.dll

LoadedModule[27]=C:\Windows\system32\MSIMG32.dll

LoadedModule[28]=\\Valais\Martigny\PTT\PEGASUS\FreeImage.dll

LoadedModule[29]=C:\Windows\syswow64\WS2_32.dll

LoadedModule[30]=C:\Windows\syswow64\NSI.dll

LoadedModule[31]=\\Valais\Martigny\PTT\PEGASUS\tcpip.dll

LoadedModule[32]=\\Valais\Martigny\PTT\PEGASUS\LIBEAY32.dll

LoadedModule[33]=\\Valais\Martigny\PTT\PEGASUS\SSLEAY32.dll

LoadedModule[34]=C:\Windows\system32\VERSION.dll

LoadedModule[35]=C:\Windows\system32\WINMM.dll

LoadedModule[36]=C:\Windows\SysWOW64\SophosAV\SOPHOS~1.DLL

LoadedModule[37]=C:\Windows\syswow64\PSAPI.DLL

LoadedModule[38]=C:\Windows\system32\api-ms-win-core-synch-l1-2-0.DLL

LoadedModule[39]=\\Valais\Martigny\PTT\PEGASUS\SSGP.DLL

LoadedModule[40]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.23721_none_5c052bcda00f9399\gdiplus.dll

LoadedModule[41]=C:\Windows\system32\UxTheme.dll

LoadedModule[42]=\\Valais\Martigny\PTT\PEGASUS\ICONV.DLL

LoadedModule[43]=C:\Windows\syswow64\WININET.DLL

LoadedModule[44]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll

LoadedModule[45]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll

LoadedModule[46]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll

LoadedModule[47]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll

LoadedModule[48]=C:\Windows\syswow64\normaliz.DLL

LoadedModule[49]=C:\Windows\syswow64\iertutil.dll

LoadedModule[50]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll

LoadedModule[51]=C:\Windows\syswow64\USERENV.dll

LoadedModule[52]=C:\Windows\syswow64\profapi.dll

LoadedModule[53]=C:\Windows\system32\MSFTEDIT.DLL

LoadedModule[54]=C:\Windows\system32\CRYPTSP.dll

LoadedModule[55]=C:\Windows\system32\rsaenh.dll

LoadedModule[56]=C:\Windows\system32\WSOCK32.DLL

LoadedModule[57]=\\Valais\Martigny\PTT\PEGASUS\wi_sph.dll

LoadedModule[58]=C:\Windows\system32\mpr.dll

LoadedModule[59]=\\Valais\Martigny\PTT\PEGASUS\sqlite3.dll

LoadedModule[60]=\\Valais\Martigny\PTT\PEGASUS\DICT.RLO

LoadedModule[61]=\\Valais\Martigny\PTT\PEGASUS\libhunspell.dll

LoadedModule[62]=\\Valais\Martigny\PTT\PEGASUS\IERenderer\IERenderer.dll

LoadedModule[63]=C:\Windows\syswow64\crypt32.dll

LoadedModule[64]=C:\Windows\syswow64\MSASN1.dll

LoadedModule[65]=C:\Windows\system32\olepro32.dll

LoadedModule[66]=C:\Windows\system32\Riched32.dll

LoadedModule[67]=C:\Windows\system32\RICHED20.dll

LoadedModule[68]=C:\Windows\syswow64\UrlMon.dll

LoadedModule[69]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll

>>>>>>>>>> LoadedModule[70]=\\Valais\Martigny\PTT\PEGASUS\LibTidy.dll           

>>>>>>>>>> LoadedModule[71]=\\Valais\Martigny\PTT\PEGASUS\IERenderer\LibTidy5.dll

LoadedModule[72]=C:\Windows\syswow64\SETUPAPI.dll

LoadedModule[73]=C:\Windows\syswow64\CFGMGR32.dll

LoadedModule[74]=C:\Windows\syswow64\DEVOBJ.dll

LoadedModule[75]=C:\Windows\syswow64\CLBCatQ.DLL

LoadedModule[76]=C:\Windows\system32\propsys.dll

LoadedModule[77]=C:\Windows\system32\ntmarta.dll

LoadedModule[78]=C:\Windows\syswow64\WLDAP32.dll

FriendlyEventName=Stopped responding and was closed

ConsentKey=AppHangXProcB1

AppName=Pegasus Mail for Windows

AppPath=\\Valais\Martigny\PTT\PEGASUS\winpm-32.exe

ReportDescription=A problem caused this program to stop interacting with Windows.

 

<p>I do not believe the issue is related to a shared installation, after all PM was design, all those years ago, for Novell Network and it has worked for me for the last 20+ years. In this case W10 is not relevant as it is working perfectly well with V2.6</p><p> </p><p>Would the event log give a clue?  (sorry about the long post)</p><p> </p><p>Error #1 </p><p><span style="font-size: 13.3333px;">Th</span>e program winpm-32.exe version 4.7.3.639 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.</p><p><span style="font-size: 10pt;">Process ID: 186c</span></p><p><span style="font-size: 13.3333px;"> Start Time: 01d6494758c302a8</span></p><p><span style="font-size: 13.3333px;"> Termination Time: 12</span></p><p><span style="font-size: 13.3333px;"> Application Path: \\Valais\Martigny\PTT\PEGASUS\winpm-32.exe</span></p><p><span style="font-size: 13.3333px;"> Report Id: bf4f5419-b53a-11ea-ae5e-00241daed5d1</span></p><p> </p><p>Nothing relevant in the Action Center </p><p> </p><p>Error #2</p><p><span style="font-size: 13.3333px;">Fault bucket , type 0</span></p><p><span style="font-size: 13.3333px;">Event Name: AppHangB1</span></p><p><span style="font-size: 13.3333px;">Response: Not available</span></p><p><span style="font-size: 13.3333px;">Cab Id: 0</span></p><p><span style="font-size: 13.3333px;"> </span></p><p><span style="font-size: 13.3333px;">Problem signature:</span></p><p><span style="font-size: 13.3333px;">P1: winpm-32.exe</span></p><p><span style="font-size: 13.3333px;">P2: 4.7.3.639</span></p><p><span style="font-size: 13.3333px;">P3: 5ac43ebf</span></p><p><span style="font-size: 13.3333px;">P4: bb1e</span></p><p><span style="font-size: 13.3333px;">P5: 0</span></p><p><span style="font-size: 13.3333px;">P6: </span></p><p><span style="font-size: 13.3333px;">P7: </span></p><p><span style="font-size: 13.3333px;">P8: </span></p><p><span style="font-size: 13.3333px;">P9: </span></p><p><span style="font-size: 13.3333px;">P10: </span></p><p><span style="font-size: 13.3333px;"> </span></p><p><span style="font-size: 13.3333px;">Attached files:</span></p><p><span style="font-size: 13.3333px;">F:\Temp\WER516D.tmp.appcompat.txt</span></p><p><span style="font-size: 13.3333px;">F:\Temp\WER519D.tmp.WERInternalMetadata.xml</span></p><p><span style="font-size: 13.3333px;"> </span></p><p><span style="font-size: 13.3333px;">These files may be available here:</span></p><p><span style="font-size: 13.3333px;">C:\Users\pierre.ONSLOW\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppHang_winpm-32.exe_10a784b7f540dbf2106fead21af92e4959a3a5c_21fa5489</span></p><p><span style="font-size: 13.3333px;"> </span></p><p><span style="font-size: 13.3333px;">Analysis symbol: </span></p><p><span style="font-size: 13.3333px;">Rechecking for solution: 0</span></p><p><span style="font-size: 13.3333px;">Report Id: bf4f5419-b53a-11ea-ae5e-00241daed5d1</span></p><p><span style="font-size: 13.3333px;">Report Status: 1</span> </p><p> </p><p> </p><p>Content of WER </p><p>please note the two lines I marked >>>>>>>  is that correct?</p><p> </p><p><span style="font-size: 13.3333px;">Version=1</span></p><p><span style="font-size: 13.3333px;">EventType=AppHangB1</span></p><p><span style="font-size: 13.3333px;">EventTime=132373810521679192</span></p><p><span style="font-size: 13.3333px;">ReportType=3</span></p><p><span style="font-size: 13.3333px;">Consent=1</span></p><p><span style="font-size: 13.3333px;">UploadTime=132373810543179192</span></p><p><span style="font-size: 13.3333px;">ReportIdentifier=bf4f5418-b53a-11ea-ae5e-00241daed5d1</span></p><p><span style="font-size: 13.3333px;">IntegratorReportIdentifier=bf4f5419-b53a-11ea-ae5e-00241daed5d1</span></p><p><span style="font-size: 13.3333px;">WOW64=1</span></p><p><span style="font-size: 13.3333px;">Response.type=4</span></p><p><span style="font-size: 13.3333px;">Sig[0].Name=Application Name</span></p><p><span style="font-size: 13.3333px;">Sig[0].Value=winpm-32.exe</span></p><p><span style="font-size: 13.3333px;">Sig[1].Name=Application Version</span></p><p><span style="font-size: 13.3333px;">Sig[1].Value=4.7.3.639</span></p><p><span style="font-size: 13.3333px;">Sig[2].Name=Application Timestamp</span></p><p><span style="font-size: 13.3333px;">Sig[2].Value=5ac43ebf</span></p><p><span style="font-size: 13.3333px;">Sig[3].Name=Hang Signature</span></p><p><span style="font-size: 13.3333px;">Sig[3].Value=bb1e</span></p><p><span style="font-size: 13.3333px;">Sig[4].Name=Hang Type</span></p><p><span style="font-size: 13.3333px;">Sig[4].Value=0</span></p><p><span style="font-size: 13.3333px;">DynamicSig[1].Name=OS Version</span></p><p><span style="font-size: 13.3333px;">DynamicSig[1].Value=6.1.7601.2.1.0.256.1</span></p><p><span style="font-size: 13.3333px;">DynamicSig[2].Name=Locale ID</span></p><p><span style="font-size: 13.3333px;">DynamicSig[2].Value=2057</span></p><p><span style="font-size: 13.3333px;">DynamicSig[22].Name=Additional Hang Signature 1</span></p><p><span style="font-size: 13.3333px;">DynamicSig[22].Value=bb1ee84150af6aaaabadf5b9a6d27840</span></p><p><span style="font-size: 13.3333px;">DynamicSig[23].Name=Additional Hang Signature 2</span></p><p><span style="font-size: 13.3333px;">DynamicSig[23].Value=1410</span></p><p><span style="font-size: 13.3333px;">DynamicSig[24].Name=Additional Hang Signature 3</span></p><p><span style="font-size: 13.3333px;">DynamicSig[24].Value=14103faed19411a71f153e16e2f49fe3</span></p><p><span style="font-size: 13.3333px;">DynamicSig[25].Name=Additional Hang Signature 4</span></p><p><span style="font-size: 13.3333px;">DynamicSig[25].Value=bb1e</span></p><p><span style="font-size: 13.3333px;">DynamicSig[26].Name=Additional Hang Signature 5</span></p><p><span style="font-size: 13.3333px;">DynamicSig[26].Value=bb1ee84150af6aaaabadf5b9a6d27840</span></p><p><span style="font-size: 13.3333px;">DynamicSig[27].Name=Additional Hang Signature 6</span></p><p><span style="font-size: 13.3333px;">DynamicSig[27].Value=1410</span></p><p><span style="font-size: 13.3333px;">DynamicSig[28].Name=Additional Hang Signature 7</span></p><p><span style="font-size: 13.3333px;">DynamicSig[28].Value=14103faed19411a71f153e16e2f49fe3</span></p><p><span style="font-size: 13.3333px;">UI[3]=Pegasus Mail for Windows is not responding</span></p><p><span style="font-size: 13.3333px;">UI[4]=If you close the program, you might lose information.</span></p><p><span style="font-size: 13.3333px;">UI[5]=Close the program</span></p><p><span style="font-size: 13.3333px;">UI[6]=Close the program</span></p><p><span style="font-size: 13.3333px;">UI[7]=Close the program</span></p><p><span style="font-size: 13.3333px;">LoadedModule[0]=\\Valais\Martigny\PTT\PEGASUS\winpm-32.exe</span></p><p><span style="font-size: 13.3333px;">LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[2]=C:\Windows\syswow64\kernel32.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[4]=\\Valais\Martigny\PTT\PEGASUS\TER32.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[5]=C:\Windows\syswow64\ole32.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[6]=C:\Windows\syswow64\msvcrt.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[7]=C:\Windows\syswow64\GDI32.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[8]=C:\Windows\syswow64\USER32.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[10]=C:\Windows\SysWOW64\sechost.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[11]=C:\Windows\syswow64\RPCRT4.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[12]=C:\Windows\syswow64\SspiCli.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[14]=C:\Windows\syswow64\LPK.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[15]=C:\Windows\syswow64\USP10.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[16]=C:\Windows\syswow64\SHELL32.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[17]=C:\Windows\syswow64\SHLWAPI.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[18]=C:\Windows\syswow64\COMDLG32.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[19]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18837_none_41e855142bd5705d\COMCTL32.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[20]=C:\Windows\system32\WINSPOOL.DRV</span></p><p><span style="font-size: 13.3333px;">LoadedModule[21]=C:\Windows\syswow64\IMM32.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[22]=C:\Windows\syswow64\MSCTF.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[23]=C:\Windows\syswow64\OLEAUT32.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[24]=\\Valais\Martigny\PTT\PEGASUS\HTS32.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[25]=\\Valais\Martigny\PTT\PEGASUS\PMHelp.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[26]=\\Valais\Martigny\PTT\PEGASUS\TextEdit.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[27]=C:\Windows\system32\MSIMG32.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[28]=\\Valais\Martigny\PTT\PEGASUS\FreeImage.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[29]=C:\Windows\syswow64\WS2_32.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[30]=C:\Windows\syswow64\NSI.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[31]=\\Valais\Martigny\PTT\PEGASUS\tcpip.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[32]=\\Valais\Martigny\PTT\PEGASUS\LIBEAY32.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[33]=\\Valais\Martigny\PTT\PEGASUS\SSLEAY32.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[34]=C:\Windows\system32\VERSION.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[35]=C:\Windows\system32\WINMM.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[36]=C:\Windows\SysWOW64\SophosAV\SOPHOS~1.DLL</span></p><p><span style="font-size: 13.3333px;">LoadedModule[37]=C:\Windows\syswow64\PSAPI.DLL</span></p><p><span style="font-size: 13.3333px;">LoadedModule[38]=C:\Windows\system32\api-ms-win-core-synch-l1-2-0.DLL</span></p><p><span style="font-size: 13.3333px;">LoadedModule[39]=\\Valais\Martigny\PTT\PEGASUS\SSGP.DLL</span></p><p><span style="font-size: 13.3333px;">LoadedModule[40]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.23721_none_5c052bcda00f9399\gdiplus.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[41]=C:\Windows\system32\UxTheme.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[42]=\\Valais\Martigny\PTT\PEGASUS\ICONV.DLL</span></p><p><span style="font-size: 13.3333px;">LoadedModule[43]=C:\Windows\syswow64\WININET.DLL</span></p><p><span style="font-size: 13.3333px;">LoadedModule[44]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[45]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[46]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[47]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[48]=C:\Windows\syswow64\normaliz.DLL</span></p><p><span style="font-size: 13.3333px;">LoadedModule[49]=C:\Windows\syswow64\iertutil.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[50]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[51]=C:\Windows\syswow64\USERENV.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[52]=C:\Windows\syswow64\profapi.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[53]=C:\Windows\system32\MSFTEDIT.DLL</span></p><p><span style="font-size: 13.3333px;">LoadedModule[54]=C:\Windows\system32\CRYPTSP.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[55]=C:\Windows\system32\rsaenh.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[56]=C:\Windows\system32\WSOCK32.DLL</span></p><p><span style="font-size: 13.3333px;">LoadedModule[57]=\\Valais\Martigny\PTT\PEGASUS\wi_sph.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[58]=C:\Windows\system32\mpr.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[59]=\\Valais\Martigny\PTT\PEGASUS\sqlite3.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[60]=\\Valais\Martigny\PTT\PEGASUS\DICT.RLO</span></p><p><span style="font-size: 13.3333px;">LoadedModule[61]=\\Valais\Martigny\PTT\PEGASUS\libhunspell.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[62]=\\Valais\Martigny\PTT\PEGASUS\IERenderer\IERenderer.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[63]=C:\Windows\syswow64\crypt32.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[64]=C:\Windows\syswow64\MSASN1.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[65]=C:\Windows\system32\olepro32.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[66]=C:\Windows\system32\Riched32.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[67]=C:\Windows\system32\RICHED20.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[68]=C:\Windows\syswow64\UrlMon.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[69]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll</span></p><p><span style="font-size: 13.3333px;">>>>>>>>>>> LoadedModule[70]=\\Valais\Martigny\PTT\PEGASUS\LibTidy.dll           </span></p><p><span style="font-size: 13.3333px;">>>>>>>>>>> LoadedModule[71]=\\Valais\Martigny\PTT\PEGASUS\IERenderer\LibTidy5.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[72]=C:\Windows\syswow64\SETUPAPI.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[73]=C:\Windows\syswow64\CFGMGR32.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[74]=C:\Windows\syswow64\DEVOBJ.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[75]=C:\Windows\syswow64\CLBCatQ.DLL</span></p><p><span style="font-size: 13.3333px;">LoadedModule[76]=C:\Windows\system32\propsys.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[77]=C:\Windows\system32\ntmarta.dll</span></p><p><span style="font-size: 13.3333px;">LoadedModule[78]=C:\Windows\syswow64\WLDAP32.dll</span></p><p><span style="font-size: 13.3333px;">FriendlyEventName=Stopped responding and was closed</span></p><p><span style="font-size: 13.3333px;">ConsentKey=AppHangXProcB1</span></p><p><span style="font-size: 13.3333px;">AppName=Pegasus Mail for Windows</span></p><p><span style="font-size: 13.3333px;">AppPath=\\Valais\Martigny\PTT\PEGASUS\winpm-32.exe</span></p><p><span style="font-size: 13.3333px;">ReportDescription=A problem caused this program to stop interacting with Windows.</span></p><p> </p>

Did you return to the latest running installation before you've tried to copy the new IER dll? Therefore I always duplicate (copy) the entire Pmail directory. Hope you got a backup of the last running Pmail installation at the server.

When the last working condition is restored and working also with W7 client, try to replace the IER dll only (if all other auxiliary files are of no newer date)

<p>Did you return to the latest running installation before you've tried to copy the new IER dll? Therefore I always duplicate (copy) the entire Pmail directory. Hope you got a backup of the last running Pmail installation at the server.</p><p>When the last working condition is restored and working also with W7 client, try to replace the IER dll only (if all other auxiliary files are of no newer date) </p>

Like Joerg, I extract the IERenderer installation file and then manually replace the files that have changed.

Do I understand correctly that the problem is only on one Win7 PC; it is fine on other Win7 and Win10 PC's?  If so, is the problem Win7 PC the one that the IER installs were run on?
<p>Like Joerg, I extract the IERenderer installation file and then manually replace the files that have changed.</p>Do I understand correctly that the problem is only on one Win7 PC; it is fine on other Win7 and Win10 PC's?  If so, is the problem Win7 PC the one that the IER installs were run on?

Michael,

What are your thoughts on whether running the IER installer from that Win7 PC created some registry or other entries that are incompatible with the execution of the shared installation?  Do you think uninstalling it using that PC and then installing it to the server manually would reverse whatever happened?

<p>Michael,</p><p>What are your thoughts on whether running the IER installer from that Win7 PC created some registry or other entries that are incompatible with the execution of the shared installation?  Do you think uninstalling it using that PC and then installing it to the server manually would reverse whatever happened? </p>

A registry search for Pegasus show a few entries, mainly SendTo and basis Software path, mailbox location and user. plus a few keys I don't understand (can anyone?)

<p>A registry search for Pegasus show a few entries, mainly SendTo and basis Software path, mailbox location and user. plus a few keys I don't understand (can anyone?)</p>

Pierre, When I posted earlier I was thinking of a machine specific problem without thinking that it might be Pegasus Mail user specific.  Do you know whether it is PC or PMail user specific?

Pierre, When I posted earlier I was thinking of a machine specific problem without thinking that it might be Pegasus Mail user specific.  Do you know whether it is PC or PMail user specific?

I believe it is machine specific.

If PM is started from an other W7 PC with same short cut

\\Valais\Martigny\PTT\PEGASUS\winpm-32.exe -I Pierre -id Apelec

it works perfectly well with V2.636

This use the same executable and same user as per rogue PC

 

<p>I believe it is machine specific.</p><p>If PM is started from an other W7 PC with same short cut</p><p>\\Valais\Martigny\PTT\PEGASUS\winpm-32.exe -I Pierre -id Apelec</p><p><span style="font-size: 10pt;">it works </span><span style="font-size: 10pt;">perfectly well with V2.636</span></p><p>This use the same executable and same user as per rogue PC</p><p> </p>

[quote user="Brian Fluet"]Do you think uninstalling it using that PC and then installing it to the server manually would reverse whatever happened?[/quote]

IER doesn't add any Registry entires other than its uninstall entry. Other setup entries created by the IER setup are the path entries in renderer.pm (containing the relative path below Pegasus Mail's ...\programs\ subdirectory) and IERenderer.fff containing the location of IERenderer.dll (usually Form DLL = "~a\IERenderer\IERenderer.dll" where "~a" substitutes the full path of the same ...\programs\ subdirectory). Both these entries are "hard coded" and don't need to be changed at any time as long as nobody moves the IER directory to a different location. All of IERs files including the ones mentioned above should be deleted automatically on unistall.

<p>[quote user="Brian Fluet"]Do you think uninstalling it using that PC and then installing it to the server manually would reverse whatever happened?[/quote]</p><p>IER doesn't add any Registry entires other than its uninstall entry. Other setup entries created by the IER setup are the path entries in <i>renderer.pm</i> (containing the relative path below Pegasus Mail's ...\programs\ subdirectory) and <i>IERenderer.fff</i> containing the location of IERenderer.dll (usually Form DLL = "~a\IERenderer\IERenderer.dll" where "~a" substitutes the full path of the same ...\programs\ subdirectory). Both these entries are "hard coded" and don't need to be changed at any time as long as nobody moves the IER directory to a different location. All of IERs files including the ones mentioned above should be deleted automatically on unistall. </p>

			Michael

--
PGP Key ID (RSA 2048): 0xC45D831B
IERenderer's Home: https://www.pmpgp.de/renderer/History.htm
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

Machine specific indicates that you have encountered the same problem Joerg did.

Nothing in the post just made by Michael contradicts that so if I were you I would uninstall IER and then add it back manually (backup first).

  • make certain no one is running Pegasus Mail
  • Use Add/Remove Programs on that PC to remove IER (listed as something like Pegasus Mail HTML Renderer)
  • Manually add IERenderer files to \PTT\PEGASUS from an extracted installation file (replace any existing ones)
  • test a PMail startup


<p>Machine specific indicates that you have encountered the same problem Joerg did.</p><p>Nothing in the post just made by Michael contradicts that so if I were you I would uninstall IER and then add it back manually (backup first). </p><ul><li>make certain no one is running Pegasus Mail </li><li>Use Add/Remove Programs on that PC to remove IER (listed as something like Pegasus Mail HTML Renderer)</li><li>Manually add IERenderer files to \PTT\PEGASUS from an extracted installation file (replace any existing ones) </li><li>test a PMail startup</li></ul><div> </div><div> </div>
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft