Struggling with getting IoT Edge installed on our devices. Have tried both Linux and Windows 10 and always end up with the Edge Agent reporting "Agent Configuration format is Invalid" when we try and push the tempSensor container from the walk-through to the device.
Thoughts?
This is most likely caused by an issue on the Azure Portal yesterday. The deployment schema was changed on the portal, which caused the current preview release some difficulty. A change has been rolled out on the portal to revert the schema on the portal.
However, this does require you to submit the deployment again, so that the correct schema is generated.
Related
After updating from TFS 2018 v3 to DevOps Server 2019.0.1 last weekend I now receive this authentication error when attempting to manage security:
TF30063: You are not authorized to access tfs.
I receive this error when attempting to manage security from the Server Administration Console via Application Tier > Administer Security. I also receive the error when I attempt to set permissions via tfssecurity cli tool. I am in the local administrator group and I am listed in the console administration user section.
I'm trying to set permissions because after the update I received several reports from employees that receive errors when they try to access their projects. Those errors are:
TF40049: You do not have licensing rights to access this feature: Code.
*** Edit: Update
This error reoccurred when I upgraded from 2019 to 2020 RC1. The difference is, this upgrade required a migration of the server- since server requirements changed for the new version of DevOps Server.
I spent 8 hrs working through this issue yesterday, and this is what fixed our problem:
deleted DevOps server cache. (location of cache listed in devops admin console on server)
reboot server.
I deleted the cache off the server based on an article I read with the same error, a user was having security/permissions issues with visual studio and they deleted the vs cache on their local machine and it solved their problem. I don't know if deleting the cache or the reboot would have fixed it independently because I did them both as a single troubleshooting step.
Hope this helps someone.
** Edit: Update 08/13/20 **
After upgrading again, I have ran into the same issue and this does not fix my error anymore. I've tried deleting the server cache, rebooting, reapplying permissions, configuring a new service account, reapplying changes, rebooting again, etc. I still have not found a solution for this error. I cannot schedule backups through the supplied backup scheduler without permissions to manage security settings through the configuration panel.
We currently have upgraded our Team Foundation Server 2015 to Team foundation server 15, RC1.
But i cannot get our existing or new build agents running. The error we got is always the same.
No agent pool found with identifier 1 (or 2, ....).
I have checked the database and there is an agent pool with that ID.
Any idea anyone?
thanks.
If the build agent pool definitely exists, but the error is can't find the agent pool. Then the issue is very likely related to permissions.
When configuring the build agent(new created or existed), you need to make sure the account which running the configure command or script have enough permission.
The user account needs to be part of the Agent Pool Administrator Accounts.
Update
Try below ways to narrow down the issue:
First check in that if the build server is available and enabled in
TFS at https://YOURCOMPANYNAME:8080/tfs/_admin/_AgentQueue, and
your build agent should be “Green”.
Make sure the agent is in interactive mode.
Try to change a domain account which is a member of the Build
Agent Service Accounts group and belongs to "Agent Pool Service
Account" role, to see whether the agent would work or not.
Double check whether there are some Firewall interface block the
build, try to disable all related settings.
Update 2
Browse the Control Panel - Team Project Collection - Team Project- Agent queues- click agent pool - Roles- click Add... - Add your user ID and select Administrator in Role
After this try again.
Thanks for your time, however the issue is solved with Microsoft support.
It turned out that my default access level was stakeholder, while build permissions are in the basic. So i had to change the default access level to Basic.
That's obvious a bug in the new RC1, but like you said, it was some kind of a permission issue.
thanks again.
I had the exact same thing: an existing build server, which was working until somebody upgraded it. Error message in the .\BuildAgent_Diag\ folder kept saying
Failed to create session. Sleeping for 10 seconds before next retry
----------------------------------------
Microsoft.TeamFoundation.DistributedTask.WebApi.TaskAgentPoolNotFoundException: No agent pool found with identifier 7.
I already had the service running as a domain account with "build admin" permissions.
The solution was to run 'ConfigureAgent' again: Open a command prompt as administrator. Change directory to your 'BuildAgent' folder (or where ever your 'ConfigureAgent.cmd' file is located) and run 'ConfigureAgent.cmd'. It will ask a few questions. I stayed with the current settings. I had to enter the password for the service account. Eventually the wizard completed and everything worked again.
We are working on Xcode Project connected to our local TFS 2013 (Update 3) Server via TFS Provided Git Repository.
When we use older version of Xcode, we are successfully able to check-in the files and perform all other Git operations. We are also able to perform all Git Operations via command line Git.
The trouble is when we use latest version of Xcode - Version 7.1 (7B91b).
On entering valid credentials, we are getting error saying
Authentication failed because the user name or password was incorrect.
The same credentials / configuration work on older version of Xcode and Git Command Line Options.
To add more to the surprises, we are able to connect to github.com successfully.
We are able to reproduce issue on other systems too. Please provide us the best way to resolve this error.
For us it turned out to be because Xcode 7 does not support Windows Authentication. The solution described here solved it for us:
"This happens because XCode 7 doesn't support Windows Authentication.
I don't know why. It seems to be a common problem amongst users
because there are many posts about it in google.
To make it all work you should enable Basic Authentication in your IIS
TFS website on "tfs" virtual folder.
Be careful though because basic authentication sends your credentials
over network as plain text. You definitely must use SSL in this case."
(source)
I have successfully built my project for Android but during building for iOS I get an error:
The remote build server denied the build request, because the client
certificate is invalid or has expired. To build your project, you must
generate and configure a security PIN. See
http://go.microsoft.com/fwlink/?LinkID=511904
I have generated a new pin (after doing a resetServerCert, followed by a generateClientCert), as described in the link above, I reinstalled the remotebuild tool, but all to no avail. It also doesn't matter if I just try to build or build/deploy to a local device.
I also tried building without pin, but that doesn't work either:
Cannot POST
/build/tasks?command=build&vcordova=5.1.1&cfg=debug&options=--device
I am close to releasing my app, but the issues above have set me back a couple of days.
Any suggestions?
From your comment that VS is trying to POST //build/tasks?command=build&vcordova it looks like it isn't configured properly: That empty URL segment should be "cordova", and that is discovered when you configure VS to talk to the remote agent in tools -> options.
If you go to Tools -> Options -> Tools for Apache Cordova -> Remote Agent Configuration and reconfigure your settings (Either disabling secure mode on the mac server, or generating a new pin to use) then VS should be able to connect.
I finally got my first successful build after going through this page: https://github.com/Microsoft/cordova-docs/blob/master/known-issues/known-issues-ios.md
The issue was that I first had vs-mda-remote installed and then changed to remotebuild. You have to follow these steps in this situation:
generate and use a new PIN
If you are not using secure mode, turn secure mode on
Turn secure mode off again to cause VS to reinitalize
I've successfully created a Bot and run an integration test for an iOS application hosted on a remote SVN server over HTTP. When trying to run the same test over HTTPS the test fails and I receive the error: Integration failed. Unexpected internal server error. See the integration's logs for more details. The certificate used for the SVN server is self signed and I ensured I am able to still update/commit to the server over HTTPS. After looking through the logs I can't seem to find out what the error is or how to fix it. (I would post the logs but it's like 100 pages to read through...)
Steps taken so far:
Deleted the bot and project, checked out the project over HTTPS, re-made the bot.
Ensure the correct HTTPS repository is listed both in OS X Server --> Xcode --> Repositories, and in Xcode's repository preferences. (Deleted the old repository as well)
Place the self signed certificate into the keychain's System Store and ensure it is set to Trust All.
Modified the Xcode config file xcsbuildd.plist and changed TrustSelfSignedSSLCertificates to true.
Nothing has seemed to fix it so far. If anyone can think of a fix for this issue please let me know.
I finally was able to fix this by adding to the System keychain our company's Root certificate authority and Intermediate certificate authority certs.
I used Charles (web debugging proxy) to intercept requests and responses and see what was wrong. It gave me a clue that OS X Server was struggling with certs.