The 'Get Container URL' is fairly obvious: to have access to what is in the container - especially when the container is set up for interactive content - FM needs to set up a 'streaming' link to that content.
The 'update reference count' - you'll have to give us some more context, what is happening before or after?
As always, thank you for your response.
First, a correction: the operation in question is called "adjust reference count" as opposed to "update file references". Sorry for the confusion there.
By ensuring that there was only one user in the system, performing this one action, we were able to narrow these top call hits down to an operation where the user is dragging and dropping a file from the OS file system into a global container field, where an onObjectModify script trigger runs a script that creates a record in our "Attachments" table, sets some keys, and copies the file from the global into a container field in the new Attachments record (in an externally stored container field), then clears the global.
The target value in the log entries for this operation is "SAI::table(142)::containers" where SAI is the file name and "142" is the afore-mentioned Attachments table.
If it's helpful, we can post the log file so you can see what we're getting.
While investigating a FMS15 crash, I also saw these two entries in the Top Call Logs.
Did you ever find out what adjust reference count means?
I've taken the issue up with FMI tech support and we've been circling in on some topics that may be at play, but I don't have a definitive answer yet. I'll post our findings here when they come.