Could Not Start Network Connections Service Local Computer Error 193
Contents |
we highly recommend that you visit our Guide for New Members. error 0xc1 Discussion in 'Windows XP' started by jonathan731, May 18, 2004. Thread Status: Not open for further replies. Advertisement jonathan731 Thread Starter Joined: error 193 0xc1 when start a windows services Aug 29, 2003 Messages: 425 My pc can not connect to the internet b/c the Remote
Error 193 0xc1 Windows 7
Access Connection Manager is stopped. When i try to start the service i get an error saying " Could not start the Remote Access
Error 193 0xc1 Windows Update
Connection Manager service on local computer error 193: 0xc1" Does anyone know what this is. I dont know if this has anything to do the problem but when i start my pc the task manager shows "userinit.exe" and dwwin.exe" running on my pc and they dissapear quickly. thanxz for any help jonathan731, May 18, 2004 #1 Sponsor JesuSlaveX Joined: Jul 4, 2003 Messages: 90 dwwin.exe is Doctor Watson (never heard of it? Dont feel bad, its useless) userinit.exe is an Application used to run a program before a shell starts. The service runs logon scripts, reestablishes network connections and starts the shell Dr. Watson is a software utility included with Microsoft Windows that is used to help detect, decode and log errors that are encountered while windows or windows programs are running From the looks of waht your describing, try this START->RUN sfc/ scannow (notice the space in between / and scannow) See if that will fix ya up JesuSlaveX, May 18, 2004 #2 JesuSlaveX Joined: Jul 4, 2003 Messages: 90 MY BAD!!!! ITs sfc /scannow Put the space in the wrong spotty Sorry JesuSlaveX, May 18, 2004 #3 jonathan731 Thread Starter Joined: Aug 29, 2003 Messages: 425 If that doesnt work what else can i do? jonathan731, May 19, 2004 #4 jonathan731 Thread Starter Joined: Aug 29, 2003 Messages: 425 that didnt work b/c it asks for the winXP proffessional CD and i dont have that CD. IS there anything else i can do? jonathan731, May 21, 2004 #5 jonathan731 Thread Starter Joined: Aug 29, 2003 Messages: 425 help!!!! PLEASE???!!!! jonathan731, May 23, 2004 #6 fat_arse_phil Joined: Oct 20, 2006 Messages: 1 i know how to help you. i had the same problem with that damn error as well as many other .dll errors. i followed the instructions of JesuSlaveX and was asked to put in an XP Pro disc before i could continue, even though in running xp home on my computer. after i had put the xp home disc in i pressed the retry and the continued pressing it. the pro
SQL Server 2014 Express resources Windows Server 2012 resources Programs MSDN subscriptions Overview Benefits Administrators Students Microsoft Imagine Microsoft Student Partners ISV Startups TechRewards Events Community Magazine Forums Blogs Channel 9 Documentation APIs and reference Dev centers Retired content Samples We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: could not start service .NET Framework > .NET Framework Class Libraries Question 0 Sign in to vote Hi, https://forums.techguy.org/threads/error-0xc1.230455/ I am trying to run a .NET service I installed and I get the error could not start service servicename on local computer. Error 193:0xc1. I have unistalled and reinstalled the service but to no avail. What could be the problem thanks in advance Wednesday, March 28, 2007 11:00 AM Reply | Quote Answers 0 Sign in to vote https://social.msdn.microsoft.com/Forums/en-US/6b336241-2cfa-4160-b570-9429ee66f763/could-not-start-service?forum=netfxbcl See this link - http://support.microsoft.com/default.aspx?scid=kb;en-us;Q325680 Apparently, this might be due to having a file named "program", "common" (or some of the others) on your system drive. Andrej Wednesday, March 28, 2007 3:44 PM Reply | Quote All replies 0 Sign in to vote Hi, If you're the developer of this service, try putting some exception handling into your OnStart method and write any exception message to event log or txt file. You could also try debugging this service by ataching a debugger to it, but you'll have to insert some timeout into your OnStart method, which would allow you to do this quickly enough. Andrej Wednesday, March 28, 2007 3:10 PM Reply | Quote 0 Sign in to vote I need to fix this on a production machine on which I cannot debug. Is this a bug or is the registry corrupt, How can I get my service running again thanks Wednesday, March 28, 2007 3:34 PM Reply | Quote 0 Sign in to vote See this link - http://support.microsoft.com/default.aspx?scid=kb;en-us;Q325680 Apparently, this might be due to having a file named "p
error message that I've never seen before when I tried to start the service: Could not https://corengen.wordpress.com/2009/11/23/could-not-start-the-service-on-local-computer-error-193-0xc1/ start the Vitality PASMDI Service service on Local Computer Error 193: 0cx1 I http://www.pcreview.co.uk/threads/error-193-0xc1-when-windows-services-try-to-start.1223802/ knew the service worked as I'd been running it on my development PC. I'd also successfully started the service after installing an earlier version of the installer so why wouldn't the service start after installing using the latest version of the installer ? The last change that I'd made to error 193 the installer was to add an XML data file that the service loads when it starts. I reviewed the WiX source code and realised that I'd added the new file incorrectly. The WiX ServiceInstall element is associated with the first File element in a component or with the File element that specifies KeyPath="yes". I was using the ‘first File element in error 193 0xc1 the component' method but had added the new file as the first File element in the component and so had inadvertantly replaced the association of the ServiceInstall element and the Windows Service executable with an association to the XML data file. I confirmed this by checking the service properties in the Services console. As expected, the ‘Path to executable' value was the path for the XML data file and not the service excutable. The problem was resolved by moving the File element for the new file so that the first File element in the component was the one for the service executable. The point is, the inscrutable "Error 193: 0cx1" error message simply indicates that the file that the service definition references is not an executable. Like this:Like Loading... Related Written by Sea Monkey November 23, 2009 at 8:00 am Posted in Deployment Tagged with Deployment « It's only human to makemistakes Reading values in an XML configuration file from a batchfile. » Leave a Reply Cancel reply Enter your comment here... Fill in your details below or click an icon to log
Hi, I am having problem trying to install and start a Windows Services. I build the exe using Visual Studio 2003 (framework 1.1). I can install it using installutil, no problem there. But when I tried to add a new setup and deployment project which created a msi to install the exe as a Windows Services. It installed fine, but whenever I tried to start the service, I receive 'Could not start the service on Local Computer. Error 193: 0xc1' (net start displays ' *** is not a valid Win32 application.') In VS.Net, I added a 'Custom Actions' to Install/Commit/Rollback/Uninstall the service but haven't change any other properties. Am I missing some steps? It is a W2k3 box. Thanks in advance. daniel, Aug 31, 2003 #1 Advertisements Yan-Hong Huang[MSFT] Guest Hello Daniel, Thanks for posting in the group. Please do the following so that we can determine what the problem maybe: 1. What is the exact name and directory location of the service.exe file on the Win2003 machine? 2. In that directory holding the exe, is there another subdirectory that has a similar name to the exe? 3. What is the registry key value at this location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MyNewService\ImagePath = ? Make sure that the value for this key is the same for the location of the exe for the windows service. Generally the error message means service manager couldn't find the exact exe path to run the service. Sometimes, the service is installed from a directory with multiple words for the directory name. So the registry patrh to the service needs to be placed with double quotes. I also suggest you test it on another machine to see if the problem is machine specific. You could also use a tool named FileMon file www.sysinternals.com to see which file is accessed by service.exe. In this way, you may see which step is failed when starting service. Hope that helps. This response contains a reference to a third-party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to ma