SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Integration Services evaluation period has expired.


Integration Services evaluation period has expired.

Author
Message
MyDoggieJessie
MyDoggieJessie
SSC-Dedicated
SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)

Group: General Forum Members
Points: 32463 Visits: 7515
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

Eirikur Eiriksson
Eirikur Eiriksson
SSC Guru
SSC Guru (114K reputation)SSC Guru (114K reputation)SSC Guru (114K reputation)SSC Guru (114K reputation)SSC Guru (114K reputation)SSC Guru (114K reputation)SSC Guru (114K reputation)SSC Guru (114K reputation)

Group: General Forum Members
Points: 114767 Visits: 21426
Guess you need to ask someone some questions, best bet is that it wasn't a clean install in the first place,
Cool
Did this node have a previous live?
MyDoggieJessie
MyDoggieJessie
SSC-Dedicated
SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)

Group: General Forum Members
Points: 32463 Visits: 7515
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
MyDoggieJessie
SSC-Dedicated
SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)

Group: General Forum Members
Points: 32463 Visits: 7515
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
MyDoggieJessie
SSC-Dedicated
SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)

Group: General Forum Members
Points: 32463 Visits: 7515
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
Sue_H
SSC-Forever
SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)SSC-Forever (41K reputation)

Group: General Forum Members
Points: 41580 Visits: 11523
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
MyDoggieJessie
SSC-Dedicated
SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)SSC-Dedicated (32K reputation)

Group: General Forum Members
Points: 32463 Visits: 7515
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

Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search