http://www.emailcashpro.com

Server Service - Error 2: The system cannot find the file specified

Had a customer with a brand new Windows 2008 R2 server VM that started representing the error shown below.

Error 2: The system cannot find the file specified


I spent some time trying different authentication methods for the service, and trying to confirm versions of srv.sys, all seemed to be correct and OK with the server, and it was patched and up to date as well.

I stumbled upon this thread talking about solving a similar issue:

User m_a_tt's post is what lead me to resolve this issue. 

I checked the "dependencies" of the service on my server:

Compared to another server with the same patch level:

So I browsed into the registry to get the multi-string data that represents these two dependencies:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanServer


And then added them to my "broken" server's registry.

Rebooted, and all was working again.  After some further digging, I found out that this was indeed manually configured this way by a co-worker who was following instructions from an HP Lefthand SAN installation.  The exact line in their documentation was:

sc lanmanserver depend= MSiSCSI

Future note if you implement storage - this seems to replace existing entries entirely.  The command below would be more appropriate:

sc lanmanserver depend=SamSS/Srv/MSiSCSI

Active Directory: Active Directory Upgrade - High Level Steps

sourcelink

Here are the high level steps which you can use to upgrade the Active Directory.  
AD_Upgrade_WiKi

Steps :





1.  Upgrade the schema using correct version of OS – Adprep







     Reference - http://technet.microsoft.com/en-us/library/dd464018(WS.10).aspx







Note - Windows Server 2008 R2 includes a 32-bit version and a 64-bit version of Adprep.exe. The 64-bit version runs by default. If you want  to run one of the Adprep.exe commands on a 32-bit computer, use the 32-bit version of Adprep.exe. It is called Adprep32.exe. In Windows 2008 R2, it is located in the \Support\Adprep folder.







You can ignore the following message. However, if you are planning to install RODC later, you need perform ADPREP/RODCPREP first. First Windows 2008 DC cannot be a Read Only Domain Controller (RODC). 
ADPREP







2.  Verify the schema version







Note - You can verify the schema version using dsquery * cn=schema,cn=configuration,dc=sivarajan,dc=com -scope base -attr objectVersion command. The following table lists the Active Directory Schema and the corresponding Object Version:







Active Directory Object Version
Windows 2000 13
Windows 2003 30
Windows 2003 R2 31
Windows 2008 44
Windows 2008 R2 47
Windows 8 Beta 52
Windows 2012 56
Windows 2012 R2 69




***ObjectVersion 39 - Please refer http://blogs.technet.com/b/askds/archive/2011/07/15/friday-mail-sack-peevish-nediquette-edition.aspx







3.  Install a new server with correct version of OS and join this server to the existing domain.







4.  Perform DCPRMO on this server and select Additional Domain Controller for an existing Domain option.



     Beginning with Windows Server 2012, you can install AD DS using Windows PowerShell the Install-ADDSDomainController command.







     Reference - http://technet.microsoft.com/en-us/library/cc753720(WS.10).aspx







     Reference PowerShell - http://technet.microsoft.com/en-us/library/hh472162#BKMK_PS







     Note - If you are using Active Directory Integrated (ADI) DNS, it will get replicated as part of the Active Directory replication.  
5.  If you are planning to decommission the old servers, you need transfer FSMO roles, DHCP etc to the new server.







Note - You can identify the FSMO role DC information using Netdom /Query FSMO command.







   Reference FSMO http://support.microsoft.com/kb/324801







   DHCP - http://support.microsoft.com/kb/962355/en-us







6.  You can remove (demote) a domain controller using DCPROMO command and again, since WS2012 also possible with PowerShell.







    Reference - http://technet.microsoft.com/en-us/library/cc740017(WS.10).aspx







    Reference PowerShell - http://technet.microsoft.com/en-us/library/hh472163#BKMK_RemovePS  

Networking Error: IP address already assigned to another adapter (1179)

sourcelink

Details

  • An error message indicates that the IP already exists in the network, but no other virtual machine in the network is sharing the IP.
  • On a Windows virtual machine, you see this error:

    The IP address XXX.XXX.XXX.XXX you have entered for this network adapter is already assigned to another adapter

  • After rebooting the virtual machine, the guest operating system NIC is assigned a private IP address.
  • After a physical to virtual (P2V) conversion of a machine, you cannot assign an IP address to a NIC.
  • After removing and re-adding a virtual NIC, the previous device is no longer visible in Device Manager.
  • The NIC is re-enumerated in the guest operating system.
  • After a P2V conversion, installed devices such as a Universal Serial Bus (USB) device or ghosted device, are not connected to the computer.
  • The Show Hidden Devices option in Device Manager does not display the devices.

    Note: To view the hidden devices, navigate to My Computer > Properties > Hardware > Device Manager > View > Show Hidden Devices.

Solution

Cause

Under certain conditions, you may see this error message from a Windows guest operating system:

