timbo343 Posted November 13, 2015 Posted November 13, 2015 I have seen threads about this topic on earlier versions however I'm running 5105 and there are a few users who are still getting this error. The only way to get round it, is to reinstall impero on the machine. Does anyone know why this is occurring still 2 versions later?
Arreks Posted November 13, 2015 Posted November 13, 2015 I've never had this issue on 5105 and I've been using it since beta. What's the exact error? reinstall may only be a temporary fix.
clockend25 Posted November 13, 2015 Posted November 13, 2015 Can't wait for a new version. 5105 has been a complete PITA.
timbo343 Posted November 13, 2015 Author Posted November 13, 2015 Its only started in the last few weeks on my machine and the bursars - im not sure what has changed, if anything. Its just the box standard failed service message... ImperoClientSVC could not start....
Arreks Posted November 13, 2015 Posted November 13, 2015 Which operating system? also, have you set both Impero services to start delayed? 1
timbo343 Posted November 13, 2015 Author Posted November 13, 2015 Which operating system? also, have you set both Impero services to start delayed? Windows 7. Ah no, they are both set to Automatic rather than delayed start. Will make the change and see what happens, might be a couple of days before i come back with an update.
howartp Posted November 13, 2015 Posted November 13, 2015 (edited) Rename the ilog.whatsit file - if it's corrupt, the service sez nope. Translated into English.... rename the YYYY-MM.ilog file in Program Files (x86) > Impero Solutions Ltd > Impero Server > Data > Logs > Text Peter Edited November 13, 2015 by howartp
NokiX Posted November 13, 2015 Posted November 13, 2015 I believe this can also be caused when auto update is enabled as it will try and shutdown the service to perform the upgrade when it already has the latest version and then it prevents the service from being able to start at all. You can fix this by deleting part of the updates folder on the client however I'm unable to remote into my machine currently so I can't actually check which those files were! If you check the contents of that folder against a working machine that should tell you if anything is in there that shouldn't be.
timbo343 Posted January 4, 2016 Author Posted January 4, 2016 (edited) Just want to open this thread again, we are seeing more and more machines on our network having this problem where the Impero Client SVC is not starting. The only way to get it started on problematic machines is to connect remotely to the local machine's services and force the service to start. Even forcing the service to start, i get errors on how the service could not start. It takes about 3 - 4 forces to get the service to start. I was wondering if anyone is having the same problem? Edited January 4, 2016 by timbo343
timbo343 Posted January 4, 2016 Author Posted January 4, 2016 Is this on the server? Its only effecting the local machines rather than the server. I would have thought it would be something on the local machine that needed changing.
timbo343 Posted January 4, 2016 Author Posted January 4, 2016 For us the issue was a server issue and a restart of the server software and rename of the file shown resolved clients not being able to connect. Cheers, i know @howartp mentioned it before but thought that was when all machines had a problem, for us it's affecting a handful of machines.
howartp Posted January 4, 2016 Posted January 4, 2016 Our problem was the server service not restarting; we've not had a problem with the client services starting. Peter
timbo343 Posted January 11, 2016 Author Posted January 11, 2016 Just to update this thread, Impero support have come back to me and said: Could you try the following on problematic machines: Navigate to C:\Program Files (x86)\Impero Solutions Ltd\Impero Client\Update Delete the 'pending' folder if it exists Start the client service (should start first time) This has resolved the problem in case anyone else has the same problem
timbo343 Posted January 11, 2016 Author Posted January 11, 2016 I tried that too, it was the pending folder which was at fault.
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