[quote user="Greenman"]Thanks, Michael - you're a star :)[/quote]
I'm only a failing human like any other, I'm afraid ... but thanks!
Michael -- IERenderer's Homepage PGP Key ID (RSA 2048): 0xC45D831B S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C
Hello
Problem: One of our staff's Pegasus Mail mailbox has become corrupted. When accessed from a Win 7 PC most new mail when accessed crashes Pegasus as does accessing mail in other folders. I tried removing all .cnm's first and then adding them back gradually, but accessing most of them results in a crash - both in Preview mode and double-clicking the message from non-preview mode.
Installation: Pegasus Mail is installed on a Windows 2008 server, and links the exe are available on staff's desktops. So, the program is always run across the network.
I have moved all mail files out of the account, used Mercury to delete the files, manually deleted the folder, then used Mercury to recreate the account, and moved the files back in - same problem.
When I access the mail account from our Win 2008 server, it works fine. Same from Win XP.
The account was fine until this morning. Pegasus Mail is working fine on other Windows 7 machines on the network.
The following event is saved to the Application Log:
Log Name: Application
Source: Application Error
Date: 20/05/2011 09:37:42
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: GREENMAN.htlincs.local
Description:
Faulting application name: winpm-32.exe, version: 4.6.1.0, time stamp: 0x4d532c43
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17514, time stamp: 0x4ce7b8f0
Exception code: 0x0eedfade
Fault offset: 0x0000b760
Faulting process id: 0x10a4
Faulting application start time: 0x01cc16c92da838be
Faulting application path: \\ORION\Pmail\winpm-32.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 6d41803e-82bc-11e0-864a-002564bfee78
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-05-20T08:37:42.000000000Z" />
<EventRecordID>33022</EventRecordID>
<Channel>Application</Channel>
<Computer>GREENMAN.htlincs.local</Computer>
<Security />
</System>
<EventData>
<Data>winpm-32.exe</Data>
<Data>4.6.1.0</Data>
<Data>4d532c43</Data>
<Data>KERNELBASE.dll</Data>
<Data>6.1.7601.17514</Data>
<Data>4ce7b8f0</Data>
<Data>0eedfade</Data>
<Data>0000b760</Data>
<Data>10a4</Data>
<Data>01cc16c92da838be</Data>
<Data>\\ORION\Pmail\winpm-32.exe</Data>
<Data>C:\Windows\system32\KERNELBASE.dll</Data>
<Data>6d41803e-82bc-11e0-864a-002564bfee78</Data>
</EventData>
</Event>
Luckily, I have a spare Win XP machine on the network today. I have enabled Remote Desktop and the member of staff is using that to successfully access his mail account.
If anyone has any suggestions about how I might fix this or determine the problem, or insight from the event details above I would be very grateful if you could post them.
Thanks
Three in a row :)
I have just read this post:
http://community.pmail.com/forums/thread/28296.aspx
I wonder if this might solve the problem? Both the affected Win7 machines have just had I.E.9 installed, the others have not.
Bearing in mind that there are XP clients and one Win2000 client on the network I don't want to run the installer if it will adversely affect the way Pegasus Mail runs on those systems.
Will it be OK to run the installer on the Windows 2008 server (64bit)?
Thanks
[quote user="Greenman"]http://community.pmail.com/forums/thread/28296.aspx
I wonder if this might solve the problem? Both the affected Win7 machines have just had I.E.9 installed, the others have not.[/quote]
Most probably, yes, but you may want to wait a couple of hours since the most recent version needs another fix as well which I'll certainly provide later today: The Exception code: 0x0eedfade indicates that it's very likely IERenderer causing this, but I'm a bit surpised that it indicates Kernel32.dll being the crashing module. This crash should be fixed by the current version, though, if you need an urgent fix.
[quote user="Greenman"]Bearing in mind that there are XP clients and one Win2000 client on the network I don't want to run the installer if it will adversely affect the way Pegasus Mail runs on those systems.
Will it be OK to run the installer on the Windows 2008 server (64bit)?[/quote]
It might even be the only way to update IERenderer, provided you can get everyone to close Pegasus Mail before trying. If you'd rather prefer to not use the installer read this post.
Michael -- IERenderer's Homepage PGP Key ID (RSA 2048): 0xC45D831B S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C
[quote user="idw"]Most probably, yes, but you may want to wait a couple of hours since the most recent version needs another fix as well which I'll certainly provide later today: The Exception code: 0x0eedfade indicates that it's very likely IERenderer causing this, but I'm a bit surpised that it indicates Kernel32.dll being the crashing module. This crash should be fixed by the current version, though, if you need an urgent fix.[/quote]
The announced version is now available.
Michael -- IERenderer's Homepage PGP Key ID (RSA 2048): 0xC45D831B S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C
Thanks, Michael
One small problem. When I run the installer, it displays a message stating 'Setup has detected that Pegasus Mail is currently running'.
Pegasus Mail is not running. I also closed Mercury but the same message appeared.
What do you think might be happening here?
Cheers!
[Edit]
False alarm!
After waiting several minutes I ran it again and it displayed the same message, this time though, after I clicked OK setup continued. I just logged onto one of the affected Win 7 clients and successfully opened several messages from one of my mailboxes.
Thanks, Michael - you're a star :)
[quote user="Greenman"]What do you think might be happening here?[/quote]
The installer actually checks whether it has write access to WINPM-32.EXE (without actually writing to it, of course) as there's no other way to check whether it's closed on all client machines, IOW: If you don't have write access to WINPM-32.EXE for other reasons it will fail as well.
Michael -- IERenderer's Homepage PGP Key ID (RSA 2048): 0xC45D831B S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C
