Error 1935 While Installing Symantec Mail Security for Microsoft Exchange (SMSMSE): An error occurred during the installation of assembly"policy.8.0.Microsoft.VC80.ATL,type="win32-policy"

Article:TECH160445  |  Created: 2011-05-19  |  Updated: 2014-06-04  |  Article URL http://www.symantec.com/docs/TECH160445
Article Type
Technical Solution


Issue



While running the SMSMSE installer a dialog box displays the following error message:

Error 1935. An error occurred during the installation of assembly ''policy.8.0.Microsoft.VC80.ATL,type="win32-policy",version="8.0.50727.42",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86". Please refer to...

The last message displayed in the SMSMSE installer slideshow is Registering Product Information. The installation rolls back and SMSMSE is not installed.


Error



 

  • SMSMSE MSI log file smsmse_verbose_install.log shows the following error sequence:

MSI (s) (80:90) [15:36:31:900]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=461405369)
MSI (s) (80:90) [15:36:38:203]: Assembly Error:An HRESULT could not be translated to a corresponding Win32 error code.
MSI (s) (80:90) [15:36:38:203]: Note: 1: 1935 2: {66332652-9C28-58B1-A01F-C8B3B9A1E18E} 3: 0x800736FD 4: IAssemblyCacheItem 5: Commit 6: policy.8.0.Microsoft.VC80.ATL,type="win32- policy",version="8.0.50727.42",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86"
MSI (s) (80:90) [15:36:38:203]: Assembly Error (sxs): To get more diagnostic information, enable the Component Based Servicing Log.

See the KB How to Obtain Detailed Logging While Installing Symantec Mail Security for Microsoft Exchange (SMSMSE) article for information on obtaining installation debug logs.

Conditions

  • Windows Component Based Service log (default location %windir%\logs\cbs\cbs.log) shows the following error sequence:

2011-05-25 14:49:26, Info                  SXS    Install Assembly from C:\Windows\WinSxS\InstallTemp\20110525144807873.0\8.0.50727.42.policy
2011-05-25 14:49:26, Info                  SXS    Submitting stage transaction with 2 operations
2011-05-25 14:49:26, Info                  CSI    00000005 Performing 2 operations; 2 are not lock/unlock and follow:
  Stage (1): flags: 8 app: [policy.8.0.Microsoft.VC80.ATL, Version = 8.0.50727.42, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:24{12.EN_US}]"win32-policy", TypeName neutral, PublicKey neutral]) comp: policy.8.0.Microsoft.VC80.ATL, Version = 8.0.50727.42, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:24{12.EN_US}]"win32-policy", TypeName neutral, PublicKey neutral man: @0x465688
  AddCat (14): flags: 0 catfile: @0x4657a8
2011-05-25 14:49:26, Info                  CSI    00000006 Creating NT transaction (seq 1), objectname [6]"(null)"
2011-05-25 14:49:26, Info                  CSI    00000007 Created NT transaction (seq 1) result 0x00000000, handle @0x234
2011-05-25 14:49:26, Info                  CSI    00000008@2011/5/25:18:49:26.404 CSI perf trace:
CSIPERF:TXCOMMIT;12029
2011-05-25 14:49:26, Info                  SXS    Submitting install transaction
2011-05-25 14:49:26, Info                  CSI    00000009 Performing 1 operations; 1 are not lock/unlock and follow:
  Install (5): flags: 0 tlc: [policy.8.0.Microsoft.VC80.ATL, Version = 8.0.50727.42, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:24{12.EN_US}]"win32-policy", TypeName neutral, PublicKey neutral]) ref: ( flgs: 00000000 guid: {27dec61e-b43c-4ac8-88db-e209a8242d90} name: [l:0]"" ncdata: [l:62{31.EN_US}]"C:\Windows\system32\msiexec.exe") thumbprint: [l:128{64.EN_US}]"f7bf65ca621d8ad32ead1500a08827be239d0f49d83dc20dabf57d2eb17adbd7"
2011-05-25 14:49:26, Info                  CSI    0000000a Component change list:
2011-05-25 14:49:26, Info                  CSI    0000000b Couldn't find the hash of component: policy.8.0.Microsoft.VC80.ATL, Version = 8.0.50727.42, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:24{12.EN_US}]"win32-policy", TypeName neutral, PublicKey neutral in the catalog [l:192{96.EN_US}]"\SystemRoot\WinSxS\Catalogs\f7bf65ca621d8ad32ead1500a08827be239d0f49d83dc20dabf57d2eb17adbd7.cat".

