I spent most of the day troubleshooting why OWA stopped working.. (after the login page i'd get a blank/white page), also if I used Windows Authentication OWA would work. Turns out its due to the Microsoft Exchange Forms-Based Authentication service crashing on startup. I have three services in my event log that are terminating on startup, oddly if I start them manually or load them with "Automatic (Delayed Start)" their fine, but in the default "Automatic" configuration they output these errors.. Not sure how to correctly fix it, any ideas? Running Exchange 2010 SP1 Rollup 2 Event Log The Microsoft Exchange Forms-Based Authentication service service terminated with service-specific error %%-2147467259. --- The Microsoft Exchange Service Host service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. A timeout was reached (30000 milliseconds) while waiting for the Microsoft Exchange Service Host service to connect. --- The Microsoft Exchange Protected Service Host service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. A timeout was reached (30000 milliseconds) while waiting for the Microsoft Exchange Protected Service Host service to connect.

Hi, Please try to create a new OWA virtual direcotry: 1. Open ems, type: Remove-OwaVirtualDirectory -identity "Contoso\OWA (default web site)" New-OwaVirtualDirectory 2. Run IISRESET to restart IIS service. Then try to start Forms-Based Authentication service . If the issue persists, please restart exchange server to resolve any potential issue then test it again. Gen Lin TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Thanks Gen Lin-MSFT

Rebuilding the OWA virtual directory had no effect, for fun I also tried it via the EMC. I'm wondering if a dependency isn't attached to those services. The services are stable once all the other exchange services start (Automatic (Delayed)), however if they load with automatic they timeout & terminate. For fun I setup a VM w/ W2K8 R2, Joined the Domain, and Installed Exchange 2010 SP1 from media (no rollup's), and it had the same issue.

Gen, Sorry, but in my opinion what you propose is nothing more than a form of superstitious three-fingered-salute-style solutions sure to accomplish just one thing: wasting time. Basically, you are telling this guy who has spent most of the day troubleshooting a common Exchange issue to recreate his site and repeat his work again. Google clearly shows that the Microsoft Exchange Forms-Based service has got automatic startup issues; true for this gentleman, me and many other folks. Has no one at Microsoft got the check-list of things to look for published? Specifically what's the source of this event log entry? <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" /> <EventID Qualifiers="49152">7024</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8080000000000000</Keywords> <TimeCreated SystemTime="2011-03-17T00:39:45.171875000Z" /> <EventRecordID>195055</EventRecordID> <Correlation /> <Execution ProcessID="560" ThreadID="3604" /> <Channel>System</Channel> <Computer><fqdn></Computer> <Security /> </System> <EventData> <Data Name="param1">Microsoft Exchange Forms-Based Authentication service</Data> <Data Name="param2">%%-2147467259</Data> </EventData> </Event> The only solution I've found to "solving" this problem is to start the service manually after every reboot, if the service doesn't start by itself.

I am experiencing this exact issue. Anyone having any luck?

@David; I agree @ Tony; I see the same @MS: what I also see is one the 1 (of 4) servers this happens, there is never a service controll event indicating the FBA service starts: The first event after reboot from the FBA Service is actually 'entering stopped state' Log Name: System Source: Service Control Manager Date: 4/25/2011 10:23:33 PM Event ID: 7036 Task Category: None Level: Information Keywords: Classic User: N/A Computer: xxxnamexxx Description: The Microsoft Exchange Forms-Based Authentication service service entered the stopped state. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" /> <EventID Qualifiers="16384">7036</EventID> <Version>0</Version> <Level>4</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8080000000000000</Keywords> <TimeCreated SystemTime="2011-04-26T02:23:33.377249000Z" /> <EventRecordID>235658</EventRecordID> <Correlation /> <Execution ProcessID="476" ThreadID="852" /> <Channel>System</Channel> <Computer>xxxnamexxx</Computer> <Security /> </System> <EventData> <Data Name="param1">Microsoft Exchange Forms-Based Authentication service</Data> <Data Name="param2">stopped</Data> <Binary>4D005300450078006300680061006E00670065004600420041002F0031000000</Binary> </EventData> </Event> I also just found the same to be true for the RPC client access service, but not on the same server: Log Name: System Source: Service Control Manager Date: 4/25/2011 10:42:01 PM Event ID: 7036 Task Category: None Level: Information Keywords: Classic User: N/A Computer: yyynameyyy Description: The Microsoft Exchange RPC Client Access service entered the stopped state. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" /> <EventID Qualifiers="16384">7036</EventID> <Version>0</Version> <Level>4</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8080000000000000</Keywords> <TimeCreated SystemTime="2011-04-26T02:42:01.388409900Z" /> <EventRecordID>121959</EventRecordID> <Correlation /> <Execution ProcessID="480" ThreadID="5328" /> <Channel>System</Channel> <Computer>yyynameyyy</Computer> <Security /> </System> <EventData> <Data Name="param1">Microsoft Exchange RPC Client Access</Data> <Data Name="param2">stopped</Data> <Binary>4D005300450078006300680061006E00670065005200500043002F0031000000</Binary> </EventData> </Event> cdue

Have same problem: Exchnage 2010 sp1 RU3v3+Forefront for Exchnage version 11.0.713.0 1)Incresed ServicesPipeTimeout to 120 seconds - no luck 2) Open MS Support ticket - 2 weeeks -no result Someone may be have any idias?

