locked
Faulting application name: ClientDeploy.exe RRS feed

  • Question

  • I am getting an issue also. It might be the same as the other ones but not sure. The connector software crash right at the point of it wanting to install .net framework 3.5.1( which windows 7 has). So disable .net framework and enabled it, with still the same issue. I then ran the .net framework verification tool and everything checks out. And yes all the time zones are right. So here is a little something that I found in the error logs that might be of help to find the root issue here. Oh and also I ran a  repair install on Windows 7 x64 just for the fun of it and still get the same error!!!!

     

    Faulting application name: ClientDeploy.exe, version: 6.1.7495.0, time stamp: 0x4bc7a10c

    Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdfe0

    Exception code: 0xc000041d

    Fault offset: 0x000000000000aa7d

    Faulting process id: 0x137c

    Faulting application start time: 0x01caed512b8a783f

    Faulting application path: C:\Program Files (x86)\Windows Server\Client Deployment Files\ClientDeploy.exe

    Faulting module path: C:\Windows\system32\KERNELBASE.dll

    Report Id: 6b6c116b-5944-11df-8a5d-0019d1ff82ec

    Any help would be awesome as I have googled, and binged so much at well............ 

     

     

    Thanks again

     

    Jeremiah

    Thursday, May 6, 2010 8:34 PM

Answers

  • I fixed the issue!!! Had to reinstall WHS Vail. I geuss some files on the server must have been corrupt.
    • Marked as answer by fatboie Thursday, May 6, 2010 8:49 PM
    Thursday, May 6, 2010 8:49 PM

All replies

  • Could you submit a bug on Connect , please?
    I'm not on the WHS team, I just post a lot. :)
    Thursday, May 6, 2010 8:49 PM
    Moderator
  • I fixed the issue!!! Had to reinstall WHS Vail. I geuss some files on the server must have been corrupt.
    • Marked as answer by fatboie Thursday, May 6, 2010 8:49 PM
    Thursday, May 6, 2010 8:49 PM
  • That's good to hear, thank you.

    We've seen very few actual crashes like this. I guess there are no server logs available since you flattened the server? Either way, it would be great if you could file a bug with the client side logs, those are cumulative so would have the old entries in there.


    This post is "AS IS" and confers no rights.
    Kind regards /Lennart
    Thursday, May 6, 2010 9:15 PM
  • Will do!! I am getting the tool to do so right now. I think I might be able to do the same error again!! I am going to try.
    Thursday, May 6, 2010 9:21 PM