This is the first we've heard of this problem. I have personally been able to successfully send more than that amount on more than one occasion.

I will send you some coins to test. Please let me know if they arrive without issue.

Tranactions are created with other inputs, if you have to many inputs making up the transaction it can become to large.

Its is an issue that affects ALL wallets, and is worse if you have lost of tiny transactions or mined blocks

You can fix this by "dusting" or "defragmenting" your wallet.

1. Backup old wallet.dat and move to a safe location
2. start wallet so you get a new wallet.dat, record the address
3. swap the old wallet back and send all your coins to the new address (you may have to do a bunch of small transactions)
4. once you have moved all the coins to the new wallet, you can send them back to the original wallet in one transaction.

Now you wallet will just have one input to build transactions from

Check us out on Cryptopia! 

https://www.cryptopia.co.nz/Exchange?market=BSY_BTC

Then buy some!!! 

Why?  I have some already!!!

http://bitcoinagile.com/27885D/digital-artwork-becomes-tradeable-scarce-on-the-bitcoin-block-chain-cryptocoinsnews_stream

tagging digital artwork onto the blockchain .. cutting edge

oh dear.
was the competition just a bit too much ?

hmm

i'm seeing strange behaviour from my daemon.

start it up.
it is busy for a few minutes - high CPUMEM usage and will not respond (this seems normal to previous behaviours)
once it's calmed down, to the point where previously it would respond.

it either
a) responds normally

b) responds once then shuts down. eg will give appropriate response to
Banksycoind getinfo
then shut down so next response will be "error: no response from server"

yet to capture anything from debug.log. it seems to be not doing this at the moment.

c) shuts down before responding. eg is running, upon a
Banksycoind listaddressgroupings
shuts down "error: no response from server"

there is nothing obvious in the debug.log and db.log is empty

debug ends with ->

>>> CheckStakeKernelHash: nTimeWeight = 5450902
>>> CheckStakeKernelHash: passed GetKernelStakeModifier
>>> bnCoinDayWeight = 33753, bnTargetPerCoinDay=298528506367175458951681909829523$
>>> CheckStakeKernelHash - hashProofOfStake too much
ThreadRPCServer method=listaddressgroupings



edit.
trying it with a new wallet.dat seems to have fixed it

bump

Is a new wallet out yet?