Announcement

Collapse
No announcement yet.

Can't Manage C4R projects?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Can't Manage C4R projects?

    Is anyone else having problems managing their C4R models? For several days whenever my coworker or I have tried to access the "Manage A360 models" button (2017.0.3) the message "A360 projects that contain A360 models cannot be retrieved at this time. Please try again later." appears. I could understand it being flaky when trying around the time either C4R or Bim 360 was down or degraded, but they aren't now, and we need to get models published.

    I've tried opening the Manage A360 models dialog with and without a project opening, after signing out, restarting Revit and resigning in - no changes. I have sent a comment to Autodesk through the health dashboard dialog.

    Attached Files
    Julie Kidder
    Architect + BIM Director
    Hartman + Majewski Design Group

    #2
    Sorry about that. We've seen this happen when the version of Revit 2016 is newer than the corresponding C4R code that's installed. What's confusing is that you list 2017 as the version, which includes the corresponding C4R addon update as part of the install. My working theory is that you guys might have gotten a deployment of a Revit update, but not the corresponding C4R addon. Easiest solution, assuming you are at liberty to install updates, would be to install Revit 2017.1, which will fix the mistmatch + get you running on the latest, most stable code.

    -Kyle
    Director
    Building Design Strategy

    Comment


      #3
      We're small enough that we don't deploy, and the projects we're trying to update are Revit 2017. When 2017.1 came out it seemed that people were having issues with cloud models, so I was holding off on updating until those issue shook out. If I update my version to 2017.1 to test will it cause problems for anyone on 2017 if we're working on it in different versions? I'd like to test it before having everyone else update.
      Julie Kidder
      Architect + BIM Director
      Hartman + Majewski Design Group

      Comment


        #4
        As a general rule, working across update versions in C4R isn't a problem. In this case, however, the 2017.1 update does change branding to BIM 360 Team, which updates the file path saved in Revit. We've seen side-by-side issues that arise as a result, so I wouldn't recommend it unless everybody moves forward.

        If you still have the installer for your update kicking around (probably in C:\Autodesk) then try to re-run it. That should make sure the right C4R addon code is installed.

        -Kyle
        Director
        Building Design Strategy

        Comment


          #5
          Will the same thing cause a problem for consultants linking in the models, or just people working in the same model? I can upgrade everyone in the office in the same time span, but our consultants probably can't, at least for all projects.

          I removed and reinstalled both collaboration for 2016 and 2017, but I still can't manage models.
          Julie Kidder
          Architect + BIM Director
          Hartman + Majewski Design Group

          Comment


            #6
            Nope, it won't. It should just be for the team members working directly on the models.

            -Kyle
            Director
            Building Design Strategy

            Comment


              #7
              I tried installing 2017.1, but the only download is for 2017.1.1 Fixes, and trying to install that gives this error message "The upgrade cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade." I can't find a 2017.1 to install first, so I'm not sure what the problem would be (I am an admin on my computer and have admin rights)
              Julie Kidder
              Architect + BIM Director
              Hartman + Majewski Design Group

              Comment


                #8
                jmk, do you have SP2 installed? I THINK 2017.1 and 2017.1.1 both require SP2, which is non subscription. 2017.1 has been superseded, as it had "issues".
                Pragmatic Praxis

                Comment


                  #9
                  As far as I can tell I have sp 2 installed, I think I remember doing it and the version number is post sp 2. It certainly doesn't appear in the desktop updater.

                  I assumed that if 2017.1 was broken any links to download it would be replaced by 2017.1.1, so I was surprised when it didn't work.
                  Julie Kidder
                  Architect + BIM Director
                  Hartman + Majewski Design Group

                  Comment


                    #10
                    I did have both service packs as well as the latest security fix. I had to uninstall Revit 2017 entirely, then was able to upgrade straight to 17.1.1. Now cloud worksharing works. I suspect something in the 17.0.3 security fix is causing the 17.1.1 update to fail. I was able to update a user who only had sp 1 installed without issue, but it has failed on every computer with the 17.03 update.

                    Update:
                    Every user I have tired to upgrade that has no service packs, sp1 or sp2 can be updated directly 2017.1.1. Any user that has the security fix .03 I have to completely uninstall Revit 2017, reinstall it, and then update to 2017.1.1 without doing the service pack/security fix bundle.
                    Last edited by jmk; January 13, 2017, 03:34 PM. Reason: Additional information
                    Julie Kidder
                    Architect + BIM Director
                    Hartman + Majewski Design Group

                    Comment

                    Loading...
                    Working...
                    X