I upgraded a SQL Server 2014 occasion to SQL Server 2019 (additionally required upgrading the OS from Home windows Server 2012 R2 to Home windows Server 2019), after which patched to CU4.
In the course of the SQL Server improve course of, all the pieces confirmed inexperienced checks on the finish (together with Integration Providers), so nothing to point that there was a problem with upgrading the Integration Providers (or some other options or elements for that matter).
After doing the required reboots, now the SQL Server Integration Providers 12.Zero service won’t begin.
The Occasion Viewer Software log reveals the next for Supply SQLISService120 (Occasion ID 260):
Microsoft SSIS Service failed to start out. Error: The SQL Server
Integration Providers service requires Integration Providers to be
put in by certainly one of these editions of %SQL_PRODUCT_SHORT_NAME%:
Commonplace, Enterprise, Developer, or Analysis. To put in Integration
Providers, run SQL Server Setup and choose Integration Providers.
I’ve a legacy third occasion ETL resolution that makes use of CLR and Service Dealer which might be hard-code depending on the 12.Zero Integration Service, so I have to get this operating once more as these ETLs are failing (regardless of having the newer SSIS model put in). Let’s assume that I can not change the appliance code, so I have to get this service operating once more.
I’ve already tried to make use of the SQL S014 (with Service Pack 2) set up media to attempt to set up solely the Integration Providers function (as advised by the Occasion Viewer), however Integration Providers is already checked and grayed out, stopping me from trying to re-install it.
This third occasion ETL resolution throws the next error once they execute and fail:
Integration Providers analysis interval has expired.
Nonetheless, I am unsure if that may be a deceptive error as a result of the 12.Zero service is offline, or if it discovered the binaries however thinks it’s expired?
I wasn’t right here when this was initially applied 6 years in the past in 2014, so I do not suppose I’ve a technique to affirm if this setting began as Analysis then was upgraded to Commonplace.
I’ve already tried altering the
CommonFiles DWORD from 1 to three at
HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL Server150ConfigurationState, described in each "SSIS Analysis Interval Has Expired" on Dev Occasion? and Microsoft steerage at https://help.microsoft.com/en-us/assist/971268/evaluation-period-has-expired-error-message-when-working-with-sql-serv described in
Case three Possibility 2 part and re-running the SQL 2019 Improve Version to attempt to get it to Commonplace Version.
Unsure if this can be a clue, however following the query posed by the reply on this put up https://stackoverflow.com/questions/527839/ssis-package-fails-on-execute-integration-services-evaluation-period-has-expire/528479#528479 :
Verify what model of DTEXEC you might be utilizing as default (start-run: cmd, dtexec)
After I do dtexec from a cmd immediate, it says it is
Model 12.0.5659.1 for 64-bit which appears to point the default dtexec is the outdated one.
Is there a technique to change the default dtexec to be the brand new SQL 2019 model and maybe that can permit the third occasion ETLs to work (with no need the IS 12.Zero service)?
In any other case:
What different choices or methods do I’ve to get the Integration Providers 12.Zero service to start out efficiently in order that I can run these legacy ETLs?