Skip to Content

Ok, first a few caveats:

  • Windows Server 2012 R2 isn’t quite yet officially supported by SAP at the time of this writing, but it’s coming very soon.  It is currently supported in the First Customer Shipment program, details of which can be found in Note 1955608.
  • In-place upgrades of Windows servers with SAP software installed are supported, but not in all situations, and generally a system copy or migration to new hardware with a fresh install of Windows is recommended instead.  Details about when in-place upgrades are supported can be found in Note 1494740, which is applicable for Windows Server 2012 and higher as well as the versions explicitly mentioned in the Note’s title.

So, with that out of the way, here’s an interesting ‘gotcha’ which you may encounter if you do elect to perform an in-place upgrade with SQL Server installed.

The scenario is upgrading a Windows Server 2008 R2 sp1 system with SQL Server 2012 sp1 to Windows Server 2012 R2.  SQL Server is previously upgraded from 2005, which may or may not be a factor.

After the Windows upgrade is complete, everything works fine, except the SQL Server Configuration Manager tool is missing from the Start menu.  This is definitely a minor annoyance, and it appears to not be an isolated case, as I found external blogs mentioning this issue.  I want to give credit to Marnix Wolf for figuring out what is happening and how to fix it (Thoughts on OpsMgr and System Center 2012: Quick Trick: Where Is SQL Server Configuration Manager After Updating To WS20…).  In a nutshell, the upgrade is unregistering the Configuration Manager MMC snap-in, but the files required to operate the Configuration Manager are still present.


So, how to fix it?


The easy way is to find another SQL Server 2012 system and copy a shortcut from it.  If you install SQL Server 2012 fresh on Windows 2012, you won’t have this problem, so with a little luck you have such a system sitting around.  Open the folder C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft SQL Server 2012\Configuration Tools, and copy the shortcut SQL Server Configuration Manager from that folder to the same folder on your upgraded system, where you’ll notice that it is missing.


Alternatively, you may be able to copy the shortcut from a location on the same server you just upgraded.  By default, the 2012 R2 upgrade creates a copy of the critical folders on your C: drive before starting the upgrade and places them in C:\Windows.old.  So, if you drill into C:\Windows.old\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft SQL Server 2012\Configuration Tools, you should find that same shortcut for SQL Server Configuration Manager there.  Copy it to the same location outside of \Windows.old (i.e., just remove \Windows.old from the file path), and you will be good to go.


That’s it.  Look in your Start menu, and now the Configuration Manager shows up as it should, with the correct icon.  Click it, and the tool starts and operates correctly.


If you don’t have another functioning SQL 2012 system from which to copy the shortcut, then you should be able to make your own shortcut, in this same folder, with the target pointing to C:\Windows\SysWOW64\mmc.exe /32 C:\Windows\SysWOW64\SQLServerManager11.msc.

To report this post you need to login first.

6 Comments

You must be Logged on to comment or reply to a post.

  1. Ari Kanter

    Hi Matt, now that its been some time since you did this, curious about how you feel about your inplace winOS upgrade with SQL 2012.  Am thinking of doing the same thing in my testing env, and wondered if you came across any other issues.

    (0) 
    1. Matt Fraser Post author

      Hi Ari,

      It ended up just fine, and that box is still running today. However, the multi-step upgrade of OS and DBMS was a lot of work, and I suspect it would have been faster to wipe the system and install the OS/DBMS fresh and then install the SAP system via system copy from a backup of the original. That, incidentally, is the Microsoft- and SAP-supported method. My motivation for not doing so was that this would require waiting on other people to do the OS installation, and as they were quite busy I wasn’t inclined to wait, given that it is a sandbox system.

      Regards,

      Matt

      (0) 
    2. Matt Fraser Post author

      By multi-step, I should mention that this started out as a Win2003/SQL2005 box, so it required first upgrading from Win2003 to Win2008 R2, then from SQL2005 to SQL2012, then from Win2008 R2 to Win2012 R2.

      (0) 
  2. Sridhar Nannuru

    Matt

    We are on ERP 6.0 EHP5 Dual start system Support pack 13

    OS: Windows 2003 R2 ( Clustered physical system)

    DB: MSSQL 2008 SP3. ( Clustered physical system)

    we are planning to virtualize our systems and go for Windows 2012 OS and DB

    This can be achieved in 2 ways

    1. Export and Import

    2. Back up restore ( attach detach)

    Export and import method is time consuming but we get the DB compression and we save a lot of storage space.

    I am planning to follow below steps

    1. Back up original system DB ( 2008)

    2. Install Windows 2012 OS

    3. Install MSSQL 2012

    4. Restore the DB to new system (2012)

    5. Run swmp and perform homogenious system copy detach attach method.

    6. Post system copy steps

    After the migration I am planning to use ABAP report MSSCOMPRESS report to compress the DB.

    Am i missing any steps?

    Is this approach supported by SAP

    (0) 
    1. Matt Fraser Post author

      Hi Sridhar,

      At a high level, your plan is exactly what I would recommend for most circumstances, i.e don’t do the in-place upgrade, but instead install the new OS fresh, and then restore your system to it via the homogeneous system copy, and yes, I like the backup/restore (or detach/attach, they achieve the same thing) method. The export/import method is really only needed if you plan to redistribute your database to a different number of disk devices and/or files. If you are keeping your disk/file structure the same, and you are happy with your current distribution of used and free space per file, then there is no benefit, and backup/restore (detach/attach) is superior.

      The approach you have laid out is a supported and recommended approach.

      Regards,

      Matt

      (0) 
  3. Matt Fraser Post author

    I don’t yet have direct personal experience with Always On, so I can’t really speak to your question. You might want to raise that as a question/discussion in the forum in this space.

    (0) 

Leave a Reply