This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
anilkumar_mca
Level 8
‎Apr 04, 2009 07:12 AM

Error 1935 & Error 1603, during GAC installation -- please help

Hi,
My installer is installing all the files, registrys and all.... but at some stage it rollback everything.
when i checked the log file, it is showing as:

MSI (s) (1C:64) [13:54:07:281]: Note: 1: 1935 2: {E6B71B0A-896E-4D3E-A63F-79C0D5CBE7DD} 3: 0x80131043 4: IAssemblyCacheItem 5: Commit 6: MyDll.Net,Version="4.0.0.1030",PublicKeyToken="CB595201818609EE",Culture="neutral",FileVersion="4.0.0.1030",ProcessorArchitecture="MSIL"
MSI (s) (1C:64) [13:54:07:296]: Product: MyProduct 4.0.0 -- Error 1935.An error occurred during the installation of assembly component {E6B71B0A-896E-4D3E-A63F-79C0D5CBE7DD}. HRESULT: 0x80131043. assembly interface: IAssemblyCacheItem, function: Commit, assembly name: MyDll.Net,Version="4.0.0.1030",PublicKeyToken="CB595201818609EE",Culture="neutral",FileVersion="4.0.0.1030",ProcessorArchitecture="MSIL"

and it also showing the following error.....

One more surprise is
when i build the same installer with same files in IS2009 evaluation version, it is working fine with no issues
If i build the same in IS2009 licenced version it is throwing error

whats wrong????
Labels (1)
Labels
Preview file
148 KB
0 Kudos
(1) Reply
anilkumar_mca
Level 8
‎Apr 04, 2009 12:05 PM

Hi,
Issue resolved..... 🙂

fyi...
reason for issues:

+ The dll which is causing issue('MyDll.Net') is having 'Check Dependencies & Properties' as .NET... property, so some dlls are getting copied to the release media and those dlls are causing issues.

+ Since i am building in two different machines, dependent dlls are not getting copied with evaluation version's build because those dlls are not there in evaluation's build machine....
0 Kudos