Ask a question

User

Fix to DataCollectorSvc error when uninstalling Exchange

Mariette, I did not find mention of this on your site (unless I didn't look hard enough). I was performing the steps (chapter 13) to uninstall Exchange from SBS2011. When running the "setup.com /mode:uninstall", it gave the following error: "Setup cannot continue with the uninstall because the DataCollectorSvc process has open files. Close the process and restart setup".

Solution: open up Task Manager, locate and stop DataCollectorSvc.exe. Then rerun the "setup.com" instruction to uninstall Exchange

Also, you might include a note that depending on the server, uninstalling Exchange could take 15-20 minutes or more!

Cheers. Kevin


asked05/20/2018 15:06
5282 views

endorsed by
  • Rob Ellett
  • Mariette Knap
Add Comment
Last Activity 07/23/2020 06:08

2 Answer(s)

  • Mariette Knap
    Add Comment
    User

    That's surprising to me, as Datacollectorsvc is part of SBS 2011 and I thought it would be running on every SBS server. But that's OK, I posted this as a question ni hopes if someone does run into it and searches on Datacollectorsvc they might find my answer. Thanks again.

    Mariette Knap

    What Exchange Service pack level are we talking about?


    replied 05/20/2018 15:48
    User

    It was Exchange 2010 SP3, but I don't recall off the top of my head which rollup it was on. But let's not waste anytime on it. Exchange successfully uninstalled. I was posting this mostly as a comment in case someone else encounters it. Thanks.


    replied 05/20/2018 16:08
    Mariette Knap

    Yes, thanks for that. I have not seen this on all the migrations I have done and that were a lot :)


    replied 05/20/2018 16:45
    Bill Swan

    I got it... thanks for the heads up.. hehe


    replied 08/03/2019 20:29
    Christian Kokot

    Hi Kevin,

    your solutions works! Thanks!


    replied 10/19/2019 09:42
    Robert Berger

    This helped me, too.  Thank you!


    replied 02/13/2020 20:20
    User

    Also helped me! I Googled the error message and was delighted that the top search result was to here! 


    replied 02/22/2020 21:27
    Rob Whiteside

    I got the same error today and cleared it with Kevin's solution


    replied 07/23/2020 06:08

    Reply
    replied 05/20/2018 15:28
  • Raeford Liebenberg
    Add Comment
Add an Answer