Hi,

Running Exchange Server 2013 CU3 Standard.

This is an unusual issue which has been bugging me since setting up this system. The event log is frequently producing this error although other log entries imply that MSExchangeApplicationLogic is operational.

Log Name:      Application
Source:        MSExchangeApplicationLogic
Date:          19/02/2014 15:07:31
Event ID:      3018
Task Category: Extension
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      server.contoso.com
Description:
Scenario: GetConfig.GetConfig. The request failed. Mailbox:  Url: https://o15.officeredir.microsoft.com/r/rlidMktplcWSConfig15 Exception: System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 65.55.69.140:443
   at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at Microsoft.Exchange.Data.ApplicationLogic.Extension.BaseAsyncOmexCommand.<>c__DisplayClass2.<EndGetResponseCallback>b__1()

The other server of a pair is showing no such errors.

Does anyone have any experience of dealing with this?

Cheers, Nick C

Hello,

If I run: 

Get-Mailbox -RecipientTypeDetails UserMailbox -ResultSize unlimited | select samaccountname

It will out put all the samaccounts. What I need to be able to do is list only those that are 3 characters or less long. 

Doing this in powershell, tried working with length such as: 

Get-Mailbox -RecipientTypeDetails UserMailbox -ResultSize unlimited | select samaccountname | select $_.length -lt 3

However, it doesn't work. 

Anyone have experience with this? 

Hi,

We have a single Exchange 2013 server and are getting this error many times in a day.  I haven't been able to find a solution and was wondering if anyone came across this error or have any suggestions.

Edition             : Standard
AdminDisplayVersion : Version 15.0 (Build 913.22)

Watson report about to be sent for process id: 5816, with parameters: E12IIS, c-RTL-AMD64, 15.00.0913.022, M.Exchange.Imap4, M.Exchange.Net, M.E.N.NetworkConnection.BeginNegotiateTlsAsClient, System.InvalidOperationException, 99a4, 15.00.0913.007.
ErrorReportingEnabled: True 

Thanks

Amit

I get this at boot and when restarting the Microsoft Exchange Diagnostics service ever since I updated to CU7.  Anyone know anything about this?

Log Name:      Application
Source:        MSExchangeDiagnostics
Date:          12/19/2014 12:30:09 PM
Event ID:      1039
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Server.contoso.com
Description:
Failed to detect the bitlocker state for EDS log drive 'C:\'.
Exception
System.Management.ManagementException: Invalid namespace
   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
   at System.Management.ManagementScope.InitializeGuts(Object o)
   at System.Management.ManagementScope.Initialize()
   at System.Management.ManagementObjectSearcher.Initialize()
   at System.Management.ManagementObjectSearcher.Get()
   at Microsoft.Exchange.Diagnostics.Service.DiagnosticsService.DriveLocked(String diagnosticsRootDrive)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchangeDiagnostics" />
    <EventID Qualifiers="49156">1039</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-12-19T19:30:09.000000000Z" />
    <EventRecordID>68590</EventRecordID>
    <Channel>Application</Channel>
    <Computer>server.contoso.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>C:\</Data>
    <Data>
Exception
System.Management.ManagementException: Invalid namespace
   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
   at System.Management.ManagementScope.InitializeGuts(Object o)
   at System.Management.ManagementScope.Initialize()
   at System.Management.ManagementObjectSearcher.Initialize()
   at System.Management.ManagementObjectSearcher.Get()
   at Microsoft.Exchange.Diagnostics.Service.DiagnosticsService.DriveLocked(String diagnosticsRootDrive)</Data>
  </EventData>
</Event>

Help, not sure how to proceed via Powershell or EMC.

Thanks!!

Hi,

I have deployed Exchange 2013 co-existence with Exchange 2010, Currently doing migrations and now we are getting below error. When I try to access other user mailbox (B) from Account (A) which is having full permission on mailbox B.

I tried by reset attributes and inherit permissions but, issue still persists....

X-OWA-Error: SDServerErr;Microsoft.Exchange.Data.Storage.AccessDeniedException
X-OWA-Version: 15.0.995.28
X-FEServer: ZAJNBEXC11
X-BEServer: zajnbexc05.cws.sasol.com
Date: 2/4/2015 6:27:12 AM

Hi All,

Running Exchange 2010 SP3  with Rollup Update 8V2. (Role –HT ; certificate - self signed)

When use EMC giving an error. But I can do all the stuff using EMS. Even getting same error when  connect the server from local system EMC. I have not found any valid logs in Event viewer.

Below is the error snapshot. Please share you suggestions to fix this issue.

  Dear all, thanks for viewing this question, any help is appreciate. 

In exchange 2010, I can set OAB generation schedule to "Never" or "Always" with commands like this:

Set-OfflineAddressBook -Identity "\Default Offline Address Book" -Schedule never
Set-OfflineAddressBook -Identity "\Default Offline Address Book" -Schedule always
But in exchange 2013, it seems that these command don't work. And to set the OAB generation schedule, Exchange 2013 use command like this:
Set-MailboxServer -Identity MBXServer01 -OABGeneratorWorkCycle 01.00:00:00 -OABGeneratorWorkCycleCheckpoint 06:00:00 
How to set the generation schedule to "Never/Always"?

