Error 193 Oxc1
Contents |
services, the following error message is received: Could not start the %{Service} service on local computer. Error 193:0xc1 Upon further investigation, the following entry is found in the Application logs in windows service error 193 Event Viewer: Event ID: 7000 Source: Service Control Manager Type: Error Description: The
Error 193 0xc1
"Online Backup Scheduler (Mindtime Pro Backup)" service failed to start due to the following error: "Online Backup Scheduler (Mindtime Pro
Error 193 Oxc1 Vista
Backup)" is not a valid Win32 application. Note: The issue can also occurs for other Windows services, such as the Online Backup Scheduler (Mindtime PC Backup) service, AutoUpdateAgent (Mindtime PC Backup) service ...
Error 193 0xc1 Wlan
etc. Cause This issue occurs when one or both of the following conditions is true: There is a file named 'Program' in your SystemDrive folder. There is a file named 'Common' in your ProgramFiles folder. When Windows Service Control Manager (Services.exe) tries to start the Server service, the program verifies the following paths: SystemDrive\Program Program Files\Common If the Program or Common paths exist as files, the error 193 0xc1 windows 7 Service Control Manager cannot locate the required folders, you will receive the error messages and event ID messages that are listed in the Problem Description section of this article. This issue can also occurs if the path of the executable file for the service contains spaces. When a service is started by Windows, the operating system first parses the path of the service from left to right. If both of the following conditions are true, Windows may locate and try to run the file or folder before it locates and runs the executable file for the service: The path of a service’s executable file contains spaces. There is a file or folder on your computer’s hard disk that has the same name as a file or folder in the path to the service's executable file. For example, if the path of the executable file for a service is 'C:\Program Files\Mindtime Pro Backup\bin\Scheduler.exe', and if a folder that is named 'C:\Program' also exists on your hard disk, Windows locates the 'C:\Program' folder on your hard disk before the 'C:\Program Files\Mindtime Pro Backup\bin\Scheduler.exe' file, and then tries to run it. For more details, please refer to the following article
be down. Please try the request again. Your cache administrator is webmaster. Generated Mon, 10 Oct 2016 17:04:57 GMT by s_ac15 (squid/3.5.20)
(4 total) 1 Change Directory to System32. Open My Computer. Open the path C:\Windows\System32. 2 Alphabetical Order Change the sort order on the https://community.spiceworks.com/how_to/85301-solved-windows-installer-service-start-error-193-0xc1 page to Alphabetical Order, and locate msiexec.exe 3 Remove the Bad File. Now look right above msiexec.exe you should see a new file called msiexec with no extension. The size http://itgroove.net/brainlitter/2008/10/09/error-193-0xc1-weird-but-solved/ of the file should also be 0kb. Delete this file. 4 Start your engines. Now open services, and start Windows Installer. It should now successfully start! Conclusion This was a error 193 tough error to get through with very little information on the web, I hope this helps someone else. 1 Comment Pimiento kaelabenoja Feb 28, 2015 at 09:44am Sir, how about for Font Cache? It also has the same error -thanks :) Read these next... Tablets, never again Hardware As far as I'm concerned, tablets are not up to the challenge error 193 0xc1 of being good business machines. Spark: UK targets internet trolls with new legislation Spiceworks Originals Your morning news, a Community wrap up, a lunch recommendation, and the funnies. How the cloud works: The advantages of Infrastructure-as-a-Service Here's what you need to know about IaaS (which totally isn't a buzzword). © Copyright 2006-2016 Spiceworks Inc. About Advertising Privacy Terms Help Sitemap × Join millions of IT pros like you Log in to Spiceworks Reset community password Agree to Terms of Service Connect with Or Sign up with your email address First Name Last Name Email Join Now or Log In Email Password Log In Forgot your password? Email Reset Password Cancel Need to recover your Spiceworks IT Desktop password? By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks. By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks. Not a member? Join the community Back I agree Powerful tools you need, all for free. Help Desk » Inventory » Mon
Error 193: 0xc1 - Weird but solved! October 9, 2008 This is an oldie but a goodie… I've reposted this as I noticed it wasn't appearing in search, but on my old blog, it was helping a significant amount of people - so I wanted to give it a new push here, in case it helps others. Ok, this one took a while to sort out and I believe people will have different results… In my case (but I don't think it was even specific to MS SQL, just the result of it, an MSDE database (MSSQLSERVER) service failed to start. After much troubleshooting and only "Error 193: 0xc1" to work with (no event logs, nothing!), I managed to figure out that it was because there was a file called ‘program' at the root of the D: (whatever drive impacts you). Not sure at this writing how it got there (no it wasn't a virus, probably just bad code by somebody or a pipe) but that file wasn't needed but the SQL Service was following that path instead of honouring the path it should have (as identified in the service path). So, I renamed the file called ‘program' to something else and voila, I was back in business. I hope this helps someone, somewhere faster than I was able to help myself 🙂 Let me know about if it helped you - heck, buy me a beer Share this:FacebookTwitterEmailLinkedInRedditPress ThisGoogleTumblrPinterestPocketPrint Related 10 Responses Jim Trainor says: January 6, 2012 at 1:15 pm This proved to be very useful in resolving a problem with Radiant Counterpoint v8.4. Located the program file (root of D:) and renamed it. Voila! Many thanks. Reply Richard Hale says: March 25, 2013 at 10:34 pm Very helpful in solving the Error 193: 0xc1 issue. Two separate 3rd party programs running under Windows 2008 Server began failing with this error. The "program" file was in the root of the C: drive. I moved it to a temp folder and the programs began working. Thanks for the tip. I am now examining the file to try and determine how and why it got there. Thanks!! Reply Jeyson Guzman says: December 31, 2013 at 8:23 am Hola, los saludo desde Colombia, tuve el mismo problema con un ISA Server 2004, pues los servicios de firewall del mismo dependen del servicio MSSQL$MSFW que no subía y daba error 193: 0xC1. Windows a su vez mostró una ventana de error diciendo que el archivo program, que en mi caso se encontraba en C: estaba corrupto bloqueando un programa, por lo tanto sugería renombrarlo a program1, luego de esto el servicio y sus dependencias subieron b