Cannot connect to server from Visual Studio
Depending on how I try to access it, I get different errors.
A) Just trying to login, I get "Failed to contact repository 'myusername@server'. Try again?". (I used my real user name and server, but hid it in this message.)
B) Through some attempts at setting my workspace, I got the error... "CRRTC8500E: Server Error: Failed to log in to "{url provided}": CRJAZ2381E Cannot connect to the respository at URL "{url provided}", make sure that the server is running and available.
I don't believe there is any firewall in place that stops me from accessing the server, and I am indeed able to get to the website. Other people on my team are able to access the server, and so it may be an issue on my local machine, but I do not know what.
One answer
Comments
I am not aware of the upgrade schedule of the server, though it may have been updated recently. Talking with the sys-admins over it, they say that I have a valid version still.
After some time, I was able to log in again. I am currently able to connect fine.
Looking through the logs, there are two types of errors I see.
(a) 04/20/2015 17:00:10 FilesystemUILibrary:
SyncViewDTO is null
(b) The path lib\log4j-1.2.8.jar is not valid on initJnbridge()
The path lib\shared.jar is not valid on initJnbridge()
The path lib\jacorb.jar is not valid on initJnbridge()
The path lib\xml-apis.jar is not valid on initJnbridge()
The path lib\xercesImpl.jar is not valid on initJnbridge()
The path lib\jsr173_1.0_api.jar is not valid on initJnbridge()
The path lib\plcs.jar is not valid on initJnbridge()
The path lib\ncpro.jar is not valid on initJnbridge()
The path lib\logkit-1.2.jar is not valid on initJnbridge()
The path lib\avalon-framework-4.1.5.jar is not valid on initJnbridge()
...
What do these error messages mean?
The log does not tell anything related to the login failure. The fact that you are able to login again indicates that login failure is not consistent and your client and server versions have a match. I would think that it might have been some stale session. Did you have to restart your client or kill scm.exe process?
I had restarted the application, and also rebooted my machine, with the problem continuing. I'm not sure why it resolved itself later. This seems to happen periodically, so I'm very curious to know the cause, though it is probably quite hard to determine.
You can open a support PMR so someone can investigate your problem.