[quote user="Greenman"]Many thanks again for your help with this.[/quote]

Thanks for reporting back, just doing my job (I have to!) ... [;)]

Hi

I have two network installations of Pegasus Mail and Mercury/32. Each installation is designed to send mail for different domains with each instance of Mercury announcing itself differently. The installation on Orion is the workhorse and manages business mail. The installation on Titan is used for mailing lists only.

Recently I upgraded Pegasus Mail to 4.61 on our 'main' installation on Orion which went well. I had some issues with IERenderer, but perseverance fixed this.

Today I upgraded Pegasus Mail on Titan. I logged onto the server as the domain administrator and launched setup. But, setup identified the path to the mail folders as being \\orion\pmail. So, I chose new installation and pointed it to the correct path which was C:\PMail. The upgrade worked fine.

I am not having the same luck with IERenderer, though. I am having the same problem I had before - the IERenderer program thinks that Pegasus Mail is running.

Pegasus Mail is not running on this machine, nor was it being accessed across the network.

In a previous reply here, it was stated that "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."

As you can see the process is not open locally, nor is it being accessed remotely. I checked whether the sole member of staff who manages the mailing lists had Pegasus Mail open and their machine was not even switched on. The administrator account has full control permissions over the file and the System account has full control permission too:

http://img683.imageshack.us/img683/8663/ierend.jpg

Is there anything else I need to check to determine whether the file is open and whether the setup program has write access to winpm-32.exe? Or, does anyone have any suggestions I can use to resolve this, please?

Thanks.

I rebooted Titan last night and this morning I tried to run IERenderer again but the same message appears. It is quite obvious that Pegasus Mail is not running. I also tried closing Mercury/32 but this made no difference either.

I don't see why your initial install identified the mailboxes as being on orion.  It may be that IER is looking at orion to check for writability.

Can you use process explorer from sysinternals to see what the install is trying to open?

Unfortunately, I am not at all familiar with Process Explorer. I ran it, but neither the information contained in the detail windows for IERenderer.exe, IERenderer.tmp nor the .txt file that can be saved contained any references to ..\winpm-32.exe either locally or across the network.

http://img863.imageshack.us/img863/7748/ierendpe1.jpg

http://img560.imageshack.us/img560/2877/ierendpe2.jpg

*************************** 

Process PID CPU Description Company Name
System Idle Process 0 93.57  
System 4   
 Interrupts n/a < 0.01 Hardware Interrupts and DPCs 
 smss.exe 284  Windows NT Session Manager Microsoft Corporation
  csrss.exe 332  Client Server Runtime Process Microsoft Corporation
  winlogon.exe 356  Windows NT Logon Application Microsoft Corporation
  csrss.exe 6028  Client Server Runtime Process Microsoft Corporation
  winlogon.exe 6052  Windows NT Logon Application Microsoft Corporation
   logon.scr 5572  Logon Screen Saver Microsoft Corporation
  csrss.exe 700  Client Server Runtime Process Microsoft Corporation
  winlogon.exe 2356  Windows NT Logon Application Microsoft Corporation
explorer.exe 6128  Windows Explorer Microsoft Corporation
 ALMon.exe 2640  Sophos Endpoint Security and Control Sophos Limited
 jusched.exe 2796  Java(TM) Update Scheduler Sun Microsystems, Inc.
 ctfmon.exe 4832  CTF Loader Microsoft Corporation
 oobechk.exe 4720  Server Out-of-the-box UI Microsoft Corporation
  mshta.exe 296  Microsoft (R) HTML Application host Microsoft Corporation
 loader.exe 2816  Mercury/32 Loader Module v4.72 David Harris
  mercury.exe 5464  Mercury/32 Core Processing Module v4.73 David Harris
 procexp.exe 5472 5.00 Sysinternals Process Explorer Sysinternals - www.sysinternals.com
 IERenderer.exe 4492  BearHtml Replacement for Pegasus Mail                        Micha's Midnight Manufacture                               
  IERenderer.tmp 1296  Setup/Uninstall 

Process: IERenderer.exe Pid: 4492

