Help!! Timeout (30000 milliseconds) waiting for a transaction response from the Windows SteadyState service
I have read the postings on this error, and there does not appear to be a good resolution. I have reinstalled Windows Steady State, and I have left all of the dependencies as-is, as Microsoft recommends.I am logged in as an administrator. The steady state service starts, then within 1 minute, I get that message: Timeout (30000 milliseconds) waiting for a transaction response from the Windows SteadyState serviceThe service depends on RPC and WMI, both of which are started. There are no listed depends on steady state. I really would like to use this tool, but the 30+ second delay in boot is very frustrating.Can someone please help me solve the problem?Thanks.
February 10th, 2009 6:49am
Hi JApple KC, I hope you have checked the following thread: Timeout during windows logon http://social.microsoft.com/forums/en-US/windowssteadystate/thread/f161202c-42a4-4951-b7fc-79c52ba2140b/ If the issue still occurs, you can temporarily remove Windows SteadyState and perform a Clean Boot, then install it again: Clean Boot=========== 1. Click Start, go to run, type "MSCONFIG" (without the quotations) and Press "Enter" to start the System Configuration Utility. Note: Please click Continue if the "User Account Control" window pops up. 2. Click the "Services" tab, check the "Hide All Microsoft Services" box and click "Disable All" (if it is not gray). 3. Click the "Startup" tab, click "Disable All" and click "OK". 4. Restart the computer and test the issue. Note: Clean Boot is a troubleshooting step. If some programs have been disabled, we can re-enable them later. If you see the System Configuration Utility, check the box of "Don't show this message" and then click "OK". Please test this issue in the Clean Boot environment. If the issue disappears, we can use a 50/50 approach to quickly narrow down which entry is causing the issue. Hope this helps!Sean Zhu - MSFT
February 12th, 2009 11:15am
Sean, I checked that thread before I submitted one of my own. However, it basically said not to mess with the installation of steady state, nor change its dependencies. I'm not reading directly in that article that tells me the potential fix, other than adding new dependencies to that steady state service, other than the 2 I listed on this thread.I would like to leave it as an automatic start up service. In your view, if I manually add the dependencies listed in that thread, should that most likely take care of my problem? If so, I'd be pretty happy because I like the tool, and it's a great help.Thank you.
February 12th, 2009 8:15pm
Thank you for the update. I suggest you try the suggestions in the thread except changing start up type. As we have not successfully repro the error message on our computers, you can try the solution and let us know the result. Thank you for using this product, we will still strive to improve it. Sean Zhu - MSFT
February 13th, 2009 6:42am
Sean, I spent the last 30 or so minutes trying everything in that solution. The basis of that solution is adding a dependongroup, and I also received the same error the gentlemen you gave it to had, "But no member of this group has been started"I also tried the clean boot. It seems like there may be a service start ordering issue, if we're talking about dependencies on WMI and RPC, plus a group depends on wscsvc. Is there a way I can impact this?? The wscsvc dependencies, when manually added as you suggested for the group depends, do not show up on the service dependencies, but I'm not sure if I should see them there. I also noticed the path for the actual wscsvc is thru the svchost exe with some command line args.Anything else I might try without having to pick each service apart? Thanks for your time and patience.
February 13th, 2009 7:43am
Try the solution set forth here. It involves turning on Terminal Services. It immediately and permanently resolved that problem for me.Hope that helps.
February 16th, 2010 5:29pm
I realize this post has been dormant for over a year, but I read a ton of posts related to this "Timeout (30000 milliseconds) waiting for a transaction response from the Windows SteadyState service" log in my event viewer. I also noticed that my Terminal Service would start after the SteadyState timeout error message in my event viewer. I discovered that SteadyState is not programmed correctly and it is indeed dependent on the Teminal Services service from my testing. I found this MS Support article http://support.microsoft.com/kb/193888 that explains how to add dependencies to any service. So I added the Terminal Services service as a dependency to the Windows SteadyState Service and viola....the timeout error disappeared and my account did not hang at login.
February 25th, 2011 9:21am