Unable to log in to the home page (404)

Kinetic ERP
1

What am I overlooking here? It is a fresh install of 2024.1.17, using our 10.2.600.11 DB. I performed the Upgrade DB steps prior to deployment of the app server, and once the app server was deployed I ran the conversions that are required when running the client for the 1st time.

When trying to log in, I am getting the error shown below. Clicking OK launches the client as expected.
image

If I keep the “Form to Use” as User Choice, anything that tries to open with Kinetic returns a 404. But, if I go to the web UI and log in and open up the same form there, it works as expected.

Changing the Form to Use to Classic gets everything working as expected.

I’ve looked everyw3here I can think of in the App Server and the Classic UI to try and find this HomePageUrl setting, but am not having as much luck as I would have hoped for. I am sure it is a simple thing that I am not familiar with yet.

2

What does the url look like in the client sysconfig?

1 Like
3

Well, that’s one place I did fail to look…and oddly enough, the URL in there is pointing to a completely different server than where it should be…

This is what it reads now:

value=“https://-
epicor2.*****.local/E11ProdConv/Apps/Erp/Home”

This is what it should read:
value=“https://-kinetic.*****.local/E11ProdConv/Home”

I’ll need to poke around and see why it is referencing a decommissioned server there.

4

try

value=“https://-kinetic.*****.local/E11ProdConv/apps/erp/home”

4 Likes
5

image

I’m willing to bet this is the issue…they were both set to the old server for some reason. (probably force of habit on my part).

I’m going to change those to the new one and redeploy. :crossed_fingers:

1 Like
6

@klincecum - without fail, every time you interact with a post I find myself looking in the cupboards for some popcorn to munch on. Granted, it is a tad too early for me to be eating popcorn (doesn’t mix well with coffee, heh), but at least I know I have some for later :slight_smile:

And that did appear to be the issue. I redeployed, checked the sysconfig and it looks correct. Logging into the client did not produce any errors this time. As always, thank you for helping me find the obvious, Kevin! :rofl:

2 Likes