Archive for June, 2010

Network virtually disappeared.

June 16, 2010

Ok sorry for the pun,

But seriously I booted up an VHD into a new hyper V machine and despite my best efforts, nothing, no connectivity … nada.

Now I’ll admit this is not my primary area of expertise, but I do try to at least understand the basics … so I investigated.

Checking out the virtual network device I was informed that the VMBus Network Adapter had failed to start

“This device cannot start (Code 10)”

Turns out that all I had to do was connect to the VM from the host select Actions -> Insert Integration Service Setup Disc (Ctrl + I) and voila fixed (after a quick restart).

It’s the simple things in life that are often the best, if I’d bothered to read the error messages from the Hyper-V role manager all of this would have been made clear to me a lot sooner <sigh>

This is still a glitch in 2010 … C’MON !

June 15, 2010


I encountered this bug in 2007, and it’s happening again in sp2010, you really would have thought this would be low hanging fruit.

Ok so maybe I was a little over the top in the subject line of this post … but REALLY !! (there I go again).

Basically when your go to provision search it fails with the error

The call to SPSearchServiceInstance.Provision (server ‘APP1’) failed. Setting back to previous status ‘Disabled’. System.Runtime.InteropServices.COMException (0x8007052E): Logon failure: unknown user name or bad password.

The fix is to supply the SearchService\ContentAccess user details with domain names in the “format DOMAIN\username, not just username” (copied verbatim from the linked article, but I know sometimes people don’t like to click through the links.

To get a little philosophical, I guess this might demonstrate the wide chasm that sometimes exists between business users expectatons of how easy/fast a tech fix should be
and the poor little programmers view.

To state it clear

  1. I found the problem
  2. followed the diagnostic trail to the ULS logs
  3. copied the error msg into Google
  4. followed that to the linked blog
  5. followed the advice
  6. had a moment of recognition as I realized I’d encountered the same problem in 2007 installations.
  7. had the mild euphoria of watching my problem fade away

I didn’t do anything particularly clever that would actually result in me understanding this problem any better.

Another way too look at the same situation would be to use the rationale, if something this obvious has been left unresolved in two releases the must be some serious complication that forces it to be there. That serious complication is probably worth knowing about as it is likely to be impacting other parts of the system/systems development as well.

Anywayz, it’s working now which makes me happy, but I don’t really know why it was broken in the first place which makes me … vaguely disquieted.