I have had a few hours frustration and an eventual work around to installing the Exchange 2007 Load Generator in one of my test environments.
I have been trying to install the Exchange 2007 Load Generator (LoadGen.msi) on a range of servers with the same installation error occurring each time. The errors occured when installing both the 64-bit package on some Windows 2008, 64-bit servers and also the 32-bit package on some Windows 2003 R2 SP2, 32-bit servers. Here are the range of errors and diagnosis:
The Microsoft Exchange Load Generator installer gives the following error message:
There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact you support personnel or package vendor.
The server's application event log gives the following error message:
Event ID: 11722 Source: MsiInstaller
Product: Microsoft Exchange Load Generator -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action START_REMOTE_SERVICE.B08E90EE_3FC7_4509_A7F3_DE16BC275F17, location: net.exe, command: START LoadGenRemote
If I run the MSI with verbose logging (msiexec /i LoadGen.msi /l*v C:\LoadGen.txt) I get the following error in the verbose log file.
Generator\LoadGenRemoteSvc.exe", ServiceType=16,StartType=2,ErrorControl=0,,,,StartName=LocalSystem,Password=**********, Description=Enables distributed load generation for the Microsoft Exchange Load Generator tool.)
Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action START_REMOTE_SERVICE.B08E90EE_3FC7_4509_A7F3_DE16BC275F17, location: net.exe, command: START LoadGenRemote
When you click OK to the installer error message it of course rolls back all actions in the MSI. The last error message pointed me in the direction of it being a service problem. If you do not click OK and look in the Services.msc you will see there is a service called Microsoft Exchange Load Generator Remote Agent. This service is configured as Automatic, but is unable to startup using the Local System account credentials. If you give it another account (I used an admin account in my test lab) it does start. Of course this is useless as the installer has already failed and the only option is to click OK and roll back the install.
As an absolute pot luck guess, before beginning to think about attempting to edit the MSI the following action allowed the installation to complete. The answer is.....
Disable the network card during the MSI installation!
Yep - for some completely unknown (to me) reason, this allows the installation to complete and the service to run as the Local System account.
Subscribe to:
Post Comments (Atom)
7 comments:
Had same issue...(2003x86 R2). Your solution worked. Thank you for saving me a LOT of time.
Your solution worked! Thank You! But if you try to use LoadGenRemoteSvc to work remotely, then you will fail. If so, write a file hosts "127.0.0.1 crl.microsoft.com"
thanks! Great! Hope somebody brings this back to Microsoft.
Microsoft has listed this issue in the download page of Loadgen.
Fix has been discussed in
http://support.microsoft.com/kb/944752/
What worked for me is creating a host record 127.0.0.1 crl.microsoft.com as suggested by Михаил Даньшин
Hi.I had the same error . Was ready with load testing over the weekend and suddenly had this error and things looked bad . Adding the host file entry "127.0.0.1 crl.microsoft.com" fixed the problem.:-)
Harry
its excellent
Really i like this blog.
Its highly informative I would invite you to take tour on my website which also related Exchange Hosted.For more information about Web Hosting please visit on http://www.prestigetechnologies.com
I hope you like it most.
I have many good friends. But unfortunately no one of them couldn't help me in one situation with MS Exchange. I applied for help to the Google:) I was absolutely right in my decision. A tool which I was found where can quite resources for working with such question - microsoft exchange email recovery.
Post a Comment