While I have lots of experience with earlier version of both Epicor and Vantage, Kinetic is fairly new to me. Much of my earlier customization experience at my previous employer had centered around using those now obsolete built-in extra fields such as “character0X” when needed. Consequently, I don’t have a lot of experience using the UD tables and fields.
Anyways, yesterday I attempted to add my first UD field to the Customers table inside of a Kinetic test-DB, and then regenerate its data-model. Unfortunately, 20+ hours later this process still appears to be running, and I have no idea how much longer we should expect for this regeneration process to take.
Our database is about 27 gigs in size, and so-far both our Epicor server, and our SQL server do not appear to be getting slammed in terms of CPU, Memory, Network, or Disk usage. So, I do not know where the bottleneck is.
I’m assuming that when this process completes that a dialog will pop-up telling me so. But so far, I’m only seeing a never-ending “Work in process” dialog box inside of the Epicor Administration Console on the server.
I’d appreciate input in terms of what I should expect to see, from anyone who has done this before.
If you have a test environment you could try it there.
Also, in previous versions of the admin console (if you are on prem which I should’ve checked on your profile before starting to type this response), the “complete” message box would pop up behind things at times so you would think it’s still running when in reality the message popped up 10 minutes ago…
We are running on-prem. And I never, ever try new-to-me stuff like this inside of a production database without trying it inside of a test database first.
And I have wondered if a hidden dialog telling me that the process has completed might have popped-up inside of the admin console 19 hours ago. But if there such a dialog, I can’t find it.
Will it hurt anything if I try to close the admin console, and re-launch it?
Well it’s not that it was “hidden” like it never popped up, it just would pop up without focus… so it would be behind all the other forms that were open.
How do you know it hasn’t finished yet?
@klincecum do you know of any flags that say it finished besides the little pop up?
I would think something would tell you/indicate that it’s not running anymore.
The admin console is unresponsive other than allowing me to move the “Work in progress” dialog around the screen. And since that dialog lacks an OK button, I cannot get it to go away to let me see anything else inside of the console without killing the console process first.
This happened to me. The “Complete” box popped up and wasn’t even in the same taskbar icon as the Regenerate window. I waited like 4 hours and it was just sitting there the whole time. These usually take about 15 minutes on our server.
That’s the thing, the inprogress bar isn’t the one that has an OK button, it’s always been a separate dialog box that pops up for me when I’m done. But I don’t think I’ve done a kinetic regen in some time so I don’t know if they fixed that.
Did you reach out to support to help you with this yet? If you get the upgrades/install team they should be able to rip through this inquiry with some ease.
Yes, but I’m still waiting to hear back from support. Although I strongly suspect that this process completed long ago.
FWIW: I did find another task-bar Icon as described above. And when I closed it (even though it did not indicate that the process had completed), the busy dialog went away.
Got to love the MMC. Don’t forget you can craft your own powershell, batch, command files to run many of the operations that the Admin console provides. Take a look at the administration command line tech reference for more detail.
After learning that the “finished” dialog does not always display (or that it gets hidden somehow) when launching this process, I tried another regeneration yesterday. And it only took about 5 minutes. And amazingly, the “finished” dialog actually did display the second time around.
So, this is an intermittent display-only bug. The regeneration process itself appears to only take a few minutes, regardless of what the busy window may indicate.
I think this is Epicor’s way of hazing new admins. Sending you to look for stuff in the basement of an aircraft hangar, etc. (Not a real example at all…)