2011-05-25 14:49:26, Error                 CSI    0000000c@2011/5/25:18:49:26.638 (F) d:\longhorn\base\wcp\componentstore\csd_winners.cpp(1303): Error 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] originated in function CCSDirectTransaction::AddImplicationsToCatalogsAndVerifyComponentHashes expression: (null)
[gle=0x80004005]
2011-05-25 14:49:36, Error                 CSI    0000000d (F) 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] #1156# from CCSDirectTransaction::PrepareForCommit(...)[gle=0x90092004]
2011-05-25 14:49:36, Error                 CSI    0000000e (F) 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] #1155# from CCSDirectTransaction::ExamineTransaction(...)[gle=0x90092004]
2011-05-25 14:49:36, Error                 CSI    0000000f (F) 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] #1154# from CCSDirectTransaction_IRtlTransaction::ExamineTransaction(...)[gle=0x90092004]
2011-05-25 14:49:36, Error                 CSI    00000010 (F) CRYPT_E_NOT_FOUND #1045# from Windows::COM::CPendingTransaction::IStorePendingTransaction_Analyze(...)[gle=0x80092004]
2011-05-25 14:49:36, Error                 SXS    Analyze Transaction failed with 0x80092004

In this error sequence the installer is attempting to install a new version of the Microsoft Visual C++ 8.0 ATL library.  The installer uses the Windows Side-by-Side policy file from C:\Windows\WinSxS\InstallTemp\20110525144807873.0\8.0.50727.42.policy. The component based installer fails when trying to look up the has information from the file \SystemRoot\WinSxS\Catalogs\f7bf65ca621d8ad32ead1500a08827be239d0f49d83dc20dabf57d2eb17adbd7.cat.

 


Cause



The SMSMSE installer is unable to install the Microsoft Visual C++ 2005 Redistributable binaries.  This is typically the result of missing or corrupt files in the operating system.

These libraries are packaged into the SMSMSE installer.  During the "Registering Product Information" section of the install process the SMSMSE 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.

Some enhancements have been made to this section of the SMSMSE installer in the 6.5.8 release.

 


Solution



It is necessary to resolve the operating system missing files or corrupted files.

Workaround

Some customers have found that installing the Visual C++ 2005 libraries outside of SMSMSE then allows installation of SMSMSE.  Symantec has developed a stripped-down installer that only does the installation of the Microsoft Visual C++ 2005 Redistributable libraries.  Use this installer and then install SMSMSE.

1. Download the attached ZIP file strippedinstaller.zip to the exchange server and extract the files.
2. Open a command prompt and CD into the directory with the extracted files.
3. Run the following command:

setup.exe /v"/l*v log.txt"
 

4. If the install succeeds without any errors then run the SMSMSE installer.  NOTE:  Use the steps below to clean up settings before installing SMSMSE again.
 

If the installation of the stripped down installer fails collect the log file log.txt and open a case with Symantec Technical Support.

Technical Information

Installer Cleanup

After the installer rolls back certain items from SMSMSE are not uninstalled:

Services
Web Site
IIS Application Pool

If the installer is run again immediately after this issue different errors occur. 

Perform the following steps to remove the remaining items before running the installer again:

1. Open a command prompt and run the following command to remove the service:

sc delete smsmse

2. Remove IIS component

a. Open Start|Administrative Tools|Computer Management.
b. Navigate to Services and Applications > Internet Information Services.
c. On the right hand side menu expand Server Name > Sites.
d. Right click Symantec Mail Security for Microsoft Exchange and select Remove.
e. On the right hand side menu expand Server Name > Application Pools.
g. Right click on SMSMSEAppPool and select Remove.

NOTE:  If the installer runs and there are errors other than the 1935 error it is recommended to go through manual uninstall steps using this article: Manual removal instructions for Symantec Mail Security for Microsoft Exchange, Symantec AntiVirus/Filtering for Microsoft Exchange, or Norton AntiVirus for Microsoft Exchange.  See also: 

Manual removal script for Symantec Mail Security for Exchange (SMSMSE) for all versions

http://www.symantec.com/business/support/index?page=content&id=TECH214662

Checking Operating System File System Corruption and Missing Files

The Microsoft System Update Readiness Tool can be used to identify operating system corruption.

1. Download and run the tool on the computer. 
2. Open the file %windir%\logs\cbs\CheckSUR.log in an editor.

If there are no problems the log looks like this:


=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 14.0
2012-03-22 06:04

Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store

Summary:
Seconds executed: 897
 No errors detected
(w)    Unable to get system disk properties    0x0000045D    IOCTL_STORAGE_QUERY_PROPERTY    Disk Cache   

