locked
Unable to register test agent with test controller. RRS feed

  • Question

  • Kindly assist for below issue.

    I am setting up Test Controller and Test Agent on two different server machine with same domain.

    The NT user (sysperftest) has local admin privilege on controller machine. In agent machine I have logged with different NT user which also has local admin privilege and I configured the Test agent with  NT user (sysperftest) account. NT user (sysperftest) account also added to Administrators group in the Test Agent machine.

    I have installed Visual Studio Ultimate 2013 and Test Controller 2013 in my controller machine and configured the controller successfully.I have used Microsoft Agents for Visual Studio 2013 Version:12.0.40629.0 Update 5 for Test Controller and Test Agent machine. 

    The Test Controller is configure with Load Testing (Not using Team Project Collection).

    The firewall is closed on both controller & agent machine. 

    The NT user has added in TeamTestAgentService and TeamTestControllerUser group in controller machine.

    Earlier I installed Test Agent 2012 in my agent machine and tried to configure. Then uninstalled Test Agent 2012 and installed Test Agent 2013 and rebooted the machine.

    I have also tried below work around

    Comment out any hostfile entries on the agent machines that have the 127.0.0.1 IP address with a "#" pound sign.
    Run "ipconfig /flushdns" on the agent and the controller.
    Restart all of the services starting with "Visual Studio" on both the agent and the controller.
    Rerun the agent configuration.

    Screen shot of Test Agent

    When I try to configure the test agent got the below error.

    Error Log

    Configuration started on 2016/08/24, 09:49:44.
    OS Version : Microsoft Windows NT 6.1.7601 Service Pack 1
    Executable version : 12.0.40629.0 Update 5

    I, 2016/08/24, 09:49:44.250, Listing agent configurations
    I, 2016/08/24, 09:49:44.425, GetControllerName : The controller name managed by lab is 
    I, 2016/08/24, 09:49:45.567, IsManagedByLab : lab managed controller name : 
    I, 2016/08/24, 09:49:45.568, GetControllerName : The controller name managed by lab is 
    I, 2016/08/24, 09:49:45.569, GetLabEnvironmentName S-KMDEV010D under 
    I, 2016/08/24, 09:49:45.780, Creating Channel
    I, 2016/08/24, 09:49:45.794, IsManagedByLab : lab evironment name : 
    I, 2016/08/24, 09:49:45.800, NotManagedByLab = True
    I, 2016/08/24, 11:08:54.435, Agent configuration update pack details :
    I, 2016/08/24, 11:08:54.435, Run as interactive process : False
    I, 2016/08/24, 11:08:54.437, User name : syspkmperftest
    I, 2016/08/24, 11:08:54.437, Change Port : False
    I, 2016/08/24, 11:08:54.437, Chang eService Account : True
    I, 2016/08/24, 11:08:54.437, Change Test Controller : True
    I, 2016/08/24, 11:08:54.437, Test Controller Uri : SIN0M2APP0205XP:6901
    I, 2016/08/24, 11:08:54.437, Disable Screensaver : False
    I, 2016/08/24, 11:08:54.437, Enable autologon : False
    I, 2016/08/24, 11:08:54.437, Port : -1
    I, 2016/08/24, 11:08:54.473, Validating user name and password.
    I, 2016/08/24, 11:08:54.506, Validated user name and password.
    I, 2016/08/24, 11:08:54.514, Starting firewall configuration...
    I, 2016/08/24, 11:08:55.088, IsPortExceptionEnabled: Checking for port exception for port 6910 in firewall profile STANDARD
    I, 2016/08/24, 11:08:55.363, Exception for port 6910 in not enabled in firewall profile STANDARD
    I, 2016/08/24, 11:08:55.364, BaseConfig: AddFirewallExceptionIfRequired: Adding Port=6910,Description=Microsoft Visual Studio Test Agent Service in firewall exceptions.
    I, 2016/08/24, 11:08:55.407, Added port exception for service Microsoft Visual Studio Test Agent Service on port 6910 for profile STANDARD
    I, 2016/08/24, 11:08:55.450, Added port exception for service Microsoft Visual Studio Test Agent Service on port 6910 for profile DOMAIN
    I, 2016/08/24, 11:08:55.475, EnablePortExceptionInAllProfiles: Service Microsoft Visual Studio Test Agent Service already has a exception in profile CURRENT
    I, 2016/08/24, 11:08:55.475, BaseConfig: AddFirewallExceptionIfRequired: Added Port=6910,Description=Microsoft Visual Studio Test Agent Service in firewall exceptions.
    I, 2016/08/24, 11:08:55.476, Configured firewall exceptions for: 'Microsoft Visual Studio Test Agent Service'.
    I, 2016/08/24, 11:08:55.478, Enabling Remote Desktop on the machine...
    I, 2016/08/24, 11:08:55.916, No change to the Remote Desktop setting as Remote Desktop was already enabled on the machine.
    I, 2016/08/24, 11:08:55.946, Starting firewall configuration...
    I, 2016/08/24, 11:08:56.327, BaseConfig: AddFirewallExceptionIfRequired: Firewall exception already enabled for service Remote Desktop.
    I, 2016/08/24, 11:08:56.328, No change to the firewall setting as the firewall exception was already enabled for the service 'Remote Desktop'.
    I, 2016/08/24, 11:08:56.328, Configured firewall exceptions for: 'Remote Desktop'.
    I, 2016/08/24, 11:08:56.328, Adding agent setting Microsoft.TeamFoundation.Lab.TestIntegration.AgentVersion=3.0.0 on agent machine
    I, 2016/08/24, 11:08:56.328, Adding agent setting Microsoft.TeamFoundation.Lab.TestIntegration.AgentVersion=3.0.0 on agent machine - 32 bit hive
    I, 2016/08/24, 11:08:56.330, Creating Key: EnterpriseTools\QualityTools\Agent
    I, 2016/08/24, 11:08:56.331, Added agent setting Microsoft.TeamFoundation.Lab.TestIntegration.AgentVersion=3.0.0 on agent machine - 32 bit hive
    I, 2016/08/24, 11:08:56.331, Adding agent setting Microsoft.TeamFoundation.Lab.TestIntegration.AgentVersion=3.0.0 on agent machine - 64 bit hive
    I, 2016/08/24, 11:08:56.331, Creating Key: EnterpriseTools\QualityTools\Agent
    I, 2016/08/24, 11:08:56.332, Added agent setting Microsoft.TeamFoundation.Lab.TestIntegration.AgentVersion=3.0.0 on agent machine - 64 bit hive
    I, 2016/08/24, 11:08:56.357, Adding agent setting NetworkAdapterInfo=0050568B02BD on agent machine
    I, 2016/08/24, 11:08:56.358, Adding agent setting NetworkAdapterInfo=0050568B02BD on agent machine - 32 bit hive
    I, 2016/08/24, 11:08:56.359, Added agent setting NetworkAdapterInfo=0050568B02BD on agent machine - 32 bit hive
    I, 2016/08/24, 11:08:56.359, Adding agent setting NetworkAdapterInfo=0050568B02BD on agent machine - 64 bit hive
    I, 2016/08/24, 11:08:56.360, Added agent setting NetworkAdapterInfo=0050568B02BD on agent machine - 64 bit hive
    I, 2016/08/24, 11:08:56.360, Adding agent setting InstallationPath=C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE on agent machine
    I, 2016/08/24, 11:08:56.360, Adding agent setting InstallationPath=C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE on agent machine - 32 bit hive
    I, 2016/08/24, 11:08:56.361, Added agent setting InstallationPath=C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE on agent machine - 32 bit hive
    I, 2016/08/24, 11:08:56.361, Adding agent setting InstallationPath=C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE on agent machine - 64 bit hive
    I, 2016/08/24, 11:08:56.362, Added agent setting InstallationPath=C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE on agent machine - 64 bit hive
    I, 2016/08/24, 11:08:56.362, Creating event sources VSTTAgent 
    I, 2016/08/24, 11:08:56.363, Creating event sources VSTTAgent 
    I, 2016/08/24, 11:08:56.793, Created event source VSTTAgent 
    I, 2016/08/24, 11:08:56.793, Creating event sources VSTTAgentProcess 
    I, 2016/08/24, 11:08:56.794, Event source VSTTAgentProcess already exists.
    I, 2016/08/24, 11:08:56.794, Adding event source for event logging
    I, 2016/08/24, 11:08:56.795, ResetForceGuestKey : Getting the value of ForceGuest key
    I, 2016/08/24, 11:08:56.795, ResetForceGuestKey : The value of ForceGuest key is 0
    I, 2016/08/24, 11:08:56.799, Updating the startup registry
    I, 2016/08/24, 11:08:56.799, Removing VSTTAgentProcess from Run registry
    I, 2016/08/24, 11:08:56.800, Starting service configuration...
    I, 2016/08/24, 11:08:56.802, Started checking the status of agent service VSTTAgent.
    I, 2016/08/24, 11:08:56.804, Agent service VSTTAgent is not installed, attempting to install it now.
    I, 2016/08/24, 11:08:56.807, Installing service ServicenName=VSTTAgent, DisplayName=Visual Studio Test Agent, Path=C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\QTAgentService.exe, Description=Provides distributed test engine agent services, userName=GICNT\syspkmperftest, Dependencies=System.String[]  
    I, 2016/08/24, 11:08:56.808, Dependency string is dhcp labagentservice  
    V, 2016/08/24, 11:08:58.124, Service installed with return code 156525696
    V, 2016/08/24, 11:08:58.124, Updating the description Provides distributed test engine agent services of the service VSTTAgent.
    I, 2016/08/24, 11:08:59.549, Installed agent service VSTTAgent.
    I, 2016/08/24, 11:08:59.552, Found binary Sid 'System.Byte[]' for account GICNT\syspkmperftest 
    I, 2016/08/24, 11:09:00.402, Granted LogonAsService permission to agent service account GICNT\syspkmperftest.
    I, 2016/08/24, 11:09:00.402, Adding agent setting AgentRunMode=AsService on agent machine
    I, 2016/08/24, 11:09:00.402, Adding agent setting AgentRunMode=AsService on agent machine - 32 bit hive
    I, 2016/08/24, 11:09:00.404, Added agent setting AgentRunMode=AsService on agent machine - 32 bit hive
    I, 2016/08/24, 11:09:00.404, Adding agent setting AgentRunMode=AsService on agent machine - 64 bit hive
    I, 2016/08/24, 11:09:00.405, Added agent setting AgentRunMode=AsService on agent machine - 64 bit hive
    I, 2016/08/24, 11:09:00.405, Adding agent setting AgentInteractiveProcessUserName= on agent machine
    I, 2016/08/24, 11:09:00.406, Adding agent setting AgentInteractiveProcessUserName= on agent machine - 32 bit hive
    I, 2016/08/24, 11:09:00.406, Added agent setting AgentInteractiveProcessUserName= on agent machine - 32 bit hive
    I, 2016/08/24, 11:09:00.406, Adding agent setting AgentInteractiveProcessUserName= on agent machine - 64 bit hive
    I, 2016/08/24, 11:09:00.407, Added agent setting AgentInteractiveProcessUserName= on agent machine - 64 bit hive
    I, 2016/08/24, 11:09:00.407, Removing agent setting DisableScreenSaver on agent machine
    I, 2016/08/24, 11:09:00.407, Removing agent setting DisableScreenSaver on agent machine - 32 bit hive
    I, 2016/08/24, 11:09:00.408, Removed agent setting DisableScreenSaver on agent machine - 32 bit hive
    I, 2016/08/24, 11:09:00.408, Removing agent setting DisableScreenSaver on agent machine - 64 bit hive
    I, 2016/08/24, 11:09:00.409, Removed agent setting DisableScreenSaver on agent machine - 64 bit hive
    I, 2016/08/24, 11:09:00.410, UpdateServiceStartTime : Getting the value of ServiceStartTimeout key
    I, 2016/08/24, 11:09:00.410, UpdateServiceStartTime : The value of ServiceStartTimeout key is 600000
    I, 2016/08/24, 11:09:00.412, Configured service successfully.
    I, 2016/08/24, 11:09:00.415, Setting Tcp Parameters
    V, 2016/08/24, 11:09:00.415, Setting Tcp Parameters in 32bit Hive
    V, 2016/08/24, 11:09:00.416, Setting Tcp Parameters in 32bit Hive completed. 
    V, 2016/08/24, 11:09:00.416, Setting Tcp Parameters in 64bit Hive. 
    V, 2016/08/24, 11:09:00.416, Setting Tcp Parameters in 64bit Hive completed. 
    I, 2016/08/24, 11:09:00.417, Setting Tcp Parameters completed.
    I, 2016/08/24, 11:09:00.421, Registering this test agent with the test controller. This may take few minutes...
    I, 2016/08/24, 11:09:00.421, AgentConfiguration: Starting controller configuration.
    I, 2016/08/24, 11:09:00.421, GetControllerName : The controller name managed by lab is 
    I, 2016/08/24, 11:09:00.422, GetControllerName : The controller name managed by lab is 
    I, 2016/08/24, 11:09:00.422, AgentConfiguration: Found agent is not configured on any controller.
    I, 2016/08/24, 11:09:00.433, Getting information about controller: SIN0M2APP0205XP:6901.
    I, 2016/08/24, 11:09:00.433, Creating Channel
    I, 2016/08/24, 11:09:00.454, CreateControllerObject : ControllerVersion : 12.0
    I, 2016/08/24, 11:09:02.106, CreateControllerObject: attempt 0, Microsoft.VisualStudio.TestTools.Exceptions.AccessDeniedException: You do not have the appropriate permissions to perform this action.

    Server stack trace: 
       at Microsoft.VisualStudio.TestTools.Controller.ControllerUtilities.AuthenticateUserforControllerAndTfsPermissions(WindowsIdentity identity, ControllerAction controllerAction, TfsTeamProjectCollection server, String teamProjectName, ControllerObject controllerObject, Guid testRunId, Boolean isVirtualEnv)
       at Microsoft.VisualStudio.TestTools.Controller.ControllerUtilities.AuthenticateUserforControllerAndTfsPermissions(WindowsIdentity identity, ControllerAction controllerAction, TfsTeamProjectCollection server, String teamProjectName)
       at Microsoft.VisualStudio.TestTools.Execution.ControllerAccessManager.Microsoft.VisualStudio.TestTools.Execution.IControllerAccessManager.GetControllerObject(Version versionInfo)
       at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
       at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)

    Exception rethrown at [0]: 
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at Microsoft.VisualStudio.TestTools.Execution.IControllerAccessManager.GetControllerObject(Version versionInfo)
       at Microsoft.VisualStudio.TestTools.ConfigCore.TestControllerHelper.CreateControllerObject(String controllerUri, NetworkCredential labServiceAccount)
    I, 2016/08/24, 11:09:02.207, CreateControllerObject : ControllerVersion : 12.0
    I, 2016/08/24, 11:09:02.210, CreateControllerObject: attempt 1, Microsoft.VisualStudio.TestTools.Exceptions.AccessDeniedException: You do not have the appropriate permissions to perform this action.

    Server stack trace: 
       at Microsoft.VisualStudio.TestTools.Controller.ControllerUtilities.AuthenticateUserforControllerAndTfsPermissions(WindowsIdentity identity, ControllerAction controllerAction, TfsTeamProjectCollection server, String teamProjectName, ControllerObject controllerObject, Guid testRunId, Boolean isVirtualEnv)
       at Microsoft.VisualStudio.TestTools.Controller.ControllerUtilities.AuthenticateUserforControllerAndTfsPermissions(WindowsIdentity identity, ControllerAction controllerAction, TfsTeamProjectCollection server, String teamProjectName)
       at Microsoft.VisualStudio.TestTools.Execution.ControllerAccessManager.Microsoft.VisualStudio.TestTools.Execution.IControllerAccessManager.GetControllerObject(Version versionInfo)
       at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
       at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)

    Exception rethrown at [0]: 
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at Microsoft.VisualStudio.TestTools.Execution.IControllerAccessManager.GetControllerObject(Version versionInfo)
       at Microsoft.VisualStudio.TestTools.ConfigCore.TestControllerHelper.CreateControllerObject(String controllerUri, NetworkCredential labServiceAccount)
    I, 2016/08/24, 11:09:02.312, CreateControllerObject : ControllerVersion : 12.0
    I, 2016/08/24, 11:09:02.316, CreateControllerObject: attempt 2, Microsoft.VisualStudio.TestTools.Exceptions.AccessDeniedException: You do not have the appropriate permissions to perform this action.

    Server stack trace: 
       at Microsoft.VisualStudio.TestTools.Controller.ControllerUtilities.AuthenticateUserforControllerAndTfsPermissions(WindowsIdentity identity, ControllerAction controllerAction, TfsTeamProjectCollection server, String teamProjectName, ControllerObject controllerObject, Guid testRunId, Boolean isVirtualEnv)
       at Microsoft.VisualStudio.TestTools.Controller.ControllerUtilities.AuthenticateUserforControllerAndTfsPermissions(WindowsIdentity identity, ControllerAction controllerAction, TfsTeamProjectCollection server, String teamProjectName)
       at Microsoft.VisualStudio.TestTools.Execution.ControllerAccessManager.Microsoft.VisualStudio.TestTools.Execution.IControllerAccessManager.GetControllerObject(Version versionInfo)
       at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
       at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)

    Exception rethrown at [0]: 
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at Microsoft.VisualStudio.TestTools.Execution.IControllerAccessManager.GetControllerObject(Version versionInfo)
       at Microsoft.VisualStudio.TestTools.ConfigCore.TestControllerHelper.CreateControllerObject(String controllerUri, NetworkCredential labServiceAccount)
    E, 2016/08/24, 11:09:02.417, Failed to register this test agent with the test controller. Possible reasons could be you do not have permissions to connect to the test controller or a firewall is blocking the connection.
    To fix this problem, verify the test controller is running and you have appropriate permissions to register test agent with the test controller. Refer to this page for more details: http://go.microsoft.com/fwlink/?LinkID=212977&clcid=0x409
    E, 2016/08/24, 11:09:02.502, Got Exception : Microsoft.VisualStudio.TestTools.ConfigCore.ConfigToolException: Failed to register this test agent with the test controller. Possible reasons could be you do not have permissions to connect to the test controller or a firewall is blocking the connection.
    To fix this problem, verify the test controller is running and you have appropriate permissions to register test agent with the test controller. Refer to this page for more details: http://go.microsoft.com/fwlink/?LinkID=212977&clcid=0x409 ---> Microsoft.VisualStudio.TestTools.Exceptions.AccessDeniedException: You do not have the appropriate permissions to perform this action.

    Server stack trace: 
       at Microsoft.VisualStudio.TestTools.Controller.ControllerUtilities.AuthenticateUserforControllerAndTfsPermissions(WindowsIdentity identity, ControllerAction controllerAction, TfsTeamProjectCollection server, String teamProjectName, ControllerObject controllerObject, Guid testRunId, Boolean isVirtualEnv)
       at Microsoft.VisualStudio.TestTools.Controller.ControllerUtilities.AuthenticateUserforControllerAndTfsPermissions(WindowsIdentity identity, ControllerAction controllerAction, TfsTeamProjectCollection server, String teamProjectName)
       at Microsoft.VisualStudio.TestTools.Execution.ControllerAccessManager.Microsoft.VisualStudio.TestTools.Execution.IControllerAccessManager.GetControllerObject(Version versionInfo)
       at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
       at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)

    Exception rethrown at [0]: 
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at Microsoft.VisualStudio.TestTools.Execution.IControllerAccessManager.GetControllerObject(Version versionInfo)
       at Microsoft.VisualStudio.TestTools.ConfigCore.TestControllerHelper.CreateControllerObject(String controllerUri, NetworkCredential labServiceAccount)
       --- End of inner exception stack trace ---
       at Microsoft.VisualStudio.TestTools.ConfigCore.TestControllerHelper.CreateControllerObject(String controllerUri, NetworkCredential labServiceAccount)
       at Microsoft.VisualStudio.TestTools.ConfigCore.TestControllerHelper.GetControllerInformation(String controllerUri, NetworkCredential labServiceAccout)
       at Microsoft.VisualStudio.TestTools.ConfigCore.AgentConfiguration.BindToController(String testController, ServiceAccount agentServiceAccount, NetworkCredential labServiceAccount)
       at Microsoft.VisualStudio.TestTools.ConfigCore.AgentConfiguration.HandleControllerChange(AgentConfigurationUpdatePack updatePack, DelegateStatusUpdate statusListener)
       at Microsoft.VisualStudio.TestTools.ConfigCore.AgentConfiguration.Configure(AgentConfigurationUpdatePack updatePack, DelegateStatusUpdate statusListener)
       at Microsoft.VisualStudio.TestTools.AgentConfigUI.AgentConfigUI.ConfigureWorker_DoWork(Object sender, DoWorkEventArgs e)
       at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
       at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
    I, 2016/08/24, 11:09:02.502, Work completed for GetConfiguration() call : got out of turn error
    E, 2016/08/24, 11:09:02.503, Failed to register this test agent with the test controller. Possible reasons could be you do not have permissions to connect to the test controller or a firewall is blocking the connection.
    To fix this problem, verify the test controller is running and you have appropriate permissions to register test agent with the test controller. Refer to this page for more details: http://go.microsoft.com/fwlink/?LinkID=212977&clcid=0x409

    Regards,

    David.



    • Edited by David Naveen Wednesday, August 24, 2016 11:10 AM
    Wednesday, August 24, 2016 11:09 AM

