TechOnTip Weblog

Run book for Technocrats

Archive for April, 2012

How to retrieve MS CRM 4.0 Serial Key??

Posted by Brajesh Panda on April 11, 2012

How to retrieve MS CRM 4.0 Serial Key??????

Execute “SELECT LicenseKey FROM ConfigSettings” SQL Query against your MSCRM_Configs database!!

Posted in Microsoft CRM | 2 Comments »

RDP failed after Windows 2008 R2 SP1 and OS Hotfix Installation

Posted by Brajesh Panda on April 10, 2012

Recently I have upgraded one of our servers with Windows 2008 R2 SP1 & other patches. And observed I can’t connect to this server using RDP. As it is a Hyper-v virtual machine, logged in to the server using hyper-v console & found RDP service is failing in this virtual machine.

Googled & found it is related to KB2667402. I have other servers with this hotfix & they are working fine. In that discussion thread I read somebody saying if you install this patch before SP1 it is causing this issue! I am not sure!!

Posted in WindowsServer | 5 Comments »

P2V Migration Gotcha 3: Unable to create a VSS snapshot of the source volumes. Error code 2147754776 (0x80042318)

Posted by Brajesh Panda on April 9, 2012

  • I was running P2V conversion of a Citrix server & below error came up;

    “Failed: Unable to create a VSS snapshot of the source volumes. Error code 2147754776 (0x80042318)”

  • Afterwards I have come across this issue multiple times & almost every time it resulted due to corrupted vss registry keys.

  • Logon to the source server and check vss providers & writers
    • Vssadmin list providers
    • It should show you out put like below

  • Vssadmin list providers
  • It should show you out put like below screenshot

  • If you are not getting about output, you have to delete the registry key & restart respective services; it will rebuilt the VSS configuration.
    • Click Start, click Run, type Regedit, and then click OK.
      • Locate and then click the following registry subkey:
      • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions
      • On the Edit menu, click Delete, and then click Yes to confirm that you want to delete the subkey.
      • Exit Registry Editor.
      • Click Start, click Run, type services.msc, and then click OK.
    • Right-click the following services one at a time. For each service, click Restart:
      • COM+ Event System
      • COM+ System Application
      • Microsoft Software Shadow Copy Provider
      • Volume Shadow Copy

Here is a MS article how to fix it.

Posted in ServerVirtualisation | 7 Comments »

P2V Migration Gotcha 2: Event ID 6013 OLEDB Error, SQL Server doesn’t exist or access denied

Posted by Brajesh Panda on April 9, 2012

  • VMWare Converter uses Microsoft Software Shadow Copy Provider services to take VSS base snapshot of the source machine & transport the same to vSphere environment.
  • As you may know VSS comes with different application related VSS writers (like Exchange, SQL etc), if any of the VSS writer didn’t did their job properly converter will not able to do it’s conversion job.
  • Migration may not reported as failed in the converter console but it will be in hung state at “Creating a snapshot for source system” for quite some hours before you kill it with frustation.
  • In this case verify Application event log for any kind of VSS errors. Before you re-run the converter tool again make sure this VSS error is fixed.


  • Mostly you can disable the problamatic application & run the converter tool again. Here is a screenshot of SQL (MSDE) VSS error.
  • In this case I disabled MSDE service to make the converter run & after conversion we restarted the MSDE service again.

Posted in ServerVirtualisation | Leave a Comment »

P2V Migration Gotcha 1: x00007B Blue Screen Error while migrating Windows 2003 x64bit Server

Posted by Brajesh Panda on April 9, 2012

Lately I was migrating some Windows 2003 x64bit servers to virtual machines using vmware converter. After multiple attempts realised converter is failing at a certain stage; not completing the task. Even if we start the converted virtual machine, it shows blue screen error with x00007B error. This error refers to disk driver issues. Here are my findings about this issue!

  • Mostly all Windows 2003 x64bit servers do not come with LSI logic SCSI drivers in their driver folder. So if you migrate a Win2003x64 server, your migration may fail at VM reconfiguration phase of migration. And if you start the same VM, it will end up with x00007B Blue Screen of Death error!
  • Here are 3 possible reason for this kind of failure (mostly the 1st one)
    • Missing driver file
    • Missing registry keys for these drivers/devices (Registry Entry)
    • Missing start up services entry to load the driver & registy at the boot. (Registry Entry)
  • Missing Driver File
    • Copy symmpi.sys file to C:\Windows\system32\drivers folder of x64bit server.

       

  1. Missing registry keys for these drivers/devices (Registry Entry)

