4 Replies Latest reply on Feb 7, 2011 6:25 AM by karen west

    DFS Troubleshooting

    Jordan Sarris Novice

      I wanted to see if anyone has any experience in troubleshooting Desktop File Sync.


      My company recently implemented contract management and our users can't get DFS to work.  I have been working on this issue for several weeks and have I dentified that the problem is being caused by our users permission within windows.  We have the active x control for DFS installed, we changed our internet explorer settings to those recomended by Ariba but our updates to contract documents are being blocked.  My testing has demonstrated that users who have administor privlidges within windows are able to submit updates to contracts but people with more restriced access are not.  The simple solution would be to give everone admin access but my IT department is reluctant to do this.  I know there must be a middle ground, some setting we can change that will allow contract changes to go back through to Ariba.


      So my question is: has anyone else had this problem, if so how did you solve it?

      Your responses are greatly appreciated.


        • Re: DFS Troubleshooting
          dreid Journeyman

          I am attaching a PDF document which might help you with this.  Parts of it are relatively technical, but it is an excellent overview of the whole system.


          Hope this helps you and others!



            • Re: DFS Troubleshooting
              Russ Stebbins Master
              Any consideration to move away from an ActiveX agent?  I know that DFS is MS software focused and it may be a bigger effort than Ariba is willing to undertake with all the dependencies.
                • Re: DFS Troubleshooting
                  dreid Journeyman


                    As you say above, this is one of the thorniest problems around.  We have invested heavily in DFS.  It is a very tricky problem to be able to support Word 2000, 2002, 2003, 2007 (and shortly 2010) all at the same time.  The only way we can do that is by "meeting Word on its own turf."  We could theoretically get around the need for ActiveX if Word moved completely to XML, but that isn't happening, and in order to do so, we'd have to desupport the old versions.  None of which is optimal.


                  In short, we don't see a good way to move away from ActiveX in the near/medium term.  It is something we always evaluate, but the benefits are so large, they dwarf the current issues.