I am at wits end here.
Revit 2013 BSP - Structural Flavor
Revit Arch 2013
Working in the same project file. Revit BSP doesn't get the error. However, RAC users gets the follow error:
File <xxx> was modified by the third-party updater AREXRevitStart:Extensions:DReinfWall which is not installed.
If you continue to edit the file, data maintained by AREXRevitStart:REXExtension: DReinfWall will not be updated properly. This may create problems when <xxx> is later opened when AREXRevitStart:REXExtension: DReinfWall is present.
1) What is this extension? in question
2) How do I turn off this error OR how do I install the needed 3rd party extension
SEE IMAGE FOR FULL DETAILS
Solved! Go to Solution.
Solved by richardbeatson. Go to Solution.
Solved by dkwolek. Go to Solution.
Solved by sasha.crotty. Go to Solution.
I fixed this issue by Detaching and then Saving the Central using a different filename. This caused the Do Not Warn selection to "persist" and it no longer showed. More at: Disconnecting an API Addin or Macro Updater from a Revit Project where the code is no longer availab...
That will only fix it for 1 project!
What about the other couple of hundred on going project files 😄
Sasha,
I know that this is an old post, but I have recently begun having this issue.
We have several network licenses of BDSP and a couple network licenses of Revit Structure. We had been installing BDSP at all workstations thinking that Revit would pull from either license. As it turns out, that does not work unless we install Revit Structure instead of BDSP. We removed teh Revit BDSP installation from sebveral workstations, we installes Revit Structure to those stations, we installed the Revit Extensions from Autodesk. Now, when a station that has Revit Structure opens a file, we getthe error. When a station that has BDSP open the file, we do not get the error.
Is there another addin or extension that the BDSP pcs have, that is not on the other ones? Usually, a missing addin or macro results in this error.
Hi jandrews407,
The warning is triggering on precisely the kind of situation it is supposed to catch: that two machines are potentially going to have different behavior when modifying the model because one is missing an add-in that updates to the model based on user changes.
I think there are three options in your case:
1. Install the missing add-in on the Revit Structure machines
2. Remove the add-in from the BDSP machines and use the techniques described above to reset the file(s).
3. Ignore the error ("Continue working") on the Structure machines, particularly if those machines are not making modifications to the files (e.g. links).
Thanks,
Sasha
Thanks for the input.
We have installed the REX on the Revit Structure machines. We used the same REX intallation for Revit Structure and BDSP. I guess the question is - Does BDSP install something else as part of the install?
I can't do 2, too cumbersome with teh quantity of projects.
I can do 3, but I really don't like getting into teh habit of ignoring errors.
What is the exact add-in that's being reported in the message? I will ask someone that team to take a look.
Thanks,
Sasha
I wonder if something changed between REX versions, leaving this issue after upgrade? Did you install the exact same Extensions package on both workstations?
Hi
It happens that file saved with Revit and opened with Revit Architecture, Revit Structure or Revit MEP causes the warning about Missing Third Party Updater to be shown.
In this case it is perfectly safe to choose “Do not warn me about this updater again and continue working with the file.”
If the file is central I suggest opening it with option “Detach from Central”, choose option “Do not warn me…” and save again as a new central file using computer with not installed Revit Extensions.
After saving recreate all local copies of project on all machines.
Additionally there is an option to turn off Dynamic Model Update mechanism on all user machines by choosing Extensions->Preferences->
Dynamic update->Uncheck “Turn on dynamic model update”.
This will assure DMU not to be used and cause warning any more.
Hope that helps
We've just had this issue in the office. Re-creating the central model solved it for us.
http://whatrevitwants.blogspot.co.uk/2014/01/disconnecting-api-addin-or-macro.html
And.. here we are in 2020 with no solution and the same problem:
so do we continue to ignore it or will it get fixed ?