Cannot start service on computer ‘.’

I’m trying to create and start a windows service using PowerShell.

The service is created but cannot be started when I use various names besides one particular name.

When I create the service with the name of the exe file it can be started but when I give it a different name it fails to start.

I’m running the PowerShell script as administrator.

The Error I get: Start-Service : Service ‘Service1 (Service1)’ cannot be started due to the following error: Cannot start service Service1 on computer ‘.’.

When I try to start it manually I get: «Error 1053: The service did not respond to the start or control request in a timely fashion»

3 Answers 3

The problem is that, unless your service is written to handle it, you need to use a particular service name in order to run a particular service (and note that the name is case-sensitive). This is because the service, on startup, needs to register with the Service Control Manager to receive start/stop notifications and send status updates, using its service name. If you install the service with a different name, but the executable has no way of knowing this (through a configuration setting or whatnot), this registration will fail and the service can’t start (to the operating system, it will look as if the service is failing to respond).

You can set the display name to whatever you like, but you cannot use an arbitrary service name unless the service is designed to support this.

Cannot start Windows process activation service on Windows 10

After upgrading from Windows 7 Pro x64 to Windows 10 Pro x64, I cannot start IIS. Most of the Windows 10 system works fine. Some study tells me that the primary problem is that the Windows Process Activation Service (WAS) will not start.

I have another machine that upgraded to Windows 10 with IIS fine (Windows 7 Home Premium x64 up to Windows 10 Home Premium x64). The IIS on that machine works OK (it only serves one website; so simpler setup.)

• I have had NO LUCK finding anything on the Internet that resolves this.
• I tried using the clean.iinstall IIS config files (no improvement).
• I tried uninstalling IIS — uninstall failed and rolled back (see below).
• I tried uninstalling WAS — uninstall failed, and rolled back.

My first error trying to run IIS Manager program:

(The link to see the IIS 7.0 compatibility information was a dead link.)

I decided to give it a try despite the compatibility warning. I started the services IIS, MSFTP, WAS and W3SVC (depends on WAS), then tried to start IIS Manager.

The IIS configuration files exist with non-zero length; they look coherent.

I have a backup that I made that should be good (not just the automatic backups).

machine.config exists ok: C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config\machine.config

The appPools folder exists: C:\inetpub\temp\appPools

The upgrade changed IIS from v7.5 to v10.0.10240.16384

This machine has one user account (me) and the account is marked Administrator.

My previous Windows 7 Pro with IIS 7.5 worked FINE for several years. IIS was giving no trouble before the upgrade.

I can use other network stuff OK: Internet, Outlook, PuTTY, MySQL Workbench (remote & local), and FileZilla.

Trying to start the Microsoft FTP service, or run appcmd or start W3SVC or WAS all give the same error: Error 183: Cannot create a file when that file already exists.

appcmd list backup —> failed (running as Admin) ERROR ( hresult:800700b7, message:Command execution failed. Cannot create a file when that file already exists.)

Event Log after error starting WAS: The configuration manager for Windows Process Activation Service (WAS) did not initialize. The data field contains the error number. error # = B7000780

I used the MS error lookup tool:

To see the appcmd error ( 800700b7)

for hex 0x800700b7 / decimal -2147024713 :

FIX: Windows Process Activation Service (WAS) does not start when you use the IISRESET /RESTART command to restart IIS 7.0 or IIS 7.5

Not sure if this is the right fix? We’ve added this issue to our memory dump diagnostic which can confirm.

Symptoms

Consider the following scenario:

You have Internet Information Services (IIS) 7.0 installed on a computer that is running Windows Vista or Windows Server 2008.Or, you have IIS 7.5 installed on a computer that is running Windows 7 or Windows Server 2008 R2.

You restart IIS by using the IIRESET /RESTART command.

In this scenario, IIS World Wide Web Publishing Service (W3SVC) does not start. Additionally, the following events are logged in the application event log:

Cause

After IIS 7.0 or IIS 7.5 starts, Windows Process Activation Service (WAS) calls the LookupAccountName function to resolve account names on the local system. If no name is succesfully resolved, the LookupAccountName function tries to resolve account names by using domain controllers (DCs) trusted by the local system. Depending on the configuration of the DCs, the LookupAccountName query may take more than 30 seconds to be completed. In this situation, it takes a long time to start WAS. Additionally, W3SVC does not start because W3SVC depends on WAS.

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a «Hotfix download available» section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=supportNote The «Hotfix download available» form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have IIS 7.0 or IIS 7.5 installed on a computer that is running one of the following operating systems.

Windows Search service not starting with Windows Search service on local computer started and then stopped error

This article provides a resolution to solve the error that occurs when you try to start the Windows Search Service.

Original product version: В Windows 10 — all editions
Original KB number: В 2484025

Symptoms

Windows Search service doesn’t start and when you try to start the service manually, you receive this error message:

========
Services
========
«The Windows Search service on local computer started and then stopped. Some services stop automatically if they are not in use by other services or programs»
===
OK
===

Cause

You may see this issue if there are missing subkeys or registry entries under the following registry location:

Or if there are corrupted log files at the following location:

The above regisrty key is unique to each machine, so should not be replaced manually.

Resolution

To resolve this issue, delete all files with .BLF and .REGTRANS-MS extension in the following directory:

The files in the folder location above are hidden and will thus not be visible unless you set the system to not Hide Protected Operating System Files under Tools > Folder Options.

Once these files are deleted, reboot the machine. Once rebooted, observe that the Windows Search service has already started and is in process of rebuilding the Index.

You may observe High CPU while the Search Index is being rebuilt.

Windows service cannot start process

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

Answers

Do you mean you cannot start service from the command line?

Like following cmd,

Using net stop [service name] to stop it and net start [service name] to start it up again basically restarting the service.

If so, you should make sure you have done the thing correctly. If tha’t not what you want, please be more specific about what you are trying to do and feel free to let me know.

Firstly you should make sure your service code is working fine.

Secondly, if you are win7 or win8 os,

1. On the Windows Start menu or Start screen, choose Visual Studio , Visual Studio Tools , Developer Command Prompt .
2. A Visual Studio command prompt appears.
3. Run InstallUtil.exe from the command prompt with your project’s output as a parameter:

Here is my screenshot,

We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click HERE to participate the survey.