Error: new BigNumber() not a base 16 number:

[yep]

Error: new BigNumber() not a base 16 number:

[5chdn]

Google just sent me here. FYI, This error message appears if the blockchain is not fully synced yet. This also explains the differences in comment 1 and 2.

[yep]

Strange. This is what the output of the exact same commands looks for me (first line is not shown completely):

> {:"result","type":"int256"}],"type":"function"},{"inputs":[],"type":"constructor"}]).at("0x9e82d1745c6c9c04a6cfcde102837cf0f25efc56"); TweetAccount
{
  address: "0x9e82d1745c6c9c04a6cfcde102837cf0f25efc56",
  adminDeleteAccount: function(),
  adminRetrieveDonations: function(),
  allEvents: function(),
  getLatestTweet: function(),
  getNumberOfTweets: function(),
  getOwnerAddress: function(),
  getTweet: function(),
  isAdmin: function(),
  tweet: function()
}
> 
> TweetAccount.getLatestTweet()
["hello world", 1449750863, 1]
>

What geth version are you using, maybe it's old? Get version by running geth version. This the output for me:

Version: 1.3.3
Protocol Versions: [63 62 61]
Network Id: 1

[jikkujose]

Tried again, same output :(. I did geth version and got this:

Geth
Version: 1.3.3
Protocol Versions: [63 62 61]
Network Id: 1
Go Version: go1.5.1
OS: linux
GOPATH=
GOROOT=/usr/lib/go

[yep]

As I can not reproduce the problem locally, could you please provide additional information so I could try to reproduce this on AWS if I find the time for it?
Helpful would be: what AWS AMI are you using? Did you install geth from source and how?
Is the problem reproducible? That is, if you create a new AWS VM and repeat the steps you did, does the problem occur again?
Same error message as in this web3 isssue.
Thanks.

[jikkujose]

Seems it was my issue; I was able to have it run in a Ubuntu machine & Mac locally.

[yep]

Glad to hear it's working now!