Could not create database: null

[blackgryphon9999]

Hello,

I'm teaching an online database course at the college level. One of my students has run into a problem that I don't know how to solve. I'm hoping that someone here on the forum has seen the same thing and knows a fix. He has been trying to create a new database and when he does, Servoy displays the error message "Could not create database: null." He says he has entered a name for the new database so he can't figure out where the "null" might be coming from.

He thought about deleting Servoy and reinstalling, but he says he can't get rid of all the files. There are some files in a temp folder that Windows won't delete because it thinks they are being used by some other program. He's running a 32-bit version of Windows Vista. (I'm a Mac user, which makes trying to help him long distance really, really hard.)

I'd be grateful for any insight you folks might have.

Thanks,
Jan

[rgansevles]

Jan,

This sounds like a nullpointer exception, check the log files (/path/to/servoy/application_server/servoy_log.txt and /path/to/servoy_workspace/.metadata/.log)

Rob

[blackgryphon9999]

Jan,

This sounds like a nullpointer exception, check the log files (/path/to/servoy/application_server/servoy_log.txt and /path/to/servoy_workspace/.metadata/.log)

Rob

OK. But if that is the case, how do go about fixing the problem?

[rgansevles]

If you post the stacktrace, maybe we can see what causes this.

Rob

[sergei.sheinin]

I'm having the same issue. Here is call stack from /path/to/servoy_workspace/.metadata/.log:

!ENTRY com.servoy.eclipse.model 4 0 2014-05-07 20:11:02.439
!MESSAGE Unexpected Exception
!STACK 0
java.lang.NullPointerException
at com.servoy.eclipse.ui.views.solutionexplorer.actions.NewPostgresDbAction.createDatabase(NewPostgresDbAction.java:58)
at com.servoy.eclipse.ui.views.solutionexplorer.actions.AbstractNewDbAction$1.runInWorkspace(AbstractNewDbAction.java:85)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)

[sergei.sheinin]

Problem solved: I had another instance of Postgres running on the machine with same port.