Reinstall a fairly simple MX onto the repository fails

Question

I have a pretty simple Model. Compiling and installing it is no problem. But the reinstallation with "-force" fails. Any Ideas?

C:\Workbench\wbs\trunk\Models\bin\Debug>mx install Wbs.mx -database:Repository -
tf:"Applications\Wbs" -f
Microsoft (R) Codename "M" Command-line Utility version 3.0.1803.10
Copyright (c) Microsoft Corporation. All rights reserved.

Installing Image: Wbs;Version=1.0;Locale=neutral...Succeeded

C:\Workbench\wbs\trunk\Models\bin\Debug>mx install Wbs.mx -database:Repository -
tf:"Applications\Wbs" -f
Microsoft (R) Codename "M" Command-line Utility version 3.0.1803.10
Copyright (c) Microsoft Corporation. All rights reserved.

Failed

Cannot insert the value NULL into column 'schema_id', table '@Schemas'; column d
oes not allow nulls. INSERT fails.
The statement has been terminated.

Answer 1

Hi,

Unfortunately you are hitting a bug in our internal implementation of force install. The fix should be available by PDC.

Can you give me the scenario you're trying to accomplish, and the M you have? Perhaps I can find a workaround for you.

/K

Answer 2

Sure. I'm Kompirrr at Skype. Let me go online.

/K

Answer 3

Although this is not a real answer, you can get around this problem by dropping the schema for your model and all associated database objects. Of course, please make sure you don't have any data in the model that you want to keep first as this deletes everything in the schema and then drops the schema. There is a spDropSchemaObjects stored procedure that you can use: http://msdn.microsoft.com/en-us/library/dd129549(VS.85).aspx. If your M module was named "Wbs" then you could drop everything in the Repository related to this model by calling:

spDropSchemaObjects @schemaName='Wbs'

Hope this helps work around the problem while you figure out why "-force" is failing.

Jason Roth

Answer 4

We synced up offline, and found another bug in force install that prevents this scenario from being realized.

Lars, let us know if you need more help on this one.

/K

Answer 5

I filed a bug for this issue. The error happens when force-installing modules without any extents.

https://connect.microsoft.com/oslo/feedback/ViewFeedback.aspx?FeedbackID=471075