To edit/change registry keys you have to connect system drive VMDK to another live x64bit server & mount the registry hive to perform necessary action.

  • Shutdown broken VM & take copy backup of system drive (C Drive)
  • Connect the system drive to another x64bit working VM & make sure it is detected with a drive letter
  • In the work VM, Open registry, Click on HKLM, Select File & Load Hive, browse to the above drive letter\Windows\system32\Config, Double Click Syste, it will ask you a name, type BrokenSystem
  • Now you can browse HKLM hive of broken system
  • Expand BrokenSystem -> ControlSet001 -> Control -> CriticalDeviceDatatabase
  • Look for a key called pci#ven_1000&dev_0030,
  • If you have a key called pci#ven_1000&dev_0030, Select the same;
  • There should be two strings in pci#ven_1000&dev_0030
  • ClassGUID which has a value of {4D36E97B-E325-11CE-BFC1-08002BE10318}
  • Service which has a value of symmpi
  • If these two strings are either not present in pci#ven_1000&dev_0030 or contain different information, change them.
  • If you do not have a key called pci#ven_1000&dev_0030
  • RIGHT-CLICK on the LEFT PANE and click new -> key
  • key name is pci#ven_1000&dev_0030
  • RIGHT-CLICK in the RIGHT PANE and click new -> string value the name of this value is ClassGUID the value is {4D36E97B-E325-11CE-BFC1-08002BE10318}
  • RIGHT-CLICK in the RIGHT-PANE and click new -> string value the name of this value is Service the value is symmpi

     

  1. Configure “Missing start up services entry to load the driver & registy at the boot” following below process
    1. Shutdown broken VM & take copy backup of system drive (C Drive)
    2. Connect the system drive to another x64bit working VM & make sure it is detected with a drive letter
    3. In the work VM, Open registry, Click on HKLM, Select File & Load Hive, browse to the above drive letter\Windows\system32\Config, Double Click Syste, it will ask you a name, type BrokenSystem
    4. Now you can browse HKLM hive of broken system
    5. Expand BorkenSystem -> ControlSet001 -> Services; if you have a service called symmpi left-click on it Or if you do not have a service called symmpi RIGHT-CLICK on the LEFT-PANE and click new -> key
      1. Key name is symmpi
      2. f the symmpi key is setup properly you should have 7 keys in the right pane.
      3. (Default) (value not set) STRING
      4. ErrorControl (DECIMAL) 1 DWORD
      5. Group SCSI miniport STRING
      6. ImagePath system32\DRIVERS\symmpi.sys STRING
      7. Start 0 (DECIMAL) DWORD
      8. Tag 33 (DECIMAL) DWORD
      9. Type 1 (DECIMAL) DWORD
      10. If you have all of the keys in the right pane, most likely you will notice that the ImagePath key is missing and Start is set to 4 instead of 0.
      11. RIGHT-CLICK on the RIGHT PANE and select new -> String Value name = ImagePath value = system32\DRIVERS\symmpi.sys
      12. Double-Click on Start in the RIGHT-PANE, make sure DECIMAL is selected and change it to 0 if it is not 0 already.
      13. if you do not have all of the keys listed above create them using the method listed below.
      14. RIGHT-CLICK on the RIGHT PANE and select new -> type is either String Value or DWORD (see table above for types, names a values)
      15. Note: when entering DWORD values it helps to ensure that you have DECMIAL selected.

         

Make sure after you have added, adjusted or just verified the configuration of the symmpi service configuration take back the registry hive until you reach to SYSTEM2 and then unload it.

Posted in ServerVirtualisation | 9 Comments »

“Memory Demand” is not showing up any value in Windows 2008 R2 SP1 Hyper-v instance

Posted by Brajesh Panda on April 9, 2012

I was consolidating our RnD virtual machines to a new Windows 2008 R2 SP1 Hyper-v server. After I imported all virtual machines, configured dynamic memory minimum & maximum range for all of them! Then installed new integration pack in them because I imported those VMs from other 2008 & R2 hyper-v servers. Thought they will start using dynamic memory.

Later couple of days I got a complaint from one of my colleague his VM is pretty slow. Saw two VMs are not showing memory demand values. As these are Windows 2008 R2 Virtual machines, I was not thinking these machines don’t have SP1 installed in them. I was only concentrating on integration pack. Then I referred to my old dynamic memory notes & realized SP1 need to be installed on them. Seems like as these are test virtual machines my colleague forget to install SP1 and I overlooked them.

Silly…

Posted in MsHyper-V | Leave a Comment »

VHD compact error: This request operation could not be completed due to file system limitation

Posted by Brajesh Panda on April 6, 2012

I was trying to compact my dynamically expanding VHD file of a hyper-v virtual machine. Here the error what I got;

“The system failed to compact <MyDrive>.VHD. Error code: The requested operation could not be completed due to a file system limitation.”

Event viewer error looks like below

The system failed to compact ‘S:\Virtual Machines\<server_name>\Virtual Hard Disks\VHD_C.vhd’. Error Code: 2424869

So this means we have some volume shadow copies for the drive inside the operating system. We have to remove them.

# Vssadmin list shadows

# vssadmin delete shadows /all

Well I don’t have that backup software anymore. In windows 2008 R2 there is a inbuilt command to delete shadows forcefully i.e. Diskshadow.exe.

Now I am able to compress my vhd from 130GB to 50GB. WOOOT!!

Posted in MsHyper-V | 1 Comment »

Upgrade Windows 2008 R2 Standard to Enterprise/DataCenter without Media

Posted by Brajesh Panda on April 5, 2012

Using Windows Edition-Servicing Command-Line Options We can upgrade Windows 2008 R2 Standard to Enterprise or higher (Lower to Higer) edition of the operating system without using Operating System Media.

Upgrade Scenario;

Windows Server 2008 R2 Standard -> Windows Server 2008 R2 Enterprise -> Windows Server 2008 R2 Datacenter

Windows Server 2008 R2 Standard Server Core -> Windows Server 2008 R2 Enterprise Server Core -> Windows Server 2008 R2 Datacenter Server Core

Windows Server 2008 R2 Foundation -> Windows Server 2008 R2 Standard

To determine the installed edition, run:

DISM /online /Get-CurrentEdition

To check the possible target editions, run:

DISM /online /Get-TargetEditions

To Start upgrade;

DISM /online /Set-Edition:<edition ID> /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

Where XXXXX-XXXXX-XXXXX-XXXXX-XXXXX is the product key. If your environment use KMS server. You have to use KMS keys. You can find KMS keys from here;

Here is the screenshot for my lab server; upgrading to enterprise edition;

Posted in Windows 2012 | 1 Comment »

 
%d bloggers like this: