Making a change in our environment and adding a Hybrid server.  We installed a new CAS and Transport  but did not install the Mailbox Role.  We installed an Exchange 2010 SP1 and upgraded to SP3 Rollup 8.  We now need to add the mailbox roll to the hybrid server.  The SP3 upgrade obviously doesn't allow us to install the mailbox role.  Tried using the Exchange 2010 with SP1 and that does not seem to work. Presents with an error.

Anyone have any ideas on how to add this to role to our server.

X-ClientId: RCQK - POTE - WQNE - IGNHG
X-OWA-Error: ScriptLoadError;Failed to load script: https://XXXXXX/owa/prem/15.0.1076.9/scripts/globalize/globalize.culture.en-hk.js
X-OWA-Version: null
X-FEServer: XXX-XXX01
X-BEServer: undefined
Once i change the regional setting to other language, Chinese, English US, the user can access owa normally. 

I have search it but don't find any related information. My exchange server is fresh install and most recent update patched
Regards,
Andrew

Hi. I am in MS Exchange 2010 and Outlook environment.  Meghan's email bounces back when she tries to email Kim who is on the same GAL but different domain. I am on the same domain as Meghan and I can email Kim without a problem.  Both Meghan and I can email user Nadia. Nadia is on Kim's domain.  

So we know it is a Meghan to Kim problem.  Meghan can receive email from all of us without problem. 

We have cleared the cache (deleted .nk2). even had her try 'reply' from her work email on her phone instead of the computer. Meghan tried to reply directly to Kim's email without luck;  

Why is Meghan not able to email Kim?

Here is one of the error messages received (modified to secure users name and domain names):

Delivery has failed to these recipients or groups:

Cxxxx, Kimberly - (XYZ City)

There is a problem with the recipient's e-mail system. More than one person has this e-mail address. The recipient's system administrator will have to fix this problem.

Diagnostic information for administrators:

Generating server: retexch001.ABC.ORG

IMCEAEX-_O=RETEXCHANGE_OU=First+20Administrative+20Group_cn=Recipients_cn=KCxxxx@SenderDomain.ORG

#550 5.1.4 RESOLVER.ADR.Ambiguous; ambiguous address ##

Original message headers:

Received: from retexch001.RETLAN.ORG ([192.168.65.223]) by retexch001

([192.168.65.223]) with mapi; Mon, 18 May 2015 14:06:41 -0400

Content-Type: application/ms-tnef; name="winmail.dat"

Content-Transfer-Encoding: binary

From: "Hxxx,Meghan"

To: "Cxxxx, Kimberly - (XYZ City)"

Subject: test

Thread-Topic: test

Thread-Index: AdCRlYTa1xuvVwAIScC55l+TmE/cGQ==

Date: Mon, 18 May 2015 14:06:40 -0400

Message-ID: <501C5C4BAC2989498C40F198DE8185A50DE8E2BF@retexch001>

Accept-Language: en-US

Content-Language: en-US

X-MS-Has-Attach:

X-MS-TNEF-Correlator: <501C5C4BAC2989498C40F198DE8185A50DE8E2BF@retexch001>

MIME-Version: 1.0

Bamedele

exchange 2013.

I have relay connector to allow our AS400 and various copier\printers to forward email through exchange.

if I go to mail flow-receive connectors and check on the relay filter, it shows Logging -On.

but when running powershell commands to track messages going out to particular email address, it does not seem to return any of the emails going through the connector.

emails our people are sending via outlook are showing up, but none of the emails through the connector do.

is there another place I need to turn on logging, or something additional I need to do?

below is example of my powershell command

Get-MessageTrackingLog -Start "03/01/15 00:00:00" -End

"05/19/15 23:59:59" -Recipient "blah@blah.net" | select

sender, recipient, timestamp, messagesubject, totalbytes | export-csv

c:\scripts\messlog1.csv

Dear IT PRo Team

             I have one question about migration exchange , we plan to migrate server 2003 or exchange server 2003 to server 2012 and exchange server 2013 , we have new server for migration or we dont have many user around 40 user ,please help  me and tell what the best way to migrate 2003 ADS ,exchange mail box to 2012 ,exchange 2013

I'm trying to perform a MailboxSearch on my singular Journaling Mailbox.  

