Archive for the 'Windows Server 2003' Category

Windows cannot access the specified device

This is an old problem, but I still see it from time to time.  You are trying to run and executable that you downloaded, and you are on a Windows 2003 system.  You double click and get:

image

 

As you can see here, I am simply trying to install the windirstat utility to figure out what is taking up all the disk space.  If you have drive space issues, and we seem to always have drive space issues, this is a great utility.

The problem is this:

image

Notice the Security section at the bottom.  if you click on Unblock, then it looks like this:

image

Apply the change and the security section at the bottom goes away, and you can then run the program.

SCVMM and P2V Adventures

Where I work, we have been using Microsoft Virtualization since Virtual Server was in Beta.  Of course, we don’t necessarily use all of the functions and features of all the software we have, but one feature that I have used a good bit is the “Convert physical server” action in System Center Virtual Machine Manager.  Until recently, I have used this with great success.  We run IBM xSeries servers and I have converted something like 50 of them to virtual machines running on Hyper-V over the past several years. 

In late 2007, we bought our first IBM Blade Center (which I am very happy with) and with that move we also decided to do “boot from SAN” for all of our blades.  Just seemed to make sense that we wouldn’t put moving parts in a device that was designed to run so well without moving parts. 

At the time, we were implementing a new ERP system and several “hanger on” type applications, and Hyper-V (virtualization in general) wasn’t something that was supported by a lot of the software we were deploying.  So we have a lot of powerful blade servers, running a lot of low use applications.  I have managed to eradicate several of those wasteful installations, but there are a set that I am only now getting buy-in to virtualize. 

And today’s adventure begins with a Windows Server 2003 SP2 machine installed Boot from SAN on an IBM HS21-XM Blade server.

First attempt:

1.  Convert physical server

2.  Virtual machine name

3.  Scan System

image

Looks good..

4. Conversion options

image

we can try the defaults..

5.  Specify the processor and memory… 

6.  Select the host, path, network, start options, etc..

7.  The job starts, the machine gets copied over, and …

That try resulted in a blue screen loop.. 

image

Ok… time to try the Offline conversion:

1. Proceed as above but select the Offline conversion option at step 4.

2.  hmm..  conversion warnings… must correct to proceed..

Warning (13246)
No compatible drivers were identified for the device: Broadcom BCM5708S NetXtreme II GigE (NDIS VBD Client). The offline physical-to-virtual conversion requires a driver for this device.

Device Type: network adapter
Device Description: Broadcom BCM5708S NetXtreme II GigE (NDIS VBD Client)
Device Manufacturer: Broadcom Corporation
Hardware IDs (listed in order of preference):
B06BDRV\L2ND&PCI_16AC14E4&SUBSYS_03271014&REV_12

Compatible IDs (listed in order of preference):
B06BDRV\L2ND&PCI_16AC14E4&SUBSYS_03271014
B06BDRV\L2ND&PCI_16AC14E4
B06BDRV\L2ND

Recommended Action
Create a new folder under C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\Driver Import on the Virtual Machine Manager server and then copy the necessary 32-bit Windows Vista driver package files for this device to the new folder. The driver package files include the driver (.sys) and installation (.inf and .cat) files. Check the device manufacturer’s website for the necessary drivers.

We don’t really need to do that right…

Had some trouble with that part…  finally figured out that the drivers that need to be placed in that folder are the “RIS” drivers. 

Try number 3 (or 30, I lost count)…

1. Proceed as try number 2, ignore warning because we did put the driver in there, and

Blue screen loop…

Hmm… maybe this is just not meant to be.  Did some more searching and found this article:

http://blogs.msdn.com/b/robertvi/archive/2009/10/07/after-installing-hyper-v-integration-services-on-the-next-reboot-the-vm-displays-bsod-0x0000007b.aspx 

Basically, there are some people seeing the exact same blue screen that I was seeing, except this was after the install of updated integration components.  But I wasn’t installing integration components yet… or was I?

image

Ok so maybe it was getting that far and just “blowing up” after the install of the components.  Good thing about this being a P2V, I can go back to the source machine pretty easy and check the registry:

image

Looks like we may have an answer here.  Change the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Wdf01000\Group entry to be WdfLoadGroup instead of base. 

It is my guess, that this would have worked even with the online conversion option.

An online pack already exists…

Situation:  I have a 32bit file server running Windows Server 2003.  I have a new 2008 R2 (x64) file server running on Hyper-V.  Did I mention that the R2 server is on Clustered hosts?

