I’ve tried repairing all .NET packages, removing the database from EAC, adding it back, and the DataModelGenerator.log spews out this:
C:\Users\REDACTED\AppData\Local\Temp\Epicor\DataModelGenerator\Source\Server\Db\Ice.Data.Model\Ice.Data.Model.csproj : error NU1101: Unable to find package Microsoft.NETCore.App.Ref. No packages exist with this id in source(s): Offline
C:\Users\REDACTED\AppData\Local\Temp\Epicor\DataModelGenerator\Source\Server\Db\Ice.Data.Model\Ice.Data.Model.csproj : error NU1101: Unable to find package Microsoft.WindowsDesktop.App.Ref. No packages exist with this id in source(s): Offline
C:\Users\REDACTED\AppData\Local\Temp\Epicor\DataModelGenerator\Source\Server\Db\Ice.Data.Model\Ice.Data.Model.csproj : error NU1101: Unable to find package Microsoft.AspNetCore.App.Ref. No packages exist with this id in source(s): Offline
Failed to restore C:\Users\REDACTED\AppData\Local\Temp\Epicor\DataModelGenerator\Source\Server\Db\Ice.Data.Model\Ice.Data.Model.csproj (in 2.18 sec).
Determining projects to restore...
C:\Users\REDACTED\AppData\Local\Temp\Epicor\DataModelGenerator\Source\Server\Db\Ice.Data.Model\Ice.Data.Model.csproj : error NU1101: Unable to find package Microsoft.NETCore.App.Ref. No packages exist with this id in source(s): Offline
C:\Users\REDACTED\AppData\Local\Temp\Epicor\DataModelGenerator\Source\Server\Db\Ice.Data.Model\Ice.Data.Model.csproj : error NU1101: Unable to find package Microsoft.WindowsDesktop.App.Ref. No packages exist with this id in source(s): Offline
C:\Users\REDACTED\AppData\Local\Temp\Epicor\DataModelGenerator\Source\Server\Db\Ice.Data.Model\Ice.Data.Model.csproj : error NU1101: Unable to find package Microsoft.AspNetCore.App.Ref. No packages exist with this id in source(s): Offline
Failed to restore C:\Users\REDACTED\AppData\Local\Temp\Epicor\DataModelGenerator\Source\Server\Db\Ice.Data.Model\Ice.Data.Model.csproj (in 233 ms).
Error Generating the Data Models: Unable to build Data Model 'Ice.Data.Model'.
I’ve created a support case on epicare, and they cannot give me a solid resolution. Unfortunately I cannot seem to find much online either. Anyone have experience with this?
Yes, we’ve started the upgrade process to 2024.2.10, so there are multiple .NET versions installed, along with the 2024.2.10 update. I think that may have been the root cause, but during that time I had no reason to regenerate the data model so cannot be sure.
Was able to get this resolved by trying anything I could imagine. Finally clicked after re-reading the logs a couple of times. Pretty much a guessing game.
Open this directory: C:\Users\{username}\AppData\Local\Temp\Epicor\DataModelGenerator
Find the file: NuGet.config, open it with notepad or another text editor.
Awesome to hear! I provided the details in my ticket with epicare, so here’s hoping they add some documentation on it for anyone else having this issue.
I just ran into this issue fresh today. I am running 2025.2 with 2026.100 CR installed on this server.
What I found is that even if I add they key to the NuGet.config when the regen starts it was clearing it out back to just offline.
I started the regen and immediately added the key back and saved the config and the regen completed ok.
Case CS0005434480 is open with Epicor because obviously it shouldn’t require that song and dance to get a regen to work. Something is wrong. This is our first regen since installing 2026.100 which required installing .NET10 SDK. I’m wondering if the core of the issue has to do with multiple .NET versions needing to be used for projects by Admin Console.
Order of operations issue they indicated they will update documentation. Support rep response today.
I think the reason for the behavior was that the Kinetic portion was done before the .NET install was completed. Personally, I install .NET 10 first and then installed Kinetic and deployed the appservers, etc. I did not run into this issue.
However, there were people on the Development and QA teams to installed Kinetic first and ran into issues like the one you reported. Log story short, I will be reviewing the installation guides to suggest making some changes to make it clear that the .NET Components should be install first. We will then have the documentation deploy updated versions of the guides.