The IP address XXX.XXX.XXX.XXX you have entered for this network adapter is already assigned to another adapter Name of adapter. Name of adapter is hidden from the network and Dial-up Connections folder because it is not physically in the computer or is a legacy adapter that is not working. If the same address is assigned to both adapters and they become active, only one of them will use this address. This may result in incorrect system configuration. Do you want to enter a different IP address for this adapter in the list of IP addresses in the advanced dialog box?

In this message, XXX.XXX.XXX.XXX is the IP address you are trying to set and Name of adapter is the name of a network adapter that is present in the registry but hidden in Device Manager.

This error can occur when you change a network connection's TCP/IP configuration from DHCP to a static IP address if:
  • You have upgraded VMware virtual network adapters (for example, when you migrate a virtual machine from an older to a new version of VMware software). This can also include updating the virtual machine hardware version and/or upgrading the version of VMware Tools.
  • You have added and removed network adapters multiple times.
This issue occurs if a network adapter with the same IP address is in the Windows registry but is hidden in the Device Manager (My Computer > Properties > Hardware > Device Manager). This hidden adapter is called a ghosted network adapter.
  • You may see this if you recently performed a P2V and the resulting virtual machine still has the physical NICs and drivers for those NICs present. These ghost NICs have the old IP address and the virtual NIC cannot be assigned the same IP address.
Using the Show hidden devices option in the Device Manager (View > Show hidden devices) does not always show the old virtual NIC (ghosted adapter) to which that IP Address is assigned.

For more information, see the Microsoft Knowledge Base article 269155.

Note: The preceding link was correct as of August 20, 2013. If you find the link is broken, provide feedback and a VMware employee will update the link.

Resolution

To resolve this issue, make the ghosted network adapter visible in the Device Manager and uninstall the ghosted network adapter from the registry:
  1. Click Start > Run.
  2. Type cmd and press Enter.
  3. At the command prompt, run this command:
    Note: In Windows 2008 and Windows 7, open the command prompt using the Run as Administrator option.

    set devmgr_show_nonpresent_devices=1
    Note: If this command does not work (a possibility in Windows Server 2000 and 2003), you may need to add the parameter to Windows and set its value:

    1. Right-click the My Computer desktop icon and choose Properties.
    2. Click the Advanced tab and select Environment Variables.
    3. In the System variables section, click New.
    4. Set the Variable name to devmgr_show_nonpresent_devices and set the Variable value to 1 to enable the parameter.
    5. Click OK to add the variable to Windows.
  4. Start the Device Manager by running this command from the same command prompt:

    start devmgmt.msc
  5. Click View > Show Hidden Devices.
  6. Expand the Network Adapters tree (click the plus sign next to the Network adapters entry).
  7. Right-click the dimmed network adapter, then click Uninstall.
  8. Once all of the grayed out NICs are uninstalled, assign the IP address to the virtual NIC.

    Note: To assign the IP address to the virtual NIC on the command line, run the command:

    netsh interface ip set address "Local Area Connection #" static IP_Address Subnet_Mask Default_Gateway

    For example:

    netsh interface ip set address "Local Area Connection 2" static 192.168.1.101 255.255.255.0 192.168.1.1
  9. Close the Device Manager.

    Note: In some Windows versions, a reboot may be necessary to apply the changes.
For more information, see the Microsoft Knowledge Base article 241257.

Note: The preceding link was correct as of August 20, 2013. If you find the link is broken, provide feedback and a VMware employee will update the link.

Resolve issue using DevCon utility

Alternatively, you can also resolve this issue using the DevCon utility. This is a command-line utility that acts as an alternative to Device Manager. When you use DevCon, you can enable, utility disable, restart, update, remove, and query individual devices or groups of devices.

To resolve the issue using DevCon:
  1. Download the DevCon tool from Microsoft Knowledge Base article 311272.

    Note: The preceding link was correct as of August 20, 2013. If you find the link is broken, provide feedback and a VMware employee will update the link.
  2. Unpack the 32-bit or 64-bit DevCon tool binary to a local folder.
  3. Click Start > Run, type cmd, and press Enter.
  4. Type CD:\path_to_binaries to navigate to where the devcon.exe file is located.
  5. Use this syntax to find installed network adapters:

    devcon findall *net*
    or

    devcon listclass net
    Note: In the output of the previous commands, there is a line for the ghosted network adapter that is similar to PCI\.
  6. Run this command to remove the adapter:

    devcon remove @device\name

    For example:

    devcon remove "@PCI\VEN_14E4&DEV_1600&SUBSYS_01C21028&REV_02\4&378EDFA4&0&00E2"

    Note: IDs that include an ampersand character (&) must be enclosed in quotation marks as seen in the example.
  7. Reboot the system and you no longer see the ghost network adapters.
Note: If you did not get the Device Instance ID or the OCI name from devcon, search for the adapter name in the registry using Find by clicking Start > Run and typing regedit. Then copy the Device Instance ID for the appropriate adapter. When you locate the device, use the command from Step 6.

For related information, see: