Apr 10

Unable to open Outlook on Exchange 2013 – Cannot open your default e-mail folders. Microsoft Exchange is not available.

I got a case where a mailbox was not able to open Outlook. OWA and ActiveSync worked good. I also got information that the same mailbox had a working Outlook profile on another computer.

Tried all the known tricks of course (Repair profile, delete ost file, recreate profile. I even tried to delete mailbox and reconnect). The only thing that happened was this:


I opened RPC Client Access log on Exchange server under C:\Program Files\Microsoft\Exchange Server\V15\Logging\RPC Client Access .

I then compared a working user with the none working user: I then saw this ncacn_http is not allowed for this user, and also (StoreError=RpcHttpDisallowed).

I know that Exchange 2013 only uses RPC over HTTP, not MAPI as earlier.

Then I runned the command : get-casmailbox “user” | fl – And found this


Therefore I runned the command: set-CASMailbox “user” -MAPIBlockOutlookRpcHttp $false. And finally Outlook started.

And also the Outlook profiles that already set up  was working (I guess this was did before MAPIBlocOutlookRPCHTTP was set to true), did not stop working. But only new outlook profiles was not working. 

Mar 20

Exchange 2013 Transport Log Search service keeps restarting and event id 4999 is logged

I was going to trace some e-mails with the Out-GridView  (Get-MessageTrackingLog -ResultSize Unlimited -Start “Mar 18 2013” | Out-GridView). I got this error thrown in my face.

[PS] C:\Windows\system32>Get-MessageTrackingLog -ResultSize Unlimited -Start "Mar 18 2014" | Out-GridView
Failed to connect to the Microsoft Exchange Transport Log Search service on computer "EXCHANGESERVER". Verify
that the Microsoft Exchange Transport Log Search service is started on the target computer.

I went in to services console, and saw that the Transport log search service restarted every time it was started. So it was doing loops.

Also in the event viewe I saw EventID:  4999

Watson report about to be sent for process id: 41848, with parameters: E12IIS, c-RTL-AMD64, 15.00.0847.032, MSExchangeTransportLogSearch, MSExchangeTransportLogSearch, M.E.T.L.S.MailFlowStatistics.InitializeRecord, System.OutOfMemoryException, b5ff, 15.00.0847.030.
ErrorReportingEnabled: True

After some research and digging with proccess monitor from Mark Russinovich I was able to see that the service was trying to read from this folder: C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Logs\Hub\ActiveUsersStats\Backup.

Simply tried to rename the backup folder the folder, and suddenly a new backupfolder was created. And the MSExchangeTransportLogSearch service was able to start and stay started:)

Mar 18

Dell TechCenter Rockstar 2014

Yesterday I got a mail I hoped would come. I was accepted as a Dell TechCenter Rockstar for 2014. Really enjoy beeing part of such a great program, and looking forward to another year together with Jeffrey Sullivan and his colleagues over at Dell Techcenter.


Feb 11

Outlook clients not connecting to correct public folder server

I was troubleshooting a strange problem with Exchange 2010 public folder calendars and Outlook 2010.

The normal operation was:

User added a public folder calendar to favorites and that Calendar was then automatically  added to  Other Calendars in Outlook.

The symptoms that started this troubleshooting was that users complained that the “connections” to shared public folder calendars was missing each time Outlook was restarted. In other words: the calendars disappeared from Outlook and needed to be manually added again.

I found out that the connection in “Favorites” still was active. And if I opened the calendar from favorites again, the calendar was added in the shared calendars again… Strange. I also saw that opening Public folder opening was pretty slow.

When looking at connections status from Outlook client, I saw that the Outlook client was connecting to wrong public folder server. In another AD site across WAN.

I started some traces, and found out that the Outlook client tried to connect to correct server but timed out. And after the time out, Outlook successfully connected to wrong server.

The CAS role was installed on a separate server, so I could restart some services on back-end server without interrupt the Outlook clients.

I know that the RPC Client Access service on the mailbox servers is used for public folder access on Exchange 2010. I was unable to restart the service, it could not be stopped. I needed to kill the service and then start it again. After this the Outlook could connect to correct public folder server. And guess what, the public folder calendar was not disappearing anymore.

Jan 06

Outlook 2013 will not be redirected to new Exchange server after mailbox move

I was working on a Exchange 2013 migration (from Exchange 2007), and we was moving mailboxes. All services worked, but we suddenly got some feedback that some Outlook 2013 clients was not able to reconfigure to new Exchange servers.

1. When checking Outlook Connection Status, SMTP Address only shows "SMTP:"

2. Creating new profile works

After some research we found this hotfix for Outlook 2013:


If you are using Outlook to connect to a Microsoft Exchange Server 2007 mailbox:

  • You receive an error message that resembles either of the following when you try to configure Automatic Replies (Out of Office):

    Your automatic reply settings cannot be displayed because the server is currently unavailable. Try again later.

  • You cannot retrieve Free/Busy data for calendar scheduling.
  • Add-ins that use the Account.SmtpAddress property no longer work.

These features rely on an underlying Autodiscover technology. After you install this security update, Autodiscover may fail for Exchange 2007 configurations. Therefore, Outlook features that rely on Autodiscover will also stop working.
To resolve these issues, install update 2850061.

Looks like Microsoft has another problem after releasing a Office patch. Not good!

So I recommend installing http://www.microsoft.com/en-us/download/details.aspx?id=41544 before you do mailbox moves:)

