SQL Server with multiple installs: evaluation period has ended and SSIS packages failing

I've inherited a SQL Server box that I'm not an expert on. At the time I installed SSMS 2014 to keep an eye on the daily SSIS jobs that were running on it. I think because I'm an idiot and used the 2014 evaluation copy of SSMS, once that evaluation period stopped, the jobs stopped.

I have SSMS 2016 installed on the same machine. Is there a way to get the SSIS jobs running again if I just uninstall 2014 and use 2016 instead?

Executed as user: [*]. Microsoft (R) SQL Server Execute Package Utility Version 12.0.2000.8 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved.
Started: 8:00:00 AM
Error: 2017-04-03 08:00:00.76
Code: 0xC0000033
Source: *
Description:
Integration Services evaluation period has expired.
End Error

Error: 2017-04-03 08:00:00.76
Code: 0xC0000033
Source: ***
Description:
Integration Services evaluation period has expired.
End Error

Could not execute package because of error 0xC0000033.

Started: 8:00:00 AM
Finished: 8:00:00 AM Elapsed: 0.187 seconds.
The command line parameters are invalid. The step failed.

For clarity, here's a rough chronology of events that's led up to here:

• Feb - given access to workstation while current maintainer of it is preparing to leave. Two accounts set up on the OS (just regular old windows 10): his and mine. I install SQL Server Management Studio 2014 so I can access the DB on the computer
• Mar - I need access to an Azure SQL data warehouse, so I need to install SSMS 2016 for integrated authentication which isn't supported in SSMS 2014. I installed SQL Server 2016 on 3/14.
• Apr - old manager of the system leaves and his account is deactivated. This is when I start getting issues with 2014 saying its evaluation period has expired. This is probably true since I think I skipped putting a product key in it at the time of install. The Sql Server Agent jobs tied to the DB started failing shortly after.

SSMS is a separate free product now, with monthly updates. Uninstall the old version, then download and install the latest one. The latest version at this point is 16.5.3.

Don't download 17.0 RC3, it's still missing some important features.

BTW SSIS jobs aren't executed by SSMS. They are executed by SQL Server Agent. Once you install SSMS 16.5.3 you need to check the job history to see why they stopped, what errors occured etc.

If there is a problem with the SSIS package, you'll have to check the package's Execution history. Open the Integration Services Catalog, find the package, right click on it and select Reports > All Executions.