We are having an issue with the email address policy self resolving internal collisions by appending the number "2" to email addresses.

Basically what we do is new employees receive contacts for the GAL automatically. The user can then choose to create a user object or even get an exchange account via online self-provisioning site.

So our process deletes the contact object, then creates a user object. That user object is then mail-enabled.  At that moment the email address policy kicks in and adds a few addresses  ( [user]@[domain] [user]@excahnge.[domain] etc)

here is example code of how we sometimes do this manually for users that don't self-provision.

#remove contact
Get-ADObject -filter { cn -eq $user } -Server $script:dc | Remove-ADObject -Confirm:$false -Server $script:dc

#create new user object
New-ADUser -Name $user -SamAccountName $user -Enabled $true -ChangePasswordAtLogon $True  -UserPrincipalName $userPrincipalName -DisplayName $User_displayname -Path $ou -GivenName $userFirstName -Surname $userLastName -AccountPassword $Private -Server $script:dc

#mail enable user object
Enable-MailUser -identity $user -ExternalEmailAddress $externalAddress -Alias $user -domainController $script:dc 

Now the problem seems to be that even thought the contact is deleted the address is still somewhere in the system because when the user is mail enabled their addresses look like this: [user]2@[domain] and [user]2@exchange.[domain]. it sticks 2s on all of them

best guess is the policy sees the old address *somewhere* but rather than fail it just appends a 2 to avoid the collision and goes on it's merry way.  All the script lines run against the same DC and all the exchange servers point to one DC.

what is causing this and how do we stop it ?

I Copied  the file to "C:\Program Files\Microsoft\Exchange Server\V14\Bin\CmdletExtensionAgents" directory with name ScriptingAgentConfig.xml however script does not works as per intended purpose but i do have a query how do i verify if the script placed in CmdletExtensionAgents ever executed or not ? below code is suppose to fire a alert or mailbox movement to specified email address in code but i kinda feel helpless with CmdletExtensionAgents there is no error log or clue what happened after placing XML code in directory . Please suggest.

<?xml version="1.0" encoding="utf-8" ?><Configuration version="1.0"><Feature Name="Notify Mailbox Move" cmdlets="New-MoveRequest"><ApiCall Name="OnComplete">
             if($succeeded)
			 {
                $MailboxAlias = $provisioningHandler.UserSpecifiedParameters["Alias"]
				$DisplayName = $provisioningHandler.UserSpecifiedParameters["DisplayName"]
				$AdminEmailAddress = "Administrator@domain.com"
				$emailMsg = "Mailbox -" + $MailboxAlias + "With DisplayName -" + $DisplayName + "has been Moved"
				$EmailSubject = "Mailbox - " + $MailboxAlias +" Has been Moved"
				Send-MailMessage -From "MailboxMoveNotifyAgent@domain.com" -To $AdminEmailAddress -SMTPserver "smtp.domain.com" -Subject $EmailSubject -Body $emailMsg -BodyAsHTML
			 }</ApiCall></Feature></Configuration>

Aditya Mediratta

I've been trying to resolve some of the many issues I've run into after installing Exchange 2013 CU2 as a fresh install before migrating my users from 2007.  We'd run into this bug that was generating a ton of event logs for missing performance counters:

http://support.microsoft.com/kb/2870416

It includes a PowerShell script to reregister all of the performance counters that come with Exchange 2013.  When running it on my servers, it generated an error for one of the performance counter definition files.

53 C:\Program Files\Microsoft\Exchange Server\V15\Setup\Perf\InfoWorkerMultiMailboxSearchPerformanceCounters.xml
New-PerfCounters : The performance counter definition file is invalid.
At line:6 char:4
+    New-PerfCounters -DefinitionFileName $f
+    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (:) [New-PerfCounters], TaskException
    + FullyQualifiedErrorId : [Server=EXM-SNA-0001,RequestId=b7edcf81-0f96-4937-a4a7-3bc8f6165132,TimeStamp=10/10/2013 9:30:50 PM] 79EF1430,Microsoft.Exchange.Management.Tasks.NewPerfCounters

I opened the files in Notepad and this one didn't have any obvious errors or differences in structure compared to the other files.  An internet search showed no one else reporting this error processing this file that I could find.  I'd be curious if anyone else running CU2 is able to register this performance counter.

New-PerfCounters -DefinitionFileName "C:\Program Files\Microsoft\Exchange Server\V15\Setup\Perf\InfoWorkerMultiMailboxSearchPerformanceCounters.xml"

Aditya Mediratta

We are having many problems with the health monitoring of exchange in our SCOM 2012 environment. We have 9 exchange servers, with 3 DAGS across the 9 servers. WE are constantly getting health events in SCOM, even for monitors i've explicitly disabled. For example, the FIPS monitor. Following this guide (http://blogs.technet.com/b/exchange/archive/2013/08/13/customizing-managed-availability.aspx) i disabled the FIPS probes/monitors all together across our entire Exchange environment, and yet in SCOM, all 9 servers show this monitor as being unhealthy. Is my understanding on this functionality incorrect, or is it just not functioning properly?

