I don’t think this is strictly a Filemanager question but it is part of the question.
I have a C6 application that is being hosted on Azure for some users and self hosted on local PCs for other users.
The latest update has some file changes and it is triggering a Filemanager process to convert some TPS files, which I suspect haven’t been updated in some time. This update process is working fine for all the self hosted users but about half of the Azure hosted users are getting a problem with the updated files.
I’m not 100% sure what the problem is, it could be that…
-
The file is being updated, but the temporary file created is not being renamed to the appropriate file name, so when the app runs the customer.tps file, for example, is empty.
-
The file has a corruption of some sort? The techos who handle this report that restoring the original file and running TPSFix before calling the Filemanager process allows Filemanager to complete successfully.
I haven’t dug too deep into the process at this stage, I am unable to reproduce it, even with the original data that has problems on Azure, but I’m not running it on Azure.
Does anyone have any insight into what might be happening? e.g. a resources issue with Azure?
TIA for any advice.