search

MicrosoftDocs / azure-devops-server-docs

Documentation for Azure DevOps Server
Creative Commons Attribution 4.0 International
7 stars 11 forks source link

The Admin Console is a bit lacking in error reporting, this is the work around in place since 2010. #12

Closed SamGrantham closed 5 years ago

SamGrantham commented 6 years ago

The process here: https://blogs.msdn.microsoft.com/roberthorvick/2009/10/27/enabling-tracing-during-tfs-2010-configuration/ works for versions up to 2017, and there is a different key that can be used for 2018 (I can provide upon request and PG approval). Is this something that we can add to this documentation or is it more appropriate for a Blog. Personally I'd like it more easily accessible as it is a painful experience to try and discover what is happening behind errors in thins application?

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

SamGrantham commented 6 years ago

To be clear this isn't specifically about the opening from command line, it's more general to the TFS Admin Console. Thanks!

steved0x commented 6 years ago

@SamGrantham I'll assign this to Elijah and he can ping you next week when he is back.

elbatk commented 6 years ago

Thanks for the feedback @SamGrantham , @aaronhallberg could you take a look at this and let me know if you want to spin something up for this?

DLP-ABUHB commented 6 years ago

@SamGrantham, We have a TFS 2018 setup; We can access the web portal just fine ... however we are having problems with connecting our vs ide and with Office Integration 2017 to the TFS... Any help would be appreciated.. with help in mind, please would you let me know the key so as I can enable logging on the server? Thanks

stale[bot] commented 5 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

aaronhallberg commented 5 years ago

Enabling tracing during server configuration is overkill for the vast majority of Azure DevOps Server customers, so I don't think of this as a high priority documentation item. I don't have any problem with you blogging about it, however - especially if you can give an example of a problem it helped you solve.