Primus Posted August 23, 2018 Posted August 23, 2018 Hi all, following our upgrade to Windows 10 we're seeing lots of errors on clients - most client PCs cannot login and get error 7326-5979-8000 which I cannot find on Capita's website. A few PCs can log in and there's no discernible difference between them and those that can't. Anyone seen this error before or have any ideas? Full error output below. 7326-5979-8000 Parameter is not valid. at SIMS.UserInterfaces.MainContainer..ctor(ParameterlessDelegate splashScreenClose, String autoStartMenuItemPath) at SIMS.UserInterfaces.DefaultEntryPoint.Main(String[] commandLineArguments) Pulsar -2147024809
Accura2k7 Posted August 23, 2018 Posted August 23, 2018 Generally i would say check .net is installed, and check the connect.ini file is correct.
Primus Posted August 23, 2018 Author Posted August 23, 2018 Yeah both are right - like I say there's no difference between PCs that work and PCs that don't.
Rawns Posted August 23, 2018 Posted August 23, 2018 Rename one of the SIMS .net folders to .OLD and try a clean reinstall via SOLUS?
Esteban_Child_of_the_Sun Posted August 23, 2018 Posted August 23, 2018 Is there any more detail in the Windows application logs?
Esteban_Child_of_the_Sun Posted August 23, 2018 Posted August 23, 2018 (edited) "Event viewer | Windows Logs | Application Logs" then go to the time you last ran it Edited August 23, 2018 by Esteban_Child_of_the_Sun
PD1279 Posted August 23, 2018 Posted August 23, 2018 Don't shoot me but have you tried disabling Anti-Virus as we had major issues after moving to Windows 10 with McAfee
Primus Posted August 23, 2018 Author Posted August 23, 2018 I'm looking at antivirus but they all have the same and some work (granted only a small number).
PD1279 Posted August 23, 2018 Posted August 23, 2018 Yes, but just disable it on one of them (and McAfee Access Protection) to rule it out. We have to disable the whole suite just so SOLUS3 can update the clients - MAD
Primus Posted August 23, 2018 Author Posted August 23, 2018 We never got to the bottom of this - some machines it was working, some wouldn't. We had to go back to an image we had from a week or two back and that's worked so no clue what was causing this as the difference between the two images was very very minimal.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now