Integration Services evaluation period has expired.

Question

Integration Services evaluation period has expired.

MyDoggieJessie

SSC-Forever

Points: 44484
More actions
December 19, 2017 at 8:37 am

#402767

I have a 3-node cluster running SQL 2014 Enterprise Edition and one of the active nodes started throwing this error last night at 2am while executing a scheduled SQL Agent job that runs an SSIS package:
"Integration Services evaluation period has expired."
Executing SELECT @@VERSION returns:
Microsoft SQL Server 2014 - 12.0.4100.1 (X64)
                Apr 20 2015 17:29:27
                Copyright (c) Microsoft Corporation
                Enterprise Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: )
When I RDP into the node and attempt to launch SSMS I get:
This is an active node in an an extremely busy OLTP production cluster...To the best of my knowledge no prior version of SQL (like an EVAL copy, etc) were ever installed on this node and this cluster was built in February 2017. Has this ever happened to anyone before? Any idea on a fix without having to reinstall everything on the node?
______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Eirikur Eiriksson SSC Guru Points: 182881 More actions · Answer 1

Guess you need to ask someone some questions, best bet is that it wasn't a clean install in the first place,
😎
Did this node have a previous live?

MyDoggieJessie SSC-Forever Points: 44484 More actions · Answer 2

No, no previous existence. I thought the same thing...perhaps it was first installed with an evaluation copy of SQL Server but don't believe it to be the case. In any event, since it was installed on 3-nodes at the same time in February...and it's been 305 days since the install, it far exceeds the 180-day trail period. The other 2 nodes appear to be fine.

______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience

MyDoggieJessie SSC-Forever Points: 44484 More actions · Answer 3

To further this "oddness", other jobs which are using SSIS on the node are running just fine...

______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience

MyDoggieJessie SSC-Forever Points: 44484 More actions · Answer 4

This node has 3 jobs that are nearly identical...and are the only ones we have that are deployed to the MSDB store...so compare the sysjobstep's command for each and noticed a difference:

The 32-bit run-time was enabled for this (which I thought we had set back on the SQL 2008 EE version prior to this server's 2014 EE build)

I reran the job, and it was successful...

Weird. So when I go to the actual node via RDP and attempt to open SSMS 2014, I still get the error about the evaluation edition being expired...yet all services appear to be running just fine.

Is it possible that someone pulled a bonehead move and initially installed a trial version of SSMS only, and then reinstalled the enterprise version on top of it? If so, why would it break after 305 days and not 180...and why would only that 1 job be affected...???

Seems to be like something changed on the actual server at the OS-level...an update, etc.

______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience

Sue_H SSC Guru Points: 90860 More actions · Answer 5

MyDoggieJessie - Tuesday, December 19, 2017 11:23 AM
This node has 3 jobs that are nearly identical...and are the only ones we have that are deployed to the MSDB store...so compare the sysjobstep's command for each and noticed a difference:

The 32-bit run-time was enabled for this (which I thought we had set back on the SQL 2008 EE version prior to this server's 2014 EE build)
I reran the job, and it was successful...
Weird. So when I go to the actual node via RDP and attempt to open SSMS 2014, I still get the error about the evaluation edition being expired...yet all services appear to be running just fine.
Is it possible that someone pulled a bonehead move and initially installed a trial version of SSMS only, and then reinstalled the enterprise version on top of it? If so, why would it break after 305 days and not 180...and why would only that 1 job be affected...???
Seems to be like something changed on the actual server at the OS-level...an update, etc.

Maybe. One thought I had is that SSIS apparently reads the version from the registry and I've seen people report similar errors when the registry get locked down more than it had been previously. So that's one possibility - can't remember which registry key but you should be able to find some similar posts.

Sue

MyDoggieJessie SSC-Forever Points: 44484 More actions · Answer 6

So...seriously a silly question but does anyone know how to fill out a support ticket with Microsoft? Every attempt I've tried on multiple browsers results in this entire section below "hiding" after selecting the options to "Determine the Severity"

Multiple attempts to load/reload, selecting/deselecting allowed me to get a shot at clicking continue, however, that results in:

Access Denied

You don't have permission to access "http://support.microsoft.com/oas/oasp_handler?" on this server.Reference #18.84ee2117.1513712409.525d60b

Frustrated.

______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience