All
Accepted answers
Vic Sun · Nov 10, 2025 go to post

Sure, it is documented here in the health monitor pages.

"Time (milliseconds) required to obtain a response from the listed Web Gateway server when fetching the metrics represented by the CSP sensor objects."

Vic Sun · Oct 30, 2025 go to post

My instinct is that this <WRITE> error is just indicating that there's some issue with the TLS communication. Can you confirm using another method that the certificate(s) are appropriate?
What is the error from the API when unsecured? Is there a test version of the API you can test without TLS?

Vic Sun · Oct 16, 2025 go to post

Hi Jack,

Generally it can be a bit difficult to track lock issues because there is not an after-the-fact audit of locks. To answer a question like this would likely need additional context that the WRC (support) could help you collect. In my experience, this may involve setting up a script to collect lock snapshots over intervals so you can review problem periods and cross reference which processes are running at those times and taking those locks. This could involve running irisstat / SystemCheck.

I'm not sure I follow your question about lock propagation - is this a failover mirror or a reporting mirror? If a failover mirror, locking is irrelevant. The primary is sending sets/kills and the backup member has no independent ability to lock / make changes. If R/W reporting - that would be a situation I am less familiar with, though my suspicion is that as locks are stored in memory that they are handled independently on each node.

Vic Sun · Oct 16, 2025 go to post

Hi Jack,

IRIS locking works optimistically; the lock does not do anything in and of itself. It is the responsibility of other processes to attempt to take out a lock and/or verify if an existing lock has already been taken out. Shared locking would generally be used so that multiple processes can read a value at the same time while the values are not being modified. It may take consideration of the table architecture and an understanding of the general access patterns and what types of queries you are running to efficiently only lock what is necessary and not block modifications on a large scale.

It does feel like this is a small question that fits into a bigger project so there might be more to consider. I would recommend reaching out to your ISC contact / sales engineer to discuss this in larger scope.

Vic Sun · Jul 17, 2025 go to post

If you're looking for moving individual productions, guidance like the AI bot provided might be what you need. For larger migration style events I would suggest looking at the documented migration guide, from which you can pick and choose the settings / steps that pertain to what you are looking to sync.

Vic Sun · Jun 18, 2025 go to post

First thing that comes to mind is disabling TLS 1.1 as that is deprecated. For TLS 1.3 (if that's required) you'll need to migrate to IRIS ( being on Cache 2017 probably has other security implications that would be remedied by upgrading at least to Cache latest.)

You might be able to find out more about this issue using ^REDEBUG as discussed in another post on the community, else support can probably help look into what the issue is. It's been a bit since I've worked on something like this myself.

Vic Sun · Jun 10, 2025 go to post

The file spec is pretty straightforward so it is hard to guess what could be going wrong without actually looking at what's going on. I would suggest reaching out to support.

Vic Sun · May 21, 2025 go to post

Studio is deprecated so as far as I can tell there is no Studio 2024.1.3. The version I see on offer in the WRC components is 2024.1.2, which based on the linked post may work with a later version of IRIS.

Do you have a particular need for that Studio version? The general recommendation at this point is to use VS Code instead.

Vic Sun · Apr 30, 2025 go to post

Hi Giannis,

That's just a generic login error, what is the situation you are encountering? If none of your users can login maybe you can try getting in with emergency access mode and checking the audit log / user settings.

Vic Sun · Mar 12, 2025 go to post

Glad you found that interesting! One warning I can add is that if you do decide to add a "no-integrity" type purge and if you've never run one, depending on how many messages you have you may trigger a very large purge (and a lot of journaling activity as a result). Often times when making significant purge changes, it can be safer to increment the time period you are purging bit by bit to make sure you're not asking too much of a single purge.

ex. If you run daily message purges then every day you are purging 1 day's worth. If you have "expired" messages going back a few years and decide to purge them all of a sudden, that might be a surprising number.

Vic Sun · Feb 24, 2025 go to post

On a bit of a tangent but I might recommend reviewing the following post by my colleague and considering whether a 2 phase purge schedule would make sense for you. One purge task running as standard to clean up the completed messages and one running on a lag to catch any suspended / leftover messages that are old enough that you think they could be removed:

https://community.intersystems.com/post/why-keep-integrity-important-when-purging-healthshareensemble-data

Vic Sun · Feb 10, 2025 go to post

I would generally caution against killing IRIS jobs from outside IRIS, as under rare conditions this could lead to IRIS hanging. If this is a concern I would suggest reaching out to WRC who can help you confirm that a process is safe to terminate.

Vic Sun · Feb 6, 2025 go to post

The journal does not contain the line of code (imagine needing to log that information for every single global modification), so to find the relevant code would require the type of cross referencing I suggested. The other option I would suggest would be to go through the program in the debugger. Especially if you have a general sense of where the relevant change would be made. But again, maybe the best option depends on why you are looking for this specific global set.

Vic Sun · Feb 6, 2025 go to post

Most likely more context on what you are trying to look up would be helpful to understand how best to approach this request. What occurs to me immediately is this might be a good case for involving the WRC to help investigate.

If you want to look into it yourself I think you would want to read through the journals to find the global set in question and what is being done around that set, then tracking from the process to what else it was doing at the time. You may need to have a SystemCheck / irisstat running in order to correlate the process to whatever routine it was running.

Vic Sun · Apr 17, 2024 go to post

Failing somebody who has run into this before, I would suggest opening a WRC ticket so somebody from InterSystems can look at the relevant code and see what (if anything) can be done to avoid this behavior. Once you get that reply I'm sure there would be no problem sharing with the class here 😉

Vic Sun · Feb 16, 2024 go to post

Hi Scott, just to double check that this setting is per namespace. If that isn't working, I'd suggest opening a WRC case.

Vic Sun · Nov 13, 2023 go to post

Hi Wayne,

Please try scrolling to the right. If it still doesn't work I'd contact InterSystems support to see what the issue is. There may be a network security issue preventing parts of the web page from loading.

Vic Sun · Oct 19, 2023 go to post

For posterity, the solution WRC proposed was to implement a CreateRS method allowing for the sort order to be modified by changing the SQL query.

Vic Sun · Sep 15, 2023 go to post

To piggyback off this, the initial way to run IRIS under a certain user is to use setserviceusername:

https://docs.intersystems.com/iris20232/csp/docbook/DocBook.UI.Page.cls?KEY=GSA_using_windows#GSA_using_windows_nonadminperm_change

As far as I know you can then update the credentials from services as suggested above, but you may want to keep in mind using setserviceusername if you run into other credentials / Windows permission style issues.

Vic Sun · Aug 16, 2023 go to post

Agreed with Alex. If you're seeing inexplicable issues when you think the data should be arriving correctly, I'd suggest looking at a network trace to get the details on how data is coming across.