Error 1053 Terminal Services
Contents |
360 games PC games remote desktop services error 1053 Windows games Windows phone games Entertainment All Entertainment cannot start terminal services xp Movies & TV Music Business & Education Business Students & educators error 1053 starting service windows 7 Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet
Error 1053 Starting Service Server 2008
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 Lumia All error 1053 the service timely fashion 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
2, 2005. Keith Guest I have this exact problem...however, am unable to fix. I want to start TS in Remote Admin mode on Windows 2k Advanced SP4. I have removed and error 1053 the service did not respond to the start re-installed the service and it did not help. ANy ideas? Error Message: Could
Error 1053 Windows Service C#
Not Start the Terminal Services Service on Local Computer Article ID : 222146 Last Review : November 13, 2003 Revision :
Error 1053 Windows Server 2008 R2
2.0 This article was previously published under Q222146 On this page SYMPTOMS CAUSE RESOLUTION STATUS SYMPTOMS When you start the Terminal Services service from the Computer Management snap-in, you may receive the following error https://support.microsoft.com/en-us/kb/222146 message: Could not start the Terminal Services service on Local Computer. Error 1053: The service did not respond to the start or control request in a timely fashion. The device continuously shows a status of Starting. When this symptom occurs, the following event description is logged in Event Viewer: The Terminal Services service hung on starting. CAUSE This behavior can occur if the Terminal Services component is not http://www.pcreview.co.uk/threads/error-1053-service-will-not-start.1610945/ installed or is disabled. RESOLUTION Add the Terminal Services component by using the Add/Remove Programs tool in Control Panel before attempting to start the service. STATUS This behavior is by design. .. Keith, Mar 2, 2005 #1 Advertisements Show Ignored Content Want to reply to this thread or ask your own question? It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum. Sign Up Now! Similar Threads Applying Office 2003 service pack not working Chris Elson, Jul 18, 2003, in forum: Microsoft Windows 2000 Terminal Server Application Replies: 1 Views: 673 Colin M. McGroarty Jul 18, 2003 Terminal Service Licensing Terminates Error Event ID 7024 mnoriega, Nov 15, 2003, in forum: Microsoft Windows 2000 Terminal Server Application Replies: 1 Views: 1,152 Vera Noest [MVP] Nov 15, 2003 Terminal Service error 1017 dabt, Dec 29, 2003, in forum: Microsoft Windows 2000 Terminal Server Application Replies: 1 Views: 558 response Dec 30, 2003 Terminal Server Spooler service crashes sometime with Error 12: The access code Lonnie, May 6, 2004, in forum: Microsoft Windows 2000 Terminal Server Application Replies: 0 Views:
General Discussions View all Getting Started with the Community Community News Get Connected Business Strategy & Best Practices Suggestions for this Community Technical Discussions View all Announcements Visualization Gallery Tech Corner https://community.microstrategy.com/t5/Miscellaneous/TN31838-quot-Error-1053-The-service-did-not-respond-to-the-start/ta-p/182733 Idea Exchange Platform (Installation & Deployment) Object Development Reporting, Dashboards, and Document Development MicroStrategy Desktop Clients (Interfaces & Visualizations) Administration Tools Intelligence Server Mobile Enterprise Assets (Data Sources & Gateways) MicroStrategy Software Development Kit (SDK) Security (Usher) Performance Events View all Events Blog Symposia 2016 Symposia 2015 Education World 2016 Discussions World 2015 Discussions World 2015 Track Sessions & Customer Presentations Community Menu Register · error 1053 Sign In · Help Miscellaneous MicroStrategy > Miscellaneous > TN31838: "Error 1053: The service did not respond to the start or control request in a timely fashion" error message app... CommunityCategoryKnowledge BaseUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. TN31838: "Error 1053: The error 1053 starting service did not respond to the start or control request in a timely fashion" error message appears when starting Distribution Manager service in MicroStrategy Narrowcast 8.1.x and 9.0.0 Started 12-10-2009 by Kun Modified 09-29-2015 by ekanamala Article Options Article History Subscribe to RSS Feed Mark as New Mark as Read Bookmark Subscribe Email to a Friend Printer Friendly Page Report Content 0 Likes SYMPTOM: When MicroStrategy Narrowcast 8.1.xand 9.0.0 is running on Microsoft Windows Server 2003, and users connect to the server machine by Microsoft Windows Terminal Services or Remote Desktop Connection, Distribution Manager service cannot be started, as shown below: Could not start the MicroStrategy Distribution Manager service on Local Computer. Error 1053: The service did not respond to the start or control request in a timely fashion. CAUSE: There are many causes related to this issue. One of the reason is related to Remote Desktop connection configuration. When using Microsoft Windows Terminal Services or Remote Desktop on Microsoft Windows Server 2003, the user is connected by a virtual session. Some changes to MicroStrategy products done through a virtual session may not be applied when that