Service Operations Workspace (sn_sow) version 4.0 needs to be purchased

[Rook_Beyond20]

Running into a situation on both a Demo instance and a PDI where installing any of the Service Operations Workspace add-ons/plugins (such as the ITOM Applications) results in the above error.  Service Operations Workspace is already installed but cannot be updated, because of the same above error. 

1. Doing a search on "sn_sow" in the Store and in the Application Manager comes up with nothing, not even the Service Operations Workspace application page(s).
2. Nowhere does the version "4.0.0" show up.  Versions include data such as "24.0.3 (latest)".
3. Having an ITOM license seems to have no effect, so it doesn't seem to be a licensing obstacle, despite the ITOM Operator Professional dummy being installed and present.
4. Opting-in to the ITOM Service Operations Workspace entries in the Store does not seem to enable it (on either instance), even though I didn't expect that to have a true impact since these are not Production instances.

Any thoughts of things to try would be welcome.  I have a HI Case open on this, but it is (of course) Low Priority.

[Maik Skoddow · Accepted solution]

Hi @Rook_Beyond20 

I think it's the best to raise a support ticket as the Community has no insights into the Store management and thus cannot help you.

Maik

[Maik Skoddow · Accepted solution]

Hi @Rook_Beyond20 

I think it's the best to raise a support ticket as the Community has no insights into the Store management and thus cannot help you.

Maik

[Rook_Beyond20]

As I posted, I do have a HI Case open, but I don't expect any sort of rapid resolution due to it being a Low Priority.

[marcos_castro]

I'm facing the same problem on my PDI. I'm trying to get into Process Automation Designer and was getting a error related to not having the Remedial Actions Framework installed for two process that come with it (Remediate server and Remediate device). Since this plugin is a part of the Service Operations Workspace package, I'm kinda stuck there.

[Andy Smith2]

Having the same problem in one of our Demo Instances.

Hunted in the Store for "sn_now" with no luck.

I've posted this here just to let you know that you're not alone. 

Happy New Year!

Andy