Stay Connected
Posts tagged exchange
Exchange 2007: unexpected error with management shell
Feb 1st
I received the following error message when opening and running a cmdlet with my Exchange Management Shell:
[PS] C:\Documents and Settings\admin>Export-Mailbox -identity user1 -PSTFolderPath c:\user1.pst
WARNING: An unexpected error has occurred and debug information is being generated: Unable to determine the installed file version
from the registry key ‘Software\Microsoft\Exchange\Setup’.
Export-Mailbox : Unable to determine the installed file version from the registry key ‘Software\Microsoft\Exchange\Setup’.
At line:1 char:15
+ Export-Mailbox <<<< -identity user1 -PSTFolderPath c:\user1.pst
+ CategoryInfo : NotSpecified: (:) [Export-Mailbox], TaskException
+ FullyQualifiedErrorId : Microsoft.Exchange.Configuration.Tasks.TaskException,Microsoft.Exchange.Management.RecipientTasks.ExportMailbox
Just looking on the error message it seems that something was missing in the Windows Registry. I opened Registry Editor and browsed to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange. The Setup key was missing. Exchange 2007 management tools were installed to another server than Exchange Server was installed. I logged on the Exchange 2007 server, opened Registry Editor and browsed to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange key. The Setup folder was visible and I right-clicked on the Setup folder and exported the Setup branch.
I went back to my Exchange 2007 Management installed server and imported the reg file.
After importing the reg file my problem was solved and I had another challenge with Export-Mailbox cmdlet.
(No Ratings Yet)
Loading ...Exchange 2007: Services fail to start
Oct 26th
If you are running a Windows Server 2008 virtual machine with “AD DS” Services (Domain Controller) and you installed Exchange 2007 SP1 on the same machine than three services may fail to start. During the boot process of the virtual machine Active Directory Services are not ready and some Exchange 2007 services will fail to start.
Screenshot of the Services console during my troubleshooting actions.
Microsoft Exchange Information Store, Microsoft Exchange Service Host and Microsoft Exchange System Attendant services are not started. The Startup Type of has been set to Automatic.
The System EventViewer will show the following error events:
- EventID 7024: The Microsoft Exchange Information Store service terminated with service-specific error 0 (0×0).
- EventID 7009: A timeout was reached (30000 milliseconds) while waiting for the Microsoft Exchange Service Host service to connect.
- EventID 7000: The Microsoft Exchange Service Host service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
- EventID 7022: The Microsoft Exchange Transport service hung on starting.
Exchange Management Console message:
- ERROR: Could not connect to the Microsoft Exchange Information Store service on server Networknet.nl. One of the following problems may be occurring: 1- The Microsoft Exchange Information Store service is not running. 2- There is no network connectivity to server Networknet.nl. 3- You do not have sufficient permissions to perform this command. The following permissions are required to perform this command: Exchange View-Only Administrator and local administrators group for the target server. 4- Credentials have been cached for an unpriviledged user. Try removing the entry for this server from Stored User Names and Passwords.
To fix this problem change the Startup Type of Microsoft Exchange Information Store, Microsoft Exchange Service Host and Microsoft Exchange System Attendant to “Automatic (Delayed Start)”
Reboot the virtual machine again and everything should be started as smooth as you would have two separate virtual machines.
Related links:
(No Ratings Yet) Loading ...SSL certificate Windows Server 2008 and Exchange 2007 SP1
Aug 26th
Thanks to guys from Telnetport25 I was able to finish my SSL certificate migration for my new Windows Server 2008 virtual machine running a Exchange 2007 SP1 installation.
My work log:
- Logon on the old Windows Server 2003 hosting the OWA front-end role
- Start MMC and add the Certificate Snap-In; choose the Computer Account.
- Go to Personal/Certificates and locate the SSL certificate assigned to IIS for SSL encryption. Right click ; All Tasks and choose export. Choose the appropriate options like the certificate path; assign password and save the PFX file to "My Documents"
- Copy the PFX file to your Windows Server 2008 Client Access Server
- Logon on the Windows Server 2008 and add the Certificate Snap-In to a new MMC console for the Computer Account
- Go to Personal/Certificates; right click; All Tasks and choose Import.
- Locate the PFX file; enter the password and make sure you check "Mark this key as exportable" to enable future migrations of the SSL certificate.
- Place the certificate in the Personal Store
- Open the certificate and go to Details tab. Locate the Thumprint field and select Value with mouse; press CRTL-C to copy the data.
- Paste the value in Notepad and replace the "SPACE’ with CRTL-H. In the Find what field press space on the keyboard and click Replace All
- Copy the Thumbprint
- Start the Exchange Management Shell and run the Enable-ExchangeCertificate cmdlet
- Type IIS as Services and paste the copied data from Notepad to Thumbprint
- Start Exchange Management Console and go to Server Configuration / Client Access / Select the server and open owa from Outlook Web Access tab
- Type External URL of the SSL certificate and DNS. E.g. https://webmail.domain.tlk
- Click OK and you are finished to test the configuration.
- Start IE and test your OWA role. Review your NAT and Firewall rules also.
Related links:
(No Ratings Yet) Loading ...Exchange 2007 SP1 upgrade Windows Server 2003 x64
Apr 27th
After fixing my Active Directory I start the upgrade of my current Exchange 2007 server. As you will see from the screenshots below the installation is straight forward but the requirements are killing me with this service pack upgrade. First of all make sure a) your Active Directory replication is working properly, b) Exchange 2007 server has been installed with Windows Server 2003 SP2 and c) Microsoft .NET Framework 2.0 Service Pack 1 has been installed. To complete these requirements as posted before I was forced to remove one of my domain controllers running in a virtual machine with dcpromo /forceremoval and metadata cleanup; this box did not replicate for three months.
You can also upgrade from command line. I used gui mode to illustrate the process.
Setup.com /mode:upgrade
Check the hyperlink at Technet for all updates within SP1 What’s New in Exchange Server 2007 SP1. I like to integration with Windows Server 2008 and Exchange 2007 Sp1, Exchange Management console updates and the OWA premium changes.
(No Ratings Yet) Loading ...ISA 2006 and Published ActiveSync CAS role Exchange 2007
Feb 6th
Since ActiveSync role was published in ISA 2006 to my Exchange Server 2007 my Samsung i600 Windows Mobile 6 client start complaining with the warning message below.
"Your account in Microsoft Exchange Server does not have permission to synchronize with your current settings. Contact your Exchange Server administrator.
Support code: 0×85010004"
Before it was published with NAT and I have never seen this warning. I was not able to sync the mobile device anymore.
To fix this problem locate the Microsoft-Server-ActiveSync virtual directory in IIS MMC and uncheck Require secure channel (SSL) checkbox. Restart IIS.
This fixed my problem. Make sure you configure the internal SSL bridge to encrypt the data behind your ISA firewall. The communication between ISA and Exchange 2007 is not encrypted which is fine for lab, but for production generate a computer certificate on both ends for encrypted communication.
(No Ratings Yet) Loading ...
