Receive Transfer Order - hourglassing on initial load

[JMPCONJ (John Magee)]

EDIT - this is in browser, 11.2.400.11…

Program opens…and the wheel spins and spins and spins…does finally load in one site but not the other two where the most receiving activity occurs. We ARE able to receive by filling in a Pack number and hitting TAB or ENTER…lines for the pack come up then…so we’re not entirely dead in the water.

Have an EpicCare case open, seems to be going by the playbook so far. (EDIT 3 - just gave up and closed it.)

No personalizations on mine - deleted everyone else’s as precaution. Tried their “application studio” reset (load base layer, exit). No dice. No associated BPMs at method level. Only one at data level is on TFOrdDtl.Update (so that wouldn’t come into play on an initial screen load). Their latest recommendation was a data model regen, recycle-app-pool and an IIS reset…which doesn’t seem to match up to previous screen-load issues we’ve had.

Anyone ever see this before?

EDIT 2: not only does the entry of the pack number work…but the basic search function will let you call up any pack with a “not received” status, check it off and receive it.

It’s just on the initial load coming in from the menu where the wheel goes round and round.

[JasonMcD (Jason McDermott)]

Oh yeah, it would crash our system.

I disabled it via BPM that says this:

I think they fixed it later…

Good reminder - I might be able to un-disable this when we upgrade.

Oh I had posted this:

SOS - Kinetic keeps freezing up for most users - I'll take any advice

I think we found the culprit. It is (I believe): Erp.BO.TransOrderReceiptSvc.GetRowsLandingPage So, a PSG consultant showed us how to look at the processes currently running in a specific app pool. Here is how (expand to see): And it showed this guy, with exceptionally long times on it. (The top one is 2,290 seconds, or 38 minutes.) This is a snapshot during a freeze-up today (before I did IISRESET to it). [image] You may have deduced as I did that this method is the Kinetic landing page …

[EDIT] And I guess there is no hope:

[JMPCONJ (John Magee)]

@JasonMcD

Oh yeah, it would crash our system.

I disabled it via BPM that says this:

Thanks for the advice…the search or the direct-entry of a valid pack number has been our workaround in the interim.

[klincecum (Kevin Lincecum)]

@JasonMcD

I disabled it via BPM that says this:

[JasonMcD (Jason McDermott)]

I’m not at all offended by the laughing minions, and I certainly have made some sarcastic BPM messages.

But I thought this one was pretty straightlaced. Curious what the humor is? Or am I that sarcastic all the time and don’t even realize? (Yes.)

[JMPCONJ (John Magee)]

I’d like to think the laughing minions GIF is about you having to put in a BPM in the first place. At least you had the ingenuity to block it from blowing up. Kudos.

[JasonMcD (Jason McDermott)]

I don’t know about ingenuity. The business was crippled and it was do or die.

Not because transfers are important, but because this one SQL query was bringing down the whole server.

[JMPCONJ (John Magee)]

We haven’t had that issue…yet…hopefully it stays that way.

[klincecum (Kevin Lincecum)]

@JasonMcD

Curious what the humor is?

@JMPCONJ

I’d like to think the laughing minions GIF is about you having to put in a BPM in the first place.

Pretty much.

@JasonMcD

Or am I that sarcastic all the time and don’t even realize? (Yes.)

Nah, you seem a’ight. I could probably deal with more sarcasm.