(imported topic written by richard91)
After upgrading the BES console, all client deployment actions are failing with this error:
Assembling computer name…
Connecting to remote machine…
Copying installation files…
Opening the Service Control Manager…
Creating the installer service…
Starting the installer service…
Installation Error: Windows Error: The system cannot find the file specified.
Deleting installation files…
Closing connection…
Installation failed.
What’s the fix?
(imported comment written by mynameisbear91)
richard
After upgrading the BES console, all client deployment actions are failing with this error:
Assembling computer name…
Connecting to remote machine…
Copying installation files…
Opening the Service Control Manager…
Creating the installer service…
Starting the installer service…
Installation Error: Windows Error: The system cannot find the file specified.
Deleting installation files…
Closing connection…
Installation failed.
What’s the fix?
Going out on a limb here,
Do the System or Application event logs on the client(s) show anything abnormal?
(imported comment written by richard91)
Unfortunately, no.
(imported comment written by BenKus)
Hi Rich,
This error indicates that the deploy tool is copying an executable over to the remote machine and trying to start that executable as as service. It looks like the service is failing to start because the executable isn’t at the place we expected it to be… What OS are you deploying to? Is it a 32-bit or 64-bit OS?
Ben
(imported comment written by richard91)
Hey Ben,
We are pushing out to Windows XP Professional, 2K Professional and 2K3 Server – all 32 bit. Odd thing is this is happening after we ran fixlet ID #00-2468 “Updated BES Installation Folders Now Available! (Version 7.0.1).”
Thanks!
(imported comment written by bdoellefeld)
Same issue here. Been meaning to bring it up but hadn’t had the chance.
(imported comment written by BenKus)
Can you guys verify that the file “InstallerService.exe” exists at “C:\BESInstallers\BESClientDeploy\BigFixInstallSource” and there is a subfolder “ClientInstaller” with the agent installer in it?
If this issue continues, please contact our support who can hopefully figure it out.
Ben
(imported comment written by bdoellefeld)
Ben Kus
Can you guys verify that the file “InstallerService.exe” exists at “C:\BESInstallers\BESClientDeploy\BigFixInstallSource” and there is a subfolder “ClientInstaller” with the agent installer in it?
I confirmed this on my end, all exist. I just got done calling support for 2 other issues and am not eager to do another support call today.
Additionally, client deploy versions previous to 7.0.1 do work on the same machines this is failing on. I had a group of machines that I needed to get the agent on quickly. I ended up using version 6.0.21 client deploy on them and then sending the upgrade fixlet.
(imported comment written by BenKus)
Hi bdoellefeld,
If your 6.0.21 client deploy tool works well for you, you can try copying the 6.0.21 besclientdeploy.exe over the 7.0 version. If this works for you, then it tells us that it is the new client deploy tool that is failing and not the agent installer.
Thanks,
Ben
(imported comment written by saravanan@safezone91)
I am Saravanan. On Client deployment i faced the following error log. Installtion failed. Any one tell me the solution for this.
Assembling computer name…
Connecting to remote machine…
Copying installation files…
Opening the Service Control Manager…
Creating the installer service…
Starting the installer service…
Waiting for setup.exe to finish…
Deleting the installer service…
Waiting 10 seconds to verify installation…
Verifying installation…
Waiting 10 seconds to verify installation…
Installation Error: Windows Error: Access is denied.
Deleting installation files…
Closing connection…
Installation failed.
Thanks,
Saravanan
(imported comment written by saravanan@safezone91)
In some clients it is showing that “no network provider accepts the given network path”, how to solve this issue ?
saravanan
(imported comment written by BenKus)
Hi saravanan,
This is a Microsoft issue that can occur when connecting to shares. I did a search on Google for the error message and found thousands of articles that describe many reasons why this might happen… I am not sure the core cause, but it looks like the client deployment tool is connecting to the remote computers by hostname (or maybe the remote computers are connecting back to the client deploy tool’s share) and this error is being thrown by the Microsoft sharing code.
I think one article mentioned that they might have file and print sharing disabled on these computers.
Can you browse to these computers using \?
Ben
(imported comment written by rdamours91)
I use a group policy on the ou that the computers are in that enables file and print sharing. I leave the group policy on for a while until the pc’s pickup the policy. I deploy the clients to the pc’s and then unlink the group policy as I don’t want file and print sharing enabled all the time.
Works perfectly for me especially with the latest version client deployment tool.