We have an app deployed in house and will often make updates by just renaming the old version of file and replace it with the new one(all the files are located on a shared network drive that everone uses) but while we are in the process of this, users are getting the 1325 error from the installer. First off, why is it doing this and second, is there a way to make it quit?

0 Comments   [ - ] Hide Comments


Please log in to comment

There are no answers at this time
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity