[SAGE 200] Blank (white) login screen today?

[Jaan]

This has started happening today.

 

We just get a blank login screen. Anybody else got this?

 

Nothing has change ourside. Nothing hitting the filters or firewall..... alittle stumped.

Edited March 1, 2022 by Jaan

[SpaceInvader83]

Applocker blocking, they've added a new unsigned exe as part of the update process in Appdata, the executable is: CefSharp.BrowserSubprocess.exe

 

The path will be something like c:\users\BillyBob\appdata\Local\Apps\2.0\Random\Random\Stan..Random but you can pull it from eventvwr

 

I'm about to email them raising it as an issue for anyone using Applocker.

Edited March 1, 2022 by SpaceInvader83

[Jaan]

yep got 100s of hits for all 4 of our sage users on "CefSharp.BrowserSubprocess.exe"

 

Have you added you're applocker rule yet? has it worked? fancy sharing?

[Julian]

Thank you for this information, this is causing lots of grief.

[Jaan]

I've just added the file as above to the allow list for our user group using the file hash. Everything started working.

 

Thanks again SpaceInvader83, i didn't think of looking at applocker, i thought i was a webfilterig issue.

 

Cheers

[Julian]

SpaceInvader83, you may wish to add that the use of Applocker to restrict executables is regarded as best practice NCSC (UK National Cyber Security Centre), and as such not testing such a configuration is disappointing!

[SpaceInvader83]

A separate issue connected with the upgrade, when using the Data to excel function in reports it no longer works, report to excel still works mind.

[MicrodigitUK]

We just had this problem again today. Then I remembered that for the applocker policy we have set too a file hash because the executable it’s not signed. Obviously, with the Sage 200 updates there was a new unsigned executable that had a different file hash. Was chasing my own tail for a few hours before coming across this old thread, and looking in Event Viewer at applocker. The gotcha was you don’t get a normal applocker error message. And not even the white login box now, It just crashes executable. So giving this a bump if anyone’s got the same problem again after the recent Sage 200 updates. Don’t forget to update your applocker up policy If using a file hash after the update.

[newpersn]

We just had this problem again today. Then I remembered that for the applocker policy we have set too a file hash because the executable it’s not signed. Obviously, with the Sage 200 updates there was a new unsigned executable that had a different file hash. Was chasing my own tail for a few hours before coming across this old thread, and looking in Event Viewer at applocker. The gotcha was you don’t get a normal applocker error message. And not even the white login box now, It just crashes executable. So giving this a bump if anyone’s got the same problem again after the recent Sage 200 updates. Don’t forget to update your applocker up policy If using a file hash after the update.

Yes. We use this method as well and had to do the same this morning.

 

Thought something was broke on the image as it was only reimaged the other day..

[Jaan]

same here yesterday and i also referenced this thread.

[Jaan]

Anybody having issues with sage over the past few days just showing a splash screen and closing?

[timbo343]

Anybody having issues with sage over the past few days just showing a splash screen and closing?

We've had that in the past. Going into the local profile > AppData > look for sage and rename to .old usually fixes this though you have to gwt the user to re-run the setup exe.

[Jaan]

I had to update applocker as sage had a update