none
System Center Service Manager SP1 Update Rollup 2 error RRS feed

  • Question

  • Hi

    We are trying to update Service Manager 2012 sp1 and when running SCSM2012_CU_KB2802159_AMD64_7.5.2905.125.exe it will quickly give us an error that it has stopped working with the error details below.

    Any ideas?  It is doing this all all of our service manager instances.

    Description:
      Stopped working

    Problem signature:
      Problem Event Name:    CLR20r3
      Problem Signature 01:    scsm2012_amd64_patchwizard.exe
      Problem Signature 02:    7.5.2905.125
      Problem Signature 03:    5150c405
      Problem Signature 04:    mscorlib
      Problem Signature 05:    2.0.0.0
      Problem Signature 06:    503ef855
      Problem Signature 07:    34a5
      Problem Signature 08:    1c5
      Problem Signature 09:    System.IO.IOException
      OS Version:    6.1.7601.2.1.0.272.7
      Locale ID:    1033

    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

    If the online privacy statement is not available, please read our privacy statement offline:
      C:\Windows\system32\en-US\erofflps.txt

    Friday, April 19, 2013 8:52 PM

Answers

  • Try to clear your Temp (don't forget to clear high privileged temp too, Temp\2 or something like that) folder and re-login then.

    SCSMSolutions
    email: freemanru (at) gmail (dot) com

    Monday, April 22, 2013 11:20 AM
    Moderator
  • I had the same issue on Windows Server 2008 R2 SP1 after a clean SCSM 2012 SP1 installation.

    Applying the following updates helped:

    Security   Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server   2008 R2 for x64-based Systems (KB2832414)

    Security   Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server   2008 R2 SP1 for x64-based Systems (KB2736422)

    Security   Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server   2008 R2 SP1 for x64-based Systems (KB2756921)

    Security   Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server   2008 R2 SP1 for x64-based Systems (KB2840631)

    Update for   Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 SP1   for x64-based Systems (KB2836942)

    Update for   Windows Server 2008 R2 x64 Edition (KB2834140)

    Friday, October 18, 2013 8:56 AM
  • Stefan,

    This turned out to be our problem as well.  Folks, be sure you have all your updates from Microsoft.  We use SCCM for Windows updates, but only Critical, Important and Security updates, so KB2836942 and KB2834140 were not installed.  I got us up-to-date on patches and the Service Manager patch wizard finally finished without error.

    Thanks,
    TsunamiSteve

    Thursday, November 7, 2013 2:48 AM

All replies

  • Hi,

    I also had problems with this update. It seems you have a different error, but you can still take a look at the folowing post: http://www.bctechnet.com/service-manager-2012-sp1-cu2-install-error/. It may give you some idea.

    Regards

    Monday, April 22, 2013 8:14 AM
  • Try to clear your Temp (don't forget to clear high privileged temp too, Temp\2 or something like that) folder and re-login then.

    SCSMSolutions
    email: freemanru (at) gmail (dot) com

    Monday, April 22, 2013 11:20 AM
    Moderator
  • Try to clear your Temp (don't forget to clear high privileged temp too, Temp\2 or something like that) folder and re-login then.

    SCSMSolutions
    email: freemanru (at) gmail (dot) com

    Hi Anton,

    Thanks,  that seemed to do the trick. 

    LL


    Monday, April 22, 2013 4:18 PM
  • I believe that there is an undocumented hotfix requirement for this CU.  After applying EVERY AVAILABLE update to every server, I was able to then install in this order:

    1. SQL Server hosting CMBD and DW

    2. DWMS

    3. MS

    4. SSP

    5. Clients

    Of course, it could just be that every server has to be rebooted two or three times before installing this CU.  :)


    • Edited by UKCats Thursday, April 25, 2013 8:20 PM
    • Proposed as answer by UKCats Tuesday, May 28, 2013 7:14 PM
    Thursday, April 25, 2013 5:14 PM
  • I had the same issue on Windows Server 2008 R2 SP1 after a clean SCSM 2012 SP1 installation.

    Applying the following updates helped:

    Security   Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server   2008 R2 for x64-based Systems (KB2832414)

    Security   Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server   2008 R2 SP1 for x64-based Systems (KB2736422)

    Security   Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server   2008 R2 SP1 for x64-based Systems (KB2756921)

    Security   Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server   2008 R2 SP1 for x64-based Systems (KB2840631)

    Update for   Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 SP1   for x64-based Systems (KB2836942)

    Update for   Windows Server 2008 R2 x64 Edition (KB2834140)

    Friday, October 18, 2013 8:56 AM
  • Stefan,

    This turned out to be our problem as well.  Folks, be sure you have all your updates from Microsoft.  We use SCCM for Windows updates, but only Critical, Important and Security updates, so KB2836942 and KB2834140 were not installed.  I got us up-to-date on patches and the Service Manager patch wizard finally finished without error.

    Thanks,
    TsunamiSteve

    Thursday, November 7, 2013 2:48 AM
  • Hi. As an update to this problem, i dit have the same issue but on a server 2012 system. 

    The updates listet in this post, is all for windows 7 or server 2008 an cannot be apply to server 2012. 
    Running windows update and installing all updates and clearing the temp folder did not resolve the issue.

    My fix was removing .net3.5 reboot and reinstall .net 3.5.

    after that install did run perfect

      

    Saturday, July 19, 2014 2:24 PM
  • is it possible you're running into this IO Exception? there is a known issue with some of the service manager patchers that causes this. The executable is simply a wrapper for the MSP, which can be safely applied directly to all systems.
    • Proposed as answer by Thomas Bianco Friday, November 21, 2014 6:39 PM
    Monday, July 21, 2014 1:59 PM
  • We are having the same issue.  Cant apply  KB2836942  it says its not applicable to my system (2008 R2 SP1). KB2834140  is installed.  We cannot move forward with our deployment until this is updated.  Really wish they would roll requirements into these packages because this is rediculous


    Warm Fuzzies!

    Wednesday, November 19, 2014 6:19 PM
  • Try to uninstall .net 3.5 and then reinstall it. 

    That solved the problem for me 

    Friday, November 21, 2014 6:47 PM
  • Try to clear your Temp (don't forget to clear high privileged temp too, Temp\2 or something like that) folder and re-login then.

    SCSMSolutions
    email: freemanru (at) gmail (dot) com

    I usually have to do this, especially when rebuilding the data warehouse.  Usually needs a reboot after too, don't forget!
    Tuesday, January 31, 2017 3:57 PM
  • is it possible you're running into this IO Exception? there is a known issue with some of the service manager patchers that causes this. The executable is simply a wrapper for the MSP, which can be safely applied directly to all systems.

    There is also a reference to this same fix here, I usually have to do some session bouncing until it forgets but this seems to happen because the EULA (QFEList.xml) is still being referenced by the installer and you have to force the handle closed in the middle of the install.  Yet another unsupported fix that fixes the problem :)
    • Proposed as answer by Jason Decou Tuesday, January 31, 2017 4:41 PM
    Tuesday, January 31, 2017 4:41 PM