2026.100.3 is here

I thought I’d start another post for 2026.1 now it is available in the downloads for On-Prem.

I just started reading the release upgrade guide, and I have to say I am a bit confused.

One section takes you through the process of Installing the Kinetic Client on a Workstation and a few pages later in the Troubleshooting it has a section “Desktop Client No Longer Launches” and of course “You are NO LONGER able to launch Kinetic from your desktop” … so why step even try to install in the first place… IDK..

Anyway I thought this might be a good thread to point put issues related to installing 2026.1 Maybe it should go in the Service Packs and Major Upgrades section…

Copy and paste fail? I’m sure there in a bit of a rush on documentation.

Classic Epicor (pun intended). Came here to also say copy paste fail. The user community does the editing on these guides

Let’s say there is always room for improvement. I thought this sort of stuff would have been “Prisimed” by now… Eat your own dogfood and all that…

I am going to say the Architecture guide is very handy with lots of information about EF core and upgrading your code. Including tidbits on Linux-runtimes/windows runtimes, Cloud and Enterprise Cloud. Even executing Raw SQL Queries…

So I have been corrected it’s 2026.100.3 actually

hotfix n? :laughing:

Now I am really confused…

Will be a while before they find and clean up all the .1 references and change to .100. Not sure why they did that to themselves.

I thought there was still a local installer but that it basically just installed a URL shortcut? I have not looked at anything 2026 related yet so I could be wrong but I thought that was the way things were described, the smart client would not be there but there would still be an ‘installer’ that basically just created a URL shortcut.

Maybe IDK

I haven’t looked at 2026 yet either - maybe the local installer handles any required PowerTools and/or Edge Agent updates?

Great tip on the architecture guide.

At least they say “Kinetic.”

And a bit of installing later…

On an on-prem install the LocalClients folder still exists.

A shortcut does get installed. When you click on it you get.


An if you have not run your conversion after you attempt to login you get.

Then after you run your conversions in the browser you can login again and you get

Tada…

and a short while later you get… Drumroll please…

Surprise!

So the ‘local client’ installer we are all used to now installs Power Tools, not sure I like that, I’d much prefer if it was labeled distinctly so that people do not accidentally install PT on everyone’s machine.

I know most functionality can’t be used based on security rights but still, not such a fan of this change.

Let’s donate one - free of charge. Here’s some quickies with Word fonts

I was asked by a concerned Epiusersitizen about the buttons not working on powertools from previous verisons..

I can report that they all seem to work apart from Functions it throws:

Full Error
functions maintenance 2026.1 through powertools

## System Information ##
==================

AppServer Connection: https://StarLord/Kinetic2026_1_Demo
Form Name: Power Tools Menu
Customization Name: 
Menu ID: Ice.Menu.PowerTools
Software Version: 2026.1

============

Application Error

Exception caught in: Ice.Lib.EpiClientLib

## Error Detail ##
============
##!Message:##! The process failed to construct new instance of object Ice.Lib.App.Launch
##!Inner Exception Message:##! Exception has been thrown by the target of an invocation.
##!Program:##! Ice.Lib.EpiClientLib.dll
##!Method:##! LaunchDotNet

## Client Stack Trace ##
==================
   at Ice.Lib.Framework.PCallReflector.LaunchDotNet(String assemblyName, String className, Hashtable ctorList, String methodName, Hashtable methodList)

## Inner Exception ##
===============
Exception has been thrown by the target of an invocation.

##  ##

   at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)
   at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
   at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
   at System.Activator.CreateInstance(Type type, Boolean nonPublic)
   at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, StackCrawlMark& stackMark)
   at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
   at System.Reflection.Assembly.CreateInstance(String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
   at Ice.Lib.Framework.PCallReflector.LaunchDotNet(String assemblyName, String className, Hashtable ctorList, String methodName, Hashtable methodList)


## Inner Exception ##
===============
The type initializer for 'Ice.Lib.App.Launch' threw an exception.

##  ##

   at Ice.Lib.App.Launch..ctor()


## Inner Exception ##
===============
Could not load file or assembly 'Microsoft.Extensions.Caching.Abstractions, Version=10.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

##  ##

   at Ice.UI.EfxLibraryMaintenance.DI.MainContainerFactory.Create()
   at Ice.Lib.App.Launch..cctor()

But you have functions designer. I have not tested that… so others may know more.

Home button does not seem to work on FD… Could be my install

and the final test.

I had no errors on the way through which was nice. Unlike previous earlier versions where the EAC would break or you would get 503 errors etc trying to connect to the app server…

I did notice errors in the conversion logs though when I ran it.

Please report this