Solarwind's whole licensing procedure is terrible.  Everything was running just fine with Dameware Remote Support (which includes Dameware Mini Remote Control) until today when I received a "License Expired" popup when launching DMRC.  I tried to re-activate and  I get a "License Activation" failure whether I use the local license manager or online activation.  Our maintenance was up a couple of years ago, but we only have one client on Dameware and they are on the same version that we are on, so there is clearly no need to upgrade to version 12 since it would force them to also upgrade to version 12.  I have tried uninstalling and reinstalling the same version 11 that was available when the maintenance was in effect.  I've even tried regenerating the license file using my unique machine ID and it still fails.  Anyone have any ideas.

I have been running on Windows 10 for quite a while (since last fall) and using Dameware Remote Support (11.0.0.1003).  Recently I upgraded to the latest W10 version (1607).  Unfortunately, this broke the remote clipboard.  I have a co-worker who had the same experience.  The only difference between the two was that his mini-remote worked fine, then he upgraded to the "full-version" (as we call it).

Any ideas about how to fix this?  I would have thought a reinstall of the application, but with the fresh install that was broken that didn't seem like a solution.  Any thoughts?

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?

Thank you

Tawna

I’m thrilled to announce that Dameware 12.0 is now publicly available. In this release we focused all our efforts to finalise the remote support story with unattended over the internet sessions. Dameware now allows to assist remotely without presence of the end-user, who is not in the intranet but travelling. Technicians can now support end-user in company network as well as in Internet anytime.

This release brings several bigger and smaller improvements, so let me highlight a few of them:

• Over the Internet (OTI) unattended sessions for Dameware Centralized users
  • Allows you to remotely support users on the move, and assist remotely without the presence of the end user
  • Deploy agents with OTI unattended support to end-points
  • Manage agents for OTI unattended sessions to maintain high security and control
• Search Hosts in Mini Remote Control
• Support for Windows 10
• Ability to switch between the Standalone and Centralized versions without reinstallation
• And many other improvements and bug fixes

Dameware 12.0 is available for download on your customer portal for those customers under current maintenance.

If you are not a Dameware user yet, now go and download new version from www.dameware.com now!

I launch DNTU normally, running under my logged in ID (only localadmin on my machine). However, I do set the default security credentials to use my domainadmin account though, through the “Logon As” dialogue (using my domainadmin ID) & check the “Set as default Security Credentials” box.

With that configuration, I often get “Error: 5 - Access is denied.” When attempting to view things on the remote domain member machine (shares, service, registry, etc.). It’s strange that sometimes I can view Shares on a machine, but when I try to view Services on the same machine in the same session, it gives me the error for that.

This happens even after multiple times of clicking the “Logon As” & putting in my domainadmin credential.

However, if I launch DNTU directly under my domainadmin account (“Run as a different user”, or even logged on a different machine as my domainadmin), it can view all items on the same remote machine without any error at all. This happens at the same time (one DRS running as normal, one DRS "Run As..." my domain admin), so it’s not the remote machine being in a different state when I try either way.

Anyone know if there is any type of issue with the “Logon As” or Default Security Credential not being passed when trying to view Services, Registry, etc. ,etc.?

Note: This is a topic brought over from DameWare Forums which has been closed. If you wish to engage in this discussion, just comment here.

Unable to log onto remote machines using DameWare 5.5.0.2
by threeofspades on Thu Sep 13, 2007 5:34 am

Hi All,

We are currently having issues with logging onto some of our machines using the DameWareMini Remote Control. We recently installed some Microsoft patches on the machines and this has resulted in us having to log onto the machines using Remote Desktop rather than DameWare. Do you know of any Windows updates that may affect DameWare connection? When we try toconnect using DameWare we get the Winsock error:

Connect Error:
System Error: 10061
System Message: No connection could be made because the target machine actively refused it.

We have gone onto the DameWare help site and read through the help topics on this error but are still unable to resolve.

Any help would be greatly appreciated.

Kind regards.

Re: Unable to log onto remote machines using DameWare 5.5.0.2
by bryan on Fri Sep 14, 2007 11:13 am

Hello threeofspades,

Are you sure you're specifying the correct TCP port in your Host settings?
Is the MRC Client Agent Service already installed & running on these remote machines?
If so, have you tried stopping the Service, changing the TCP port, and then restarting the Service?

