Error Integrating TFS 2017 U3 with SQL Server 2016 Reporting Services
up vote
0
down vote
favorite
When I try to integrate TFS 2017 U3 with SQL Server 2017 Reporting Services, from TFS Administration Console, an error appear. Please see screenshot.
In the event viewer of TFS server, I see registered this error:
DCOM was unable to communicate with the computer servername using any of the configured protocols; requested by PID
1080 (C:Program FilesMicrosoft Team Foundation Server 2018ToolsTfsMgmt.exe).
Error Image
I have had checked the following:
- Windows Firewall is not blocking port 80
- Reporting service is started
- User Account has required permissions
- WMI is running on the report Server
- TFS databases are in the same server than reporting services and the TFS service is running without any problem.
Please, any idea how to revolve this error will be very appreciated
tfs2017
edited Nov 9 at 22:02
Daniel Mann
36.6k65884
asked Nov 9 at 21:40
Audberto
1
add a comment |
up vote
0
down vote
favorite
When I try to integrate TFS 2017 U3 with SQL Server 2017 Reporting Services, from TFS Administration Console, an error appear. Please see screenshot.
In the event viewer of TFS server, I see registered this error:
DCOM was unable to communicate with the computer servername using any of the configured protocols; requested by PID
1080 (C:Program FilesMicrosoft Team Foundation Server 2018ToolsTfsMgmt.exe).
Error Image
I have had checked the following:
- Windows Firewall is not blocking port 80
- Reporting service is started
- User Account has required permissions
- WMI is running on the report Server
- TFS databases are in the same server than reporting services and the TFS service is running without any problem.
Please, any idea how to revolve this error will be very appreciated
tfs2017
edited Nov 9 at 22:02
Daniel Mann
36.6k65884
asked Nov 9 at 21:40
Audberto
1
Are you on TFS 2018, or TFS 2017? The path in your log message indicates it's 2018.
– Daniel Mann
Nov 9 at 22:03
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
When I try to integrate TFS 2017 U3 with SQL Server 2017 Reporting Services, from TFS Administration Console, an error appear. Please see screenshot.
In the event viewer of TFS server, I see registered this error:
DCOM was unable to communicate with the computer servername using any of the configured protocols; requested by PID
1080 (C:Program FilesMicrosoft Team Foundation Server 2018ToolsTfsMgmt.exe).
Error Image
I have had checked the following:
- Windows Firewall is not blocking port 80
- Reporting service is started
- User Account has required permissions
- WMI is running on the report Server
- TFS databases are in the same server than reporting services and the TFS service is running without any problem.
Please, any idea how to revolve this error will be very appreciated
tfs2017
edited Nov 9 at 22:02
Daniel Mann
36.6k65884
asked Nov 9 at 21:40
Audberto
1
When I try to integrate TFS 2017 U3 with SQL Server 2017 Reporting Services, from TFS Administration Console, an error appear. Please see screenshot.
In the event viewer of TFS server, I see registered this error:
DCOM was unable to communicate with the computer servername using any of the configured protocols; requested by PID
1080 (C:Program FilesMicrosoft Team Foundation Server 2018ToolsTfsMgmt.exe).
Error Image
I have had checked the following:
- Windows Firewall is not blocking port 80
- Reporting service is started
- User Account has required permissions
- WMI is running on the report Server
- TFS databases are in the same server than reporting services and the TFS service is running without any problem.
Please, any idea how to revolve this error will be very appreciated
tfs2017
tfs2017
edited Nov 9 at 22:02
Daniel Mann
36.6k65884
asked Nov 9 at 21:40
Audberto
1
edited Nov 9 at 22:02
Daniel Mann
36.6k65884
asked Nov 9 at 21:40
Audberto
1
edited Nov 9 at 22:02
Daniel Mann
36.6k65884
edited Nov 9 at 22:02
Daniel Mann
36.6k65884
edited Nov 9 at 22:02
Daniel Mann
36.6k65884
36.6k65884
asked Nov 9 at 21:40
Audberto
1
asked Nov 9 at 21:40
Audberto
1
asked Nov 9 at 21:40
Audberto
1
1
Are you on TFS 2018, or TFS 2017? The path in your log message indicates it's 2018.
– Daniel Mann
Nov 9 at 22:03
add a comment |
Are you on TFS 2018, or TFS 2017? The path in your log message indicates it's 2018.
– Daniel Mann
Nov 9 at 22:03
Are you on TFS 2018, or TFS 2017? The path in your log message indicates it's 2018.
– Daniel Mann
Nov 9 at 22:03
Are you on TFS 2018, or TFS 2017? The path in your log message indicates it's 2018.
– Daniel Mann
Nov 9 at 22:03
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
I was wrong when placing the error text messaage. I had performed a test from TFS 2018 that's the reason why I wrote with that description eror, but the productive environment is with TFS 2017 U3 and the error message is the same thing; the difference is the path where TfsMgmt.exe is located.
Thanks for your attention.
Audberto
answered Nov 13 at 14:05
Audberto
1
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
I was wrong when placing the error text messaage. I had performed a test from TFS 2018 that's the reason why I wrote with that description eror, but the productive environment is with TFS 2017 U3 and the error message is the same thing; the difference is the path where TfsMgmt.exe is located.
Thanks for your attention.
Audberto
answered Nov 13 at 14:05
Audberto
1
add a comment |
up vote
0
down vote
I was wrong when placing the error text messaage. I had performed a test from TFS 2018 that's the reason why I wrote with that description eror, but the productive environment is with TFS 2017 U3 and the error message is the same thing; the difference is the path where TfsMgmt.exe is located.
Thanks for your attention.
Audberto
answered Nov 13 at 14:05
Audberto
1
add a comment |
up vote
0
down vote
up vote
0
down vote
I was wrong when placing the error text messaage. I had performed a test from TFS 2018 that's the reason why I wrote with that description eror, but the productive environment is with TFS 2017 U3 and the error message is the same thing; the difference is the path where TfsMgmt.exe is located.
Thanks for your attention.
Audberto
answered Nov 13 at 14:05
Audberto
1
I was wrong when placing the error text messaage. I had performed a test from TFS 2018 that's the reason why I wrote with that description eror, but the productive environment is with TFS 2017 U3 and the error message is the same thing; the difference is the path where TfsMgmt.exe is located.
Thanks for your attention.
Audberto
answered Nov 13 at 14:05
Audberto
1
answered Nov 13 at 14:05
Audberto
1
answered Nov 13 at 14:05
Audberto
1
answered Nov 13 at 14:05
Audberto
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53233593%2ferror-integrating-tfs-2017-u3-with-sql-server-2016-reporting-services%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Are you on TFS 2018, or TFS 2017? The path in your log message indicates it's 2018.
– Daniel Mann
Nov 9 at 22:03