Could Not Start Terminal Services Error 1053
Contents |
One games Xbox 360 games PC error 1053 the service did not respond to the start or control request in a timely fashion games Windows games Windows phone games Entertainment All error 1053 windows server 2012 Entertainment Movies & TV Music Business & Education Business Students &
Error 1053 Windows Server 2008
educators Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security
Error 1053 Windows Server 2003
Internet Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Band Microsoft error 1053 windows server 2012 r2 Lumia All Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
or pause a service Modified on: Tue, 26 Apr, 2016 at 12:13 PM PROBLEM When attempting to start, stop or pause a
Error 1053 Windows 10
service, one of the following error messages is encountered: "Error 1053: the service did not respond in a timely fashion windows 7 The service did not respond to the start or control request in a timely fashion.""Error 7000: windows service 1053 error during startup The
Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full https://www.experts-exchange.com/questions/24360418/Cannot-Start-Terminal-Services-Service-on-Windows-2003-Server-In-Place-Upgrade-from-2000.html Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Cannot https://community.spiceworks.com/topic/340905-unable-to-start-the-services-in-windows-server-2003-error-1053 Start Terminal Services Service on Windows 2003 Server (In Place Upgrade from 2000) Want to Advertise Here? Solved Cannot Start Terminal Services Service on Windows 2003 Server (In Place Upgrade from 2000) error 1053 Posted on 2009-04-27 MS Server OS Windows Server 2003 2 Verified Solutions 10 Comments 1,288 Views Last Modified: 2013-12-05 After performing an inplace upgrade from Windows 2000 to Windows 2003 R2, I cannot RDP to the server. I believe it is being caused by the Terminal Services service being stopped. When I try to start it up, I get the following error: Could not start error 1053 windows the Terminal Services service on Local Computer Error 1053: The service did not respond to the start or control request in a timely fashion 0 Question by:fmdb Facebook Twitter LinkedIn Google Best Solution byfmdb I resolved the issue by booting from the Windows 2003 Server CD and then performing a Repair Installation on top of itself. This fixed the problem. Go to Solution 10 Comments LVL 13 Overall: Level 13 Windows Server 2003 10 MS Server OS 5 Message Expert Comment by:rhinoceros2009-04-27 This behavior can occur if the Terminal Services component is not installed or is disabled... More info http://support.microsoft.com/default.aspx?scid=kb;en-us;222146 0 LVL 11 Overall: Level 11 Windows Server 2003 8 MS Server OS 4 Message Expert Comment by:Abhay Pujari2009-04-28 This issue may be because your 2000 Server is not a terminal server. Try above suggestion. If it does not help, then revert back here. 0 Message Author Comment by:fmdb2009-04-28 It was a Windows 2000 Server but we performed an in-place upgrade. I tried installing Terminal Services but that didn't work. I have since uninstalled it. There are a few other cases like this that I found on the Int
Chris (Microsoft) Technical Consultant/SI GROUP SPONSORED BY MICROSOFT IN THIS DISCUSSION Windows Server 2012 74584 Followers Follow Join the Community! Creating your account only takes a few minutes. Join Now Dear all, In my Additional Domain Controller (ADC), windows server 2003 sp2, I got an RPC service error while trying to connect/access shared folders/RDP and I was restarted the Remote Procedure Call(RPC) service as domain/administrator previously it was running as Networkservices. After performing this I was not able to restart the any services and not able to access shared folders and not able to take RDP. and system got very slow. I tried many times by rebooting the server but no use. I am getting 1053 error(The service did not respond to the start or control request in a timely fashion. Kindly help to resolve this issue. Thanks & Regards, Venkat Reply Subscribe RELATED TOPICS: windows server 2003 start up error DFS Windows Server 2003 => 2012 There will be stragglers after the Windows Server 2003 end of life – here's why   5 Replies Datil OP HenrikBryne May 27, 2013 at 12:32 UTC You would have to provide some more info on this - event logs errors and so on.. 0 Pure Capsaicin OP peter May 27, 2013 at 2:55 UTC Petes PC Repairs is an IT service provider. check it is fully patched and updated reboot then check the services if still in error state the export the logs and take a look there for clues as to whats causing it 0 Chipotle OP techie007 May 27, 2013 at 4:52 UTC the RCP service is supposed to be running as NetwrokService. Why'd you decide to change it? If you change it back, do things run properly (or at least the way they were before you changed it)? 1 Tabasco OP Mark Wormald May 27, 2013 at 5:59 UTC Unless you need to change one of the 'system' services to install a specific application or to comply with a particular security configuration, it is best to leave these services running with their default settings The RPC service is supposed to be accessible across the network that is why the Network Service account is used Running Services as Domain Administrator causes all sorts of issues, particularly when you need to change the account password I hope this helps... 0 Sonora OP Vemala May 28, 2013 at 4:31 UTC Hi All, Thanks for your valuable replies.. I am able to connect to share folders after restarting rpc service as networkservices from registry edit. But Iam not able to t