Exchange server stop working after updater to CU10

I recently installed the update Security Update for microsoft exchange 2013 CU10 (KB3124557) and after this my Exchange server stop working. I can see from the Service that the all the service are okay but not the Microsoft Exchange Transport. If i try to start this i get the message

Error 1068: The dependency service or group failed to start. I have looking in to this by google but no results.

I can not access the owa or the ecp. If i try an icon up and says "works" - is still working.

In my event logg i have several error like

Active Manager Client already doing query for object '' on another thread, however this thread didn't complete in 100 msec. - Event id: 10015

The setting SupportedIPMTypes in the Web.Config file was missing.  Using default value of System.Collections.Generic.List`1[System.String]. - Event id 1033

Watson report about to be sent for process id: 18136, with parameters: E12IIS, c-RTL-AMD64, 15.00.1130.007, M.E.Diagnostics.Service, M.E.Diagnostics.PerformanceLogger, M.E.D.P.PerformanceLogSet.StartLog, System.ArgumentException, 95c6, 15.00.1130.002.
ErrorReportingEnabled: False  - Error 4999

Please help!
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Matt MinorTechnical Systems AnalystCommented:
First step would be to investigate what the error is telling us - a dependency hasn't started.

Go to start, run, and type "services.msc" to see the list of services on the system.

Now I am not certain which one is causing you grief, so you'll need to play detective and have a look by double-clicking the exchange-related services and view under "dependencies" to verify that everything is started.

Here is a list of all of the critical Exchange-Services:
Matt MinorTechnical Systems AnalystCommented:
For a quick-glance to make sure your primary Exchange services are running, from the Exchange Management Shell, issue the following command:
Get-Service | Where {$_.DisplayName -Like "*Exchange*"} | ft DisplayName, Name, Status

This might give a hint as to where the problem lies, but you might still need to investigate the dependencies of each.
Jbergstrom87Author Commented:
DisplayName                             Name                                                                     Status
-----------                             ----                                                                     ------
Microsoft Exchange Search Host Contr... HostControllerService                                                   Running
Microsoft Exchange Active Directory ... MSExchangeADTopology                                                    Running
Microsoft Exchange Anti-spam Update     MSExchangeAntispamUpdate                                                Running
Microsoft Exchange DAG Management       MSExchangeDagMgmt                                                       Running
Microsoft Exchange Mailbox Transport... MSExchangeDelivery                                                      Running
Microsoft Exchange Diagnostics          MSExchangeDiagnostics                                                   Running
Microsoft Exchange EdgeSync             MSExchangeEdgeSync                                                      Running
Microsoft Exchange Search               MSExchangeFastSearch                                                    Running
Microsoft Exchange Frontend Transport   MSExchangeFrontEndTransport                                             Running
Microsoft Exchange Health Manager       MSExchangeHM                                                            Running
Microsoft Exchange IMAP4                MSExchangeImap4                                                         Running
Microsoft Exchange IMAP4 Backend        MSExchangeIMAP4BE                                                       Running
Microsoft Exchange Information Store    MSExchangeIS                                                            Running
Microsoft Exchange Mailbox Assistants   MSExchangeMailboxAssistants                                             Running
Microsoft Exchange Mailbox Replication  MSExchangeMailboxReplication                                            Running
Microsoft Exchange POP3                 MSExchangePop3                                                          Stopped
Microsoft Exchange POP3 Backend         MSExchangePOP3BE                                                        Stopped
Microsoft Exchange Replication          MSExchangeRepl                                                          Running
Microsoft Exchange RPC Client Access    MSExchangeRPC                                                           Running
Microsoft Exchange Service Host         MSExchangeServiceHost                                                   Running
Microsoft Exchange Mailbox Transport... MSExchangeSubmission                                                    Running
Microsoft Exchange Throttling           MSExchangeThrottling                                                    Running
Microsoft Exchange Transport            MSExchangeTransport                                                     Stopped
Microsoft Exchange Transport Log Search MSExchangeTransportLogSearch                                            Running
Microsoft Exchange Unified Messaging    MSExchangeUM                                                            Running
Microsoft Exchange Unified Messaging... MSExchangeUMCR                                                          Running
Tracing Service for Search in Exchange  SearchExchangeTracing                                                   Stopped
Hyper-V Data Exchange Service           vmickvpexchange                                                         Stopped
Microsoft Exchange Server Extension ... wsbexchange                                                             Stopped
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

Matt MinorTechnical Systems AnalystCommented:
If you open the transport service and go to dependencies what is appearing there?
Jbergstrom87Author Commented:
This is what i can see
Matt MinorTechnical Systems AnalystCommented:

Issue Get-ReceiveConnector and post results.
Jbergstrom87Author Commented:
Creating a new session for implicit remoting of "Get-ReceiveConnector" command...

Identity                                Bindings                                Enabled
--------                                --------                                -------
MAIL-SERVER01\Default MAIL-SERVER01     {, [::]:2525}               True
MAIL-SERVER01\Client Proxy MAIL-SERV... {[::]:465,}                 True
MAIL-SERVER01\Default Frontend MAIL-... {[::]:25,}                   True
MAIL-SERVER01\Outbound Proxy Fronten... {[::]:717,}                 True
MAIL-SERVER01\Client Frontend MAIL-S... {[::]:587,}                 True

This looks good, yes?
Jbergstrom87Author Commented:
I also checked my database which says

[PS] C:\Windows\system32>Get-MailboxDatabase

Name                           Server          Recovery        ReplicationType
----                           ------          --------        ---------------
**   MAIL-SERVER01   False           None
**                MAIL-SERVER01   False           None
Jbergstrom87Author Commented:
I have continued to investigate the problem in the log. The following does not look really good.

Event: 8
Log name: MSExchange Management
Soruce: MSExchange CmdletLogs

(PID 3944, Thread 59) Task Get-HealthReport throwing unhandled exception: System.ArgumentException: sessionState
   at Microsoft.Exchange.Configuration.Tasks.ExchangePropertyContainer.GetProvisioningBroker(ISessionState sessionState)
   at Microsoft.Exchange.Provisioning.ProvisioningLayer.GetProvisioningHandlersImpl(Task task)
   at Microsoft.Exchange.Provisioning.ProvisioningLayer.GetProvisioningHandlers(Task task)
   at Microsoft.Exchange.Configuration.Tasks.Task.<BeginProcessing>b__4()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeNonRetryableFunc(Action func, Boolean terminatePipelineIfFailed).
Jbergstrom87Author Commented:

After a few moments of thinking and troubleshooting, I managed to solve the problem. I solved first that not the  ransport started which was due to another service was not running "Microsoft Filtering Management Service"

After I fixed this the e-mail started to come through in to the server but owa and ecp was unable to visit. After a while of troubleshooting, I found the problem.

Get-ServerHealth "server" | ?{$_.HealthSetName -eq "OWA.Protocol"}OwaSelfTestMonitor                        OWA.Protocol    UnhealthyOwaDeepTestMonitor                        OWA.Protocol    Unhealthy
OwaSelfTestMonitor                        OWA.Protocol    Unhealthy
OwaDeepTestMonitor                        OWA.Protocol    Unhealthy

and after a moment of more troubleshooting, I could see that the service "IIS Admin Service" was not started. Started this again and wrote in the CMD - iisreset / noforce

After this I could again run the Get-Server Health "server" | ? {$ _. HealthSetName -eq "OWA.Protocol"}, and then see that

 OwaSelfTestMonitor                        OWA.Protocol    Healthy
 OwaDeepTestMonitor                        OWA.Protocol    Healthy

Links I used to solve the problem.

Hope my debugging can help others to solve this problem =)

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Jbergstrom87Author Commented:
This can help many to solve problem that owa, ecp and maybe mail can not go in to the Exchange server.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.