Endpoint Protection

 View Only

  • 1.  SEP deployment woes, error 1309, directory path or file doesn't exist on client machine

    Posted Apr 06, 2010 02:13 PM
    I am trying to test deploy SEP on to some test workstations via SEP Manager. The package will push, but upon installation I get this error:

    "error 1309.Error reading from file: C:\TEMP\Clt-Inst\Windows\winsxs\53t3z6j5.7ag\ATL80.dll Verify that the file exists and that you can access it."

    Thing is, the "C:\TEMP\Clt-Inst\WINDOWS" path doesn't exist at all.

    Any ideas?


  • 2.  RE: SEP deployment woes, error 1309, directory path or file doesn't exist on client machine

    Posted Apr 06, 2010 02:34 PM
    Are you able to access C$ from SEPM server and do you have permission on C:\Temp ?


  • 3.  RE: SEP deployment woes, error 1309, directory path or file doesn't exist on client machine

    Posted Apr 06, 2010 02:53 PM

    Is that a 64 bit machine ? If yes then

    From the  install media in SEPwin64\x64 run the vcredist_x64.exe

    Also it will be great if you can paste the SEP_inst.log


  • 4.  RE: SEP deployment woes, error 1309, directory path or file doesn't exist on client machine

    Posted Apr 06, 2010 03:14 PM
    Yes I am. If I manually copy the packages over to the client machine, it will install fine and contact the SEP server. Pushing the package via console will result in that error everytime.


  • 5.  RE: SEP deployment woes, error 1309, directory path or file doesn't exist on client machine

    Posted Apr 06, 2010 03:14 PM
    These are 32-bit WinXP machines


  • 6.  RE: SEP deployment woes, error 1309, directory path or file doesn't exist on client machine

    Posted Apr 07, 2010 02:58 AM
    Export a new package and push it to the clients and see...