Type Name
Desktop \Default
Directory \KnownDlls
Directory \Sessions\3\BaseNamedObjects
File C:\Documents and Settings\administrator.HTLINCS\Desktop
File C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.3790.4770_x-ww_05FDF087
File \Device\WMIDataDevice
File \Device\WMIDataDevice
File \Device\KsecDD
File C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.3790.4770_x-ww_05FDF087
Key HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\DllNXOptions
Key HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options
Key HKLM
Key HKCU
KeyedEvent \KernelObjects\CritSecOutOfMemoryEvent
Mutant \Sessions\3\BaseNamedObjects\CTF.TimListCache.FMPDefaultS-1-5-21-434221507-3794906203-392007587-500MUTEX.DefaultS-1-5-21-434221507-3794906203-392007587-500
Process IERenderer.exe(4492)
Process IERenderer.tmp(1296)
Section \Sessions\3\BaseNamedObjects\CiceroSharedMemDefaultS-1-5-21-434221507-3794906203-392007587-500
Section \Sessions\3\BaseNamedObjects\CTF.TimListCache.FMPDefaultS-1-5-21-434221507-3794906203-392007587-500SFM.DefaultS-1-5-21-434221507-3794906203-392007587-500
Semaphore \Sessions\3\BaseNamedObjects\shell.{A48F1A32-A340-11D1-BC6B-00A0C90312E1}
Thread IERenderer.exe(4492): 2208
WindowStation \Sessions\3\Windows\WindowStations\WinSta0
WindowStation \Sessions\3\Windows\WindowStations\WinSta0

*************************** 

[quote user="Greenman"]Today I upgraded Pegasus Mail on Titan. I logged onto the server as the domain administrator and launched setup. But, setup identified the path to the mail folders as being \\orion\pmail. So, I chose new installation and pointed it to the correct path which was C:\PMail. The upgrade worked fine.

I am not having the same luck with IERenderer, though. I am having the same problem I had before - the IERenderer program thinks that Pegasus Mail is running.[/quote]

Both installers (Pegasus Mail and IERenderer) check HKEY_CURRENT_USER\Software\Pegasus Mail\BaseDir for the installation path and suggest it for update resp. installation if finding one. Since this Registry key is only created by the very last instance of Pegasus Mail launched on this exact machine (i.e. the server itself which you won't usually launch Pegasus Mail on) with the current user account, it might not exist or point to an invalid path, so you have to browse for the proper location during setup in both installers.

And depending on the Windows version you're using it might even be more complicated (this is what I see on Windows 7, e.g.): If the installer uses a different (admin) account than the one the installer is launched with (i.e. if the installer prompts you with a login dialog instead of just asking for elevated access rights) it tries to read the base user's HKEY_CURRENT_USER key, not the admin user's one. On another question: Can you move or rename WINPM-32.EXE with the administrative account you're using for the install?

But anyway: If all fails there's another workaround available: Since you successfully ran Pegasus Mail's 4.61 installer the IERenderer version coming with it should be installed properly already and you can use Inno Unpacker for unpacking the IERenderer setup and copying its files manually to the proper places in Pegasus Mail program (sub)directories.

Thanks for the info, Michae. That is very useful. I will do this when I return to work on Tuesday.

For the record Titan runs W2k3 32bit, but Pegasus Mail has never been run on it. It only holds the program files for the two users who access PM remotely (myself and one other). Orion, on the other hand (w2k8 64bit), hosts it's own PM files which all staff access and I also regularly access accounts (local to Orion) when logged in as the domain admin. As I said, when I ran IERenderer I was logged in as the domain admin, and Titan is a domain controller. No one else was logged in, and my login was the only admin login present.

I was wrong - I checked the registry key you referenced and the path was indeed \\orion\pmail\. So, I must have run Pegasus Mail on this machine, but it would have been a long time ago before I installed the second Mercury/32 server. I also successfully renamed winpm-32.exe under the domain admin login.

I used the Inno Unpacker to extract the files and place them in their respective folders.

Many thanks again for your help with this.