Currently I am trying to create a task in remote machine through TaskService class. The remote machine is connected through workgroup. But I am not able to create task in remote machine. I am getting following exception.
System.UnauthorizedAccessException was unhandled
Message=Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
I am trying to create it in following way.
TaskService ts = new TaskService("COMPUTERNAME", "remoteUserAcctName", "DOMAINNAME", "remoteUserPassword");
I am trying to create task in remote computer running Windows 7 from a computer running Windows 7. Is it possible? Because as per this link, http://technet.microsoft.com/en-us/library/cc766266.aspx , one can connect to remote computers running Windows Server® 2008, Windows Vista®, Windows Server 2003, Windows XP, or Windows 2000.
Also I tried from Task Scheduler menu 'Action | Connect to Another Computer', http://screencast.com/t/wIDbDcdhOE , I got error 'You do not have permission to access this computer'.
Details here, https://taskscheduler.codeplex.com/discussions/570851.
The following is working fine in domain environment. Earlier I tried in work group environment.
TaskService ts = new TaskService("COMPUTERNAME", "remoteUserAcctName", "DOMAINNAME", "remoteUserPassword");
Related
I am trying to deploy my project to IIS using TFS Winrm:IIS web app deployment task. I am new to this.
I am getting the following error'
"Deployment failed on machine xxx with following message : System.Management.Automation.Remoting.PSRemotingTransportException: Connecting to remote server xxx failed with the following error message : The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig". "
I was able deploy the project to the same remote server using TFS Winrm: windows machine file copy task which is the prior step for web app deployment to IIS. Winrm service is running and when it type the "winrm quickconfig i am getting "winrm is already been configured".
What am i missing here ? please suggest. Thanks in advance.
The Winrm:IIS task is actually MSDeploy from Machine A to Machine B so for this to work you need to install MSDeploy on Machine B. You should then be ok to deploy from Machine A. Check this article out for more information and to see if you have all the pre-requisite. Also these articles have a bit more info.
https://learn.microsoft.com/en-us/azure/devops/pipelines/apps/cd/deploy-webdeploy-iis-winrm?view=azure-devops
https://marketplace.visualstudio.com/items?itemName=ms-vscs-rm.iiswebapp
The issue was resolved when i enable remote powershell remoting my remote machine using the command Enable-PSRemoting –force
I have a COM+ application consisting of a client DLL and many middle-tier DLLs.
The application gets run by using an MSC application file.
When I am in die IDE and run my client DLL, I have the following run parameters to launch, run and debug my client DLL (this works great):
The theory is that I should be able to debug my middle-tier by running the DLL with the following parameters (I get the ProcessID from my COM+ Application in Component Services):
Once it is running, I should then be able to start my client MSC application and that should allow me to attach and debug my middle tier. I have seen this working before.
Running my Client DLL from the IDE or as an MSC application works without issues but when I try to debug my middle-tier, as described above, I get a "The RPC server is unavailable" error.
I am running everything locally so I am not sure what server it is referring too.
I have also made sure the following services are up-and-running:
DCOM Server Process Launcher, Remote Procedure Call (RPC) and RPC Endpoint Mapper
Any idea what else could cause this error or what server it is trying to connect too?
It turns out there were more than 1 version of the DLLs registered on my pc. I inherited the pc from a previous employee and noticed some install files of the application on the C drive (all my stuff is on the E drive). I ran the uninstall procedure on the C drive that also unregistered some DLLs and my RPC problem was resolved.
When I try to deploy my artifact on IIS, I am getting the error as shown in the below screenshot. Any help will be greatly appreciated.
The "IIS Web App Management" screenshot is shown below:
The error message is pretty clear: You can't use it to install IIS on a client OS (such as Windows 10). You have to use a server OS (such as Windows Server).
There's nothing you can do about it other than to use a server OS or use an alternate tool to deploy.
Using Windows Remote Management (WinRM), connect to the host
machine(s) where IIS or SQL Server is installed, and manage the Web
application or deploy the SQL Server Database as described below:
Create a new website or update an existing website using AppCmd.exe.
Create a new application pool or update an existing application pool using AppCmd.exe.
Deploy a Web Application to the IIS Server using Web Deploy.
Deploy a SQL Server Database using DACPAC and SqlPackage.exe.
Your log mentioned the task was installing IIS, and it seemed the tasking was installing IIS on a windows client OS. You need to check your target machine to see whether it has IIS installed.
I have created a windows service which is successfully installed on my machine as well as some other local machines.
But when I try to install the same on client's server which is Windows Server 2012 R2 it is getting error stack as below:
The inner exception System.ComponentModel.Win32Exception was thrown with the following error message: The service did not respond to the start or control request in a timely fashion.
For this, I have tried some solution as below:
Adding ServicePipeTimeout in regedit so that it can increase the timeout.
Comparing Microsoft .Net Framework's version used in windows service and Windows Server 2012 R2.
Both of the solutions did not work for me. Can someone guide me through this issue?
I have a Team Foundation Server 2013 installed on a server on a domain. I can connect to this server from my domain account using VS 2012.
I also have a virtual machine which runs on Windows XP and NOT part of the domain (login as a local user). I have a VB6 project running on this VM and I want to connect to the TFS to share and control my VB6 code but I keep on getting The Request Failed with HTTP status 404: Not found.
I tried creating a local user on the server with the same name as the user I use for VM but it didn't work. I cannot join the VM to the domain as well.
Hope someone has tackled this and shed me some light.