can t instantiate chaincode after upgrade of new chaincode

0 votes
I have done upgrade of chaincode. Steps followed:

1.Install with new version

2.Upgrade with new version

3. Instantiate of new version(error:could not assemble transaction, err proposal response was not successful, error code 500, msg chaincode with name 'fabcar' already exists)
May 29, 2019 by anonymous
1,186 views

1 answer to this question.

0 votes

The error tells that a chaincode by the name 'fabcar' already exists probably because this was instantiated when you were using the older version. Either instantiate the chaincode with a new name or delete the existing chaincode and the instantiate the chaincode as follows:

docker stop $(docker ps -aq)
docker rm -f $(docker ps -aq)
answered May 29, 2019 by Omkar
• 69,220 points

Related Questions

+1 vote
1 answer

Can't instantiate any chaincodes on peers of newly Added org

Seems like chaincode install may have been unsuccessful. Before ...READ MORE

answered Sep 20, 2018 in Blockchain by Perry
• 17,100 points
2,316 views
+1 vote
1 answer
0 votes
1 answer

Unalble to pull a new container after upgrading Helm.

If there are changes to roll out, ...READ MORE

answered Apr 12, 2018 in Docker by shubham
• 7,340 points
946 views
0 votes
1 answer

Get list of rownames as values after aggregating a dataframe

You can use reshape2 library: library(reshape2) data <- read.table(text="type ...READ MORE

answered Apr 17, 2018 in Data Analytics by Sahiti
• 6,370 points
933 views
0 votes
1 answer

How to read a state after writing it into a chaincode?

Data that is 'written' in chaincode is ...READ MORE

answered May 28, 2018 in Blockchain by Perry
• 17,100 points
2,207 views
webinar REGISTER FOR FREE WEBINAR X
REGISTER NOW
webinar_success Thank you for registering Join Edureka Meetup community for 100+ Free Webinars each month JOIN MEETUP GROUP