I have an Windows agent in my server. When i run it as Administrator manually its connecting successfully. But when i added it into Task scheduler to start automatically(restart server) its getting this error
TF30063: You are not authorized to access https://dev.azure.com/my-projects
My windows scheduled task added it to Run with highest privileges. But its getting same issue.
To resolve this issue I have two methods/steps.
Step 1 is to clear the credential from credential manager:
Go to Control Panel (with small icon view)-->User Accounts-->Manage your credentials (on the left column)-->Select Windows Credentials-->Scroll down to the Generic Credentials section and look for your TFS server connection.
Step 2 is to click on the operation that Connects to the Team Projects which is the button/plug icon in the Team Explorer tab. Then to also right click the project you are getting this issue on and select Connect:
If possible, you can check if it is useful to you:
How To Fix TF30063 Error
Error TF30063: You are not authorized to access
For more information you can refer this thread
Related
I am trying to install SQL Data Sync Agent 2.0 but I got this install error
I am running virtual machines with Hyper-V.
I tried in a windows server 2016 and a windows 10. Up to date.
I added the account to log as a windows service.
What could be the issue?
Thanks
I have fixed this issue by adding Computer-name in front of the Username.
Make sure the following,
Username and password are correct.
Prefix the computer name along with the username (Eg: MYPC\user).
You can find the computer name on This PC's properties.
This error occurs in two situations:
User name and/or password are incorrect. Do not use the Windows Live login to install the agent use (create) a local Windows account to install the agent.
The specified user account does not have sufficient privileges to logon as a service, but you told us you did this already. Anyway please verify the following steps:
To Grant logon-as-a-service credentials to the user account please do the following steps:
Navigate to Start > Control Panel > Administrative Tools > Local Security Policy > Local Policy > User Rights Management.
Find and click the Logon as a service entry.
Add the user account in the Logon as a service Properties dialog.
Click Apply then OK.
Close the windows.
Some more suggestions:
Install the client agent using the least privilege account with network service access.
It is best if the client agent is installed on a computer separate from your on premises SQL Server computer.
After I installed Automation Anywhere 11 with SQL Server 2017 on windows server 2012, I could not launch the control room getting bad gateway message.
Could anyone help identifying the problem??
There are several possible reasons for this to happen, the one most easy to miss is your SQL login not having permissions to access your DB.
Open your SQL Management Studio and check that your have login logging enabled (Server Properties -> Security -> Login auditing). It is set to Failed only by default, you can change it to Both successful and failed if you wish.
Then attempt to login to Control Room and then check the logs.
You are most likely going to see an account trying and failing to connect to the DB. Give that account sufficient privileges and try again.
I was experiencing something similar after I restarted my Automation Anywhere Control Room Service from services.msc as adviced in AA forum for getting this error.
grid is invalid state...contact administrator
But, after I restarted the Automation Anywhere Enterprise Auto Login Service V11 service the control room worked fine.
Background info: Automatically run data connections in XLSM
I have a batch script which logs a start and end time, and runs a VBS scripts, which in turn opens up a excel file, runs a couple of data connections and closes the file again.
This works just fine when I run the batch script. However when I run it through the task scheduler the data connections are not run on the excel file. It seems like it might be related to some sort of security issue, but I cant figure out what the issue is exactly.
In the eventviewer of the server I was setting this up I found this little message:
The machine-default permission settings do not grant Local Activation
permission for the COM Server application with CLSID
{00024500-0000-0000-C000-000000000046} and APPID Unavailable to the
user DOMAIN\USER SID
(S-1-5-21-3431573511-3352521975-2604885492-32293) from address
LocalHost (Using LRPC) running in the application container
Unavailable SID (Unavailable). This security permission can be
modified using the Component Services administrative tool.
But I have no idea what this means.
I ran into the same issue when trying saving an Excel file via a Powershell script. I wasn't able to adjust the security settings for CLSID “000C101C-0000-0000-C000-000000000046”, which should resolve this, so I ran the task under the SYSTEM account, which already had the necessary permissions. This resolved the issue.
This error is being logged into the System event logs in Event Viewer due to inadequate permission for the farm admin account on the DCOM component 000C101C-0000-0000-C000-000000000046. In order to change the permission settings, perform the following steps:
Open Component Service by clicking Start → Administrative Tools → Component Services.
Navigate and expand the node Component Services → Computers → My Computer → DCOM Config.
Right-click the sub node “000C101C-0000-0000-C000-000000000046” and select “Properties”.
On the Properties dialog box, select Security tab. In most cases you will notice that the settings are grayed out. This is because the logged in user doesn't have enough permissions on this component to change the settings. In order to provide this permissions, perform the steps described in next section “Change Component Service Owner and Permission”. You may need to restart the server after doing this.
Once you set up the permission mentioned in previous step, in the Launch and Activation Permissions section in Security tab, select Customize option and click Edit.
In the popup window, add the farm admin user account and check Local Launch and Local Activation permissions.
Restart IIS and SP Timer. If possible, restart the server itself.
Reference: http://sajiviswam.wordpress.com/2011/04/15/the-machine-default-permission-settings-do-not-grant-local-activation-permission-for-the-com-server-application-with-clsid-000c101c-0000-0000-c000-000000000046-sharepoint-2010/
I'm currently facing an Access Denied error while connecting to an Azure VM. This VM is registered in an Active Directry. When I log with the AD credentials, I get an "Access Denied" error message with a "Ok" button without any other text on the screen. I never faced this issue before. The maching was working perfectly last week...
Do you have any idea about this issue ?
Thanks for your help
Access Denied Error Screenshot
Can you still access the VM and its using your Azure Portal login? If so, try adding the AD user via RDP.
Go to Computer Mgmt on the VM via Remote Desktop
Expand the list of Remote Desktop Users.
Select the user(s) to add.
See details in the MSDN thread:
https://social.msdn.microsoft.com/Forums/en-US/9ebce1bb-2aa0-4bb0-adc7-d1e229c5ee9e/add-user-to-remote-desktop-group-in-azure-vm?forum=WAVirtualMachinesforWindows
If you're having RDP issues with the primary user account, check the Settings blade of your VM in the Azure Portal, and look at the Users list under Resource Management.
Hope that helps!
I had the same issue, in my case it was related to Terminal Service Licensing.
First save a local copy of the RDP file from the portal and run this command at a PowerShell command prompt to connect. This will disable licensing for just that connection:
mstsc <File name>.RDP /admin
after you are able to connect then open the Event Viewer an look for an Event with ID 4105 in WIndows Logs > System. this event should appear every time a logging was attempted.
If that is the case, follow this steps to solve the issue
Event ID 4105 — Terminal Services Per User Client Access License Tracking and Reporting
Hope this helps.
Ive been trying to use Visual Studio Online's new build definitions with linux. I set up an Azure VM running CentOS 7.1 installed Nodejs (v0.10.36) and npm (v3.3.9) the prerequisites for the vNext build agent.
when running the vsoagent.js file to set up the agent and filling in the fields, i am able to connect to my VSO account successfully but the build agent doesnt start.
following is the console output i get:
Console output
Im getting a bad request (400) error, why is this occuring and how do i fix it?
You need to set some permissions before you can add and run a new agent. First, you need to enable alternate credentials for your account. Log in to VSO using your account and open your profile settings.
Then, go to the “Credentials” tab and enable your alternate credentials there.
After that, go back to the “Agent pools” administration page, go to Roles tab, there are two security groups there. You’ll need to add your account to both.
•Agent Pool Administrators: allows adding agent to pool
•Agent Pool Service Accounts: allows the agent to listen to the build queue
When you create the server, you'll need to login using the credentials you provided when creating the virtual machine. More steps of creating a Build.vNext agent on Linux, please check http://realalm.com/2015/06/26/creating-a-build-vnext-agent-on-linux/
From the screenshot you provided, you got bad request with the URL.
And the server URL you need to provide should be something like: https://servername.visualstudio.com