10.2.100 Upgrade Data Model Error


(Aaron Willett) #1

I’m working on upgrading our database on our sandbox server from 10.1.500 to 10.2.100 and received an error on the last step (3000 Data Model Regen). I tried manually regenerating it per the instructions, but I receive the same error. Has anyone seen this one?

Here’s the info from the log it references:

Start time: 3/21/2018 7:09:42 AM
Database server: TESTE9MAIN
Database name: 101500
Using Windows authentication: True
User ID: ELKAY\epicor1
Schemas to include:
Tables to exclude: Ice.SysSequence, Ice.DBMigrationLog
Generator version: 3.2.100.0
Server version: 3.2.100.0
Folder C:\Users\epicor1\AppData\Local\Temp\2\Epicor\DataModelGenerator\Source is deleted successfully.
Extracting “Epicor.ServiceModel.dll” from “C:\Program Files (x86)\Common Files\Epicor Software\Database Manager Extensions\3.2.100\DataModelGenerator…\DbMigration.zip” to “C:\Users\epicor1\AppData\Local\Temp\2\Epicor\DataModelGenerator\Deployment\Server\Bin”.
Extracting “Epicor.System.dll” from “C:\Program Files (x86)\Common Files\Epicor Software\Database Manager Extensions\3.2.100\DataModelGenerator…\DbMigration.zip” to “C:\Users\epicor1\AppData\Local\Temp\2\Epicor\DataModelGenerator\Deployment\Server\Bin”.
Extracting “EntityFramework.dll” from “C:\Program Files (x86)\Common Files\Epicor Software\Database Manager Extensions\3.2.100\DataModelGenerator…\DbMigration.zip” to “C:\Users\epicor1\AppData\Local\Temp\2\Epicor\DataModelGenerator\Deployment\Server\Assemblies”.
Synchronizing schema changes.
Generating: C:\Users\epicor1\AppData\Local\Temp\2\Epicor\DataModelGenerator\Source\Server\Db\Ice.Data.Model\IceContext.edmx
Connecting to server/database: TESTE9MAIN/101500
connection opened and DB info retrieved. (61.25 s)
Generate EDMX
generate EDMX completed. (0.24 s)
Process Extended Tables
process of extended tables completed. (0.05 s)
Saving EDMX
save completed. (0.09 s)
Transform Model T4 template
transformation completed. (10.21 s)
Transform TempRowTypes T4 template
transformation of TempRowTypes completed. (0.84 s)
Build context project
build project completed. (15.36 s)
Total generation time (88.05 s)
Copying generated assembly to database: C:\Users\epicor1\AppData\Local\Temp\2\Epicor\DataModelGenerator\Source\Server\Db\Ice.Data.Model\obj\Release\Ice.Data.Model.dll
Generating: C:\Users\epicor1\AppData\Local\Temp\2\Epicor\DataModelGenerator\Source\Server\Db\Erp.Data.910100\ErpContext.edmx
Connecting to server/database: TESTE9MAIN/101500
connection opened and DB info retrieved. (398.04 s)
Generate EDMX
generate EDMX completed. (0.86 s)
Process Extended Tables
process of extended tables completed. (0.35 s)
Saving EDMX
save completed. (0.45 s)
Transform Model T4 template
Error Generating the Data Models: The parameterized query '(@SchemaName nvarchar(4000),@TableName nvarchar(14),@ColumnName ’ expects the parameter ‘@SchemaName’, which was not supplied.


(Bart Elia) #2

That smells like an old version plugin is being used, not the current one:

e.g. - The Data Model Generator has a plugin model. Based upon the version you are using, different code is executed:

I think we added that param some time ago so some I would have assumed there in 10.1.500 even. Something odd to review with a support call


(Aaron Willett) #3

I have a quite a few of those. Should I maybe try deleting/moving the old folders?
I’ll bring this up with support when someone is assigned the call.


(Bart Elia) #4

They SHOULD be vectored to when you open the AC so SHOULDN’T be an issues. I am worried not finding why now will cause issues late (Unless somehow the wrong version dlls got copied into the wrong folder at some point.

If you don’t need to talk to those versions you don’t NEED them unless I am missing something in the minutiae. Support call is best bet as they may have a KB on something I don’t remember or they found after I was done in that area. That framework branch was Sept 2015 for me so getting a few cobwebs on it in my brain :wink:


(Aaron Willett) #5

Looks like the issue is tied to problem PRB0192191 with no work around. :confused:
I guess I won’t be upgrading any time soon.


(Bart Elia) #6

I show that issue as under investigation with no known workaround TODAY - (pre investigation). Sorry if there is a miscommunication but that is in my teams queue to investigate so it caught my eye :wink:


(Nikhil Patwa) #7

Is this an in-place upgrade or you have a separate system (preferably a VM) setup with ERP 10.2.100.x for the upgrade?
We always have a separate VM setup for upgrade since that is clean and updated with the latest ERP version, this way there are no remnants of older versions in the system.


(Aaron Willett) #8

It’s a separate sandbox VM.
We move over a copy of the 10.1.500 from live and then practice the upgrade.


(Aaron Willett) #9

@Bart_Elia, just as a data point for your team, I tried doing a step upgrade: from 10.1.500.16 to 10.1.600.0 and then from 10.1.600 to 10.2.100.0. The upgrade from 10.1.500 to 10.1.600 works just fine through the whole process. The upgrade from 10.1.600 to 10.2.100 generates the same error during the data model regen, however.

Also, 10.2.200 fails with the same issue.


(Haso Keric) #10

I went from 10.1.500.31 to 10.2.100.12 without a problem. FYI.