Visual Studio 2008 unable to create repository connection
Hi there,
Pretty much as the topic says. I've got an install of Visual Studio 2008, that I've tried to install the RTC plugin into. I've tried the 1.0.1.1 IBM License manager version, and also the Beta 2 that is a .msi file. Both have the same problem. When I open the "Team Artifacts" view, a new pane opens up, with Repository Connections and My Repository Workspaces. I right click on Repository Connections, and select New Jazz Repository Connection. As soon as I click in the text box for username, Studio crashes, and tries to send a report to Microsoft. It doesn't seem to matter if I've put in a server or not, it happens every time. Any thoughts on what I can do do get past this? Cheers, Chris |
10 answers
Hi there, Hi Chris What edition of VS, and RTC (Express/Std/etc)? Also - are you running anything else like a connection to MS Team Foundation Server or is this a completely clean install of VS. anthony |
Can you please open a work item on jazz.net and put the screen shots of the dialog just before it crashes.
Just keen to know the server url that other details that you are putting in the box. Also I would recommend that you use the release version of the product and not the beta. The release version use IBM install manager and not the MSI. If you have installed a version using MSI , you should first remove it using the Add/Remove program. Keen to hear from you. Regards Sandeep Dev Lead, RTC for VS IDE |
Can you please open a work item on jazz.net and put the screen shots of the dialog just before it crashes. Apologies for the lateness of the response, I ended up copying the code into an eclipse workspace and got it checked in, and forgot about this problem. Answering the questions - Microsoft Visual Studio 2008 Version 9.0.21022.8 RTM No connections to anything else that I'm aware of RTC Standard-Full, I've tried both the MSI and the IBM Install Manager versions (as has been pointed out the MSI is the beta, so I'm now using the Install Manager version). It is an otherwise clean version of VS, I only installed it to do this one piece of work, but it ties in with other stuff we're doing through RTC hence trying to check in the projects. I'll crack on and sort out a work item on jazz.net too, with screen shot (the server is an internal one to our intranet) Thanks, Chris |
Can you please open a work item on jazz.net and put the screen shots of the dialog just before it crashes. Apologies for the lateness of the response, I ended up copying the code into an eclipse workspace and got it checked in, and forgot about this problem. Answering the questions - Microsoft Visual Studio 2008 Version 9.0.21022.8 RTM No connections to anything else that I'm aware of RTC Standard-Full, I've tried both the MSI and the IBM Install Manager versions (as has been pointed out the MSI is the beta, so I'm now using the Install Manager version). It is an otherwise clean version of VS, I only installed it to do this one piece of work, but it ties in with other stuff we're doing through RTC hence trying to check in the projects. I'll crack on and sort out a work item on jazz.net too, with screen shot (the server is an internal one to our intranet) Thanks, Chris Defect 85510, thanks. |
|
Is it possible to do a net meeting and resolve the issue. My suspicion is that there is something wrong with the installation of VS or WPF, because what is failing is the most basic case ( login to repository ) and we have not heard it from any other place including my own team, where we use RTC VS client exclusively for any development.
|
Is it possible to do a net meeting and resolve the issue. My suspicion is that there is something wrong with the installation of VS or WPF, because what is failing is the most basic case ( login to repository ) and we have not heard it from any other place including my own team, where we use RTC VS client exclusively for any development. Hi there, I don't think we'll be able to do a netmeeting to look at this, it's probably technically possible but I have a feeling it'd go against our conduct guidelines. Is there anything else I can try - apologies again for the late reply, but I'm not getting notifications of replies, and I haven't checked back for a while. The Work Item is still open afaik though. Thanks, Chris |
Could you uninstall the 1.0.1.1 Client and try with the 2.0 version that we just released? I know that's a pain and I apologize, but we need to zero in on the problem and if it works with 2.0, then we'd need to investiagate on the client side and if it still fails, it's more likely to be a bug in WPF. From what you stated, it doesn't look that you've installed anything on top of VS except for RTC, right?
Is it possible to do a net meeting and resolve the issue. My suspicion is that there is something wrong with the installation of VS or WPF, because what is failing is the most basic case ( login to repository ) and we have not heard it from any other place including my own team, where we use RTC VS client exclusively for any development. Hi there, I don't think we'll be able to do a netmeeting to look at this, it's probably technically possible but I have a feeling it'd go against our conduct guidelines. Is there anything else I can try - apologies again for the late reply, but I'm not getting notifications of replies, and I haven't checked back for a while. The Work Item is still open afaik though. Thanks, Chris |
|
Sure, I can give that a go. In fact, I'd probably have to do that anyway as we're moving to a 2.0 server soon anyway. I'll let you know how I get on.
Could you uninstall the 1.0.1.1 Client and try with the 2.0 version that we just released? I know that's a pain and I apologize, but we need to zero in on the problem and if it works with 2.0, then we'd need to investiagate on the client side and if it still fails, it's more likely to be a bug in WPF. From what you stated, it doesn't look that you've installed anything on top of VS except for RTC, right? Is it possible to do a net meeting and resolve the issue. My suspicion is that there is something wrong with the installation of VS or WPF, because what is failing is the most basic case ( login to repository ) and we have not heard it from any other place including my own team, where we use RTC VS client exclusively for any development. Hi there, I don't think we'll be able to do a netmeeting to look at this, it's probably technically possible but I have a feeling it'd go against our conduct guidelines. Is there anything else I can try - apologies again for the late reply, but I'm not getting notifications of replies, and I haven't checked back for a while. The Work Item is still open afaik though. Thanks, Chris |
|
The problem turns out to be a WPF problem.
Here's a workaround suggested in the WPF forums on MSDN that should get you past the crash: Navigate to Control Panel > Regional and Language Options > Languages Tab > Details... Button > Advanced Tab > Check "Turn off advanced text services" Microsoft says the fix for this bug will be included in the .NET Framework 4.0. Here's a link to the post for reference: http://social.msdn.microsoft.com/Forums/en-US/wpf/thread/67f96f9c-113e-4a72-ab2a-d1bb142be24b Sure, I can give that a go. In fact, I'd probably have to do that anyway as we're moving to a 2.0 server soon anyway. I'll let you know how I get on. Could you uninstall the 1.0.1.1 Client and try with the 2.0 version that we just released? I know that's a pain and I apologize, but we need to zero in on the problem and if it works with 2.0, then we'd need to investiagate on the client side and if it still fails, it's more likely to be a bug in WPF. From what you stated, it doesn't look that you've installed anything on top of VS except for RTC, right? Is it possible to do a net meeting and resolve the issue. My suspicion is that there is something wrong with the installation of VS or WPF, because what is failing is the most basic case ( login to repository ) and we have not heard it from any other place including my own team, where we use RTC VS client exclusively for any development. Hi there, I don't think we'll be able to do a netmeeting to look at this, it's probably technically possible but I have a feeling it'd go against our conduct guidelines. Is there anything else I can try - apologies again for the late reply, but I'm not getting notifications of replies, and I haven't checked back for a while. The Work Item is still open afaik though. Thanks, Chris |
|
Brilliant, that fixes it. Thanks for digging it out!
Cheers, Chris The problem turns out to be a WPF problem. Sure, I can give that a go. In fact, I'd probably have to do that anyway as we're moving to a 2.0 server soon anyway. I'll let you know how I get on. Could you uninstall the 1.0.1.1 Client and try with the 2.0 version that we just released? I know that's a pain and I apologize, but we need to zero in on the problem and if it works with 2.0, then we'd need to investiagate on the client side and if it still fails, it's more likely to be a bug in WPF. From what you stated, it doesn't look that you've installed anything on top of VS except for RTC, right? Is it possible to do a net meeting and resolve the issue. My suspicion is that there is something wrong with the installation of VS or WPF, because what is failing is the most basic case ( login to repository ) and we have not heard it from any other place including my own team, where we use RTC VS client exclusively for any development. Hi there, I don't think we'll be able to do a netmeeting to look at this, it's probably technically possible but I have a feeling it'd go against our conduct guidelines. Is there anything else I can try - apologies again for the late reply, but I'm not getting notifications of replies, and I haven't checked back for a while. The Work Item is still open afaik though. Thanks, Chris |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.