I'm trying to extract all e-mails TO or FROM "joe.smith", but as we know, the Journaling Mailbox stores the original e-mails as attachments.

Fortunately, the "actual e-mail" in the Journaling Mailbox has a body which contains meta-data, including the attached e-mails FROM and TO.

I think it's safe to assume I can search the Journaling Mailbox for any e-mail with:

Body containing "Sender: Joe.Smith" OR "Recipient: Joe.Smith"

...but my AQS for the SearchQuery parameters must be incorrect because I never get proper results, if any.

Is my assumption correct, and what is the proper SearchQuery (AQS) for this?

If you can solve this you are my hero.

We use exchange 2013, but these clients are using outlook 2010

We have a mailbox - lets call it PS.  It used to be a public folder and we forced them to a shared folder (totally recreated the mailbox and moved items over).  The one major issue with the clients are they were going to lose their quick clicks.  Quick click settings are independent in public folders, but are shared in shared folders (meaning if someone changes the default, it changes for all) .  We migrated to this shared folder in February.  What the users found out, and never told me, is that they were still all able to set their default quick click, and it doesn't change the others.  This is NOT how shared folders act.  infact I cannot reproduce this on ANY shared folder - but somehow they are able to.  at 5pm to 530 EVERYDAY their quick clicks start working correctly and all user default quick click settings goes back to the last person who set theirs - they throw a fit, complain and then when they start their next morning they set their quick clicks independently again and work the whole day.

This is NOT the main issue, but just some background I feel I must share.

There are about 15 users, they have their normal inbox, but they open this PS folder in a new window and work mostly out of that folder.  All 15 users are in online mode(cached disabled) due to the lag cached causes when they are trying to grab or categorize emails.  They categorize the email with their name, work on the clients file, and then when done, they mark it completed and move the email down one level to a subfolder in the PS inbox

So, as a recap, they have been using this since February.  They used this for a good month with no major issues. in late march they started to receive many "cannot move errors" .  It seems to have gotten worse over the months and all 15 users have experienced and will experience this many times a day - there is no rhyme or reason, and is very sporadic.  This error prompts when they move the message from the PS inbox, to the PS inbox subfolder.  "Can't move the items. The item   could not be moved. It was either already moved or deleted, or access was   denied" .  After the move error is received, they do not have to move the mail again, it actually DOES move the item.  however it doesn't show for that person it is moved until they refresh their mailbox, but others see it was moved. 

Users also will notice that their PS inbox will stop auto refreshing new mail, but the mailbox count in bottom left remains accurate. (which they can fix by resorting, doing a send/receive does not fix the refresh).  It appears that the refresh issue occurs when one or multiple users receive the cannot move error

We also notice strange issues like when a user categorizes the email, it doesn't appear to categorize to them - but others can see it categorized and the user has to open the email to see the category

to muddy the waters - other select users on the production floor have access to this mailbox, and every now and then, users will connect to this mailbox(incached) to lookup an email - could their infiltration cause this hiccup?

Where we are today:

