Error on installing chaincode

[giridhari1]

Failed at installing chaincode locally

$ node install_chaincode.js
info: Loaded config file C:\Users\Vishal\fabric-samples\marbles\config\marbles_l
ocal.json
info: Loaded creds file C:\Users\Vishal\fabric-samples\marbles\config\blockchain
_creds_local.json
---------------------------------------
info: Lets install some chaincode - marbles v4
---------------------------------------
info: First we enroll
info: [fcw] Going to enroll with admin cert!  peer_urls=[grpc://localhost:7051],
 channel_id=mychannel, uuid=marbles-Docker Compose Network-mychannel-fabric-peer
-org1, orderer_url=grpc://localhost:7050, msp_id=Org1MSP
debug: added peer grpc://localhost:7051
debug: [fcw] Successfully got enrollment marbles-Docker Compose Network-mychanne
l-fabric-peer-org1
---------------------------------------
info: Now we install
---------------------------------------
debug: [fcw] Installing Chaincode
debug: [fcw] Sending install req targets=[grpc.http2.keepalive_time=300, grpc.ke
epalive_time_ms=300000, grpc.http2.keepalive_timeout=35, grpc.keepalive_timeout_
ms=3500, grpc.primary_user_agent=grpc-node/1.8.0, _url=grpc://localhost:7051, ad
dr=localhost:7051, , _request_timeout=90000, , _name=null], chaincodePath=marble
s, chaincodeId=marbles, chaincodeVersion=v4
info: [packager/Golang.js]: packaging GOLANG from marbles
error: [client-utils.js]: sendPeersProposal - Promise is rejected: Error: Connec
t Failed
    at C:\Users\Vishal\fabric-samples\marbles\node_modules\grpc\src\client.js:55
4:15
error: [fcw] Failed to obtain endorsement for transaction. code=14,
error: [fcw] Error in install catch block object code=14,
---------------------------------------
info: Install done. Errors: parsed=Blockchain network error - Connect Failed, ra
w=[code=14, ]

Environment :windows7 64 bit stopped,started and ran the command countless times and my network is running without errors.Is it a problem with host?Please help.

[dshuffma-ibm]

hmm i missed this issue. so if you are still having issues post back. i'd make sure you are able to reach your peer from wherever you are running marbles. send a http GET request to the peer's url/ip and port and see what you see. if it works you will get a status of 200 back with no body.

[dshuffma-ibm]

closing, inactivity