Using RAD 8.5.5.2 with the latest TFS plug-in on Windows 7 Professional
I get the following error when I attempt to connect to our secure TFS 2015 server. RAD 8.5.5.2 uses the Eclipse 3.6.3 platform.
Connection Failed
com.ibm.jsse2.util.j: PKD( path building failed:
java.security.cert.CertPathBuilderException: PKD(CertPathBuilderImpl
could not build a valid CertPath.; internal cause is:
java.security.cert.CertPathValidatorException: The certificate issued
by CN=State of Missouri, DC = state, DC = mo, DC=us is not trusted;
internal cause is:
java.security.cert.CertPathValidatorException: Certificate chaining error
RAD is installed in C:\Program Files\IBM\SDP and is running as an
administrator. I have imported the TFS server root certificate in
every carets file in the installation files which are
C:\Program
Files\IBM\SDP\runtimes\updi_v7X_64\uninstall\java\lib\security\cacerts
C:\Program
Files\IBM\SDP\runtimes\updi_v7X_64\java\jre\lib\security\cacerts
C:\Program
Files\IBM\SDP\runtimes\base_v7_stub\java\jre\lib\security\carets
C:\Program Files\IBM\SDP\runtimes\base_v7\java\jre\lib\security\carets
C:\Program Files\IBM\SDP\jdk\jre\lib\security\cacerts
I am trying to connect with no server running and no projects in the
workspace so I think the only file which needs the TFS root certificate
is C:\Program Files\IBM\SDP\jdk\jre\lib\security\cacerts but when that
did not fix the issue I imported the certificate into the other cacerts
files. I also imported the root certificate to my PC.
It looks like your server is using a custom SSL that is not in the certificate chain for Java. You need to add it...
https://docs.oracle.com/javase/tutorial/security/toolsign/rstep2.html
You have to use Keytool to get your companies root certificate into the store.
Do you have a WAS server installed in the workbench? Wondering if this is related to this problem
http://www-01.ibm.com/support/docview.wss?uid=swg1PI41436
If so then delete the WAS server from the Servers view, restart RAD, connect to TFS and then add WAS server again in Servers view.
If I recall correctly, this problem was solved on RAD 9.1.
Hope this helps.
Your Eclipse version 3.6.3 is out of date. To connect TFS 2015, suggest you to update the RAD version and Eclipse version to latest.
For the old Eclipse version, there has some issues with the default proxy detection. Try to go to Window -> Preferences -> General -> Network Connections and set Proxy to anything other than Native. Such as Direct, Or yo Manual and configure your proxy settings manually.
Related
I am unable to add Websphere (WAS) 8.5 in Rational Software Architect (RSA) 9.1 from New->Server in Rational Software Architect. It is asking for Installation Directory. I am not getting which path I have to give.
I tried in giving some random path, and error message gets popup 'The WebSphere Application Server installation directory is not correct.' Please help.
You may find this IBM KnowledgeCenter topic helpful. RSA is prompting you for the installation root of the app server. The default location for Linux is /opt/IBM/WebSphere/AppServer/, for Windows C:\Program Files\IBM\WebSphere\AppServer.
I had install RSA 9.1 but not WAS 8.5. Because of this, this issue is persisting.
After installing WAS8.5, we can give path C:\Program Files\IBM\WebSphere\AppServer in the installation directory and hence can create new server.
I want to install Microsoft ASP.NET Identity Core through the use of Manage Nuget Packages, but when I click the install button the following error occurs:
The underlying connection was closed: An unexpected error occurred on a send
Try pasting the following into a .reg file and run it. Then try running your NuGet command (no reboot required).
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001
Ran into this issue because TLS1.2 was not enabled (similar to Tony's response). Using http does not fix the situation because NuGet redirects to https now that TLS1.2 is enforced.
This is SSL cert issue on http://go.microsoft.com. Change the package source url to http://packages.nuget.org/v1/FeedService.svc/ which works for me.
Source: https://github.com/nuget/home
I got this error on an old customer developer VM with Microsoft Visual Studio Premium 2012:
Install-Package : An error occurred while loading packages from
'https://nuget.org/api/v2/': The underlying connection was closed: An
unexpected error occurred on a send
Solved it by going to Tools -> Extensions and Updates... -> Updates -> Visual Studio Gallery and Updated NuGet Package Manager from there.
After reboot everything worked:
NuGet has removed support for TLS 1.0 and 1.1 as of June 15, 2020.
See https://devblogs.microsoft.com/nuget/deprecating-tls-1-0-and-1-1-on-nuget-org/
If you are using VS2013 or less you have lost NuGet connectivity as of this date and you will only be able to use NuGet by upgrading at least to VS2015, although I would suggest upgrading to VS2019 to be at the latest at time of this comment.
This can also happen if you don't have TSL 1.0 enabled (disabled by default in Server 2012R2). In this case you may see some packages installing successfully before you hit the 'The underlying connection was closed: An unexpected error occurred on a send' error.
For more details on the error, run nuget install from the command line using "Verbosity detailed"
i.e.
System.Net.WebException: The underlying connection was closed: An unexpected err
or occurred on a receive. ---> System.ComponentModel.Win32Exception: The client
and server cannot communicate, because they do not possess a common algorithm
This can happen if your firewall is doing SSL inspection. You may need to white list the repo.
The only thing that helped me was switching from Windows 7 to Windows 10.
For people like me who don't really like updates details are described below.
As #Rob Farquharson have said above Nuget team threw away support for tls 1.0 and 1.1.
Some confusion is introduced by the fact that the https://api.nuget.org/v3/index.json opens perfectly through the browsers. Nevertheless, through Visual Studio we get an error "Unable to load the service index for source".
[nuget.org] Unable to load the service index for source
https://api.nuget.org/v3/index.json. An error occurred while sending
the request. The underlying connection was closed: An unexpected
error occurred on a send. Unable to read data from the transport
connection: An existing connection was forcibly closed by the remote
host. An existing connection was forcibly closed by the remote host
This happens because the browser like Chrome and Firefox maintain and ship their own ciphers. .NET applications however rely on the ciphers provided by the OS. And therefore no action will help if support is not implemented at the OS level.
Neither suggestions here nor in the question Nuget connection attempt failed "Unable to load the service index for source" could help me. I've tried approximately 10 various ways to solve the desribed issue.
I've checked registry 3 times. Installed kb3140245 twice and did others stepd for activates tls 1.2, but none of them helped. Updating VS2019 from 16.4 (released in december 2019) to 16.11.8 (released in december 2021) didn't help either.
After that I installed brand new Windows 10 with Visual Studio 2019 and error went away.
Typically this is related to the webserver not having a valid SSL certificate. An invalid SSL certificate can be due to it being self-signed and not trusted by a CA, or the certificate has been revoked by the CA.
Using the unauthenticated URL can be a workaround for the issue however the solution to the problem is to ensure the SSL certificate is valid.
In my case, we have rules blocking .EXE downloads, so we keep a copy of NuGet.exe in the .nuget solution folder, right next to NuGet.targets and NuGet.Config
For whatever reason, this was missing in the new branch.
When eclipse tries to reconnect to TFS (username.visualstudio.com) the 'authentication window' is replaced by a window that seems to describe available services and the authentication process stops here.
The content of this window is as follows:
LocationWebService
The following operations are supported. For a formal definition, please review the Service Description.
ConfigureAccessMapping
Connect
QueryServices
RemoveAccessMapping
RemoveServiceDefinitions
SaveServiceDefinitions
SetDefaultAccessMapping
With VS2010 I can still connect to TFS without problems.
Also, both with eclipse and VS2010 I can connect to codeplex (tfs).
Clearing cookies and/or cache from IE or Chrome doesn't help.
Everything is fresh installed, so I assume it's up to date.
How can I resolve this issue with Eclipse - TFS - username.visualstudio.com?
I had to reinstall the 2013 version (https://www.microsoft.com/en-us/download/details.aspx?id=40785) and everything started working. It's either a bug in an older version or mismatch with the server version being connected to.
I have this issue too. It only happens when I try to connect myuser.visualstudio.com, with my domain TFS it can authenticate without any problem.
I see that you are running Windows 7, in my case the eclipse TFS stop working with Windows 8.
On my windows 7 64bit machine, I completely install weblogic 12c but when I log into the admin console it gave me this error:
Please enable the DomainRuntimeMBean Server and the Edit MBean Server in this domain's configuration
I have tried uninstall and do a fresh install but to no avail. Any suggestion will be highly appreciated
Try deleting the pending folder within your domain root and restart the server. The default domain may be corrupted.
http://weblogicfordummies.blogspot.com/2008/10/wls10please-enable-domainruntimembean.html
I have Windows 7 64bit. I had Sql Server 2008 R2 Express installed. I unistalled it and then I tried to install Sql Server 2008 R2 Web. Unfortunatelly on the Setup Support Rules page for 'Consistency validation for SQL Server registry keys' I got 'Failed'. I spent half of a day trying to solve it, but then I assumed that there must be realy something wrong with registry keys and it will be faster just to reinstall Windows.
After formatting the disk and reinstalling Windows 7, rebooting dozen of times I installed all Windows upadtes as well. I also did install some programs like Skype, Thundirbird etc. which has no influence on Sql Server setup.
And then I tried again to install Sql Server 2008 R2 Web. And again an error. A bit different one. Now when the setup is on the Setup Support Rules page I get an error message box with the title "FixSqlRegistryKey_x86 - Application Error" and content: The application was unable to start correctly (0xc000007b). Click OK to close the application. 'Consistency validation for SQL Server registry keys' gets 'Failed' status as well.
My team mate has exactly the same machine as mine. He had no problem with installation (he didnt even need to reinstall Windows).
I run the setup as administrator, from a local folder. I even tried to use the setup files copied from my team mate, for a case if my copy is corrupted. In the setup options I have chosen the 'x64' version.
Any ideas what can be the reason of the problem?
Problem solved.
Someone suggested to me that Web edition should not be installed on Win 7 (just on Windows Server). So perhaps installing a different version would work. My team mate perhaps succeeded acidentially - due to having sql server installed already in express edition... but it is just a guess.
Before I tried to install another edition of SqlServer, I downloaded 2008 Express version and I started the install. From the temporary folder created by the express edition I copied FixSqlRegistryKey_x86.exe file and I had overwritten the problematic file in the Web setup with this file.
I started the setup again. It passed the verification this time. But has crashed on a later point - setup unpacks the installation files to C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2 and runs from it. So I needed to again overwrite the problematic file in this location. Now the installation succeeded.