• We found this mailbox hit a size of 120GB - we have purged this mailbox and it currently resides at 20GB.  This error is notorious for having a super full deleted items or corruption in deleted so the deleted items were cleansed in full
• All windows updates and office updates have been ran
• NIC driver update and all power save options disabled
• outlook anywhere disabled
• shared mailboxes are NOT in cached
• all users OSTs were deleted
• all users mail profiles were deleted and reestablished
• we use a netscaler/load balancer - we set one user to bypass this, because we thought they were getting disconnected, to try to fix the refresh error(they didn't move emails) - however it appears that the refresh error may be caused by the move error.  I think the netscaler disconnects every 2 min, so perhaps moving the file and it is disconnected, I think we will bypass the netscaler for a few users who move a lot of mail to see if any relief
• time stamps, and having the server team look at logs have provided no help
• Exchange is at rollup5 (I know there was an issues with similar in previous release)

I would like to start from scratch and have a full new mailbox created - but the team seems hesitant

Next steps could be to remove access from the production floor, so only the online users access this folder.

Perhaps faulty user rights, or they need elevated rights for some dumb reason, so we could up their rights

at this point I will try anything, please help :(

Hi,

I am running exchange 2013 CU7 with outlook 2013. Everything is up to date. Recently we noticed that the room finder could not show anything. So I searched for solutions on the web. I ended up creating a 3 room lists and population them with our rooms.

I did some testing with 2 user accounts on different environment. here are the results

In OWA : the 2 user accounts are able to see the room list and the room finder works fine

On my computer running outlook : none of the user account see the room list and room finder always shows "None".

On a TSE server running outlook :one account sees the room list and room finder works. with the second account, I cant see the room list and room finder always shows "None"

On the exchange server, I've tried to update the offline address book, and then force the update on client side. On my computer I also tried to recreate my outlook profile. It didnt help.

I'm getting desperate, I dont know what else to try to get it to work with any user on any outlook.

any help appreciated

Hi,

We currently have one active Exchange 2010 server and an Exchange 2013 server which we were planning to use alongside the 2010 server.

We only recently discovered that we can't sync public folders between 2010 and 2013, so we plan to uninstall 2013 and have a second 2010.

The only issue with this is that the uninstall won't complete due to arbitration mailboxes and mailbox plans.

The 2013 server was never actually used, so I'm hoping I can just disable all mailboxes in the unused databse - is that right?

The error in the unistall wizard says that if there are other servers arbitration mailboxes should be moved to another DB - but does that apply when there are no more Exchange 2013 servers?

Also, running Get-MailboxPlan and Set-MailboxPlan are giving errors that they are not recognized as cmdlets!

I'd be grateful for any advice on this.

Thanks - Lawrence

Our environment is composed of a single Exchange 2007 (Version: 08.03.0348.002)server running cas and hub roles  and 2 MBX servers running in a cluster.   Event logs (mbx, cluster, application, system) look like the same as when it running.  Currently there is 700 messages queued in the mapidelivery.  I have restarted the transport service and a few messages when through but then mailflow stops.  

Hi All,

I am trying to connect to Exchange 2010 using outlook but via POP3.

The account gets configured when i use port 110 as in the below screenshot.

When i change the option to port 995 it does not work.

Can any one help in determining the issue and how to fix it ?

Gautam.75801

Hello,

I wanted to know in depth about how CAS 2013 authenticates/verify user's credentials when they connect to via OutlookAnywhere or OWA or EAS.

Can any body refer me a good article available on Internet or a website where I can get this information in detailed.

Thanks a lot in advance.

Hello All,

We have a concern where we are unable to see mail contacts in the distribution lists. Like we have hundreds of mail contacts with the name of "Franchises", but we are able to see only 3 from different DL's. But when we check for the members of these DL's from AD or exchange management console we are able to see all the members, and when searched from outlook 2013 GAL, we are able to see only 3, rest cannot be found. Outlook address book has been download multiple times but issue still persists.

Also note we have 2007 and 2013 working at the same time with few hundred users to migrate, however the major chunk has been migrated. Also we tried updating the distribution list (exchange version 0.10) but it also did not worked out.

Any idea what could be be done in order to make these mail contact available as member to distribution groups.

Hi,

I have Exchange 2013 (CU8 installed) I configured antispam etc.. . I added Block list providers, but exchange doesn't check that the ip address is on black list. I don't have edge server.

This my configuration:

This ip address is on black list.

Please,

Can you help me with this problem ?

Hello,
I'm trying to move users from one mailbox database to another. Most people are moved without errors, but the remaining 10 are not moved in error:

Error details: MapiExceptionNoAccess: Unable to query table rows. (hr=0x80070005, ec=-2147024891)
Diagnostic context:
    Lid: 55847   EMSMDBPOOL.EcPoolSessionDoRpc called [length=284]
    Lid: 43559   EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=264][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropGetContentsTable [5]
    Lid: 27962   ROP: ropSetColumns [18]
    Lid: 17082   ROP Error: 0x80070005
    Lid: 27489 
    Lid: 21921   StoreEc: 0x80070005
    Lid: 27962   ROP: ropExtendedError [250]
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 26426   ROP: ropSetColumns [18]
    Lid: 28064 
    Lid: 13861   StoreEc: 0x80070005
    Lid: 27265   StoreEc: 0x80070005
    Lid: 1750    ---- Remote Context End ----
    Lid: 27962   ROP: ropQueryRows [21]
    Lid: 17082   ROP Error: 0x80070005
    Lid: 17153 
    Lid: 21921   StoreEc: 0x80070005
    Lid: 27962   ROP: ropExtendedError [250]
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 26426   ROP: ropQueryRows [21]
    Lid: 40685   StoreEc: 0x80070005
    Lid: 28468 
    Lid: 13029   StoreEc: 0x80070005
    Lid: 26348 
    Lid: 22252   StoreEc: 0x80070005
    Lid: 1750    ---- Remote Context End ----
    Lid: 26849 
    Lid: 21817   ROP Failure: 0x80070005
    Lid: 28414 
    Lid: 32510   StoreEc: 0x80070005
   at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, SafeExInterfaceHandle iUnknown, Exception innerException)
   at Microsoft.Mapi.MapiTable.QueryRows(Int32 crows, QueryRowsFlags flags)
   at Microsoft.Exchange.MailboxReplicationService.LocalDestinationFolder.<>c__DisplayClass15.<SetExtendedProps>b__11()
   at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
   at Microsoft.Exchange.MailboxReplicationService.LocalDestinationFolder.SetExtendedProps(PropTag[] promotedProperties, RestrictionData[] restrictions, SortOrderData[] views)
   at Microsoft.Exchange.MailboxReplicationService.LocalDestinationMailbox.Microsoft.Exchange.MailboxReplicationService.IDestinationMailbox.CreateFolder(FolderRec sourceFolder, Boolean failIfExists, Byte[]& newFolderId)
   at Microsoft.Exchange.MailboxReplicationService.DestinationMailboxWrapper.<>c__DisplayClass6c.<Microsoft.Exchange.MailboxReplicationService.IDestinationMailbox.CreateFolder>b__6b()
   at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
   at Microsoft.Exchange.MailboxReplicationService.DestinationMailboxWrapper.Microsoft.Exchange.MailboxReplicationService.IDestinationMailbox.CreateFolder(FolderRec sourceFolder, Boolean failIfExists, Byte[]& newFolderId)
   at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<>c__DisplayClass36.<>c__DisplayClass38.<CreateFolderHierarchy>b__31()
   at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
   at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<>c__DisplayClass36.<CreateFolderHierarchy>b__30(FolderRecWrapper folderRec, EnumFolderContext context)
   at Microsoft.Exchange.MailboxReplicationService.FolderMap.EnumSingleFolder(FolderRecWrapper folderRec, EnumFolderContext ctx, EnumFolderCallback callback, EnumHierarchyFlags flags)
   at Microsoft.Exchange.MailboxReplicationService.FolderMap.EnumSingleFolder(FolderRecWrapper folderRec, EnumFolderContext ctx, EnumFolderCallback callback, EnumHierarchyFlags flags)
   at Microsoft.Exchange.MailboxReplicationService.FolderMap.EnumSingleFolder(FolderRecWrapper folderRec, EnumFolderContext ctx, EnumFolderCallback callback, EnumHierarchyFlags flags)
   at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<CreateFolderHierarchy>b__2f(MailboxMover mbxCtx)
   at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.ForeachMailboxContext(MailboxMoverDelegate del)
   at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.CreateFolderHierarchy(Object[] wiParams)
   at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)
