Thank you for your anwser. Moving to REST now is not an option as the product is already deployed in live server.

To be clear, Invalid column name means the column doesn't exist in the result set.

The result set's returned columns aren't always fixed like the example I wrote above. The returned columns are dynamic due to they are left joined through some several tables.

What Kevin Chan and Warlin Garcia said about looping through the metadata's column name to check if the column exist in the result set maybe the only proper method so far.

It seems like this is a downside of Health Share studio as there isn't any solution to prevent this.

As stated by G Klein, studio becomes really annoying if it some how loses TCP/IP connection. The work-around I've used so far is increase the session timeout limit to high value (9999999), the issue still happens sometime, though.

Hello,

Is there any difference of in-place conversion feature on different HealthShare instances?

I am trying to do inplace-conversion with HealthShare 2018 to IRIS, the installer is supposed to ask me what instance (Cache, Ensemble, HealthShare,...) I want to convert, but it isn't. It just go on full install a new IRIS.

Am I missing something?

Hey there, 

I just had the same error code 112 and resolved it. Maybe you guys find this post helpful.

Step to reproduce:

- Install cache or healthshare, run it atleast one time successfully.

- Change your computer name

Error shown in <install-dir>\mgr\console.log:

2 cache.ids file was created by node Old computer name, and this machine is New computer name

Resolving method:

Delete this cache.ids file and turn off cache/healthshare instance. After that, everything works normally.