none
.Net Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.InvalidOperationException; Event Id: 1026 RRS feed

  • Question

  • I get the error only when I run the wpf client application from my local machine: 

    .Net Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.InvalidOperationException; 

    Event ID: 1026

    The above error does not occur on other machines. Steps taken to debug as per some MSDN blogs:

    1. Repaired .Net framework 4.0 and removed 4.5 because the client is supported with .Net 4.0 alone. - did not work

    2. Reinstalled VS 2010 - did not work

    Appreciate if someone can share optimal solutions. Thanks!

    Tuesday, January 12, 2016 5:37 PM

Answers

  • Hi Saman,

    Thank you for posting in MSDN forum.

    Firstly, I suggest you use .NET Framework Setup Verification Tool to check if the .NET
    Framework is ok. 
    http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx


    If you find there is anything wrong with .NET Framework, you may use Microsoft .NET Framework Repair Tool to do a repair, This tool detects and tries to fix some frequently occurring issues with the setup of Microsoft .NET Framework or with updates to the Microsoft .NET Framework.
    https://www.microsoft.com/en-us/download/details.aspx?id=30135

    Besides, you could try using a standalone installer to install .NET Framework 4.0

    You can get the Standalone Installer from below link:

    https://www.microsoft.com/en-us/download/details.aspx?id=22833

    Here are some common install tips of .NET Framework installation:

    ·         Turn off youranti-virus/antispyware software during installation

    ·         Install the latest Windows from the Windows Update site

    ·         Complete or dismiss Windows Update before installation. (and don't forget to turn it on later)

    ·         If the installation fails, you can collect the setup log file and analyze them.

    You can follow below steps to collect log files:

    1.       Try to go to your "%temp%"
    folder (Start Menu >>Run >> Type "%temp%).

    2.       Manually filter the .net framework logs from "%temp%" folder .
    Please upload the file to https://onedrive.live.com/  and share the link here.

    Best Regards,


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.

    Click HERE to participate the survey.

    Tuesday, January 19, 2016 8:06 AM
    Moderator
  • Hi Saman,

    Sorry for my delay reply, I have checked your KB2468871_20160112_002456086-Microsoft .NET Framework 4 Extended-MSP1 log file and find several error message as below:

    DEBUG: Error 2746:  Transform RTM.1 invalid for package C:\windows\Installer\ef61e.msi. Expected product {3C3901C5-3455-3E0A-A214-0B093A5070A6}, found product {8E34682C-8118-31F1-BC4C-98CD9675E1C2}.
    MSI (s) (80:0C) [01:21:16:309]: Skipping validation for patch transform #RTM.1.  Will not apply because previous transform was invalid
    MSI (s) (80:0C) [01:21:16:309]: Looking for patch transform: RTM.2
    1: 2746 2: RTM.1 3: C:\windows\Installer\ef61e.msi 4: {3C3901C5-3455-3E0A-A214-0B093A5070A6} 5: {8E34682C-8118-31F1-BC4C-98CD9675E1C2}
    DEBUG: Error 2746:  Transform RTM.2 invalid for package C:\windows\Installer\ef61e.msi. Expected product {0A0CADCF-78DA-33C4-A350-CD51849B9702}, found product {8E34682C-8118-31F1-BC4C-98CD9675E1C2}.
    MSI (s) (80:0C) [01:21:16:309]: Skipping validation for patch transform #RTM.2.  Will not apply because previous transform was invalid
    MSI (s) (80:0C) [01:21:16:309]: Looking for patch transform: RTM.3
    1: 2746 2: RTM.2 3: C:\windows\Installer\ef61e.msi 4: {0A0CADCF-78DA-33C4-A350-CD51849B9702} 5: {8E34682C-8118-31F1-BC4C-98CD9675E1C2}
    DEBUG: Error 2746:  Transform RTM.3 invalid for package C:\windows\Installer\ef61e.msi. Expected product {F5B09CFD-F0B2-36AF-8DF4-1DF6B63FC7B4}, found product {8E34682C-8118-31F1-BC4C-98CD9675E1C2}.
    MSI (s) (80:0C) [01:21:16:309]: Skipping validation for patch transform #RTM.3.  Will not apply because previous transform was invalid

    For these kind of error message, We are consistently seeing this issue caused by a missing directory, C:\Windows\Microsoft.NET\Framework\URTInstallPath_GAC (or %SystemRoot%\Microsoft.NET\Framework\URTInstallPath_GAC).

    To work around this issue, please try the steps below:

    1. Open an elevated command prompt.
    2. Type: mkdir %SystemRoot%\Microsoft.NET\Framework\URTInstallPath_GAC

    In PowerShell, use $env:SystemRoot instead of %SystemRoot%.

    If the above doesn't work, I would suggest you backuo all your important files on your machine, then do a OS reformat, a clean environment will be more helpful to re-install .NET Framwork and same much troubleshooting time.

    Best Regards,


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.

    Click HERE to participate the survey.

    Wednesday, January 27, 2016 2:45 AM
    Moderator

All replies

  • Hi Saman,

    Thank you for posting in MSDN forum.

    Firstly, I suggest you use .NET Framework Setup Verification Tool to check if the .NET
    Framework is ok. 
    http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx


    If you find there is anything wrong with .NET Framework, you may use Microsoft .NET Framework Repair Tool to do a repair, This tool detects and tries to fix some frequently occurring issues with the setup of Microsoft .NET Framework or with updates to the Microsoft .NET Framework.
    https://www.microsoft.com/en-us/download/details.aspx?id=30135

    Besides, you could try using a standalone installer to install .NET Framework 4.0

    You can get the Standalone Installer from below link:

    https://www.microsoft.com/en-us/download/details.aspx?id=22833

    Here are some common install tips of .NET Framework installation:

    ·         Turn off youranti-virus/antispyware software during installation

    ·         Install the latest Windows from the Windows Update site

    ·         Complete or dismiss Windows Update before installation. (and don't forget to turn it on later)

    ·         If the installation fails, you can collect the setup log file and analyze them.

    You can follow below steps to collect log files:

    1.       Try to go to your "%temp%"
    folder (Start Menu >>Run >> Type "%temp%).

    2.       Manually filter the .net framework logs from "%temp%" folder .
    Please upload the file to https://onedrive.live.com/  and share the link here.

    Best Regards,


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.

    Click HERE to participate the survey.

    Tuesday, January 19, 2016 8:06 AM
    Moderator
  • Thanks Lana Xu. I am reaching out to IT support as they installed it on my machine. Will upload shortly. 
    Wednesday, January 20, 2016 2:25 PM
  • Here are the logs:

    https://onedrive.live.com/redir?resid=CD99DFB5AB8D2CD7!121&authkey=!AB203Ok9uwsb72U&ithint=file%2czip

    Sorry for the delay.

    Friday, January 22, 2016 2:44 PM
  • Just checking in to see if the logs were accessible. Thanks!
    Tuesday, January 26, 2016 2:41 PM
  • Hi Saman,

    Sorry for my delay reply, I have checked your KB2468871_20160112_002456086-Microsoft .NET Framework 4 Extended-MSP1 log file and find several error message as below:

    DEBUG: Error 2746:  Transform RTM.1 invalid for package C:\windows\Installer\ef61e.msi. Expected product {3C3901C5-3455-3E0A-A214-0B093A5070A6}, found product {8E34682C-8118-31F1-BC4C-98CD9675E1C2}.
    MSI (s) (80:0C) [01:21:16:309]: Skipping validation for patch transform #RTM.1.  Will not apply because previous transform was invalid
    MSI (s) (80:0C) [01:21:16:309]: Looking for patch transform: RTM.2
    1: 2746 2: RTM.1 3: C:\windows\Installer\ef61e.msi 4: {3C3901C5-3455-3E0A-A214-0B093A5070A6} 5: {8E34682C-8118-31F1-BC4C-98CD9675E1C2}
    DEBUG: Error 2746:  Transform RTM.2 invalid for package C:\windows\Installer\ef61e.msi. Expected product {0A0CADCF-78DA-33C4-A350-CD51849B9702}, found product {8E34682C-8118-31F1-BC4C-98CD9675E1C2}.
    MSI (s) (80:0C) [01:21:16:309]: Skipping validation for patch transform #RTM.2.  Will not apply because previous transform was invalid
    MSI (s) (80:0C) [01:21:16:309]: Looking for patch transform: RTM.3
    1: 2746 2: RTM.2 3: C:\windows\Installer\ef61e.msi 4: {0A0CADCF-78DA-33C4-A350-CD51849B9702} 5: {8E34682C-8118-31F1-BC4C-98CD9675E1C2}
    DEBUG: Error 2746:  Transform RTM.3 invalid for package C:\windows\Installer\ef61e.msi. Expected product {F5B09CFD-F0B2-36AF-8DF4-1DF6B63FC7B4}, found product {8E34682C-8118-31F1-BC4C-98CD9675E1C2}.
    MSI (s) (80:0C) [01:21:16:309]: Skipping validation for patch transform #RTM.3.  Will not apply because previous transform was invalid

    For these kind of error message, We are consistently seeing this issue caused by a missing directory, C:\Windows\Microsoft.NET\Framework\URTInstallPath_GAC (or %SystemRoot%\Microsoft.NET\Framework\URTInstallPath_GAC).

    To work around this issue, please try the steps below:

    1. Open an elevated command prompt.
    2. Type: mkdir %SystemRoot%\Microsoft.NET\Framework\URTInstallPath_GAC

    In PowerShell, use $env:SystemRoot instead of %SystemRoot%.

    If the above doesn't work, I would suggest you backuo all your important files on your machine, then do a OS reformat, a clean environment will be more helpful to re-install .NET Framwork and same much troubleshooting time.

    Best Regards,


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.

    Click HERE to participate the survey.

    Wednesday, January 27, 2016 2:45 AM
    Moderator
  • Thank you Lana. I will work with the IT team.
    Thursday, January 28, 2016 2:23 PM
  • Hi Wen Xu-MSFT,

           

    As you have told about the work around as follows:-

    Open an elevated command prompt.
    Type: mkdir %SystemRoot%\Microsoft.NET\Framework\URTInstallPath_GAC


           Can you explain how will it help?

           Is there any Hotfix or KB for this issue??



    • Edited by Ram39 Wednesday, January 3, 2018 11:27 AM
    Wednesday, January 3, 2018 11:25 AM