SQL Error After Domain Model Change

1
Hi There, We made some changes to our domain model. We had multiple entities with one to one relationships and decided to couple them into one entity. There are no errors present now, but when we try to deploy, we get the following error message from the modeler in a pop up window: Request action: executeddlcommands Message: Executing DDL commands failed. Cause: com.microsoft.sqlserver.jdbc.SQLServerException: Either the parameter @objname is ambiguous or the claimed @objtype (COLUMN) is wrong. Stack trace: com.mendix.m2ee.api.AdminException: Executing DDL commands failed. at com.mendix.core.MxRuntime.c(SourceFile:492) at eh.execute(SourceFile:33) at com.mendix.m2ee.server.handler.AdminHandler.handle(AdminHandler.java:84) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:113) at org.eclipse.jetty.server.Server.handle(Server.java:334) at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:559) at org.eclipse.jetty.server.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:992) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:550) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:203) at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:406) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:462) at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:436) at java.lang.Thread.run(Thread.java:662) Caused by: ab: com.microsoft.sqlserver.jdbc.SQLServerException: Either the parameter @objname is ambiguous or the claimed @objtype (COLUMN) is wrong. at y.a(SourceFile:86) Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Either the parameter @objname is ambiguous or the claimed @objtype (COLUMN) is wrong. at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:197) at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1493) at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(SQLServerStatement.java:775) at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(SQLServerStatement.java:676) at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:4575) at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1400) at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:179) at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:154) at com.microsoft.sqlserver.jdbc.SQLServerStatement.execute(SQLServerStatement.java:649) at org.apache.commons.dbcp.DelegatingStatement.execute(DelegatingStatement.java:264) at org.apache.commons.dbcp.DelegatingStatement.execute(DelegatingStatement.java:264) at y.a(SourceFile:170) at y.a(SourceFile:46) at jp.a(SourceFile:166) at jp.d(SourceFile:159) at com.mendix.core.MxRuntime.c(SourceFile:488) at eh.execute(SourceFile:33) at com.mendix.m2ee.server.handler.AdminHandler.handle(AdminHandler.java:84) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:113) at org.eclipse.jetty.server.Server.handle(Server.java:334) at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:559) at org.eclipse.jetty.server.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:992) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:550) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:203) at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:406) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:462) at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:436) at java.lang.Thread.run(Thread.java:662) And in the Console window of the modeler, the following error gets displayed : Error on executing: EXEC sp_rename '[capture$spousedetails].[name]', 'spousename', 'COLUMN' Either the parameter @objname is ambiguous or the claimed @objtype (COLUMN) is wrong. (SQL State: S0001, Error Code: 15248) All changes are rolled back. Does anyone know what is happening and what we can do to fix it? Kind Regards Frikkie Chalmers
asked
1 answers
1

We sorted this issue out.

I had to go into the new entity, delete the attributes, that we got from the old entities. Run the application. Re-add the attributes.

Now it is working.

Kind Regards Frikkie

answered