Because a Winsock 10061 error typically means the MRC Agent Service was not listening on the TCP port that you specified (default is TCP 6129). Then a subsequent attempt at interrogating the Servcie Control Manager on the remote machine failed for some reason (insufficient rights, ports blocked, file & printer sharing not enabled, etc…). This process of interrogating the Service Control manager requires the Operating System's Installed Protocols (File & Printer Sharing - UDP 137, UDP 138, TCP 139, TCP 445) to be open between the loal & remote machines, and it also requires Administrator rights within the O/S security on the remote machine.

Therefore if we cannot connect to the MRC Client Agent on the remote machine using the specified TCP port, and then we also cannot communciate with the Service Control Manager on the remtoe machine using Microsoft’s APIs, then we have no choice but to fail. Because these same ports/protocols used by Microsoft’s APIs in order to communicate with the Service Control Manager are the same ones required to install, remove, start, or stop the MRC Client Agent Service on the remote machine.

However, please also click on the Copy button on the Winsock Error Dialog, then send me this information (paste it into this email) back to me for examination. Also include a screen shot of the actual Winsock Error dialog as well so I can review it.

Your feedback is appreciated.

Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

Re: Unable to log onto remote machines using DameWare 5.5.0.2
by threeofspades on Mon Sep 17, 2007 6:19 am

Hi Bryan,

Thank you for your response.

I have some additional information that may help to try to resolve this issue.

I can use MRC on the servers themselves to connect to my own machine, but am unable toconnect from my machine to the servers using MRC.

When i try ot connect to the server using MRC i first get a message saying the following:

"The DameWare Mini Remote Control is not running on onyxctx2.

Would you like to start it now?

Host: onyxctx2".

I select OK but then get the following error:

"Unable to start Service
System Error: 2
System Message:
The system cannot find the file specified"

When I RPC'ed onto the server and checked the DameWare Mini Remote Control service is was not running. When i selected to start it i get the error:

"Could not start the DameWare Mini Remote Control service on Local Computer

Error 2: The system cannot find the file specified."

When i checked the path to the executable 'C:\WINDOWS\system32\DWRCS.EXE -service' the DWRCS.EXE was not in there.

I have tried to load DameWare again but get the same errors. It seems that this executable has been deleted for some reason. How can i retrieve it or load it again?

Thank you for your time and effort.

Kind Regards

Re: Unable to log onto remote machines using DameWare 5.5.0.2
by bryan on Mon Sep 17, 2007 10:37 am

Hi threeofspades,

You're welcome and thank you for this additional information. It was very helpful...  

As you have already found, Microsoft's System Error: 2 means File not found, and that's definitely due to the DWRCS.EXE file being missing in the System32 folder.

However, all you should have to do is re-copy the DWRCS.EXE file from your local DameWareInstallation folder to the System32 folder on this remote machine. Then you should be able torestart the Service again.

But you might also want to do a little extra research to find out how this file could have been deleted.

I hope this helps.

Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

Re: Unable to log onto remote machines using DameWare 5.5.0.2
by threeofspades on Tue Sep 18, 2007 4:43 am

Hi Bryan,

I took your advice and copied the DWRCS.EXE file from my local machine to the WINDOWS\system32 folder on the server.

When i tried to MRC onto the server i got the request:

"The DameWare Mini Remote Control is not running on onyxctx2.

Would you like to start it now?

Host: onyxctx2".

I selected OK and it came up withthe message:

"Service Start Status:

Starting service....."

I thought that this was looking good but unfortunately it came back to the above message:

"The DameWare Mini Remote Control is not running on onyxctx2.

Would you like to start it now?

Host: onyxctx2".

It seems that the service is starting but is tehn stopping several seconds later.

I RPC'ed onto the server to check out the DameWare Mini Remote Control service. It was setto automatic and was not started. i set it to start and it did so. But about 5 seconds later it just stops.

Not sure what is going on but something is stopping the service from running.

Any ideas?

Kind regards

Re: Unable to log onto remote machines using DameWare 5.5.0.2
by bryan on Tue Sep 18, 2007 1:46 pm

Hi threeofspades,

Thanks very much for the update. This is some great information.

