shaneturner12
Tutorial Creator
Moderators - if this is in the wrong place, please move it to the correct place.
Hi Trainzers,
I have made a very interesting discovery involving Content Manager and the way that content is stored in the UserData folder.
As some will know, when an asset is installed (regardless of method) it gets put into the relevant folder in UserData.
What I have found though is due to a suspected bug in TADDaemon, it occasionally causes a folder with a name beginning with 'copytemp', which should normally be 'kuid xxxxx xxxxx' or 'kuid2 xxxxx xxxxx'.
This means that if the affected asset is opened for edit, TADDaemon will crash, as it cannot rename/move the folder correctly. I have reproduced this with certain assets including the FGA container wagons.
Can N3V investigate this please, and release patches if necessary.
Due to the nature of the issue, it does not always happen, but it can be checked by performing a search in the UserData folder for 'copytemp', then attempting to open the assets mentioned in these folders for edit.
I have previously sent a message to Helpdesk about this, but it seems nothing has been done about it. It seems that it's mainly affectting content imported from previous versions, and content installed from a CDP file.
Another way of checking is when the crash reporter box appears, there is a link for further information. Click this, and look in the bottom section for references to 'copytemp'.
Shane
Hi Trainzers,
I have made a very interesting discovery involving Content Manager and the way that content is stored in the UserData folder.
As some will know, when an asset is installed (regardless of method) it gets put into the relevant folder in UserData.
What I have found though is due to a suspected bug in TADDaemon, it occasionally causes a folder with a name beginning with 'copytemp', which should normally be 'kuid xxxxx xxxxx' or 'kuid2 xxxxx xxxxx'.
This means that if the affected asset is opened for edit, TADDaemon will crash, as it cannot rename/move the folder correctly. I have reproduced this with certain assets including the FGA container wagons.
Can N3V investigate this please, and release patches if necessary.
Due to the nature of the issue, it does not always happen, but it can be checked by performing a search in the UserData folder for 'copytemp', then attempting to open the assets mentioned in these folders for edit.
I have previously sent a message to Helpdesk about this, but it seems nothing has been done about it. It seems that it's mainly affectting content imported from previous versions, and content installed from a CDP file.
Another way of checking is when the crash reporter box appears, there is a link for further information. Click this, and look in the bottom section for references to 'copytemp'.
Shane