Tip: Service Studio 5.0 error form pops up everytime you attempt to open it
Certified

Tip: Service Studio 5.0 error form pops up everytime you attempt to open it
Certified

  
Hi All

Recently, the OutSystems R&D as identified a Service Studio 5.0 error while opening the Service Studio application, which prevents the developers to actually continue using the Service Studio 5.0. Although this problem has been identified and it be fixed in the next Service Studio 5.0 revision patch, it's likely that many users using the revision patchs from 5.0.2.17 through 5.0.2.19, will hit on this problem. On that regard, please check below how to overcome the Service Studio error, at least until the next revision patch is made available.

Symptoms:

When you attempt to run the Service Studio 5.0, a submit feedback error form pops up, and after closing that form then the application is terminated. This can happen if you execute the Service Studio 5.0 using your Start Menu or command line, or even you you attempt to double-click an espace to open it in Service Studio 5.0. If you press the Click here link on the form, as shown in the picture, you'll see the details of the error, including the main exception.











You should find an exception message like:

System.ArgumentException: Version string portion was too short or too long.

Either you press Send Feedback of Don't Send, the Service Studio will close, preventing you from developing new or existing espace. We urge you to always press the Send feedback button so OutSystems can track the most common error reports from the Agile Platform tools, and improve the quality of our products.

Please note that this problem can happen in Service Studio revisions from 5.0.2.17 to 5.0.2.19.

Cause:

This problem is caused by a corrupted cache value of the latest available version of the Service Studio 5.0, which as saved on the last time Service Studio was opened, and whenever Service Studio attempts to check that value against the OutSystems TechCenter, it will fail with this error. We acknowledge that this is a problem with the OutSystems Service Studio 5.0, and it will be fixed in the next revision patch.

Resolution:

The solution to this problem is to clear the cache of the Service Studio 5.0, deleting the corrupted value of the latest Service Studio 5.0 version. This, however, will not only clear the cache of the latest available Service Studio version, but it will also delete the cached values for connected servers, usernames, and some other UI options.

To clear the cache of the Service Studio 5.0, you'll need to:
  1. Open a command prompt window, and navigate to the Service Studio installation folder (e.g., C:\Program Files\OutSystems\Service Studio 5.0)
  2. Execute the following command: servicestudio.exe -resetSettings
After this, you should be able to open the Service Studio 5.0 again without hitting on this error again. If by any change, until you patch the Service Studio with the upcoming new revision patch, you hit this problem again, just apply the resolution above again.

Feel free to drop me a line at the forums or a private message if you have any problems related to this subject.

Cheers

Miguel Simões João
Hi All

Just updating this with the information that OutSystems released a new Service Studio 5.0 revision that fixes this problem. If you patch your Service Studio 5.0 with revision 5.0.2.22 or higher, you'll not get affected by this problem again.

It's available for download at Agile Platform 5.0.

Cheers

Miguel Simões João