Jan 06

DFS – Initial replication for replicated folder will not start

I had started to replace an old DFS 2008 DFS server, with a new 2012 R2 DFS server. After 2012 R2 server was ready, I added a small folder for DFS replication (did not care about pre-staging because the folder was small). This folder was not replicated with other servers at this time.

The events in Event Viewer  showed that the folders was correctly added, and that the initial replication should start.

This member is waiting for initial replication for replicated folder
– This member is waiting for initial replication for replicated folder <folder> and is not currently participating in replication. This delay can occur because the member is waiting for the DFS Replication service to retrieve replication settings from Active Directory. After the member detects that it is part of replication group, the member will begin initial replication.

But after I waited some hours, and nothing had happened I understood that this would not work:) The source server replicated with other servers. But I did not try to add other folders on the Win2012 R2 server.

I found out that the folder I tried to sync did not had primary member. I therefore ran this command

dfsradmin Membership Set /RGName:<replication group name> /RFName:<replicated folder name> /MemName:<member you want to be primary> /IsPrimary:True

And suddenly the replication started:)

Nov 18

Migrate Public folder from Exchange 2010 SP3 to Exchange 2013 CU2. The process is stuck at "Initial Seeding" status at 20%.

I was replicating Public folder from EX2010 SP3 to Exchange 2013 CU2 for a customer. Everything looked good and I followed http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx.

This customer had a very large PF database (500GB), so the replication took long time. I also had some issues at the beginning with alias naming, but after I resolved that the migration went on. I saw it was going to 94%. Then something happened.

Copying messages is finished. Copying rules and  security descriptors. This was the status,soon finished then i thought. But no…. It seemed stuck at “Initial Seeding” 20%Copying messages is finished. Copying rules and security descriptors.

I then started to check after similar issues on the web. I found out that someone had similar issues, but on Office365.

I started a support case with MS, and quickly got an answer:

Hello Mr. Knarvik,

The issue described is a known issue with Exchange 2013 CU2 and is expected to be solved in CU3.

I was asking if there was planned an interim update, but not at the moment. I have requested one though:)

Nov 12

New mail goes directly to Deleted Items

I recently did a migration from Exchange 2003 to Exchange 2010. One step at this migration was to convert some of the meeting rooms to type “Room” and then enabling AutoAccept on the room. And also some Shared mailboxes to type “Shared”. No problems so far. The migration went perfectly and users where able to book meeting rooms and the meeting rooms processed the requests and cancellations automatically  (Resource Booking Attendant). And the shared mailboxes also worked as they should.

I did however got a support case, and it seemed that a shared mailbox did not work as excepted. When a new mail was sent to the shared mailbox, the mail was going to inbox but was moved automatically to deleted items. I did off course checked the rules, but it was empty. And I could not find any other problems.

Since I know that room mailboxes does the exact same thing with meeting requests (process the mail, and move it to deleted items) I was curious if there was an booking attendant enabled on the Shared Mailbox? And look what I found:


The shared mailbox had the AutomateProccessing set to AutoAccept.

I could change this in EMS (not EMC as the mailbox must be “room” to get the Resource policy tabs)

So in order to check the AutoAccept policy on the mailbox, I converted it to a room with the command: Set-Mailbox “Shared mailbox” –type Room

set-CalendarProcessing “shared mailbox” -AutomateProcessing AutoUpdate

Then the incomming mail did not went directly to Deleted items:)


The root cause was, that when I migrated to Exchange 2010 I converted this mailbox to room and enabled AutomateProcessing to AutoAccept . And since this was wrong, this mailbox was directly changed to type Shared without clearing out the AutomatProcessing.

Nov 07

Fix for too many certificates in Trusted Root Certificate Authorities

Remember KB931125? The patch that broke tons of Configuration Manager management points? Yeah, that one. I just found out that as of October 17th Microsoft has released a “quick fix” for this problem so that you don´t have to manually delete the certificates yourself. Basically the fix will delete all the third party root certificate authority certificates installed on your computer/server and then download the ones needed.

Check out KB2801679 for more details. You can also read about the root cause of the schannel error in the article.

Nov 06

Failed to install Applications during Build and Capture

You want to install Applications in your thick image, but they fail.


During Build n Capture Applications fails to install (but packages installs without a problem)

Status messages: The task sequence failed to install application (Install Application) in the group () with exit code 16389.

AppEnforce.log is missing on the client



Check and verify Network Access Account

Check you Boundaries
they must be memeber of a Boundary Group
Since you don’t join the domain during build and capture AD Site Boundarys just are not anough.
Use IP Address Ranges Best practice is to let them be discovered and let ConfigMgr create them. AD Site and IP Subnet bondaries are still evil in 2012. for more infocheck out Jasons lovely post http://blog.configmgrftw.com/?p=343

Client Installation property
adding the SMSMP=myMP.mydomain.com PROPERTY to the client installation properties in the Setup Windows and ConfigMgr task in your TS. This must also be done because it can not get any info about the MP from AD because it doesn’t joins the domain

Check the applications
Try to deploy it to a working workstation (not during OSD)
Also Selected the option “Allow this application to be installed from the Install Application task sequence instead of deploying it manually” in the Application Properties.

Allow anonymously connections
And if it still does not work try enabling “Allow clients to connect anonymously” on the DP


Hope that someone will find this little post helpful.

Happy Deployment!






Older posts «

QR Code Business Card