Masuk
 
AwalPerpustakaanWikiPelajariUnduhDukunganKomunitasForum
Resources for IT Professionals >
> 
> 
Update-SPSolution Error on second WFE

Jawab Update-SPSolution Error on second WFE

  • 29 Maret 2012 16:40
     
     
    Masuk untuk Memilih
    0

    I've just tried to update a core solution to our SP2010 farm (same one used previously) and it worked on our first web front end but failed on the second one. Central Admin shows:

    'Some of the files failed to copy during deployment of the solution.'

    followed by

    Access to the path 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\Template\Features\<resourcename>\MasterPages\Home.aspx' is denied.

    This is the first time we have updated any solution with this new front end server (though the previous version deployed to it when we first built the WFE and everything else is working fine.

    Now the WFE is out of service - when browsing to it you get 'could not load file or assembly '<this solution>, the system cannot find the file specified.

    Could anyone advise what might have happened and how I can redeploy just to this server to avoid breaking the other working one?

     

Semua Balasan

  • 29 Maret 2012 18:49
     
     Jawab
    Masuk untuk Memilih
    0

    Hi,

    you can try updating the solution on that specific WFE only by using the -Local and -Force switch for the Update-SPSolution Cmdlet.

    http://technet.microsoft.com/de-de/library/ff607724.aspx

    Andrei

    • Ditandai sebagai Jawaban oleh ukDavidC 30 Maret 2012 11:42
    •  
     
  • 30 Maret 2012 9:31
     
     
    Masuk untuk Memilih
    0
    Thanks a lot, I ran this command on a test environment and confirmed that it only redeployed to that server, but the other server was interupted momentarily too. Is there a risk that one might break too? or is it likely to just solve the issue on the broken server and not touch the others (despite this apparent interruption)
     
  • 30 Maret 2012 11:42
     
     
    Masuk untuk Memilih
    0

    We went ahead and did this - problem solved with no interruption to the other servers.

    Thanks for your help!

     
  • 30 Maret 2012 19:20
     
     
    Masuk untuk Memilih
    0

    You're welcome.

    Generally there is no risk for the others servers when doing a local deployment, because the solution files (dlls, xmls, ..) get deployed only locally. So everything stays the same on the other farm servers. The interruption most likely came from the automatic IIS Reset after the deployment process.

    For details, check out:

    http://msdn.microsoft.com/en-us/library/aa544500.aspx

    Andrei