Answers

  • Hi Kim,

    Thanks for helping me to troubleshoot the issue. The issue is solved now. After enabling the test controller log found that the user account which I logged to Test Agent is not added to the admin group in the Test Controller Machine. After adding the user account (Which I used to login to Test Agent) to admin group in Controller Machine it's working as expected. 

    I was in impression that only the configuration user id should be added as admin account in the controller machine but the logged in account also need to be added it seems.

    Regards,

    David.

    • Proposed as answer by Oscar_Wu Monday, August 29, 2016 6:53 AM
    • Marked as answer by Oscar_Wu Thursday, September 1, 2016 9:06 AM
    Thursday, August 25, 2016 1:19 AM

All replies

  • are you using a domain account? the account should be member of local admin on both agent and controller. see https://msdn.microsoft.com/en-us/library/hh546459(v=vs.120).aspx#agent
    Wednesday, August 24, 2016 11:21 AM
  • Hi Kim,

    Yes, I am using domain account only. I have added the account to the Administrators group on both agent and controller machine.

    Regards,

    David.

    Wednesday, August 24, 2016 11:32 AM
  • Did you reboot the servers after configuring the memberships?
    Wednesday, August 24, 2016 11:40 AM
  • Yep, I have rebooted the Agent machine.. The controller machine was configured earlier and working with other test agent machine.
    Wednesday, August 24, 2016 11:41 AM
  • and you are using the same account as the working agents?

    Verify firewall by trying to telnet to the controller at port 6901

    Verify domain join by accessing \\SIN0M2APP0205XP\c$ it should connect without prompt for username

    Wednesday, August 24, 2016 11:50 AM
  • also try enter the controller name as FQDN
    Wednesday, August 24, 2016 12:08 PM
  • telnet working as expected. when I tried to access  \\SIN0M2APP0205XP\c$ it ask for username and password. 

    As I mentioned earlier, I have logged in to the Test Agent with different user account which also has admin rights. But when configuring the test agent  I have given the user id which is used to register the Test controller in the controller machine.


    • Edited by David Naveen Wednesday, August 24, 2016 12:11 PM
    Wednesday, August 24, 2016 12:11 PM
  • Wednesday, August 24, 2016 12:15 PM
  • Hi Kim,

    Thanks for helping me to troubleshoot the issue. The issue is solved now. After enabling the test controller log found that the user account which I logged to Test Agent is not added to the admin group in the Test Controller Machine. After adding the user account (Which I used to login to Test Agent) to admin group in Controller Machine it's working as expected. 

    I was in impression that only the configuration user id should be added as admin account in the controller machine but the logged in account also need to be added it seems.

    Regards,

    David.

    • Proposed as answer by Oscar_Wu Monday, August 29, 2016 6:53 AM
    • Marked as answer by Oscar_Wu Thursday, September 1, 2016 9:06 AM
    Thursday, August 25, 2016 1:19 AM
  • Good to hear you fixed the issue.

    The errormessages are not always easy to read...

    Thursday, August 25, 2016 4:36 AM
  • Hi David Naveen,

    Glad to know that you have resolved this issue, and thanks for sharing your solution here. Would you please mark your reply as the answer? So it would be helpful for other members who meet the same issue as yours.

    Sincerely,

    Oscar


    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.

    • Proposed as answer by mbreddy15 Tuesday, February 13, 2018 1:17 AM
    Monday, August 29, 2016 6:55 AM
  • HiDavid.

    You saved my day!!. I was workiing with  my networking and security team resolve this issue from last couple of days, but no luck. 

    Thanks for your detail explanation.

    Thanks

    BuchiM

    Tuesday, February 13, 2018 1:19 AM