remote install error 1726

i’m scratching my head trying to figure out this install error. it’s a win 7 sp1 64 bit machine all updates have been ran and i keep getting the error.

any ideas?

thanks in advance for any help.

Brian

Can you post the portion of the remote install log for this client?

11/01/12 17:10:00: WS75: Creating service
11/01/12 17:10:00: WS75: CreateService C:~AVINSTL\aswISvc.exe error 1726 (The remote procedure call failed)
11/01/12 17:10:00: WS75: RemoveOnError
11/01/12 17:10:00: WS75: RemoveFolder \WS75\C$~AVINSTL
11/01/12 17:10:01: WS75: CloseConnection
11/01/12 17:10:01: WS75: Finished with error
11/01/12 17:10:01: TerminateAll
11/01/12 17:10:01: rinstInstall end 0

so it goes through the entire install process and fails at this point.

I was running into this issue as well. I had to enable “Remote Service Management” in the domain profile for Windows Firewall > Allowed Programs. You may also want to check and see if these settings are enabled in GP under Computer Configuration > Admin Templates > Network > Network Connections > Windows Firewall > Domain Profile:
Windows Firewall: Allow inbound file and printer sharing exception
Windows Firewall: Allow inbound remote admin exception
Windows Firewall: Allow inbound Remote Desktop exceptions

It seemed to work on one PC, but now I’m getting these errors:
11/02/12 14:23:59: HLPC04: CreateService C:~AVINSTL\aswISvc.exe error 1305 (The revision level is unknown)
11/02/12 14:13:40: HLPC08: OpenSCManager error 1726 (The remote procedure call failed)

so, i’m getting this error on every machine i try to roll this out to now. i’ve made sure that firewall settings are all allowing communication and all updates have been applied. is there anyone out there with a fix?

all systems are 64 bit win 7 pro with all sp1 updates. windows firewall is turned off in gpo and sonicwall is configured properly. i’m not sure what to do at this point. i was able to factory reset 1 machine and start over and avast pushed out the install perfectly. I’d really hate to have to do that to every machine.

thanks in advance for any help or insight.

Brian

since with a reset you machine could be remote installed its not a problem on the Avast side.
It still is somewhere getting blocked by the settings you made in the machines itself…

Are you sure that the network connection type on the machines is also set to domain network?
If it is set to home or public network (for whatever reason) then the other firewall settings apply.

Did you also check in the manual to which ports actually need to be opened for remote deployment?

@VCW and @bwsanders

If your PC connected to the AD, you can use the login script to do the installation from the installation package.

or try this link http://forum.avast.com/index.php?topic=95105.0

@SPI i’ve already tried the link that you posted but it seems as those my settings are already correct so i’m thinking that it must be an update that is blocking something somewhere along the line.

is there a way to install locally to the client and have it still be managed through aea?

You can install it locally. Either generate a offline install package (AEA) or use the web download link (ASOA). In addition you can just download the client from the avast website and do a custom install and it will ask you for the address of your AEA or ASOA server.