2024.1 On-Prem Solution Workbench cannot build CAB, with "Could not find a part of the path" error

Kinetic ERP Service Packs and Major Upgrades (any → 20XY.Z)
,
1

Version 2022.1 → 2024.1 on-prem

Win 2019 SQL 15.0.2000.5

@daniel.eskenazi FYI

Installed 2024.1 on the same DEV server as 2022.1. Built using conversion workbench on initial login. System runs and testing is 85% done and even our hugely customized UI isn’t giving much trouble.

Have done a pile of issue resolution and decided to do another build. Started collecting up issue resolution items in CABs and immediately ran into a problem:

image
image809×520 102 KB

I initially ran into this in the Kinetic version, noticed there was no option to prompt for CAB location, used menu to switch to classic version, notice options are missing.

I’ve checked or tried:

  • my permissions are correct;
  • my groups are correct;
  • restarted, regenerated, recycled, etc.
  • EpicorData folder permissions appear correct for all the service accounts;
  • 2022.1 instances work fine;
  • printing works fine;
  • processes run and save logs in EpicorData;
  • process successfully saves solution workbench error log in selected or default location;
  • found a reference to changing the System Agent client program directory from a local path to a network share path using a direct database update, but it didn’t change anything and in fact overwrote the server and client data directory paths too. Reverted.
  • Error doesn’t write anything to the Event Viewer.
  • A colleague thinks he’s heard of a setup issue with a url path in one of the config files, but I haven’t found anything;

I have a vague memory of John Friend helping me with a permissions or share setup on my 2022.1 setup but I can’t find any notes on it.

Anyone run into this? @moderators this wiki won’t let me create a tag for 2024.1. Can you create it?

1 Like
2

weird, it let me tag it in frequent flyer, but not here :thinking:

3

Oh I see, it’s a “special” tag that must be from “Versions”

1 Like
4

This is fixed in a patch update. I am not sure which one I’m afraid. But .8 has the fix in it.

The issue is the period ‘.’ In your username. A workaround, if you cannot patch up, is to run solution workbench under a user with no period in it.

The bug was introduced as part of the roll out of Kinetic UI solution workbench. The processing has been moved server side.

4 Likes
5

You’ve got to be kidding me… but yeah that was it.

Thank you a million!

2 Likes
6

I’m going to ask what happened to the additional checkboxes. Create documentation and encrypt?

7

I think there’s a section called advanced settings, maybe a button to access them?

In Kinetic / Browser it gets tricky due to Edge Agent but it seems to be feasible.

8

In classic it’s disabled on 2023.2… I have full rights to everything. I’d like to know what controls the enablementness of that advanced button…

On Prem so unless it is related to the Global Security manager, but I thought that was only cloud.

9

On 2021.2, we had an issue here on-prem that required us to enable Global SM for some reason, so you may have something there.

10

@Mark_Wonsil Going to act dumb here but where is that setting?

EDIT:
Disregard. It’s a hidden field in Classic you need to enable it in the list view.

11

I think this is it. Open Epicor Admin Console, go into the app server/users, select the user (usually manager or epicor) and enable:

image
image346×549 13.2 KB

12

oh duh - so far I’ve been moving stuff TO 2023 not from. Have just finished first CRP so that’s about to change

2 Likes
13

I’ll take a look at that @Mark_Wonsil

14

Went from 2022.1 to 2023.2

There has been some weirdness around some of our BPMs, which although did not error, they just did nothing.

We do have a lot of customisations and bpms.

15

Nope still greyed out

image