HiveBrain v1.2.0
Get Started
← Back to all entries
patternsqlMinor

"SSIS Evaluation Period Has Expired" on Dev Instance?

Submitted by: @import:stackexchange-dba··
0
Viewed 0 times
evaluationperiodexpiredssisdevhasinstance

Problem

I recently started receiving the following error on a dev server. At one point SQL Server 2016 CTP was installed here but we've upgraded since then. I've tried uninstalling / reinstalling SSIS as well as repairing it. Reboots occurred along the way. For the life of me I can't figure out why this error persists.

I've verified that the DTExec.exe is located where SQL Server expects it to be, using:

SELECT * FROM msdb.dbo.syssubsystems


...and that it's not referencing some other version of DTExec.exe previously installed on the server.

Is there anything else I can attempt to clear this alleged evaluation period?


Executed as user: (Domain\SQLServiceAccount).

Microsoft (R) SQL Server Execute Package Utility Version 13.0.1601.5 for 64-bit Copyright (C) 2016 Microsoft. All rights reserved.

Started: 11:00:01 PM

Error: 2017-01-03 23:00:54.81 Code: 0xC0000033 Source: XXXX ETL XXXX

Description: Integration Services evaluation period has expired.

End Error

Error: 2017-01-03 23:00:57.39 Code: 0xC0000033 Source: XXXX ETL XXXX

Description: Integration Services evaluation period has expired.

End Error

Could not execute package because of error 0xC0000033.

The rest of the instance is fine. It is only SSIS that is producing the "evaluation period expired" error message.

Maybe someone have accidentally used an Evaluation Edition to set up SSIS? Perhaps, but you'd think an uninstall and subsequent reinstall (using a dev edition install kit) of the service would correct that problem if that were the case.

Solution

Run regedit and change the value of CommonFiles REG_DWORD under:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\130\ConfigurationState


...from 1 to 3.

Run the Edition Upgrade and this will "upgrade" the components.

If that doesn't resolve the issue, then we need to make sure the client components are on the same service pack/build version as SQL Server. If you have applied SP1 to SQL Server, check and make sure SP1 successfully installed on the client components as well. Looking at your setup bootstrap logs will help determine that.

Code Snippets

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\130\ConfigurationState

Context

StackExchange Database Administrators Q#160002, answer score: 2

Revisions (0)

No revisions yet.