This is all simple.  Just drop the LUNs from the file server, give them to the cluster and assign them as pass through disk to the guest OS.  Simple…

Except, I kept getting the following errors when I try to do the import:

An online pack already exists.

The operation failed, because an online pack object already exists.

The provider encountered an error while merging two packs.

I mean really…  what does all that mean.  I couldn’t find anything pertinent in my searches, I tried working in Diskpart, and got some of the same errors.

After lots of searches, I couldn’t find anything to help.  So I opened a ticket with Microsoft.  I got a very helpful person who told me that it basically sounds like a driver issue, but he couldn’t say for certain.  He couldn’t find much on it either.

So on a whim, I moved my test LUN from my production file server to another 2003 server.  That worked just fine, so I then moved it from there to the 2008 R2 machine that I had been working with.  That worked just fine.  Weird…

So I checked the driver for the production file server:

clip_image002

and compared that to the other 2003 server:

clip_image002[4]

As you can tell, the culprit seems to be an outdated driver on the current file server.  Seems I don’t keep things as up to date as I should.

P2V fails at Copy Hard Disk

I have been trying to get a P2V of a production system to use in our DR plan.  I have limited opportunity to do this, because I am not allowed to impact performance during production hours for this system, and the definition of production hours is fairly broad.  I have been trying for a couple of months to get this figured out.

We have our regularly scheduled maintenance once a month on the third Thursday of the month.  This is pretty awesome in that we are at liberty (most months) to take everything down from 6PM until 6AM.  I look at it as giving the company an evening off. 🙂

So, that being tonight, I had it in my mind that I was going to beat the OAS boxes.  (Oracle Application Servers, part of our new JD Edwards ERP system.)  They are an interesting setup, because they are using Apache, which as great as it may be, isn’t something I have much experience with.  They have a loopback adapter for use with the load balancing setup that they are in.  The load balancing is performed using our Cisco switches, which as great as they are, I don’t know very much about.  All in all, they are pretty complicated to troubleshoot in this case, because there are so many pieces that I am not completely familiar with. 

Such is life…

Anyway,  after a lot of hunting and a lot of posting in forums, I found an event that actually led to a solution. I probably should have found this before, and maybe I did, but didn’t pay enough attention… 

This is the exact symptoms that I had, and the errors in the event log were there, but the machine that I am trying to convert is a Windows 2003 Server, not Windows XP:

The P2V process fails at 40% when you try to run the P2V process by using Microsoft System Center Virtual Machine Manager 2008 on a source computer that is running Windows XP

You use Microsoft System Center Virtual Machine Manager 2008 to run the Physical-to-Virtual (P2V) process on a source computer that is running Windows XP. However, the process fails at 40% complete, and the following error is logged in the event log on the computer that has System Center Virtual Machine Manager (SCVMM) 2008 installed:

Type:		Warning
Date:		<Date>
Time:		<Time>
Event:		1706
Source:		Virtual Machine Manager
Category:	None
Computer:	<Computer Name>
Event Msg:	Job 7bfcd14a-884e-4a71-9984-3274622adeb7 (Physical-to-virtual conversion) failed to complete. 7bfcd14a-884e-4a71-9984-3274622adeb7 Physical-to-virtual conversion TaskFailed    

Additionally, you will find the following error logged in the event log on the source computer:

Type:		Error
Date:		<Date>
Time:		<Time>
Event:		15005
Source:		HTTP
Category:	None
Computer:	<Computer Name>
Event Msg:	Unable to bind to the underlying transport for 0.0.0.0:443. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.
Data:
 00 00 04 00 02 00 52 00 00 00 00 00 9D 3A 00 C0		 . . . . . . R . . . . . . . . À
 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00		 . . . . . . . . . . . . . . . .
 00 00 00 00 00 00 00 00 43 00 00 C0				 . . . . . . . . C . . À

The P2V process fails at 40% when you try to run the P2V process by using Microsoft System Center Virtual Machine Manager 2008 on a source computer that is running Windows XP

Insufficient system resources exist to complete the requested service

We recently implemented a new optical storage system using a software package that runs on Windows.  The particular machine that is used to host this application gradually had problems accessing the optical storage (which is essentially a NAS device) and would frequently pop the title message: Insufficient system resources exist to complete the required service. 

I thought this was a bit odd, considering the machine has 16GB of RAM, Dual Quad Core processors, and at fairly large amount of storage.  We kept thinking that there must be a driver issue, or some issue with the software, or even an issue with the optical storage.

