[ISS Support Case] Failed to Acquire a license to enable the Development Studio 2023 R2

Last updated: October 27th, 2025

Description

We are trying to do some testing of the new 2023 R2 release in anticipation of upgrading our 2017 U3 SP1 P01 system. The current license file I have for our division (PSD) is WW-6031833-53-217746-Licenses.xml dated 2023-02-24. Im able to activate these two licenses to run an all-in-one test VM but when I launch the IDE I get an error message about wspdevstudio-iocount, which Juergen pointed out might mean we need an updated license file for the new release. Can you advise on how to proceed?

Author: Kevin Modlin
Published: October 27th, 2025

Details:

Product: Application Server

Version: 2023 R2

Solution: [Solution is visible below when you're logged in and have a current subscription]

Date Created:	01/19/2024
Case:	86179

Give feedback about this article

Recommended articles

[ISS Support Case] Saving a Quick Script Resulted In EMPTY Content

Editing a script issue with a quick script error Eventually had to hit yes and the application Application Server potentially an object in side of that content. The following Errors: Have occurred scClearBinsSand: Internal.QuickScript compiler error Invalid directory. C:\Users\\AppData\Local\Temp\23\ Save Anyway?

[ISS Support Case] Trouble getting EMR400 to speak to modbus

start address: 20460 register: 2 function code: 4 320461

[ISS Support Case] SP 2023 GR Node Server OS Requirements

For a new installation we are planning on using System Platform 2023. For our current installation (SP 2017) we were told that we needed to use a Windows Server OS for our GR because of our Node Count. It looks like for SP 2023 the GR OS Server requirement is now based on the I/O count and the node count is no longer a consideration. Can you confirm that we can use a Windows 10 OS for our SP 2023 GR instead of Windows Server OS?

[ISS Support Case] Unable to update Galaxy OS Group Based security with popup warning, "Cannot configure security since templates or instances are currently checked out."

Unable to update Galaxy OS Group Based security with popup warning, "Cannot configure security since templates or instances are currently checked out." At any one time there are multiple templates and instances checked out by different users. Is there a work-a-round to this restriction?