Strange one - we use a mixture of Chrome & IE9 to admin our K1000 box - mainly only use IE to allow VNC control to desktops, and chrome for day to day monitoring as it seems faster - but after a protracted upgrade with the help of Kace Support (our DB files were way to big - although we only have a pretty small inventory -250 odd clients) - we have just noticed that we can log in perfectly using Chrome, but attempting to log in with IE9 it just hangs on the log in screen and never goes anywhere...

Anyone ever seen this before - it's most odd?

Answer Summary:
set the browser locale to en-us in affected browser or use different browser. Set the locale settings inside the box away from -default-
0 Comments   [ - ] Hide Comments


Please log in to comment

Community Chosen Answer




I would check out this blog. It sounds very similar, though he actually received an error rather than just hanging.


Answered 04/17/2013 by: Ben M
Ninth Degree Black Belt

  • BEN - you are a star! - as soon as we changed the language in the K1000 General Settings from 'default' to 'english' IE works perfectly again!!! how bizarre - Thanks very much for the pointer.
    • Glad its working for you. :)
Please log in to comment
Answer this question or Comment on this question for clarity



I would contact support immediately to get them working on the problem. Did you change your IP address on your KBOX before you performed the upgrade? If you didn't, there's going to be agent traffic bombarding your K1000 post update which can cause the WebUI to get sluggish, or not appear at all. Like I said, contact KACE support immediately in case it's something else. Good Luck!

Answered 04/17/2013 by: GeekSoldier
Red Belt

  • Thanks for the reply - I don't think its a hangover from the IP change as it was upgraded last week and seems quiet - It works tip top in Chrome, just can't use IE now..... its very odd.
    Maybe I'll have to raise a new ticket with Kace, was wondering if it was a silly config thing on 5.4 but maybe not :o)
Please log in to comment

the issue is afaik a mix up in the interpretation of the locales.
Mostly only systems with english locales except en-us are affected, as far as I have overseen this.

That was the cause why I wrote this blog.

For non english locales there is no issue but they are also suggested to modify the setting

Answered 04/18/2013 by: Nico_K
Red Belt

Please log in to comment

Did you happen to tell a bunch of machines to check in at the same time? Sometimes running several patching routines or large managed installs can cause this as well. If you check back on your server logs you should be able to see what your performance is looking like. This is probably where KACE support would start their diagnosis.

Answered 04/17/2013 by: GeekSoldier
Red Belt

Please log in to comment