During configuration of Plastic SCM client - server connection on several machines I receive an error:
This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms
This is on Windows 7 enterprise SP1 64 bit
FIPS support was added to Plastic SCM BL700 back in Oct 2015 as you can find here
Related
One of our client wants to move from TFS 2013 to TFS 2018. We don't have much information about the current TFS setup at client's end.
Can anyone please guide with what questions we need to ask to client to get the information regarding the current TFS system setup before we start with upgrade process.
Also share if there is any process document regarding upgrading the TFS 2013 to TFS 2018.
Thanks in advance.
You need to confirm the real requirements first, need to upgrade or migrate?
Check if the current device, OS and software match the Requirements and compatibility for the upgrade/migration :
Client operating systems:
TFS 2018 Windows 10 (Professional,Enterprise) Version 1607 or greater
TFS 2013 Windows 8.1 (Basic, Professional, Enterprise) Windows 7
(minimum SP1) (Home Premium, Professional, Enterprise, Ultimate)
SQL Server:
TFS 2013 Update 4 - SQL Server 2014 or SQL Server 2012 (minimum SP1)
TFS 2018 - SQL Server 2017 or SQL Server 2016 (minimum SP1)
Upgrade is a full data transfer. You will have all data in the previous TFS.
As TFS 2018 only supports SQL Server 2017 and SQL Server 2016 (minimum SP1), upgrade SQL Server is necessary.
You need to go through article Upgrade your deployment to the latest version of TFS before doing upgrade. And follow the steps in article Upgrade scenario walkthrough for Team Foundation Server to upgrade your TFS. Summarize the steps here:
Prepare your environment. The first step is to check the system
requirements for TFS 2018. Upgrade SQL Server is necessary for your
scenario. Including SQL Server, you also need to check other system
requirements and prepare the environment.
Expect the best, prepare for the worst. You must have a complete and
consistent set of database backups in case something goes wrong.
Do the upgrade. Once the preparation is done, you'll need to install
the new version of TFS to get new binaries, and then run through the
upgrade wizard to upgrade your databases.
Configure new features. Depending on what version you upgraded from,
you may need to configure each team project to gain access to some
of the new features made available.
Below threads for your reference:
https://blogs.msdn.microsoft.com/rob/2016/12/22/upgrading-from-tfs-2013-to-tfs-2017/
TFS 2012 to TFS 2018 Migration/Upgrade Path
I have a production system which had installed SQL Server 2012, so this system has the Integration Services 11. Then we upgraded the system with SQL Server 2014, so the system had two Integration Services 11 & 12. Then we upgraded to SQL Server 2016, so the system has now three Integration Services 11, 12 & 13.
I done some research on the Internet and i realized that even we upgrade the SQL Server the integration services are installed side-by-side. This is also confirmed from SQL Server Management Console.
When i run DTEXEC on CMD get default version 11, this means that my DTSX packages inside the SSISB Catalog are running using the Integration Services 11 and not the latest one? If this is correct how can i change this to the newest one?
I was recently part of such discussion. It is important to understand SSIS Backward compatibility before.
Also, refer SSIS through its SQL Server Data Tools version, as most commonly people understand it in that way. You can link your thoughts with below mentioned details:
SQL Build# PackageFormatVersion Visual Studio Version(SSDT)
2005 9 2 2005
2008 10 3 2008
2008 R2 10.5 3 2008
2012 11 6 2010 or BI 2012
2014 12 8 2012 CTP2 or 2013
2016 13 8 2015
source: sqlstudies
From this microsoft document you'll understand which SSIS version is compatible with which SQL Server.
Briefly:
Target version of SQL Server Development environment for SSIS packages
2016 SSDT 2015
2014 SSDT 2015 or SSDT-BI 2013
2012 SSDT 2015 or SSDT-BI 2012
In simple words, SSDT 2015 is capable of deployment on any server from 2012 onwards, whereas 2012, 2013 are restrictive.
Beware that, if you open sql server 2012 dtsx in SSDT 2015, then you cannot go back to open it from SSDT-BI 2012.
If this is correct how can i change this to the newest one?
Hence, if you want to upgrade all your packages, open them through SSDT-2015, select deployment version(right click project -> properties -> Target Server Version).
you can read more about these changes here(MSSQLTips)
I think the previous answer provides some very useful information. However, I think I understand the misconception here:
First, there is NO benefit or advantage of "changing this to the newest one". Some people think that SSIS 2016 (11) is better than SSIS 2014 (10) or lower - the fact is that , with SSIS2012 nothing changed except addition of several new features and a new way to deploy items. You will not obtain any speed or performance enhancement. It's just that you get access to a few extra components.
Second, this will never fail because of my answer above. Firstly, SSIS is backward compatible (which is what Microsoft brags about - but honestly, why wouldn't it be?? it's the exact same product sold under different titles, why would it NOT be backward compatible). Secondly, your previous editions of SSIS are there for those like a few features (such as ActiveX) to run in compatibility mode. All in all, I think the question is answered by the fact that SSIS is backward compatible and that NOTHING has changed in the past 3 editions of the product (2012, 2014 and 2016 are nearly identical, and no performance or architectural changes exist between 2008/2008R2 and 2012+)
If you'd like more information, have a look at this link, which starts off by stating:
SQL Server 2014 Integration Services (SSIS) can co-exist side-by-side
with SQL Server 2008 Integration Services and SQL Server 2012
Integration Services.
I tried to start an instance of SQLLOCALDB 2017 on win7 (x64) but this message box Appears :
"The procedure entry point BCryptKeyDerivation could not be located in
the dynamic link library bcrypt.dll"
Anybody knows it's reason?
more info from CMD:
Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft
Corporation. All rights reserved.
C:\Users\hashem-7-x64>SQLLOCALDB INFO MSSQLLocalDB
C:\Users\hashem-7-x64>SQLLOCALDB VERSIONS Microsoft SQL Server 2017
(14.0.1000.169)
C:\Users\hashem-7-x64>SQLLOCALDB START MSSQLLOCALDB Start of LocalDB
instance "MSSQLLOCALDB" failed because of the following error: Error
occurred during LocalDB instance startup: SQL Server process failed to
sta rt.
C:\Users\hashem-7-x64>
I had the same problem and I resolved it by uninstalling Sql Server LocalDB 2017 and installing the 2014 version.
Apparently the 2017 version is not compatible with Windows 7.
SQL Server 2017 Express LocalDB isn't supported on Windows 7. The SqlLocalDB.msi installer for me but when I tried to start an instance it would give the "BCryptKeyDerivation could not be located" error. Anecdotally the 2016 version is supposedly not supported, but it installed and default instances run for me.
Per Microsoft :
Supported Operating System:
Windows 10 , Windows 8, Windows 8.1, Windows Server 2012, Windows
Server 2012 R2, Windows Server 2016
Some additional information indicating that you'll need at least Windows 8
BCryptKeyDerivation function
The BCryptKeyDerivation function derives a key without requiring a
secret agreement. It is similar in functionality to BCryptDeriveKey
but does not require a BCRYPT_SECRET_HANDLE value as input.
Minimum supported client
Windows 8 [desktop apps | UWP apps]
Minimum supported server
Windows Server 2012 [desktop apps | UWP apps]
Install DotNET Core v2 SDK (More specifically v2.1.4 as of now)
The problem is caused by the version of assemblies for cryptographic algorithms currently installed on your PC offered via DotNET:
System.Security.Cryptography
System.Security.Cryptography.Cng
The mentioned update provides the missing dependencies. Read more about the dependencies on Nuget information page.
Install Sqllocaldb 2016 that work great in windows 7. i facing the same problem last few days and finally i get the answer to install localdb 2016. sqllocaldb 2016 support very well and even we don't need to downgrade the database version.i try sqllocaldb 2014 to but it get me error the database version is not supported. but sqllocaldb 2016 support great sqllocaldb 2016
I'm following the online installation example (https://www.youtube.com/watch?v=7ElSGLkprkY) to install PeopleSoft with PeopleTools on Windows 7 with SQLServer 2008 R2.
My PS and PT installation version differs from the online videos since I'm using most recent available versions:
PeopleSoft HM 9.2
PeopleTools 8.55
Tuxedo 12.1.3.0.0 with VS2012
WebLogic 12.1.3.0.0 64bit
JDK 7u55 x64
SQL Server 2008 R2
I could install each element with no error, excepted one VIEW during HC database creation (PS_EP_APPRMOB_PNDG), but I could re-create the view manually by slightly modifying the SQL query.
Now I'm trying to configure the Web (PIA) Server and I encounter an error while creating the domain. The piainstall_HC.log file contains following:
Tue Sep 20 09:48:32 CEST 2016:Starting PIA installation...
PS_HOME: c:\PT8.55
Install Action : CREATE_NEW_DOMAIN
Creating Domain...
Deploying Web Applications...
Deploying WebLogic Extension files...
Deploying PeopleSoft Site files...
Deploying PeopleSoft Site Doc files...
Completed.
PS_CFG_HOME: C:\PS_CFG_HOME
PIA_INSTALL_FAIL
After intensive googling, I found that some other people got a similar issue which was caused by a wrong version of the JDK: the JRockit jvm was required.
Of course I tried to use JRockit JDK 64bit, but I still get the same error. I also tried several other oracle JDK versions, among others the JDK 7u55 x64, which is provided with PeopleTools installation elements.
Unfortunately, I definitively get the same error and cannot find any other logfile which could give more information on the root cause.
Did someone experienced the same issue and could fix it ?
Thanks for help
I finally could fix the issue.
It seems that my error was to install the wrong weblogic version: originally, I installed weblogic by using the "setup_fmw_12.1.3.0.0_ohs_win64.exe" installer which was provided with PeopleTools.
It appears that the other one (fmw_12.1.3.0.0_wls.jar) was expected. After installing this version (with "Coherence"), the domain could be created successfully.
I see on github for windows it's for windows 7 and 8.
can you install it on windows server 2008 r2?
i have a fire walled server that is for our .net code as our team foundation server so I was going to use the same server to host our source control for cocoa/mac applications we have...
If you are after a Git server (as in able to host git repos), you can consider, on Windows, the Bonobo Git server.
It knows how to interface with IIS, and is compatible with various Windows releases, including windows server 2008 r2.