Typically long loading bars is anti-virus.  Configure the anti-virus so that they trust the path to the program files on the network (assuming they are loaded on an application server) and let the server check for viruses at night/after-hours.

1. Make sure your PATHs are correct.  If you ever migrated Sage servers, there might be \\oldserver\sage\runtime in your PATH, which slows things down.

2. Rebuild your SQL indexes at least once a year.

3. Make sure no users are on wireless, network speed should be 1Gb or better

4. When the train starts, look at SQL activity to see if one user is blocking others.  That user may need to have their _P.ISM deleted so that they have fresh finder settings, because they have been searching on non-indexed fields.

+1 for what Django and Jay said. But if that still isn't cutting the mustard, go to Help > Current Users > Show Screens Users Have Open. Look for instances of I/C Location Details. Ask those users to close their Location Details screens.

I don't have enough evidence yet, as it happens so infrequently, but I think there is some sort of opportunistic record locking phenomenon happening with the Location Details screen. And as soon as we start closing those Location Details screens, O/E comes back to life.

I have seen cases where SQL Index Rebuilding had been scheduled during the day and when it was working on ICILOC it locked horns with OE.

other things to watch for that can lock things up, is users leaving a search window open especially if using "auto Search", or leaving print preview windows open.  

Thanks for the suggestions everyone!

We will start of by investigating the anti-virus as suggest by Django. 

Will also suggest to all users to close search windows and print previews if they are not being used. 

From there we will monitor the results and report back to this thread. 

Sometimes this issue happens once a month sometimes multiple times a day. 

**UPDATE**

The problem is still occurring.

Lucky this time around there was only a handful of users in the system at the time.

I noticed one user was trying to post an order through order entry and their screen was not responding. So I closed the process and everything came good instantly.

We opened the order again straight away and posted it no problems. only a 3 line order.

Question now is why would an order entry screen freeze up like that when posting an order and effect everyone else.

We also double checked the anti-virus as suggested by Django and everything is good on that end.