Error context: --------
Operation: LocalDestinationFolder.SetPromotedProps
PropTags: [ExpiryTime; ReplyTime; SentRepresentingName; MessageToMe; MessageCcMe; SentRepresentingEmailAddress; DisplayBcc; DisplayCc; DisplayTo; 237699075; 245497859; Body; 276824067; 277872643; 278200323; ItemTemporaryFlag; ContentCount; 921436163; 921567235; 1737359391; 1748172872; 1748238339; 1748631555; 1749090307; 1749156098; 1750401035; 1750466591; 1750532107; 1750663199; 1750990851; 1845559299; 1879441439; 1879506947; 0x80000102(NamedProp); 0x80010003(NamedProp); 0x8003101f(NamedProp); 0x80290003(NamedProp); 0x802b0003(NamedProp); 0x8031000b(NamedProp); 0x80320040(NamedProp); 0x8074000b(NamedProp); 0x80940040(NamedProp); 0x80950040(NamedProp); 0x80980003(NamedProp); 0x809e000b(NamedProp); 0x80d20003(NamedProp); 0x80d30102(NamedProp); 0x80d50003(NamedProp); 0x80d9000b(NamedProp); 0x80db0003(NamedProp); 0x80dc001f(NamedProp); 0x844c0003(NamedProp)]