I have no way to prove it, because I couldn’t ever tell for sure exactly how the system go to the point of not being functional, but the last thing I tried APPEARS to have worked…

I took out the /3GB switch in the boot.ini. 

That was 3 days ago and the system hasn’t had the issue since, even though it had gotten to the point where it was happening several times a day.  The thing that tipped me toward this as a possible solution was the fact that everything I read said that this was likely caused by a memory leak, but we didn’t seem to have memory issues (at least when we could get into task manager there didn’t seem to be much activity) and when I came across this post…  I took a chance and it seems to have fixed the problem for now.

Error 360: The operation failed due to a virtual disk service error

I use DPM to backup a few servers, in a pilot group, and I was trying to add one to a protection group.  I kept getting this error every time I tried to modify the protection group to add another server:

Modify protection group: *Protection Group Name* failed:
Error 360: The operation failed due to a virtual disk service error
Error details: Unknown error (0x80042420)
Recommended action: Retry the operation.

I couldn’t figure out the problem until I saw a post on this that mentioned there could be a problem using RDP.  Then I remembered that I can never do disk configuration unless I use a console session.  In order to configure disks it seems you have to be in “Session 0”.  If you have to do this remotely, using “mstsc /console” for XP or 2003, or “mstsc /admin” for Vista will put you in “Session 0” just as if you were sitting at the console.

The Framework.log file grows larger…

If you are trying to free up space on your system drive you may run across a very large  log file in the system32\wbem\logs folder:

SYMPTOMS

When you use Windows Management Instrumentation (WMI) and you configure it to log all events on your Microsoft Windows Server 2003-based computer or Microsoft Windows XP-based computer for quick analysis and troubleshooting of problems, the file size of both the Framework.log and the Framework.lo_ files may be greater than what you configured for them.

The Framework.log file grows larger than 64 KB when you use WMI on a Windows Server 2003 or Windows XP computer

Windows Failed to install the update with error 0x80070643

I am responsible for keeping a number of machines (around 900 or so) up to date with all the latest Windows Updates.  Recently I noticed that a number (around 15 or so that I am sure of) weren’t installing particular updates.  I have seen this in the past, but the particular updates that wouldn’t apply weren’t of real concern to me, so I didn’t really investigate.  The latest updates were of concern though so I started looking into it.  Here are the errors that I am getting:


Description:
Installation Failure: Windows failed to install the following update with error 0x80070643: Visual Studio 2005 Service Pack 1.

Description:
The installation of C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ZNWF10\VS80sp1-KB926601-X86-ENU.msp is not permitted due to an error in software restriction policy processing. The object cannot be trusted.

As you can see, this particular update is for Visual Studio Service Pack 1.  After a little digging, I found this:

http://support.installshield.com/kb/view.asp?articleid=Q111207

It basically says that there is a problem with the way the local security policy is configured.  When I looked, it appeared that the local security Software Restrictions Policy wasn’t configured.  I “added” a policy and put the dot in the “All users except local administrators”.  After that the install ran fine.

Windows Server Virtualization Calculator

 I came across Ben Armstrong’s Blog today while doing a little searching.  He has some good stuff about Microsoft Virtual Server on there and one of the things he posted on has to do with a calculator to figure out how to configure your Virtual environment.  It doesn’t take much to figure out that Data Center Edition may actually be worth paying for when you use multi-core processors and pack a lot of VMs on one host.

Windows Server Virtualization Calculator

I do not know how I missed this one, but this is a very cool tool.  The Windows Server Virtualization Calculator allows you to specify how many virtual machines you will be running, on a given set of hardware, and it will show you all of your licensing options for buying Windows Server.  This way you can quickly determine what the best option is for your environment.

Virtual PC Guy’s WebLog : Windows Server Virtualization Calculator

The start up screen is all black and you can’t see what you are typing into the logon box

I have had a few machines that occasionally have strange color combinations and you can’t see the logon box to view what you are typing.  I finally put the right words in the search to come up with the answer: 

SYMPTOMS

After you press CTRL+ALT+DELETE to log on to a Microsoft Windows Server 2003-based computer, the logon screen turns black. Although you cannot see what you are typing, you can successfully log on to the Windows Server 2003-based computer. Then, after you successfully log on, the screen becomes visible.
Note This symptom may occur on both the terminal server sessions and the local console. Additionally, this symptom occurs even if you start the computer in Safe mode.

The logon screen turns black after you press CTRL+ALT+DELETE to log on to a Microsoft Windows Server 2003-based computer