1935 Error Vista
Contents |
font size Print view FAQ Register Login [Solved] Error 1935 on Vista Issues with installing under all versions of MS Windows Post a reply 13 posts • Page 1 of 1 [Solved] Error 1935 on Vista by gchris » Tue Dec 18, 2007 1:53 pm hi all,I error 1935 windows vista tried to upgrade my OpenOffice with 2.3.1 version but i got an Error 1935 with these microsoft office error 1935 vista informations (i translate them from french) :Error 1935. An error occur during the assembly installation : di_types,publicKeyToken="ce2cb7e279207b9e", version="1.1.11.0",culture="neutral".For more informations, bla bla bla error 1935 office ....My PC is a Dell Laptop with Windows Vista IntégralFor the installation i did :- Uninstall previous openoffice version- Download official package from fr.openoffice.orgI found informations on fews board for this trouble but all tips are for windows XP
Error 1935 Visual C++
and are not up to date for vista.Hope we will find a solution with your helpRegardsChristophe Last edited by Hagar Delest on Tue Jun 10, 2008 11:58 am, edited 2 times in total. Reason: tagged the thread as Solved. gchris Posts: 3Joined: Tue Dec 18, 2007 1:43 pm Top Re: Error 1935 on Vista by Bill » Tue Dec 18, 2007 2:24 pm Did you search the forum for the error and try anything which has already been error 1935 fix suggested? Bill Posts: 5739Joined: Sat Nov 24, 2007 6:48 am Top Re: Error 1935 on Vista by gchris » Tue Dec 18, 2007 2:45 pm hi Bill,Yes, i found information about trouble with .NET so i tried to upgrade it but a message appear telling that .NET is intégrated to system and can't be upgraded.I tried all solutions i found on the board but none permit the installation... gchris Posts: 3Joined: Tue Dec 18, 2007 1:43 pm Top Re: Error 1935 on Vista by gchris » Tue Dec 18, 2007 3:30 pm hi,I post here the solution i just found that permit the correct installation :- In the the /windows/system32 directory you'll find a file named 'mscoree.dll'- rename mscoree.dll to mscoreebak.dll- install OpenOffice- rename mscoreebak.dll to mscoree.dllThat's allHope this will helpRegardsChristophe gchris Posts: 3Joined: Tue Dec 18, 2007 1:43 pm Top Re: [Solved] Error 1935 on Vista by rABiD_kittEn » Fri Jul 11, 2008 7:51 am Thanks, Christophe, for putting your solution here!I have been battling with Vista trying to install OpenOffice. I have updated my Firefox, & then switched to IE to try to update .NET to 3.5. I came to find out that that was a waste of a lot of time. I took the time to download Vista's SP1, to find that it was already installed (oops)!When I read your solution, I had a lot of tro
be down. Please try the request again. Your cache administrator is webmaster. Generated Thu, 29 Sep 2016 19:34:47 GMT by s_hv996 (squid/3.5.20)
assemblies that occur on Windows Vista and later ★★★★★★★★★★★★★★★ Aaron StebnerOctober 7, 20095 0 0 0 Introduction 1935 errors can occur during an MSI-based installation while installing .NET assemblies or Win32 assemblies. Most https://blogs.msdn.microsoft.com/astebner/2009/10/07/diagnosing-and-resolving-1935-errors-for-win32-assemblies-that-occur-on-windows-vista-and-later/ of the workarounds that can be found on blogs and forums (including all of the information in my 1935 error troubleshooting guide) only apply to 1935 errors that happen while installing .NET assemblies. This blog post will explain how to troubleshoot 1935 errors that occur while attempting to install Win32 assemblies in an MSI-based installer. The information in this blog post only applies to Windows Vista and later versions error 1935 of Windows, and it also only applies to Win32 assemblies. For additional information about troubleshooting 1935 errors that occur on versions of Windows before Windows Vista and that occur for managed (.NET Framework) assemblies, please refer to the 1935 error troubleshooting guide. How to identify a 1935 error caused by a Win32 assembly on Windows Vista and later For 1935 errors that occur while installing Win32 assemblies in an MSI-based error 1935 vista setup (which I have seen most commonly in the past for Visual C++ runtime files), there are some specific diagnosis and troubleshooting steps that you will need to use that are different than the ones used for managed assemblies. On Windows Vista and higher, Windows Installer uses the same underlying installation engine as the OS component installation engine (also known as CBS) to install Win32 assemblies. As a result, anything that can cause an OS update or hotfix to fail to install can cause this type of 1935 error. You will typically need to do some more in-depth analysis on the affected system in order to narrow down the root cause and identify possible solutions. When this type of 1935 error occurs, you will see the following information in a verbose MSI log file: MSI (s) (54:32) [12:34:56:789]: Assembly Error (sxs): To get more diagnostic information, enable the Component Based Servicing Log. How to identify a root cause and possible solution As the above log file entry suggests, there is not enough detailed error information in a verbose MSI log file to determine a root cause of this type of 1935 error. That means you will need to look in the Component Based Servicing (CBS) log fil