3

I get an error: Error contract code couldn't be stored, please check your gas amount.

I know this error has been reported several times already. Strange thing is, until this morning, my dApp just worked fine, only this afternoon to start giving this error. I literally changed nothing.

I use metamask as wallet, you can find the project on oursurance.nl

Strange thing is that it deploys the contract and I can find the contract and similar coded contracts (that worked without a problem) through ehterscan. but still gives this error. To contract accounts now exist and bear ethers, but I can't interact with them.

Again, it has been working just fine and I haven't changed anything. I tried to add extra gas, but that didn't help. Hope anyone can help!

kind regards, Olivier

Improve this question
6
  • 1
    It is possibly an execution error in the constructor leading back to the process you use to deploy it. If the constructor can't execute without throw; it might bubble up as an "out-of-gas" error. That can happen if an expected parameter isn't present depending on how the constructor is designed.
    – Rob Hitchens
    Apr 25, 2017 at 22:27
  • 1
    Strange thing is that it deploys the contract and I can find similar coded contracts (that worked without a problem). but still gives this error. To contract accounts now exist and bear ethers, but I can't interact with them.
    – Olivier Rikken
    Apr 26, 2017 at 10:47
  • I am having the exact same issue
    – Wilfred
    May 1, 2017 at 17:39
  • After a few days, it was resolved. But I'm worried about the stability of ropsten, last Friday it as doing strange things again (deploying, but only after an hour etc).
    – Olivier Rikken
    May 23, 2017 at 13:59
  • @OlivierRikken What solved it? Would be great if you could add that as an answer so others may find the solution to the problem.
    – JohnAllen
    Jul 19, 2017 at 15:47

1 Answer 1

Reset to default
1

Turned out to be a hickup in Ropsten at that time. Problem solved itself.

Improve this answer
1
  • This appears to be the correct answer. Simply re-running my deployment also fixed it for me (I am also on Ropsten).
    – ethereum_alex
    Aug 25, 2017 at 17:41

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.