I believe you're right. There appears to be something else here that's stopping the Service from running. What other software do you have running on this machine? Do you have anything like CA eTrust, or Pest Patrol, or Pest Patrol remote (look for ppRemoteService.exe in Task Manager under Processes)?

If this is the cause, then additional information on how to configure the appropriate exception within Pest Patrol is also available in another thread on our forum:

The Dameware mini remote service is not running on XXX.
http://forums.dameware.com/viewtopic.php?f=8&t=47

Your feedback is appreciated.

Bryan Brinkman
Support Engineer
DameWare Development, LLC.
http://www.dameware.com

Re: Unable to log onto remote machines using DameWare 5.5.0.2
by threeofspades on Thu Sep 20, 2007 5:42 am

Hi Bryan,

Thank you for all your help.

We do have eTrust running on our systems and when i placed the DameWare exception into the Management Console i got DameWare back working on all but one server. But i will check it out and see if i can figure out where the problem is. I'm sure it's just something simple but the service still seems to be stopping on that particular server.

Thanks again for all your help and it was very much appreciated.

Kind Regards

hello support,

i need to found the old version 6.9.0.4 of dameware because want to upgrade the my current license version of this product 6.8.0.4

anyone know where this old version is available ?

very thanks for support

francesco

HI. there is any option in Dameware mini remote control to perform operation on other machine in invisible mode(without his knowledge)?

I have had Dameware for over 10 years I think.  A great product, but recently we don't show any but about 9 systems as online.  All of the servers show up, as do a few machines on the same VLAN.  All the other VLANs no longer show.  They have shown up for the last 2 years when the VLANs were configured.  I can connect to them still under computers, but they no longer are listed under workstations.  The "green" PCs show up under Workstations as online but the "blue" ones do not.

I tried upgrading to the newest release but the issue remains.  I really want them back under Workstations so I know what is online.  The Computers section shows all 1341 PCs in the AD, which I do not want to have to look through to find a staff member that needs assistance.

Appreciate any help.

Hello everybody,

We have several different versions of Dameware and are running into some issues using Dameware (f.ex. connecting with MRC to Windows 10 machines). My question is: from what version is Windows 10 supported by Dameware?

Thanks for your time,

Chris

Hello everybody,

I have in my Dameware Remote Support some Windows 7 clients. If i open the Task Schedueler it won't show me the tasks which are already running on my client.

If I create a task over Dameware it will be shown in Dameware in the Task and Job scheduler and on the client. But it won't show me the already existing tasks on the client neither the ones I create new on the client.
Can someone help how I can see the tasks in Dameware ?

Do I have to purchase a public ip address in order to use the internet login feature? Is there another way to do this?

Last year when we renewed our licenses we upgraded from ver 9 to version 11.  I put together a Centralized server which everyone now logs into to use DameWare.  However, when I tried to enter the keys into the License Activation program it wouldn't accept them and I had to open a service request to get it resolved so we could use DameWare.  Earlier this year I expanded my license count, and again, when I tried to update using the License Activation program it wouldn't accept the keys so I had to open another service request.

I just upgraded to the new Version 11.2 and renewed my licensing again for another year.  However, it is not reflecting in either the Server Admin Console or the Activation program.  Both still show the license is only valid through the middle of next week and the Admin Console comes up w/ warnings that there is only 7 days left.  When I click the "I Already Paid" button in the warning it just opens the web page for me to sign into.  I found the License Manager out there and downloaded it.  I ran the sync on that and it comes back fine, shows that I'm good through next year.  Still not updating in the Admin console.  I can enter the keys from my info on the customer portal in the Activation program and at least it shows that it takes them - used to always fail.  However, the dates are still showing that my licensing is about to expire.

What am I missing?!!  Why isn't it updating the date info for me so I'm not seeing the errors in the Admin console any longer?!

Hello All,

