Hi everyone,
while deploying avast! to a client installation cancels with the following error:
...
05/12/11 11:36:57: 172.xxx.xxx.xxx: Copying servers.def
05/12/11 11:36:58: 172.xxx.xxx.xxx: Creating service
05/12/11 11:36:58: 172.xxx.xxx.xxx: Starting service
05/12/11 11:37:25: 172.xxx.xxx.xxx: ReadProgress
05/12/11 11:37:25: 172.xxx.xxx.xxx: [b]Remote setup failed, error 0x20000011 (Error 0x20000011.)[/b]
05/12/11 11:37:25: 172.xxx.xxx.xxx: Finished with error in remote setup
05/12/11 11:37:25: 172.xxx.xxx.xxx: ReadLog
05/12/11 11:37:25: 172.xxx.xxx.xxx: Remote log not available
05/12/11 11:37:25: 172.xxx.xxx.xxx: RemoveProgress
05/12/11 11:37:27: 172.xxx.xxx.xxx: CloseConnection
I´ve googled for about an hour and tried everything I could think of, but no chance to fix it.
Same problem on another client.
If anyone has any idea what to do, please give me a hint ???
Thanks in advance,
best regards
Stephan
I also had the same error message today whilst trying to remote install two different clients. I’ve never had the problem before but created a manual msi package and installed that locally.
The two machines are now working fine but I’m still not sure why I couldn’t install remotely.
I’ve got around errors like this one with the manual MSI install as well, just as a work around to your problem.
What OS is it that is having problems though, I’ll assume Win 7?
I can’t comment on what OS s-kraft was using but I was having trouble with a Win 7 and XP.
Ok, well with a google search, the 0x20000011 error seems to be a “broken package” error.
Maybe try re-generating your MSI files / Deployment tasks and see if it makes any difference?
Thanks for your help.
First error was on Win XP, next day it appeared on a Win 2008 R2 server.
I already re-generated the MSI files and deployment tasks - does not change anything
Maybe manual MSI package helps, I will give you feedback on that one later.
//edit 1:
I just remote installed another Win XP client without any problems - package seems to be okay.
//edit 2:
Manual MSI install worked fine on the Win 2008 R2 server.
Problem is not solved but now I have some kind of workaround - thanks again.