I currently have a client who have been using uSync complete, they are really happy with it but came a cross an error when pushing a file (images & plain text below)
Whilst it appears that the error didn't in fact cause an issue with the process (the content was successfully pushed) my client would like to know why they were presented with an error but it was not logged?
They also use Elmah logging and would have expected it to turn up in that separate database as well.
Error while processing Push - (export/Push/0/) - Upload fail: 54a6ddc5-65fc-460a-a4f9-7ed0b4c3acfd - {"Message":"An error has occurred.","ExceptionMessage":"The file 'C:\Sites\CLIENT-ENV\CLIENT.Web\App_Data\TEMP\uSync\receive\51d6c661-c62b-4468-9ab2-a77520eba21e\files.config' already exists."
This question is more to put their mind at ease that it wasn't anything to worry about (as it worked) and for the fact that it's only happened once.
Not sure if it's worth mentioning but their network admin had not given the umbraco 8 application Write access to the web.config, but has since remedied this.
yeah seems like it was a blip, but something that should have been caught somewhere and delt with.
As you say it worked, it will have only affect the process if they where also updating templates, or files like stylesheets, (which is why the process probibly appeared to work).
but we will take a look and see if we can work out why they got this, and what uSync should actually do if it happens.
uSync error logging
Hi all,
I currently have a client who have been using uSync complete, they are really happy with it but came a cross an error when pushing a file (images & plain text below)
Whilst it appears that the error didn't in fact cause an issue with the process (the content was successfully pushed) my client would like to know why they were presented with an error but it was not logged?
They also use Elmah logging and would have expected it to turn up in that separate database as well.
This question is more to put their mind at ease that it wasn't anything to worry about (as it worked) and for the fact that it's only happened once.
Not sure if it's worth mentioning but their network admin had not given the umbraco 8 application Write access to the web.config, but has since remedied this.
Happy to answer any further questions!
Hi Rob,
yeah seems like it was a blip, but something that should have been caught somewhere and delt with.
As you say it worked, it will have only affect the process if they where also updating templates, or files like stylesheets, (which is why the process probibly appeared to work).
but we will take a look and see if we can work out why they got this, and what uSync should actually do if it happens.
Hi Kevin,
Sorry for the late reply, just want to say thanks for looking into this for us, again not a massive issue more so to put the client's mind at ease!
Take care, Rob
is working on a reply...