Similarly, even when an Exchange monitor is completely healthy, it shows as unhealthy in SCOM. Right now, HubTransport shows as unhealthy in SCOM For all our Exchange servers, but when i run this command everything shows as healthy, across all servers.

Get-ServerHealth <server name> | ?{$_.HealthSetName -eq "HubTransport"}

I understand that these monitors can be unhealthy for a while and correct themselves, but shouldn't that correct them in SCOM as well? And for disabled monitors, like FIPS, they should never be unhealthy at all. So why are they showing as unhealthy in SCOM? Am i expected to reset health in SCOM every time an unhealthy flag is thrown in Exchange?

From what i've seen there is a huge discrepancy between how SCOM works and how Exchange monitors work. They don't seem to integrate well, at all. Does anyone have any suggestions on getting Exchange 2013 monitors to work properly in SCOM? Is this my error as a user, or is it just bad software

Hi!  I've just migrated (two weeks ago) an EX2010 to EX2013. All seems to work perfectly (after a lot of hard work), but there is something really strange.Every day, at 13.00 something is happening on the server that runs for almost and hour and locks the owa access saying that annoying message with the sad face...

I've checked the maintenance hours on ecp and are configured to run at night.

Also checked the automated tasks on the server and it seems that nothing is running...

Some ideas?  Help please! users are about to hang me!

Hello experts,

We have a Windows 2008 R2 server, we didn't enable recycle feature on it before and we don't have any backup. Some admin has accidentally deleted few usernames. Those users have Exchange 2010 mailboxes. 

Is there any way to restore those deleted users? If not, how to create new users and link them to the original user mailboxes? 

Hello all,

I am wondering if people have seen issues with Universal DLs where members are not removed from the DLs. DLs are being populated through a query from an Oracle Database. Membership is removed and repopulated nightly. Scripts are written in powershell to check to see if DL exists, if it does remove members and repopulate.

We are currently in a mixed 2003/2012 R2 DC environment and are migrating to 2012 R2 shortly.

Much of what I have read indicates that Global Catalog replication seems to be a problem when updating Universal groups. This may lead to DL corruption. The process is ok in the beginning and through testing, but over a week or so the DLs dont drop members. 

Has anyone experienced issues with DL members not being removed in the mixed DC scenario? Are there any rock solid solutions.

I should add the DLs are created with accounts that are org admins and managed by those accounts.

Any help appreciated.

Hi, we have an Exchange 2013 environment for hosting purposes.

One client uses two seperate company names (and domain names). These companies are seperated in Exchange and use seperate address lists. This client uses mail between the two domains.

Let's say the domains are yin.com and yang.com. The users use Outlook Webmail and the Mac OSX builtin mailclient
The problem is that when kevin@yin.com sends email to bob@yang.com, Bob is able to receieve the mail, but the email-address from Kevin is not included in the mail. It is just listed as Kevin, without any property.

When Bob replies to the message from the OSX Mail client, it apparently tries to make up an address and generates something to the effect of this:
Kevin </o=Hosting Company/ou=Exchange Administrative Group /cn=Recipients/cn=*longnumber*>
This address is not correct and when sent, the email is bounced back with a NDR-report.

When Bob replies to the message from OWA, the address is simply the name with no email-address. This also results in an NDR report.

What can we do to make OWA or Mac mail keep the correct emailaddresses?

Hi there,

We are getting the following event log on our Exchange 2013 server, but cannot identify what the cause or issue being reported.

Event ID: 2
Event Source: MSExchange Configuration Core
Event Type: Error
Event Description: Log Name:      Application
Source:        MSExchange Configuration Core
Date:          12/11/2014 9:55:23 AM
Event ID:      2
Task Category: (1)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      ************
Description:
The description for Event ID 2 from source MSExchange Configuration Core cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer the display information had to be saved with the event.

The following information was included with the event:

12048
w3wp.exe
Exception from CmdletLogger.AsyncCommit : System.ArgumentException: activityScope is null.
   at Microsoft.Exchange.Diagnostics.CmdletInfra.CmdletLogger.AsyncCommit(Guid cmdletUniqueId Boolean forceSync)
   at Microsoft.Exchange.Configuration.Tasks.LoggingModule.CommitLog(String loggingStep)

the message resource is present but the message is not found in the string/message table

Anyone else having this issue, and what fixes/workarounds are there to stop it from occurring? Thanks. 

Hi

I need a list of emails located on a Mailbox folder, but am unable to export that data.
You help me?

[PS] C:\>Get-MailboxFolderStatistics -Identity user -FolderScope Inbox | ?{$_.FolderPath -like '/Folder'} | Select Name, ItemsInFolder | Select Timestamp, Sender, {$_.Recipients}, MessageSubject

Regards

Hello,

i activated Mailbox Audit Logging for Admin, delegate and owner with all supported operations (update, delete, etc..)

like mentioned here: http://exchangeserverpro.com/using-exchange-server-2013-mailbox-audit-logging/

But also two days later (and also one Server reboot later) search-MailboxAuditLog is still empty.

any ideas how to fix this?

Best,

martin