If there are problems detected the file contains entries like this:

(fix)    CSI Store Directory Missing    CSI Store Directory Created    C:\Windows\winsxs\amd64_microsoft-windows-winsrv_31bf3856ad364e35_6.0.6002.22662_none_14ce71156b255f5b\
(f)    CSI Payload File Missing    0x00000000    DWrite.dll.mui    amd64_microsoft-windows-directwrite.resources_31bf3856ad364e35_7.0.6002.22573_uk-ua_0b41fbec5615fde6   
(f)    CSI Store Directory Missing    0x00000002    winsxs\amd64_microsoft-windows-directwrite.resources_31bf3856ad364e35_7.0.6002.22573_uk-ua_0b41fbec5615fde6\    amd64_microsoft-windows-directwrite.resources_31bf3856ad364e35_7.0.6002.22573_uk-ua_0b41fbec5615fde6   
(fix)    CSI Store Directory Missing    CSI Store Directory Created    C:\Windows\winsxs\amd64_microsoft-windows-directwrite.resources_31bf3856ad364e35_7.0.6002.22573_uk-ua_0b41fbec5615fde6\
(f)    CSI Payload File Missing    0x00000000    DWrite.dll.mui    amd64_microsoft-windows-directwrite.resources_31bf3856ad364e35_7.0.6002.18409_ru-ru_2a21f8ee5fa3fff7   
(f)    CSI Store Directory Missing    0x00000002    winsxs\amd64_microsoft-windows-directwrite.resources_31bf3856ad364e35_7.0.6002.18409_ru-ru_2a21f8ee5fa3fff7\    amd64_microsoft-windows-directwrite.resources_31bf3856ad364e35_7.0.6002.18409_ru-ru_2a21f8ee5fa3fff7   
(fix)    CSI Store Directory Missing    CSI Store Directory Created    C:\Windows\winsxs\amd64_microsoft-windows-directwrite.resources_31bf3856ad364e35_7.0.6002.18409_ru-ru_2a21f8ee5fa3fff7\
(f)    CSI Store Directory Missing    0x00000002    winsxs\amd64_microsoft-windows-msmq-queuemanager-core_31bf3856ad364e35_6.0.6002.18005_none_ddc1f8341518e1ad\    amd64_microsoft-windows-msmq-queuemanager-core_31bf3856ad364e35_6.0.6002.18005_none_ddc1f8341518e1ad   
(fix)    CSI Store Directory Missing    CSI Store Directory Created    C:\Windows\winsxs\amd64_microsoft-windows-msmq-queuemanager-core_31bf3856ad364e35_6.0.6002.18005_none_ddc1f8341518e1ad\
(f)    CSI Store Directory Missing    0x00000002    winsxs\amd64_microsoft-windows-scanprofiles.resources_31bf3856ad364e35_6.0.6001.18000_en-us_60783839f880ee66\    amd64_microsoft-windows-scanprofiles.resources_31bf3856ad364e35_6.0.6001.18000_en-us_60783839f880ee66   
(fix)    CSI Store Directory Missing    CSI Store Directory Created    C:\Windows\winsxs\amd64_microsoft-windows-scanprofiles.resources_31bf3856ad364e35_6.0.6001.18000_en-us_60783839f880ee66\
(f)    CSI Store Directory Missing    0x00000002    winsxs\amd64_microsoft-windows-webdavredir-davclient_31bf3856ad364e35_6.0.6002.18005_none_f1d77dcf07be7706\    amd64_microsoft-windows-webdavredir-davclient_31bf3856ad364e35_6.0.6002.18005_none_f1d77dcf07be7706   

and the end of the file shows the number of issues:

Summary:
Seconds executed: 3247
 Found 13293 errors
 Fixed 6382 errors
  CSI Payload File Missing Total count: 8259
  Fixed: CSI Payload File Missing.  Total count: 1348
  CSI SP File Not Yet Pre-Installed Total count: 57
  Fixed: CSI SP File Not Yet Pre-Installed.  Total count: 57
  CSI Store Directory Missing Total count: 4977
  Fixed: CSI Store Directory Missing.  Total count: 4977

These errors must be resolved.  In many instances it is necessary to rebuild the operating system.

 


Attachments

Installer with just Microsoft runtime libraries
strippedinstaller.zip (13.5 MBytes)

Supplemental Materials

SourceETrack
Value2388656

SourceETrack
Value 2388645



Article URL http://www.symantec.com/docs/TECH160445


Terms of use for this information are found in Legal Notices