StrataFrame Forum » StrataFrame Application Framework - V1 » Issues » Version 1.41 Upgrade problem

Version 1.41 Upgrade problem

Paul Chase — Thu, 06 Jul 2006 16:26:53 GMT

I tried the upgrade to 1.41 and have an issue when I try to rebuild by bus objects I get the following error. The Fields could not be displayed.

Column 'pix_trimoption' does not belong to table DTEproject_item_expressions.

This only happens on 2 Business Objects out of 15. I don't see anything out of the ordinary about these Tables. any ideas>?

Thanks alot

Paul

RE: Version 1.41 Upgrade problem

StrataFrame Team — Thu, 06 Jul 2006 16:26:53 GMT

Well, get that beer. There is certainly a possibility that it could be looking at home. You can always check your connection through the Database Connection on the StrataFrame menu and selecting "Edit..." and viewing the properties.

RE: Version 1.41 Upgrade problem

Paul Chase — Thu, 06 Jul 2006 16:24:20 GMT

Maybe it is going through the VPN to home and looking there? I looked on the servers here and did not find any other installations. I was able to copy the code from the BO deleted it and re-add and seems to work ok not sure what the heck I customized but guess I will find out.

Like I said it has been one of those days,I am off to get a cold beer thanks for all the help you guys are the best.

Paul

RE: Version 1.41 Upgrade problem

StrataFrame Team — Thu, 06 Jul 2006 16:13:01 GMT

OK, you only have one StrataFrame connection configured in the Database Connection, but I'm betting that it's pointed at the wrong database. You probably have more that one StrataFrame database installed, and you're pointed at the one that did not get upgraded. The reason that error is being thrown is that there are fields customizations on those two business objects, but you said that the DTEproject_item_exceptions table in the database has both fields but does not have any rows. So, if there are no row, then that database does not think that there are any field customizations and the BOMapper does, so it's probably looking at a different database.

RE: Version 1.41 Upgrade problem

Paul Chase — Thu, 06 Jul 2006 16:08:57 GMT

Here is a picture of the stack trace

RE: Version 1.41 Upgrade problem

Paul Chase — Thu, 06 Jul 2006 16:06:34 GMT

ooops wrong attachment before. here is the correct one

RE: Version 1.41 Upgrade problem

StrataFrame Team — Thu, 06 Jul 2006 16:06:02 GMT

Oh, no, all of the business objects will look at the same instance. I wasn't clear earlier... you can have more than one data source "configured," but you can only have one data source "active" at any time. The reason those two business objects are having problems is that they have field-level customizations. The column missing from the database is used in field-level customizations, and therefore, when the BOMapper attempts to list off the fields that have customizations, it fails. In your screen shot, can you scroll that error message down so that I can see the StackTrace where it's being generated?

RE: Version 1.41 Upgrade problem

Paul Chase — Thu, 06 Jul 2006 16:03:25 GMT

I forgot there is only one StataFrame data store defined under the Database connection menu option.

RE: Version 1.41 Upgrade problem

Paul Chase — Thu, 06 Jul 2006 16:01:12 GMT

Ok I have multiple business objects and 2 of them are having this problem. If for some reason 2 of the objects are looking at a different install how can I make them "look" at the same instance of strataframe as the ones that work correctly. Here is a screenshot of a rebuild all.

RE: Version 1.41 Upgrade problem

StrataFrame Team — Thu, 06 Jul 2006 15:50:07 GMT

All of the business objects will look to the same StrataFrame database instance, but it is possible to have more than one instance. You can change the database referenced by the StrataFrame design-time components by going to the StrataFrame menu and selecting Database Connection.

RE: Version 1.41 Upgrade problem

Paul Chase — Thu, 06 Jul 2006 15:47:29 GMT

I don't think I do but the way this day has been going anything is possible. I have spent the entire day chasing a Com+ problem that if it was a rattlesnake I'd be bit. I'll look on my other SQL installations to see if that is what happened.

How could some BO' be mapped to one strata install and some to another>? Is there a way to have them all look at the same strataframe install?

RE: Version 1.41 Upgrade problem

StrataFrame Team — Thu, 06 Jul 2006 15:41:15 GMT

Do you by chance have the StrataFrame database installed in multiple locations? That's the exact error message you receive when the column does not exist on SQL Server. If you have more than one, chances are you've only updated one of them since the install will only upgrade one database at a time.

RE: Version 1.41 Upgrade problem

Paul Chase — Thu, 06 Jul 2006 15:39:04 GMT

Ben,

Here are some pictures that might help a bit. All the other Bus objects are fine. This is the project the will be using replication. I have not opened it in a few weeks as anothe project is the current priority.

RE: Version 1.41 Upgrade problem

StrataFrame Team — Thu, 06 Jul 2006 15:28:28 GMT

When do you get that exception? Does it show up in a red exception dialog, or does it show within build results when you try to build the partial classes. Or does it only show up when you click on a business object from the treeview and the BOMapper ties to load the fields list?

RE: Version 1.41 Upgrade problem

Paul Chase — Thu, 06 Jul 2006 15:25:31 GMT

Ben,

The fields already exist in the table. There are not any records in this table.

RE: Version 1.41 Upgrade problem

StrataFrame Team — Thu, 06 Jul 2006 15:20:52 GMT

There should be a log file within the C:\Program Files\Common Files\MicroFour\StrataFrame folder that contains the install log listing the steps that were taken and the steps that failed during the database upgrade. That should give a clue as to what might have happened.

RE: Version 1.41 Upgrade problem

Paul Chase — Thu, 06 Jul 2006 15:18:15 GMT

I'm using 2005 as my DB. I'll have a look and see what is happening and let you know

RE: Version 1.41 Upgrade problem

StrataFrame Team — Thu, 06 Jul 2006 15:13:34 GMT

Yes, 1.4.1 has some new database fields in the StrataFrame database that are used for field customization. You're probably using SQL Server 2000 as your database backend, and the database deployment package did not add the fields properly.

The easiest fix is to go into Enterprise Manager and alter the DTEproject_item_exceptions table within the StrataFrame database by adding these two fields:

piex_trimoption (int, not null) default value: 0
piex_readonly (bit, not null) default value: 0

Make sure you set the default value and set the columns to NOT NULL so that you won't run into any DbNull.Value problems within the BOMapper.