primary key error in dbo.servoy_elements ??

Classic Servoy
1

Hi,

When I come out of designer mode or attempt to close my solution, I get this error:

java.sql.SQLException: Violation of PRIMARY KEY constraint ‘PK__servoy_elements__29572725’. Cannot insert duplicate key in object ‘dbo.servoy_elements’.

We are running Servoy 2.2.5 with an MS SQL 2005 backend.

Any idea what this means? How can I reset the keys for servoy_elements?

2

Did you ever manually (with SQL) change stuff in the repository?

3

No, but we did just copy the repository database to another database (to create a separate development environment). This problem started then.

4

copy the database file? (the only time you should copy a repository is to have a backup)
Always use export/import solution to a newly created repository.

5

That’s what we did. We made a new database (servoy_repository_dev), exported the solution from the original database (servoy_repository), and imported it into servoy_repository_dev. Now, for some reason, we are getting errors in the original database.

Anyway, whether or not we made a procedural gaffe (which is certainly possible), what can we do to fix this problem?

Thanks,

Andrew

6

Not sure if we understand each other correctly, the Servoy application uses one database called “servoy_repository” to store information about solutions.
It is just impossible to get your solution in a repository named other wise

The user tables/data used by solutions can be put in any other named database.

As far as we know it is impossible to get an database error on a servoy_xxxx table, when no other (db)tools than the Servoy applications are used on the database called “servoy_repository”

7

If I understand correctly, the database can be named anything – it is the database connection that must be named servoy_repository.

We have two servoy environments – a production environment that uses a copy of Servoy Server that connects to the servoy_repository database, and a development environment with individual copies of Servoy Developer that connect to servoy_repository_dev (although this database connection is named “servoy_repository” as well).
Regarding it being impossible to get database errors… all I know is that we are getting database errors. Do you know what we can do to fix them? What can I do to make this error go away?

8

Regarding it being impossible to get database errors…

So far we never had a report of database errors on the database called repository_server. (when using servoy only apps on that db)
Did you maybe replace (stop/start) the repository database while servoy developer was running?

In short there is no solution for this problem other than exporting your solutions and reimport them in a new/empty database