So here is my issue. We have over 300 computer that we remote into here at my job. The problem is all of our desktops have dual network connections (wireless & Wired). So when I go to remote into a computer Dame ware automatically connects to the wireless connection and it brings me to the windows login screen. The problem happens when I use the local administrator account to log into the computer. Because the local administrator account does not have Network credentials it can’t connect to the wireless and I lose connection. When I go back in and try to connect to the computer by name dame ware continues looking for that wireless address and never bothers trying to find it on its wire connection that is active. When I go into command prompt and try to ping the computer by name, again it keeps trying to ping the wireless address.  The only solution I have found is go out to the computer pull the  wired address and then connect directly to it. There has to be a way to connect to this computer after the wireless connection is lost. When I remember to I will log in with my domain credentials pull the wired IP address and then connect directly to it. The problem with that is I don't always remember and then the computer also builds me a profile on the computer that 90% of the time I don't want there. Please help we have been dealing with this issue for a long time and can’t figure it out. Is this a domain controller problem? Is there a way to refresh/ renew IP address on the domain controller? Would that even help? Thanks for every ones help in advance!

I launch DNTU normally, running under my logged in ID (only localadmin on my machine). However, I do set the default security credentials to use my domainadmin account though, through the “Logon As” dialogue (using my domainadmin ID) & check the “Set as default Security Credentials” box.

With that configuration, I often get “Error: 5 - Access is denied.” When attempting to view things on the remote domain member machine (shares, service, registry, etc.). It’s strange that sometimes I can view Shares on a machine, but when I try to view Services on the same machine in the same session, it gives me the error for that.

This happens even after multiple times of clicking the “Logon As” & putting in my domainadmin credential.

However, if I launch DNTU directly under my domainadmin account (“Run as a different user”, or even logged on a different machine as my domainadmin), it can view all items on the same remote machine without any error at all. This happens at the same time (one DRS running as normal, one DRS "Run As..." my domain admin), so it’s not the remote machine being in a different state when I try either way.

Anyone know if there is any type of issue with the “Logon As” or Default Security Credential not being passed when trying to view Services, Registry, etc. ,etc.?

Yes, I've seen the June 2011 discussion blaming Microsoft for this same problem but I'm wondering if anything has changed since then. Here's why.

Since I upgraded to DRS v9.0.1.247 last week, I have been unable to use it. I continually show No PDC. Yes, when I use Hyena v9.2 and open Computers, they all show.

Does this not indicate a problem within DRS? If the problem was due to NETBIOS browsing in Windows Server 2008 shouldn't both DRS and Hyena be unable to access the computer browser?

Thanks,

Phil

Note: This is a topic brought over from DameWare Forums which has been closed. If you wish to engage in this discussion, just comment here.

Windows 7 - Cannot End Process
by laurin1 on Fri Dec 18, 2009 4:03 pm

When I attempt to do this, I get an error:

Failed to terminate process: iexplore [4016]
System Error: 2
System Message:
The system cannot find the file specified.

This occurs with all processes.

Re: Windows 7 - Cannot End Process
by laurin1 on Fri Dec 18, 2009 4:09 pm

I just realized the problem is the NT Utilities service is not running. I tried to start it and the service fails:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 12/18/2009
Time: 3:08:03 PM
User: N/A
Computer: KDAVIS.pridedallas.com
Description:
The DameWare NT Utilities 2.6 service failed to start due to the following error:
%%2

For more information, see Help and Support Center athttp://go.microsoft.com/fwlink/events.asp.

Data:

Re: Windows 7 - Cannot End Process
by Marty on Mon Dec 28, 2009 3:06 pm

Hi laurin1,

"System Errors" are actually Microsoft Operating System Errors, not DameWare Errors, and a “System Error: 2" basically means that a required file was not found, therefore, the Service was unable to start. Please make sure all the necessary files are located in the System32 folder on the remote machine (SYSWOW64 folder for 64-bit).

The files for the Client Agent Service are:

DWRCS.EXE
DWRCS.INI (may or may not be there)
DWRCK.DLL
DWRCSET.DLL
DWRCST.EXE
DWRCShell.DLX (or .DLL) (or DWRCSh32 for newer versions) DWRCShell64.DLX (or DLL) (only on 64-bit systems) (DWRCSH64 for newer versions)

If you do find that some of these files are missing from the System32 folder on the remote machine, then I would suggest you check within any type of AntiVirus, AntiSpyware, or Security type software you have installed on your machines, or on the network. This error is typically related to some type of false positive detection, which means all you should have to do is create an exception in this other software.

I hope this helps.

Marty Bonvillain
Support Staff
DameWare Development, LLC.
http://www.dameware.com

