none
Error 1309. Error Reading from File - After failed SCCM app deployment and trying to install manually RRS feed

  • Question

  • I tried to deploy an application and it failed. Due to not having time to troubleshoot the issue, I tried to manually install the application from the PC. When I do that, I get the following message.
    Error 1309. Error reading from file:....Verify that that file exists and that you can access it.
    It does this for all the computers that the SCCM application deployment failed on.
    Any suggestion?

    Monday, September 23, 2019 12:48 AM

All replies

  • That's specific to the application that you are installing so not a whole can really be said.

    Have you looked in the location to see if the file is there or not?

    Have you looked in the source files for the application to see if the file is there?

    Have you looked on the DP(s) to see if the file is there (using DP Content Explorer)?


    Jason | https://home.configmgrftw.com | @jasonsandys

    Monday, September 23, 2019 2:23 PM
  • To add to Jason's comment, If you download the file from the internet, did you unblock it before deploying it

    Garth Jones

    Blog: https://www.enhansoft.com/blog Old Blog: https://sccmug.ca/

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleashed

    Monday, September 23, 2019 2:43 PM
  • Thank you. I will check the things you mentioned and report back to you.

    Was just confused that it is trying to look in that location when I copy the installer to the local computer and try to install that way without using SCCM.

    If I go to a computer that did not have the application advertised to, the install works with no problem.

    Monday, September 23, 2019 4:00 PM
  • I did not unblock. However, without unblocking I am able to manually install the application on systems that were not part of the collection I deployed the application to.  

    I did unblock and tried to install on systems that had the application initially deployed to and I get the same error message.

    Monday, September 23, 2019 8:26 PM
  • No, The file that is referenced in the error message is not there, only the <installer>.msi is there. If I hit ignore on the error, It brings up a different file name and I have to hit ignore for more than 35 times, after that I just clicked on Abort.

    Yes, the .exe referenced in the error message is in my source admin install location, as well as all the other .exe it references when clicking ignore.

    No, the files are not on the DP, only the .msi

    I see the issue, the files are not on the DP, thus not downloaded to the client. Just hate that I cant just install the application manually from the original install location on the network.

    Monday, September 23, 2019 8:56 PM
  • Just hate that I cant just install the application manually from the original install location on the network.

    Why would you want to do that?


    Jason | https://home.configmgrftw.com | @jasonsandys

    Monday, September 23, 2019 9:14 PM
  • I have a few users who would like the application ASAP. So instead of them waiting for me to get it all figured out via sccm, I would just like to manually install on their pc so they can start using it.
    Monday, September 23, 2019 9:17 PM
  • Then honestly, you need to adjust your user's expectations. The whole point here is to enforce standards and separation. Also, how long are we truly talking here to update the content on the DP where these users are located? 5 minutes?

    Jason | https://home.configmgrftw.com | @jasonsandys

    Monday, September 23, 2019 9:20 PM
  • Try running:

    Msiexec /i "MSINAME.msi" REINSTALL=ALL REINSTALLMODE=vomus /qn


    Richard Knight | Collection Refresh Manager | Automate detection rules for patch \ msp files | Twitter

    Tuesday, September 24, 2019 5:37 PM
  • No that does not work, however I have found the cause as to why the package did not install the first time was because the wrong switches where used. The switches that should have been used are /S /v/qn

    Saturday, September 28, 2019 3:36 PM