Login Error (bad username 'admin' or password)

I am getting following error when i am trying to connect to server:

[com.objectdb.o._PersistenceException: Login Error (bad username 'admin' or password)] with root cause
com.objectdb.o.UserException: Login Error (bad username 'admin' or password)
at com.objectdb.o.MSG.d(MSG.java:61)
at com.objectdb.o.HND.K(HND.java:210)
at com.objectdb.o.SHN.K(SHN.java:208)
at com.objectdb.o.HND.run(HND.java:132)
at java.lang.Thread.run(Thread.java:662)

Here is my connection string:

    Persistence.createEntityManagerFactory(
        "objectdb://10.10.10.14/test.odb; user=admin; password=admin")

And my objectdb.conf is attached.

It works fine when i use localhost in the connection string.

Any help will be appriciated!

User admin is defined in the objectdb.conf but maybe this configuration file is not in use.

The configuration file has to be located relatively to the path of the objectdb.jar file that is in use by the server. You may have another copy of the objectdb.jar file for the client, and in that case you have to verify that the configuration is updated on both the server and the client side.

In addition, you should remove blanks from the connection url.

Thank you for qiuck response!

I checked, and both client and server objectdb.conf files are in use. I am using the same objectdb.conf on client as one on server.

Also, i tried with removing blanks from the connection url and result is still the same.

Client side is running on Windows and server side on Unix. May that be the problem?

> Client side is running on Windows and server side on Unix. May that be the problem?

No, it should work.

> It works fine when i use localhost in the connection string.

What does happen when you access localhost but using its current IP address?

> I checked, and both client and server objectdb.conf files are in use.

Maybe you should try to insert an XML error deliberately to the objectdb.conf file and restart the server, to verify that the  file is in use by the server (if the server starts with no error, then it uses another objectdb.conf file).

I solved it. Once again, thank you for your help.

.odb file was missing on the server side and that was causing the problem.

Everything works now.