Is Dashboard Entry and Maintenance still stuck in Classic? I am working in Pilot and I want to try converting more dashboards, but I can’t open Dashboard maintenance without installing the edge agent separately for pilot. Do I need to keep two versions of edge agent running so I can use pilot and live?
EDIT 1: Just tried installing edge agent for pilot and it broke the edge agent. Now it doesn’t work for live or pilot.
EDIT 2: I found Epicor Local Edge Agent in start menu and ran it, only to get this nonsense:
System.InvalidOperationException: Unable to configure HTTPS endpoint. No server certificate was specified, and the default developer certificate could not be found or is out of date.
To generate a developer certificate run 'dotnet dev-certs https'. To trust the certificate (Windows and macOS only) run 'dotnet dev-certs https --trust'.
For more information on configuring HTTPS see https://go.microsoft.com/fwlink/?linkid=848054.
at Microsoft.AspNetCore.Hosting.ListenOptionsHttpsExtensions.UseHttps(ListenOptions listenOptions, Action`1 configureOptions)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.AddressesStrategy.BindAsync(AddressBindContext context, CancellationToken cancellationToken)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindAsync(ListenOptions[] listenOptions, AddressBindContext context, Func`2 useHttps, CancellationToken cancellationToken)
at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerImpl.BindAsync(CancellationToken cancellationToken)
at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerImpl.StartAsync[TContext](IHttpApplication`1 application, CancellationToken cancellationToken)
at Microsoft.AspNetCore.Hosting.GenericWebHostService.StartAsync(CancellationToken cancellationToken)
at Microsoft.Extensions.Hosting.Internal.Host.<StartAsync>b__15_1(IHostedService service, CancellationToken token)
at Microsoft.Extensions.Hosting.Internal.Host.ForeachService[T](IEnumerable`1 services, CancellationToken token, Boolean concurrent, Boolean abortOnFirstException, List`1 exceptions, Func`3 operation)
at Microsoft.Extensions.Hosting.Internal.Host.StartAsync(CancellationToken cancellationToken)
at KineticTray.Program.Run(StartupInfo startupInfo, CancellationToken token) in C:\agent\_work\2\s\src\KineticTray\Program.cs:line 153
at KineticTray.Program.Main(String[] args) in C:\agent\_work\2\s\src\KineticTray\Program.cs:line 64
Disclaimer: This is my experience, and I am, after all, a Rookie.
The key to get the Edge Agent set up properly is the URL screen and the Path screen (URL and Path for lack of a better way of describing them). Be sure to add the URL for each environment (up to 4) to the URL screen. This step is required to do any printing from the Browser. If you want to open Classic forms from the browser, you need to the Client software loaded on the computer, and set up the next screen, the Path screen to the path for the Kinetic.exe file. The trick is to be sure to match the path screen line number to the URL screen line number. If you are running the same version on all environments, you should be able to just enter the path on the first line of he Path screen. If you are running different versions between your environments, you have to point the path to the Kinetic.exe in the appropriate client version folder. Additionally, You need to delete the unused config files from the various versions folders. For example, if you are running your Live and Test environments on 2024.1.13, and your Pilot environment at 2024.1.26, you need to delete the Pilot config file from the 2024.1.13 folder and the Live and Test config files from the 2024.1.26 folder. If the URL for Pilot is on line 2 of the URL screen, the path on line 2 of the Path screen must point to the Kinetic.exe file in the 2024.1.26 folder.
