Upgrade Utlility - creates duplicate files in root directory?

[kenmarcus]

Was checking to see if anyone has experience the following issue with the Revit 2009 family upgrade utility?

When we run the utility, everything works fine but for some reason we are also getting a duplicate of every family created in the root directory where the upgrade.txt and upgrade.bat files are located. The duplicate families have all been automatically renamed with a series of numbers after the family name.
Original family named:
BSA E1 30 x 42.rfa

Is renamed as a duplicate family:
BSA E1 30 x 42_20080707-190809-234.rfa

All of the familes have the 20080707- at the start but then the values afterward are different. When i check the journal file, the following line of code is added:

2:< [ISL] Created backup for remote file: R:\Revit 2009\BSA Content library\BSA E1 30 x 42_20080707-190809-234.rfa
' 0.405200 2:<<m_oSaveToTempFile->commit

I have also attached a screen capture from a sample of the other files.

[clay_hickling]

Same thing happens to me. This does not seem normal or useful.

[bcgatti]

I've done a couple of test upgrades and have come up with a couple of different results.

If I perform the upgrade on my local drive (c drive) I to not get the extra files.

If I upgrade the files on a "mapped" drive letter I get the same results that you bring up in your initial post (extra files with a date stamp on them).

Based on this very basic test, it looks to me that upgrading these files on the mapped network drive is what is resulting in the extra files.

I've always done the upgrades to a copy of our library items on my local computer and I have never seen these extra files. Once the upgrade is done I copy the files to the proper location on the network.

We use UNC pathing on our network (UNC paths are not supported when using the file Upgrade_RFA.bat) so I've never tried upgrading on a mapped network drive before.

Brett

[kenmarcus]

thanks for the testing but it seems that moving my entire library from my network to my local machine and back just to avoid getting the duplicate families is a lot of unnecessary work and time. It shouldn't matter where I choose to run the upgrade utlility, it never did in the past so the question is what changed and why?

Here are samples that were modified for Revit 9.1 to both upgrade families and delete all backup families. These were run from a local machine but are pointing to a network location.