Issues after upgrade to OA 2011.2.713

[XXXX]

I have had serveral issues with OpenAccess after upgrade to version 2011.2.713.  Among them are things like that the generated files were no longer placed in a seperate folder but in the project folder even if the settings said they should be placed in a dedicated folder. Those I was able to overcome by modify settings and reload the soulution.
The real issue that I can't figure out is an error I get when trying to update the database from model.
I have the 'Migrate Database' option selected. All tables in the database  are selected and have the Operation Modify. When I click "Next" button I get an error " An unexpected exception has occurred. ..." 'Using a duplicate column name attempted for field'
This model worked before I upgraded.  I'm using Visual Studio 2010 32bit on Win7 (32bit) and the backend is MS SQLserver 2008.

[XXXX]

Update :
    Can now update the database after powerdown (had rebooted the workstation after upgrading OA) and had reloaded Visual Studio many times.
But there are still issues that the generated files are created in the project directory but not in the directory specified in the Model Settings. 
AO changed one or two classes to 'default mapping' and attempted to change number of columns from 'not null' to 'null' but I count that before it was applied to the database.

But it now leaves the 'last_used_id' column in the table 'voa_keygen' as bigint. (as I asked for)

Thanks to Telerik  for all the hard work they have put into the products and support.

[PetarP]

Hello Bjössi,

 We are sorry for the bad experience you have had during your update process. Such thing should never happen. In order to ensure better user experience while updating can you please share some additional details regarding your model so that we can reproduce your issues here locally? We need information on the structure of the classes that were changed to default mapping as we all as the backend you are using.

All the best,
Petar
the Telerik team

[XXXX]

Sorry for delayed response. (and bad spelling in my last post)

The backend is MS SQL, and originally the model started in the database (backward mapping ?).
We have gone through couple of upgrades on OA with that model, from free version to full.
I could not detect anything different for those few classes/tables that were changed to default mapping during the upgrade.
Like stated earlier this model has gone through a lot of changes and experiments so there is a large chance of some "dirt" in the files that can have affected the upgrade process.

Sorry that I don't recall more details.

[PetarP]

Hi Bjössi,

 We also believe that your model has been in an inconsistent state and that caused your problems during update. Generally such issues should never happen.
Should you encounter it again please write us back with as much information as possible.

Kind regards,
Petar
the Telerik team

[XXXX]

The "Using duplicate..." error is now back.
Is there a tool or away to clean up the model ?
I have noticed that the size of the .rlinq files goes up (and down). I have seen  250 Kb and 550 Kb filesize for the same model.

I have read through the .rlinq file manually and didn't see anything obviously wrong.

The error messages says: "..Open the 'Forward Mapping' dialog from OpenAccess, select the class <My_plan> and field <_myPlans> ".   I'm not sure what this forward mappind dialog is but what is really strange is that I don't recall any field <_myPlans> in that class.

Yours
   Björn

[PetarP]

Hi Bjössi,

 The message your are seeing is from one of our old wizard and is falsely displayed. The problem is yet again caused by most probably a column being duplicated in your model. Did that happen after an upgrade again? Or where there some other circumstances that caused the false behavior?

All the best,
Petar
the Telerik team

[XXXX]

To resolve this I had to revert to an old copy of the model (rlinq file) and redo the changes since then.
It puzzels me why a message from an old wizard are popping up when everything says version 2011.2.723 (I repaired the install to be sure).
One thing I learned while redoing the changes to get the model upto date, was that there can appear some strange errormessages if there are tables in the model that are not mapped or not used.

[PetarP]

Hi Bjössi,

 The popping of old messages is caused by the common exception handling we used to have in the old reverse/forward mapping wizards. We are in the process of cleaning this up and you should not observe such behavior in the future.
Can you please share with us did your tables that did not have mapping were set to use default mapping or they were just handing in the model? 
We look forward to your reply.

All the best,
Petar
the Telerik team

[XXXX]

I'm not sure I understand the question but I will try to explain what happened.
Part of what I was doing was to delete classes from the model that are not used and their tables.
But if there were relations that used join table the join table was not removed from the model. When I attempted to update the database from the model I would get errors. Not the same error every time but most often the "duplicate column name" error .

[PetarP]

Hello Bjössi,

 You can always open the schema explorer and remove the table from there. Please note that delete is available only for tables that are not mapped to a class. 
We will continue trying to reproduce this issue on our side and we will fix any problem that might pop out. Thank you for your continued help on the matter and please find your Telerik points updated for all the useful information you provided to us.

Kind regards,
Petar
the Telerik team