Bower - EPERM, unlink error

Question

I'm encountering the below error stack trace, while I try to install "jQuery" using Bower. Can someone offer some help?

    C:\study\meanApp>bower install jquery --save
    bower not-cached    git://github.com/jquery/jquery.git#*
    bower resolve       git://github.com/jquery/jquery.git#*
    bower download      https://github.com/jquery/jquery/archive/2.1.1.tar.gz
    bower retry         Download of https://github.com/jquery/jquery/archive/2.1.1.t
    ar.gz failed, trying with git..
    bower EPERM         EPERM, unlink 'C:\Users\UserZ\AppData\Local\Temp\AUserZ\bower\jquery-8680-AaJIqU\archive.tar.gz'

    Stack trace:
    Error: EPERM, unlink 'C:\Users\UserZ\AppData\Local\Temp\A-UserZ\bower\jqu
    ery-8680-AaJIqU\archive.tar.gz'

    Console trace:
    Trace
        at StandardRenderer.error (C:\Users\UserZ\AppData\Roaming\npm\node_module
    s\bower\lib\renderers\StandardRenderer.js:72:17)
        at Logger.<anonymous> (C:\Users\UserZ\AppData\Roaming\npm\node_modules\bo
    wer\bin\bower:110:22)
        at Logger.EventEmitter.emit (events.js:95:17)
        at Logger.emit (C:\Users\UserZ\AppData\Roaming\npm\node_modules\bower\nod
    e_modules\bower-logger\lib\Logger.js:29:39)
        at C:\Users\UserZ\AppData\Roaming\npm\node_modules\bower\lib\commands\ind
    ex.js:40:20
        at _rejected (C:\Users\UserZ\AppData\Roaming\npm\node_modules\bower\node_
    modules\q\q.js:797:24)
        at C:\Users\UserZ\AppData\Roaming\npm\node_modules\bower\node_modules\q\q
    .js:823:30
        at Promise.when (C:\Users\UserZ\AppData\Roaming\npm\node_modules\bower\no
    de_modules\q\q.js:1035:31)
        at Promise.promise.promiseDispatch (C:\Users\UserZ\AppData\Roaming\npm\no
    de_modules\bower\node_modules\q\q.js:741:41)
        at C:\Users\UserZ\AppData\Roaming\npm\node_modules\bower\node_modules\q\q
    .js:557:44

    System info:
    Bower version: 1.3.9
    Node version: 0.10.18
    OS: Windows_NT 6.1.7601 ia32

P.S: I've gone through the StackOverflow could find nothing related to my error, hence posting this question.

Thanks in advance, Dave

Answer 1

Cleaning the cache resolved the error for me: npm cache clean