Automatic PDM Backup Report (Doc has no Project)
Posted: Fri Nov 13, 2015 2:01 pm
Working with Kyle in Chicago office about this, but thought I would ask here as well.. Also put an enhancement request in for a administrative PDM editing tool....
Have the automatic backup setup for our Network PDM... I get the following in the email report:
Backup type: Automatic (complete)
Backup time: 11/12/2015 10:00:00 PM
Backup information:
Document has no project: Part SCM 5.A.0 - Identifier: 19_2a3fa764-5e40-42d4-9aca-5ff26d69fe1b&458753_119_0_2
Document has no project: Part BRC 5.A.0 - Identifier: 19_2a3fa764-5e40-42d4-9aca-5ff26d69fe1b&458753_210_0_0
Document has no project: Part BRC 5.A.0 - Identifier: 19_2a3fa764-5e40-42d4-9aca-5ff26d69fe1b&458753_210_0_1
Document has no project: Part BRC 5.A.0 - Identifier: 19_2a3fa764-5e40-42d4-9aca-5ff26d69fe1b&458753_211_0_0
Document has no project: Part BRC 5.A.0 - Identifier: 19_2a3fa764-5e40-42d4-9aca-5ff26d69fe1b&458753_211_0_1
I am thinking that these files are orphaned and I am trying to find a way to reunite and fix so that I do not get these warnings in the backup report. Anybody have any experience fixing this type of problem ???
Thanks,
Eric
Have the automatic backup setup for our Network PDM... I get the following in the email report:
Backup type: Automatic (complete)
Backup time: 11/12/2015 10:00:00 PM
Backup information:
Document has no project: Part SCM 5.A.0 - Identifier: 19_2a3fa764-5e40-42d4-9aca-5ff26d69fe1b&458753_119_0_2
Document has no project: Part BRC 5.A.0 - Identifier: 19_2a3fa764-5e40-42d4-9aca-5ff26d69fe1b&458753_210_0_0
Document has no project: Part BRC 5.A.0 - Identifier: 19_2a3fa764-5e40-42d4-9aca-5ff26d69fe1b&458753_210_0_1
Document has no project: Part BRC 5.A.0 - Identifier: 19_2a3fa764-5e40-42d4-9aca-5ff26d69fe1b&458753_211_0_0
Document has no project: Part BRC 5.A.0 - Identifier: 19_2a3fa764-5e40-42d4-9aca-5ff26d69fe1b&458753_211_0_1
I am thinking that these files are orphaned and I am trying to find a way to reunite and fix so that I do not get these warnings in the backup report. Anybody have any experience fixing this type of problem ???
Thanks,
Eric