It seems that there is a problem with database field o_Project.o_serviceDeskName (in case of using MSSQL as DBMS). The problem is in unique constraint: as you may know in MSSQL NULL is treated as distinct value and having two projects with o_serviceDeskName = NULL lead to constraint violation. Also there is no means to enter this value in UI. The workarounds are to setup this value straight inside database or change (remove) this unique constraint. I know that in other databases unique constraints allow to have multiple NULL values (Oracle, MySQL,...) and I believe that this is logical and correct behavior. But sadly we are forced to use MSSQL for now...