I seem to get quite a few issues after Microsoft updates, such as:
- Owa/ecp themes being corrupt
- Services being disabled (event 25/26/1310)
- Server Manager failure (event 4999)
- Failed Database (event 1012)
These issues have occurred twice after Windows Updates, any ideas?
Regards
Adam Bhai
Exchange 2010 sp3 cu4 with Exchange 2013 CU8.
We switched autodiscover and CAS dns record webmail to the Exchange 2013 server.
All works well for users on Exchange 2010 and also some test users on Exchange 2013.
Now we have a shared mailbox/user mailbox that someone has full access to, from Exchange 2010 that we have migrated over to our 2013 environment. After the migration, users on 2010 can no longer open the mailbox via Outlook. They have all the
proper permissions (full access on the mailbox)
We are using NTLM only to authenticate. I've also set changed the shared mailbox to a 'shared mailbox' in Exchange 2013 but users still can't open it.
They recieve "Cannot open the folder. The set of folders cannot be opened. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance."
I've found this > https://support.microsoft.com/en-us/kb/2834139 but this applies for users on 2013 that not can open a 2010 mailbox, our situation is the other way around so not applies to us.
Hi all,
I took a position at a new company in the middle of a partial migration to a hybrid 2013 / 07 and 365 setup. It was a pretty large mess with multiple 2013 exch servers setup and running as well as 2 07 exch servers the primary and the DR site as well as a functioning 365 deployment. There were enough problems that after a couple of weeks I had to remove all the 13 exch servers and created fresh server and deployment which went smoothly. That lasted about a day until the ECP web gui started failing to find the web page to login to after the credentials page just as the previous servers had. I spent a few days attempting to fix the server but ended up losing the exch shell. I created a new server today went down the check list after I removed the remnants in AD of the old server and started my install and it failed on step 10 I believe it was with the following error code. As I am a one man shop don't any other brains to pick, any insight or information is greatly appreciated at this point.
Error:
The following error was generated when "$error.Clear();
if ($RoleIsDatacenter -ne $true -and $RoleIsDatacenterDedicated -ne $true)
{
if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
{
$sysMbx = $null;
$name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
$dispName = "Microsoft Exchange";
Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
$mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
if ($mbxs.Length -eq 0)
{
Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
$dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
if ($dbs.Length -ne 0)
{
Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
$arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
if ($arbUsers.Length -ne 0)
{
Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
$sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
}
}
}
else
{
if ($mbxs[0].DisplayName -ne $dispName )
{
Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
}
$sysMbx = $mbxs[0];
}
# Set the Organization Capabilities needed for this mailbox
if ($sysMbx -ne $null)
{
# We need 1 GB for uploading large OAB files to the organization mailbox
Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions:$true -MailRouting:$true -MessageTracking:$true -PstProvider:$true -MaxSendSize 1GB -Force;
}
else
{
Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
}
}
else
{
Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
}
}
" was run: "Database is mandatory on UserMailbox.".
Error:
The following error was generated when "$error.Clear();
if ($RoleIsDatacenter -ne $true -and $RoleIsDatacenterDedicated -ne $true)
{
if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
{
$sysMbx = $null;
$name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
$dispName = "Microsoft Exchange";
Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
$mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
if ($mbxs.Length -eq 0)
{
Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
$dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
if ($dbs.Length -ne 0)
{
Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
$arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
if ($arbUsers.Length -ne 0)
{
Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
$sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
}
}
}
else
{
if ($mbxs[0].DisplayName -ne $dispName )
{
Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
}
$sysMbx = $mbxs[0];
}
# Set the Organization Capabilities needed for this mailbox
if ($sysMbx -ne $null)
{
# We need 1 GB for uploading large OAB files to the organization mailbox
Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions:$true -MailRouting:$true -MessageTracking:$true -PstProvider:$true -MaxSendSize 1GB -Force;
}
else
{
Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
}
}
else
{
Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
}
}
" was run: "Database is mandatory on UserMailbox.".
Hello all,
I have installed Exchange 2013 (CAS Role) on a Windows 2008 R2 server. All the requirements where passed.
After installing and the reboot, I am unable to start the Exchange Toolbox. It gives the following error:
Unhandled Exception in Managed Code Snap-in
FX:{714FA079-DC14-470f-851C-B7EAAA4177C1}
Exception type: System.Runtime.Serialization.SerializationException
Exception stack trace:
at Microsoft.ManagementConsole.Internal.IMessageClient.ProcessRequest(Request request)
at Microsoft.ManagementConsole.Executive.RequestStatus.BeginRequest(IMessageClient messageClient, RequestInfo requestInfo)
at Microsoft.ManagementConsole.Executive.SnapInRequestOperation.ProcessRequest()
at Microsoft.ManagementConsole.Executive.Operation.OnThreadTransfer(SimpleOperationCallback callback)
Any help is appreciated and with kind regards,
Willem-Jan
Microsoft Certified IT Professional Server Administrator
I am trying to setup partnerApplication with Lync 2013 on my Exchange 2013 (both On-premises) server. When I execute "Configure-EnterprisePartnerApplication.ps1" script from D:\ProgramFiles\ExchangeServer2013\Scripts\Configure-EnterprisePartnerApplication.ps1, I am getting the below error. My account is member of "Organization Management" group.
ERROR:
Creating User <LyncEnterprise-ApplicationAccount> for Partner Application.
D:\ProgramFiles\ExchangeServer2013\Scripts\Configure-EnterprisePartnerApplication.ps1 : The term 'Get-AcceptedDomain' is not recognized as the name of a cmdlet,
function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ .\Configure-EnterprisePartnerApplication.ps1 -AuthMetadataUrl "https://lync2013pool ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Get-AcceptedDomain:String) [Configure-Enter...Application.ps1], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException,Configure-EnterprisePartnerApplication.ps1
Tek-Nerd
Hi everyone.
I need to examine the history of applied updates on Microsoft Exchange Server 2013.
I couldn't find out how to achieve this.
Of course I can check the last applied update/build level, I can retrieve OS updates history by several means, but that's not what I need.
Thanks for helping (just to retrieve updates history, pls don't advice about how to drop the idea).
Regards, Luc
We currently have Exchange 2010 SP3 CU4 co-existence with Exchange 2013 CU8
We did the cut-over of autodiscover.domain.com and webmail.domain.com from Exchange 2010 to Exchange 2013
Autodiscover, OWA, ECP all work with user on Exchange 2010 and also on Exchange 2013
Now we experience some behavior i cannot explain and don't know how to troubleshoot.
When i have a mailbox on Exchange 2010 and go to https://webmail.rdgg.nl/ews/Exchange.asmx i automatically get on the page https://webmail.rdgg.int:/EWS/Services.wsdl showing a XML
When i have a mailbox on Exchange 2013 and go to https://webmail.rdgg.nl/ews/Exchange.asmx i get a page with "you have created a service" with a link to https://internalfqdn.domain.com:444/EWS/Services.wsdl
Clicking on this link opens the https://internalfqdn.domain.com:444/EWS/Services.wsdl url with a XML but this site has a certificate error , this because this is the BackEnd website of Exchange with a self signed Exchange certificate
1)Is there something different/changed in EWS on Exchange 2013 ?
2)Is this expected behavior that in 2013 we not directly get the XML but instead 'you created a service' ?
3)which log file should i check to see that goes wrong ?
4)what is a good test to verify ews works as should ?
Running "Service Account Access (Developers)" on testexchangeconnectivity.com shows GREEN and all test succesfull
We use EWS to receive mail in a mailbox, get mail from this mailbox and forward this.
We use EWS to synchronize calendar of a roommailbox to a 3rd party application.
Currently both functions dont work anymore and looking for a solution, troubleshoot tips, determine if this is really an Exchange 2013 problem.
Regards,
Thor-Egil
I have two identical servers running Exchange 2013SP1 on Server 2012R2. When trying to run CU8, one runs through the prerequisites fine, the other has these errors. What am I doing wrong? Why does the update not see the mailbox server role?
Error:So everywhere states doing it as part of a cutover process - but how is it done in 2013? Plenty of resources/scripts available for 2007 and 2010, but nothing comes up for 2013. Is this even possible?!
Thanks.
Hi,
I'm trying to get an initial install of Exchange Server 2013 trial on Windows 2008 R2 and I keep getting stuck because when it checks the prereqs, it says I need KB 974405 (Identity Foundation). I tried installing the Identity Foundations 6.1 msu but that doesn't seem to satisfy the Exchange installer?
Can anyone tell me how I can get Exchange installed?
Thanks,
Jim
We are currently migrating to an Exchange 2013 platform. We have setup the main system and currently mail is sent out via out 2007 edge servers. We have built new 2013 edge servers and need help regarding the edge subscription.
When I create the subsciption do I just apply this to my new 2013 MBX\CAS servers? Will the they route out via this and not the 2007 one?
I have a client (22 users) who is using SBS 2008. It is time to upgrade and I am planning on using Server 2012 R2 Essentials and Exchange 2013 SP1 on separate servers. I know we can add the Exchange server to the Essentials through the Essentials interface, but I have a question about OWA. The client has one static IP address. I want to point port 25 to the IP of the new Exchange server so incoming email is delivered there. However, do I need a new static IP and a dedicated trusted certificate to do OWA or, by attaching the Exchange server through Essentials, will the Essentials Server automatically access OWA on the Exchange Server?
I'm sure someone is going to say "Use Outlook 365." The cost is more expensive than an Exchange server for this client. So, we need to configure it this way.
Any assistance is GREATLY appreciated.
Stu
Hello,
This is an Exchange 2010 to Exchange 2013 migration question; how to introduce Exchange 2013 with existing Exchange 2010 CAS servers using NLB.
Currently my Exchange 2010 environment has 4 servers:
2 CAS/HUB (CAS Arrary using NLB)
2 MBX (DAG setup)
Goal is introduce 4 EX13 servers with High Availability (HA):
2 CAS (use NLB)
2 MBX (use DAG)
The two EX10 CAS/HUB servers are part of a single CAS Array. High Availability is done using built-in Windows NLB, so both CAS/HUB servers are part of a single NLB cluster. The two MBX servers are part of single DAG.
I understand that EX13 no longer uses CAS arrays but rather OutlookAnywhere. My questions is how to introduce Exchange 2013 servers into the above environment and not break existing EX10. Installing the 2 EX13 MBX servers seems straight-forward, but cannot find guidance on how to introduce EX13 CAS servers when using NLB for HA.
When configuring the two EX13 CAS servers with NLB installed, am I joining the new servers to the existing EX10 NLB cluster or am I creating a new NLB cluster (new IPs, etc) that will have only the two new EX13 CAS servers as members?
Thanks in advance.
Hello,
I hope somebody can help me with my Issue.
First i'll give you a short Information about the Migration Scenario..
-Installation new domain
-Installation Exchange 2013
- we migrated Users with admt to a new domain
- The users are present to the Exchange so i attached the mailboxes to a MailboxDatabase
- Everything seems to be fine, we can Access the Mailbox but when I configure the Mailbox and open the "Mailbox Feature" i get the following errormessage:
The Get-MobileDeviceStatistics command that you are trying to run, which is version 15, requires that the target mailbox account is on a Mailbox server that is the same version. The command wasn't able to process your request because the target mailbox account is on a Mailbox server with version 8. Please use this version (Version: 8) of the Get-MobileDeviceStatistics command.
So im confused about that because i can Access the Mailbox without any Issues and want to start to Import the exported PST Files from the old Exchange Server 2007 from the old Domain...
Thanks for any help!
Hello,
I am attempting to move all public folders from one Exchange 2010 server to another and they simply are not showing up on the new server. I have used the command
.\MoveAllReplicas.ps1 -Server Server01 -NewServer Server02
and am getting no errors when I do so. I have check the replication scheduled and is set to Always Run on both servers. I have started the Replication Server on both servers to no avail.
When I query the database on the new server it shows the folder but they are not there in Outlook or OWA.
Any ideas would be greatly appreciated!
Hi Folks,
we are working on a cross forest migration for AD and Exchange, where Source Exchange is 2010 SP3 and Target new Exchange is 2013 CU8. while migrating the mailboxes we are getting the below issues and it takes ages to complete. i have migrated one mailbox earlier with 4.7 GB size it after lots of retries it took 28 hours to complete.
below is another mailbox which is quite smaller in size to check but i am still getting the same problem. what could be the cause for this. i have done all custom settings for MRS proxy and client binding at source Exchange server, but the results are still the same.
Informational: The request has been temporarily postponed because the mailbox is locked. The Microsoft Exchange Mailbox Replication service will attempt to continue processing the request after 6/19/2015 2:40:07 PM.
OverallDuration : 00:28:43.5949514i am in a challenging situation, need urgent support.
Regards, Owais
Hello,
We applied kb3031133 with hopes of preventing the migration process from duplicating our Contacts folders when migrating mailboxes (it creates a second, empty Contacts folder). We installed CU8, rebooted, and migrated another mailbox. The contacts folder was duplicated again. Any ideas?
RM