The error message is slightly misleading. If you were issuing the asset from node 2, the problem is probably that you have no unspent outputs at any address belonging to node 2. The MultiChain transaction model (taken from bitcoin's) requires every transaction to spend at least one output from a previous transaction. (Once an address has one output, it will keep having at least one, because every transaction sent through MultiChain's regular APIs sends back a 'change' output to that address.)
This can be a problem in the type of very open network you are using, when nothing at all is sent to an address before it wants to start transacting. The workaround is to send something (well actually, nothing) to an address before it starts transacting, something like: send [address] 0
If this is not a viable solution in your case, I'm afraid we don't have another good workaround right now. However one thing I would add is that a completely open blockchain like this, with no transaction fees, and no permission required to connect or send transactions, is liable to suffer from a deluge of spam very quickly.