Installation Error 1935: An error occurred during the installation of assembly.

Error 1935. An error occurred during the installation of assembly

'Microsoft.VC80.MFCLOC,
version="8.0.50727.762",pubicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64",type="win32"


This is issue occurs when you are trying to install Microsoft Visual C++ Redistributable package or when you are trying to install a software that needs Microsoft Visual C++ binaries.

This is typically the result of missing or corrupt files in the operating system. During the "Registering Product Information" section of the install process the installer "finalizes" the installation of the Microsoft runtime libraries. This finalization may include updates to the Windows Side-by-Side library configuration. In this case the installer is failing while updating the Windows Side-by-Side library configuration.



One of the following solutions must resolve this issue :-

1. Disable the Anti-virus.

2. Open an elavated command prompt and run the following comand:-

fsutil resource setautoreset true C:\

Reboot the system.

The "fsutil" command above will direct the "Transactional Resource Manager" to clean its metadata on the next drive mount.

3. Download and install the latest Msi installer from Microsoft

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=5a58b56f-60b6-4412-95b9-54d056d6f9f4

4. This issue may occurs due to the corrupt data store for .netframework. The .NET Framework cleanup tool is available for download at the following locations:

http://cid-27e6a35d1a492af7.skydrive.live.com/self.aspx/Blog_Tools/dotnetfx_cleanup_tool.zip
http://blogs.msdn.com/cfs-file.ashx/__key/CommunityServer-Components-PostAttachments/00-08-90-44-93/dotnetfx_5F00_cleanup_5F00_tool.zip

Save the cleanup log which will tell you what versions of .NET it cleaned and re-install them.

5. Enable the "Windows Modules Installer" service. Ensure that the Windows Installer service is set to "Manual"

6. This error has been observed when the insufficient permissions exist on this folder:

C:\Windows\winsxs\InstallTemp

The minimum needed (and default) permissions are:
Read & execute
List folder contents
Read
Write
Special permissions

7. If you do not find C:\Windows\winsxs\InstallTemp, then create an empty folder in C:\Windows\winsxs\ and name it as "InstallTemp".

8. If none of these works Run chkdsk.

Backup Exec Remote Agent Installation Fails for X and Y issues - A Workaround

Following is a workaround to install Backup Exec Remote Agent on a Windows machine. This is not a fix. There may be times when you cannot install RAWS due to Microsoft issues. For example, when windows installer is corrupted, error 1935, some .NET issues and times when you are left out with no troubleshooting.

TAKE A BACK OF REGISTRY BEFORE PERFORMING ANY REGISTRY CHANGES

You are unable to install the Backup Exec remote agent on SERVER - A for x reasons..

On Server - A

1. Uninstall the existing RAWS if present, Follow the above troubleshooting steps if the uninstallation fails.
2. Confirm to delete C:\Program Files\Symantec\Backup Exec folder.
3. Confirm you delete the following registry entries :
HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec for Windows
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BackupExecAgentAccelerator
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PDVFSDriver
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PDVFSNP
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PDVFSService
4. Reboot the server.


5. From another server Server - B which abides the following conditions :-

-Same operating system as the Server - A.
-Same type as Server - A. Both 32 bit or Both 64 bit.
-Must have the Backup Exec remote agent installed and has the latest updates installed.

Copy C:\Program Files\Symantec\Backup Exec folder from Server - B and paste under C:\Program Files\Symantec in Server- A
OR just copy the entire Symantec folder.

6. Export the following registries from Server - B :-

HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec for Windows
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BackupExecAgentAccelerator
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PDVFSDriver
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PDVFSNP
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PDVFSService

7.Import them to Server - A:-

8. Reboot Server - A.
9. Once the server boots up you will see that the remote server has been installed.
10. Confirm beremote service and error recording service are on running status.
11. Establish trust relationship. Confirm that the remote agent is publishing the correct IP address or Name.
12. Try running a backup. And it must be successfull.


The above solution will work in any case of remote agent installation failure. Visual C++ runtime redistributable package is a must for beremote service and error recording service to start. Without this package remote agent will not work. Same applies .NET.