Was there any final answers to this question? We are seeing ours is running for a couple of hours then it stops for some reason.

I am having the same issue, albeit with SBS 2011. Forms based auth, AND RPC client server both display this behavior. Help!

I'm also having this same issue with SBS 2011. Brand new install; just migrated from SBS 2003. What gives?

Still no fix in our environment yet MS PSS is still working the case.

Here it is June 15th and I still don't see a solution to this. I've just migrated to SBS2011 from SBS2003 and have the problem the the MS Forms-Based Authentication does not start. I've had to resort to manually restarting it after a server reboot. Anyone else had any luck solving this?

We put our to a delay automatic startup type in the service and that worked for us.

Sabo_e: I have done that too and I find no improvement in our environment from this step only... Now what I have seen is that when the Exchange Server starts after a reboot, the network doesnt always get ready in a timely fashion and this disrupts the startup of several Exchange services. This is a timing issue that can also relate to your network driver and negitation of speed etc, but also access to Domain conrtollers using DNS. Everytime there is an issue as such, I believe there is an impacting issue, even service. You might want to manually set the speed/duplex of your NIC (if available/the one used for DNS/AD access) to eliminate any time it could take for this to be established. Another issue seen on AD serveral times is that when LSASS is exchausted on a DC, it still responds as if it is available. If this happens, Exchange services fails to start. RPC and FBA in particular > reboot DC :) The reason I say Service is that recently, during a power outage, FPE 2010 failed and was reinstalled. When the server came back up the first time, it seeked to updated engines/patterns and the FBA Service failed to start. a restart after all engines etc was updated solved this situation. In other words, I dont believ there is a problem with the FBA...cd..

Microsoft has a fixit for this: KB940845

Not sure about OP (jeremyb1), but I'm not running Global Catalog services on any of my Ex 2010 servers. The hotfix doesn't apply to me. I've had success by setting Exchange Forms-Based Authentication service's startup type to automatic (delayed start).

Not related to this thread I presume. The delayed start seesm to be working: the netlogon sometimes comes back slow in the enviornment I have had this issue in and setting the AD Toplogy service to Automatic (Delayed) helps out the issue where this service (AD topology) starts before netlogon is ready, resulting in this services keeps retrying the health check every 15 minutes. Sort of a similar issue and I can not rule out this is not part of the issue. cd..

I made the MSExchangeFBA service dependent upon W3SVC, which seemed to solve the problem.

Hi, Check the NIC driver version and update drivers to latest and then set the “Microsoft Forms Based Authentication” services to automatic mode to delay start Cheer, Uditha

Delayed Start for both the Exchange Forms Based & RPC Client services worked for me as well on an SBS 2011 install. Bloody annoying things like this on supposedly current releases that you expect to work :out of the box".

Hi Rock, Have you got any update from Microsoft on this? Is your issue resolved? What was the fix?