Re: Windows 7 - Cannot End Process
by laurin1 on Mon Dec 28, 2009 3:11 pm

I understand all ofthat, however, we have not had this problem until we started using DW on our Windows 7 machines (all are 64 bit.)

Re: Windows 7 - Cannot End Process
by Marty on Mon Dec 28, 2009 3:21 pm

Hi laurin1,

Are you using the latest release (6.8.1.4)? If not, please try to duplicate this behavior in the latest release.

However, regardless of which O/S you are using, this system error indicates that the issue is with your anti-virus/anti-spyware preventing the client agent service from starting, usually because it has blocked or deleted one of the necessary files. For the NT Utilities client agent, it is actually just one file (DNTUS26.EXE).

You should be able to create or define an exception in your security software to resolve this problem. Also, I would recommend trying a manual install of the client agent service per the following directions:

How To Manually Install or Remove the Mini Remote & NT Utilities Client Agents
http://www.dameware.com/support/kb/article.aspx?ID=100000

I hope this helps.

Marty Bonvillain
Support Staff
DameWare Development, LLC.
http://www.dameware.com

Re: Windows 7 - Cannot End Process
by laurin1 on Mon Dec 28, 2009 3:45 pm

Ijust checked and DNTUS26.EXE file is not in the SYSWOW64 folder, but it's in the System32 folder. I disagree with your analysis. I do not think the Antivirus software is the culprit here. I am going to do some testing to find out for sure. I copied the DNTUS26.EXE into the SYSWOW64 folder, but that had no effect (same errorr.) I will try an exception as well for the AV.

Re: Windows 7 - Cannot End Process
by Marty on Mon Dec 28, 2009 3:51 pm

Hi laurin1,

Let us know how it works out.

Marty Bonvillain
Support Staff
DameWare Development, LLC.
http://www.dameware.com

Re: Windows 7 - Cannot End Process
by laurin1 on Mon Dec 28, 2009 3:55 pm

AV exception did not work. I believe whatever process you call use to call the service cannot find the file and here's why:

We've had some of the same problems with 32 bit applications on Windows 7 64 Bit not installing their files in the correct folder, or not installing the registry settings in the correct location.

Re: Windows 7 - Cannot End Process
by Marty on Mon Dec 28, 2009 4:03 pm

Hi laurin1,

Please send an email to support@dameware.com and include the following information:

What version of the software are you using?
What type of antivirus/antispyware do you have installed on your local machine and the remote machine?
If Windows 7 is the remote machine's O/S, what is the O/S on your local machine?

Thanks.

Marty Bonvillain
Support Staff
DameWare Development, LLC.
http://www.dameware.com

Re: Windows 7 - Cannot End Process
by balbright on Thu Dec 30, 2010 11:21 am

I am having the same problem on Windows 7 64 bit boxes. I would like to know the resolution once one is found.

We are using Dameware version 6.9.0.4.

Re: Windows 7 - Cannot End Process
by laurin1 on Thu Dec 30, 2010 11:50 am

6.9.0.04 fixed the problem for us.

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.

How to get of the extra popup to connect to a pc?

When I try to upgrade DameWare 8.0 to 12.0 (or 11.1), I get this popup error:

The Application Event logs show:

Product: DameWare Remote Support -- Error 1722. 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.  Action PhoneHome_DIR, location: C:\Users\myacct\AppData\Local\Temp\, command: "C:\Users\myacct\AppData\Local\Temp\PhoneHome\SWregInst.exe"

So I tried running SWregInst.exe while having the popup error, and I get another popup error saying:

The application was unable to start corredtly (0xc0000022). Click OK to close the application.

Any idea why the install is failing?

Solarwind's whole licensing procedure is terrible.  Everything was running just fine with Dameware Remote Support (which includes Dameware Mini Remote Control) until today when I received a "License Expired" popup when launching DMRC.  I tried to re-activate and  I get a "License Activation" failure whether I use the local license manager or online activation.  Our maintenance was up a couple of years ago, but we only have one client on Dameware and they are on the same version that we are on, so there is clearly no need to upgrade to version 12 since it would force them to also upgrade to version 12.  I have tried uninstalling and reinstalling the same version 11 that was available when the maintenance was in effect.  I've even tried regenerating the license file using my unique machine ID and it still fails.  Anyone have any ideas.