---
title: "ServiceNow Upgrade - Kingston (Legacy)"
canonical: "https://docs.perspectium.com/space/earlierReleases/1442218/ServiceNow%20Upgrade%20-%20Kingston%20(Legacy)"
format: markdown
---
Kingston introduces some new changes which can cause your Replication to not function properly, especially with regards to comments between ServiceNow instances.

The primary issues regarding this upgrade are for Subscribing into a ServiceNow instance. One way to diagnose this is to replicate Comments [sys_journal_field] from a Helsinki instance to a Kingston instance. Previously comments were stored in the [sys_journal_field] table with respect to the parent table name. e.g. comments on incident had their table name set to task in version prior, they are now set to incident.

If you are also upgrading from a non-Jakarta based instance you may also see the issues corresponding to that, which you can [read more about here](https://docs-perspectium.atlassian.net/wiki/pages/viewpage.action?pageId=1442214). The two options below will the cover the respective issues from Jakarta.

# Version Compatibility

This will require a version upgrade where you will have 2 options:

1. Upgrade to <span style="color: #000000">vArgon Patch 3</span>
2. Upgrade to <span style="color: #000000">vBismuth</span> or greater

# Changes

The changes made are to account for both the memory constraints introduced in Jakarta, sys_class_path handling, and comment replication between ServiceNow instances.

# Extra

Please contact [support@perspectium.com](mailto:support@perspectium.com) if you have any questions or issues and we can help guide you on how you can patch your current Update Set to avoid this.