Brian,

I have been shutting Pegasus down every few days since you provided the advice to do so and it seems to be working as it should. So I suspect that we can put this to bed for the time being and see if anything develops from here but for now, I'm satisfied.

Thanks again for your help and also to  others that offered suggestions.

Larry

I need a little bit of help, again.

This just started about a month ago on the 6th of November and it happens every week for no reason,
the 6th, 11th, 19th and 26th. Pegasus just shuts down and comes back up again with the
screen, exit or continue. I hit continue and away we go again for another week. I am
running Windows 10 Home edition. Pegasus is version 4.72 64 bit.

I have gone to Event Viewer, Windows Logs, applications and clicked on the error messages.
I have downloaded the 4 error messages that were associated with each error and if someone
can help, I can attach them to a post here as a Word/Notepad document for viewing and perhaps
a clue.

Thanks!

Larry Thivierge

See this thread: http://community.pmail.com/forums/thread/31478.aspx

The mini-dump extension creates a crash dump that can be submitted for analysis.

Also, could it be something like an app update (AV?) that is closing all open processes, doing its thing, then restarting them?  Perhaps the Event Viewer shows something occurring just prior to the Pegasus Mail restarts.

Hi Larry,

I experienced a similar issue with Mercury under Windows Server 2016, where the Mercury Icon of the running program within the Windows SysTray disappears after a few days (don't know whether it was always a 7 day period). I'm always took for granted that Windows Server 2016 (which has the same system architecture as Windows 10) has shut down the program, but checking the task manager shows that it's always still running and only the icon disappears (or has been removed by Windows). Please feel free and read the entire thread here: http://community.pmail.com/forums/thread/48118.asp

But without the icon I'm not able to open the corresponding GUI. To get access to, I have to kill the running Mercury process first, followed by a restart of Mercury where the GUI starts again.

Finally I have created a Windows Service which is starting Mercury automatically but without GUI. For any necessary adjustments I have to stop the service first, followed by manually starting of Mercury with GUI, making the adjustments, quit Mercury, retstart the service.

It seems to be a Windows 10 / Server 2016 issue that "long time running" icons (in the systray) or programs are being removed from the desktop while the process is still running. I remember a similar issue in W7 where Icons are removed from the desktop when they where not used for a specific period. I could imagine that W10 / Server2016 is removing long time running programs from the desktop as well in case of missing user interaction with.

Cheers

Joerg

Thanks Brian!

I'm not sure how to get into the community.pmail to read the thread you have shown.

I tried to find something that EV shows occurring just prior to the Pegasus Mail restarts. I really don't see or read where it does start. However what I did was take the line right after the app failed and will show it here. I did the same for each failure and it's pretty well the same thing. I hope this doesn't take up too much. If it does, please do not hesitate to tell me. Here it is:

 Log Name:      Application
Source:        Windows Error Reporting
Date:          11/26/2017 8:13:00 PM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Larry-PC
Description:
Fault bucket 129086725907, type 5
Event Name: FaultTolerantHeap
Response: Not available
Cab Id: 0

Problem signature:
P1: winpm-32.exe
P2: 4.7.2.572
P3: 56C65793
P4: ffffbaad
P5:
P6:
P7:
P8:
P9:
P10:

I hope this will tell you something.

Thanks!

Larry

Hello Joerg,

thanks for your post to me. I will try and read the thread that you provided however as I mentioned to Brian, above, I'm not sure how to get into that Section.

I just did a post to Brian on this subject and perhaps you could look and see what I've pasted into my reply.

Thanks!

Larry

Brian, I have found the thread and read about the crash dump. The question then becomes when do you create it. If you don't notice the crash for several hours do you just go back and create the dump anyway or do you re-start Pegasus again first. I suspect you would create the dump first however I see what you are driving at.

Larry

Joerg,

another post - I found the thread but the number you have quoted is not available.

Larry

Larry,

Unfortunately that Event Viewer content doesn't help.  It's just the record of the Fault Tolerant Heap kicking in.  If you aren't familiar with it it's a Windows subsystem that is supposed to help with application crashes.  I don't know any more than that about it but it's not the cause.  Perhaps it is what restarts Pegusus Mail when it crashes.  I just don't know.

As for the crash dump, it gets created automatically when Pegasus Mail crashes, generating a queued message that can be sent for evaluation. 

Finally, if you are running Pegasus Mail for weeks at a time without restart I think it would be wise to restart it at least every couple of days.  I may be dependent on the self-maintenance it performs during startups and shutdowns.

Brian,

I think you are on to something regarding a shut down of Pegasus every few days. I have a habit of just leaving it running. Now I just turned it off several days ago and then back on the next day. I'm going to wait another couple of days and see what happens. The last time it crashed was on November 26th. I'll let you know what happens in the next several days.

Many thanks!

Larry