# Aerospike Exception while client.put

**URL:** <https://discuss.aerospike.com/t/aerospike-exception-while-client-put/851>\
**Category:** Java Client\
**Created:** [January 21, 2015, 7:22am UTC](https://discuss.aerospike.com/t/aerospike-exception-while-client-put/851 "2015-01-21T07:22:07Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![holmes](https://avatars.discourse-cdn.com/v4/letter/h/e95f7d/32.png) [@holmes](https://discuss.aerospike.com/u/holmes)\
**Post date:** [January 21, 2015, 7:22am UTC](https://discuss.aerospike.com/t/aerospike-exception-while-client-put/851/1 "2015-01-21T07:22:07Z")

</div>

Hi,

I am getting following error while performing write using “client.put” :

> com.aerospike.client.AerospikeException: Error Code 1: Server error  
> at com.aerospike.client.command.WriteCommand.parseResult(WriteCommand.java:59) ~[stormjar.jar:na] at com.aerospike.client.command.SyncCommand.execute(SyncCommand.java:56) ~[stormjar.jar:na] at com.aerospike.client.AerospikeClient.put(AerospikeClient.java:295) ~[stormjar.jar:na]

When do we get “Error code 1” ?

---

<div class="post-metadata">

**Author:** ![raj](https://avatars.discourse-cdn.com/v4/letter/r/c0e974/32.png) [@raj](https://discuss.aerospike.com/u/raj)\
**Post date:** [January 21, 2015, 10:30am UTC](https://discuss.aerospike.com/t/aerospike-exception-while-client-put/851/2 "2015-01-21T10:30:30Z")

</div>

Holmes,

You should see detail message in the log when client gets Error Code 1: Can you share that?

Log can be found at /var/log/aerospike/aerospike.log

– R

---

<div class="post-metadata">

**Author:** ![bbulkow](https://avatars.discourse-cdn.com/v4/letter/b/779978/32.png) [@bbulkow](https://discuss.aerospike.com/u/bbulkow)\
**Post date:** [January 21, 2015, 6:55pm UTC](https://discuss.aerospike.com/t/aerospike-exception-while-client-put/851/3 "2015-01-21T18:55:58Z")

</div>

Holmes,

1 is a general server error. It’s not a permission problem, or being out of space, or misconfiguration, or anything else.

Thus, as Raj says, you need to look at the server log for a more specific error explanation.
