I was recently contacted regarding a problem with upgrading Exchange 2013 RTM CU1 (Build Number: 15.0.620.29) Multi-Role Servers to CU2 (Build Number: 15.0.712.24). The Customer got the same error on all his five Multi-Role Servers: Mailbox service FAILED
PS L:\install2\2013 CU2\extracted> setup.exe /IAcceptExchangeServerLicenseTerms /m:upgrade
Welcome to Microsoft Exchange Server 2013 Cumulative Update 1 Unattended Setup
Mailbox role: Transport service
Client Access role: Front End Transport service
Mailbox role: Client Access service
Mailbox role: Unified Messaging service
Mailbox role: Mailbox service
Client Access role: Client Access Front End service
Performing Microsoft Exchange Server Prerequisite Check
Configuring Prerequisites COMPLETED
Prerequisite Analysis COMPLETED
Configuring Microsoft Exchange Server
Language Files COMPLETED
Restoring Services COMPLETED
Language Configuration COMPLETED
Mailbox role: Transport service COMPLETED
Client Access role: Front End Transport service COMPLETED
Mailbox role: Client Access service COMPLETED
Mailbox role: Unified Messaging service COMPLETED
Mailbox role: Mailbox service FAILED
The following error was generated when “$error.Clear();
-PackagePath ([System.IO.Path]::Combine($RoleLanguagePacksPath, “Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.ca-ES.msi”)) `
-PropertyValues (“ARPSYSTEMCOMPONENT=1 ALLUSERS=1”) `
-LogFile ([System.IO.Path]::Combine($RoleSetupLoggingPath, “InstallSpeech-ca-ES.msilog”))
” was run: “Couldn’t open package ‘C:\Program Files\Microsoft\Exchange Server\V15\bin\Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.ca-ES.msi’. This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package. Error code is 1619.”.
The Customer had logged on with an account with the right permissions to run the upgrade (Schema- and Enterprise Admin + Domain Admin) and it was run with administrative privileges (Run as Administrator) so that wasn’t the problem.
Looking at the text that was sent to me, besides from the obvious error, I few things caught my attention:
- Welcome to Microsoft Exchange Server 2013 Cumulative Update 1 Unattended Setup
- No indication of Organization Preparation or any stopping/starting of services
- The upgrade was run in Windows PowerShell
This was an error that I hadn’t seen before, so I decided to see if I could reproduce the problem in my lab where I had one single multi-role server, also on CU1, that hadn’t been upgraded yet.
So I did exactly what my customer had done and sure enough… “Got the exact same error”
So I did as I always do when installing or patching an Exchange 2007/2010/2013 Server, I ran the command from an elevated command prompt. This time, it was clear that I was running the CU2 update, the ORG needed to be prepared and services were stopped, BUT…
…the Unified Messaging service failed with: “Cannot find path ´C:\Program Files\Microsoft\Exchange Server\V15\UnifiedMessaging\grammars´ because it doesn’t exist”.
At the time of this writing, the TechNet documentation on how to Upgrade Exchange 2013 to the Latest Cumulative Update refers to Install Exchange 2013 Using Unattended Mode that doesn’t have an example on how to run an upgrade (/m:upgrade), but it does mention to run setup.exe in a command prompt.
Some day, if I don’t forget it, I will test an Exchange 2013 Build upgrade using the Setup Wizard. There is a first thing for everything, right?