I have tried to add the option to request:  -BadItemLimit '100' -LargeItemLimit 50 -AcceptLargeDataLoss -AllowLargeItems
I run New-MailboxRepairRequest for mailbox and database: -CorruptionType ProvisionedFolder, SearchFolder, AggregateCounts, FolderView
Open mailbox with MFCMapi and delete rules

Please help how to solve this problem?

Hello!

One more strange issue: in all my deployments of Exchange Server 2013SP1 I always start from removing a default mb database and I never had any problems with it. The procedure is ~ as follows:

1) I create a new mailbox db.
2) Get-Mailbox –Arbitration | New-MoveRequest -TargetDatabase “NewDB”
3) Get-Mailbox –Monitoring| New-MoveRequest -TargetDatabase “NewDB”
4) Get-Mailbox | New-MoveRequest -TargetDatabase “NewDB”

5) Make sure Administrator account has been moved to the new db.

6) Delete the default db.
7) Restart
8) Log on to ECP as Administrator.

Today the two new installations end up  with the following error on 8)  "Log on to ECP as Administrator":

The IIS log shows this:

"2015-04-17 13:56:17 fe80::191b:2b21:3254:ddd%12 POST /owa/auth.owa &CorrelationID=<empty>;&cafeReqId=8bb165df-6c57-49f0-9ee9-9590c6f981db; 443 TestCompany\Administrator fe80::191b:2b21:3254:ddd%12 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko https://exch1.testcompany.com/owa/auth/logon.aspx?replaceCurrent=1&url=https%3a%2f%2fexch1.testcompany.com%2fowa 500 0 0 15"

Looks like the Administrator's mailbox has not been moved into the new database, butGet-MoveRequest and Get-Mailbox... showed that Administrator's mailbox was really in the new db.

Moreover, right after deletion of the default db (after item 6) I signed out from ECP and logged back to it - the logon was successfull (at this moment the default database had been already deleted!). And only after restarting the server it started showing this error.

While logged on as Administrator I created one more exchange administrative user account in the new db - it doesn't experience any issues with logging on to ECP.

No errors show in any Windows logs.

What should I check in this situation?

Thank you in advance,

Michael

Right to the very end of the Technet article for Shadow Redundancy, there's the example of one Mailbox server (Mailbox01) that has failed. 2 outcomes are illustrated - A the server is rebuilt, thus using a new transport database ID and B the server is brought back online using the same transport database.

For case A, it's stated that "When Mailbox01 becomes unavailable, each server that has shadow messages queued for Mailbox01 will assume ownership of those messages and resubmit them", indicating a total delay for the messages of only 2 minutes (the default value of ShadowHeartbeatFrequency). However wouldn't there have to pass 3 hours (default ShadowResubmitTimeSpanvalue) for the time it takes for the shadow servers to assume ownership of the shadow messages for Mailbox01) until those messages are delivered ? Or is it implied that the time taken for re-submission is indeed 2 minutes, but from the point in time when Mailbox01 is re-built, and the other shadow servers open a SMTP session only to discover that the transport database ID is different, thus issuing immediate delivery of the messages ?

Hi Guys,

For 1 year after migration from exchange 2007 to exchange 2013, there is no problem with it.

In past few days, suddenly our outlook client disconnect from server.

I just restart the exchange server but it took a long time(1 hour) for connecting in client outlook.

same with the day, we have a problem with paging file error message in exchange server.

is it related ?

Thanks,

Hilda

How can I increase this limitation of 100 recipients. When attempting to create another transport rule get the following message:

The transport rule can't be created  because you've exceeded the maximum number of recipients that can be  added to a message by all your transport rules. Your transport rules are  adding 113 recipients, and the maximum number is 100. Reduce the number  of recipients, either by removing recipients from actions in existing  rules, or by removing existing actions that add recipients. Or delete  existing transport rules that add recipients.

Thanks!

Rodrigo Henriques

IT Infraestructure