U00063047 Unable to load StatusStore into memory. Error: '32

[James Fenoulhet]

U00063047 Unable to load StatusStore into memory. Error: '32 The process cannot access the file because it is being used by another process.'

Hi Guys

I had a support ticket raised around this error message and have found it really difficult getting a viable solution from the support team. I think they assume a certain level of technical competency with AE, which our business doesn't have due to staff levels.

So every now and then i get this error message during a file transfer and i want to do away with them. I was told the settings are controlled in the below areas. But wasn't told what those settings do or how they can be amended to prevent this status store issue.
From what i can tell, none of the errored file transfers actually needed a restart point so i assume they are created for every job regardless of whether it needs a restart?

Does anyone have experience of this error and how the resolved it?

You can define those settings in the UC_HOSTCHAR_* with the key/parameter

                                         

	FT_RESTARTINFO_CHECK
	FT_RESTARTINFO_INTERVAL
	FT_RESTARTINFO_LIFETIME

Our current settings are below

                                         

	FT_RESTARTINFO_CHECK	0:00:00
	FT_RESTARTINFO_INTERVAL	60
	FT_RESTARTINFO_LIFETIME	14

[Judith Gitahi]

Hi James, did you figure out how to resolve that issue? I am getting this error 'D:\uc4\Agents\Windows\TEMP\OACOVPFK.TXT' cannot be deleted, error code '32', error description: '32 - The process cannot access the file because it is being used by another process.', but my process is not file transfer, it's a dtsx process.

[VidyaPraveenBatchu605049]

I observed this error during my course of support earlier. Once we identified that SAP process still not released pointer to the file while UC4 file transfer is started. We prevented this by adding 1 min wait statement to the file transfer step.
And in another case it was observed some other process is using that file (looks like user working on that file)
and in other cases it was determined as temporary issue. (once restarted agent about the log and once restarted object after some time). Not sure if any other issues observed by others on this.

[James Fenoulhet]

Hi Judith
I never got a solution to the problem via support. But since upgrading to the latest version of automic i have not observed the error since i last reported it in January. The strange thing is that looking at the logging there were no files awaiting to be moved so the status store file was being written the job was failing but there was nothing to be moved in the first place.

I have seen the same error with the log file being in use by another process, we get it quite often but i have not yet looked into why it happens. I think windows is still holding onto the file while automic is trying to clean it up.