Dameware The Remote Support Service Is Stopped

[Yazmín Bohon]

Inmy case, it worked after closing the Services window and verifying that the service had no processes open. Check if the Services.msc window is open. If so, close it. Then check the Task Manager to see if the service in question has any processes running. If so, kill them by right clicking on each one and choosing "End Task" from the context menu.

Closing the services console as suggested by a few of the answers here did allow me to remove the service. In my scenario this was only a short term fix since all subsequent reinstalls and removal of the service would require me to take these additional steps. Reviewing my web.config file, it was discovered that there was an error that once fixed, allowed me to easily remove the service without the additional closing of the services console step.

That means the service is still listed as disabled in services.msc.Just close the services.msc and re open as administrator...The service will not be listed. Now, install the service using the command,

Discovered one more thing to check - look in Task manager - if other users are connected to this box, even if they are 'disconnected' you have to actually sign them out to get the service to finally delete.

While on Windows 7 it just spawns another process, it is now checking whether the service process is still around and may return ERROR_SERVICE_MARKED_FOR_DELETE (1072) for any subsequent call to CreateService/DeleteService even if the service appears to be stopped.

The reason a service process is still around after it already has reported its SERVICE_STOPPED state isn't surprising. It's a regular process, whose main thread is 'stuck' in its call to the StartServiceCtrlDispatcher API, so it first reacts to a stop control action, but then has to execute its remaining code sequence.

It's kind of unfortunate the SCM/OS isn't handling this properly for us.A programmatic solution is kinda simple and accurate: obtain the service executable's process handle before stopping the service, then wait for this handle to become signaled.

This is what worked for me:- I hit the same issue: my service was stuck in 'marked for deletion'.- I opened services.msc My service did show up as running, although it was already uninstalled.- I clicked Stop Received an error message, saying the service is not in a state to receive control messages. Nevertheless, the service was stopped.- Closed services.msc.- Reopened services.msc. - The service was gone (no longer showing in the list of services).

In my case, the service name was 'Monitor' which is also used by a windows service called 'Monitor', when I tried to update my services, I tried uninstalling them, the installer tried to remove the windows service 'Monitor' which it couldn't, and the installation was always rolled back.

The main reason for the error is the process is not stopped.to resolve it start task manager go to services and see if you are still able to see your service than go to the process of that service and end process. Than the issue will be solved completely.

I was having this issue when I was using Application Verifier to verify my win service. Even after I closed App Ver my service was blocked from deletion. Only removing the service from App Ver resolved the issue and service was deleted right away. Looks like some process still using your service after you tried to delete one.

Sometimes this could happen during service deletion via PowerShell remote session script, especially when you are trying to delete service several times. In this case, try to recreate a session before the deletion:

2. I've installed DWMRCS Agent v7.5.6.0 on the remote pc of one of my customers windows XP Pro 32 bit SP3. Please note that after Installing the Agent I've rebooted the pc. I've installed the Agent after having logged in as Administrator.

If there are errors with SFT (or any other feature) there should be 1 or more dwmrcs entries in the Application Event log on the remote machine. Please copy and paste the full text of each of those entries and send this information to our support team at Sup...@dameware.com so we can review it. Please also send another screen shot of the exact error that's displayed when you try to open the SFT drop window on the remote machine (Shift + blue folder).

One more thing you might want to try is to update the MRC Client Agent service on the remote machine once you get connected, in case there is some type of file corruption. Make your MRC connection, then select File / Update Client Agent from the MRC main menu. Then try your SFT again.

We are still using the DameWare RS 9.0V where I work and I had to reload DameWare on to my system the other day. When I loaded DMRS onto my system I received a "SolarWinds.MRC.Licensor has stoppped working" error. When I click on the "Close the program", the entire program closes. What is the fix for this error?

I use DRS 9 over a VPN connection. Occasionally, my VPN connection drops out and (obviously) I lose my access to the Remote sessions (RDP View) I have open on a number of servers. However, after the VPN automatically reconnects, so will the remote sessions but they ALWAYS reconnect with 256 colours rather than the 15bit colour I have configured and which they were using before I lost the sessions. To get 15bit colour back I have to manually disconnect and reconnect, logging back in as I would normally.

In Dameware 10 mini remote control when starting i want to give in a pcnumber, when i type the first letter in the connect field a new popup displays and there i can give in the pc number to connect, when done that the screen is goiing back to the first when starting Mini Remote Control.

I have a problem with DameWare Remote Support v9, I am unable to connect using the DameWare Mini Remote Control when the "Permission Required" setting is enabled on the "Additional Settings" tab within the settings of the MRC Client Agent Service on the remote machine. When enabled, this option should prompt the currently logged on user to grant or deny permission for every connection attempt.

When I disable "Permission Required" setting on the remote machine I can establish the connection from my local machine without any problem but also without asking for permission the currently logged user.

Currently evaluating Dameware DRS 11.0.0.1003 for our environment. In past employments I have relied heavily on Dameware for my Team's support operations. I was hoping to employ this tool here in my current role, but I have come across something that may be a deal breaker. The majority(about 2/3) of our staff here use WYSE terminals and login to a session on our Terminal Servers (WIndows 2008 R2). We have been connecting via RDC to the Terminal Server, login then using the TS Admin Tools launch a remote session to the Staff member. I was hoping to use Dameware DRS to actively connected to the session directly. Does anyone know if this is possible and if so how?

When our IT remotes to our Windows PCs they leave behind the DameWare Development Mirror Driver. This driver causes problems with at least one software application, and so it needs to be removed after the remote IT session is ended. How can this be automated?

I have software I can run, until I connect to the computer using DameWare. Once the DameWare Mirror Driver is installed, the software wants to use that driver (it shows up as a device) instead of the driver it's supposed to be using. If I disable the DameWare Mirror Driver, my software works normally again.

Does anyone know if there's a work-around? Can the DameWare service be told to remove or disable the driver when a computer isn't using it? Is there a registry hack that will force Windows to tell every program (except DameWare) to use the default driver?

5. I will be the only person allowed to use Dameware, so we purchased 1 license and a years support and upgrades...

Is this sufficient for me to run about 100 machines in various locations, as long as I'm the only one accessing them from my machine?

Until recently, DRS has been working great. Then I applied the November update to Windows 10 and no the Microsoft Windows Network no longer displays anything in DRS. I am using version 12 with both hot patches applied. Other than applying the update nothing had changed in our environment. I can still find computers through the Active Directory, but it isn't nearly as convenient. It is particularly troublesome to find the few computers that are not part of the domain.

We recently replaced our domain controller which was running Windows server 2003 and replaced it with Windows Server 2012 at one site. After that change, I noticed that all the workstations from that site, Damware does not show as active. However, If I select one that I know its online, I am able to remote in with no problem with Dameware including RDP. I do noticed after 15 or 20 minutes, Dameware starts to show that group of PCs as a blue icon instead of the green icons at least for those pc that are on the network. It feels like its a browsing issue because when I click on Network, it does not show those computer in which they are on the network.

Two issues - I had DRS installed on my Windows 7 Pro workstation, but was experiencing some unexplained weirdness, so thought that I'd remove and reinstall just to rule that out. I can't get it reinstalled - keep getting the message "There is a problem with this Windows Installer Package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.".

I've also tried installing on a difference Windows 7 Pro machine, and on this computer, the installation starts but just hangs. I can see two DRS10... processes running in task manager, but they never do anything.

3a8082e126