You may have seen this error when trying to configure and start the Office SharePoint Server search service. The reason is that you probably haven’t prefixed the given account with the domain name. So, enter DOMAIN\Account instead of just Account
So I have started to use Windows Server 2008 as my primary operating system on my laptop. And since I do a lot of development on virtual machines, I wanted to have my Hyper-V VM’s to connect to the internet through my laptop’s wireless connections. It turns out that Hyper-V doesn’t support wireless connections out of the box. Luckily, there is a workaround. I’ve found this blog post from Virtual PC Guy.
I will walk through the steps here.
Start the Hyper-V manager and select you server.
Select Virtual Network Manager from the Actions pane
Select New virtual network, set the type to Internal and click Add.
Give it some meaningful name and click Ok.
Open up the Network and Sharing Center from the Control Panel.
Select the Manage network connections link.
Right click your wireless connection and select properties.
Select the Sharing tab, set the “Allow other network users to connect through this computer’s Internet connection” checkbox and choose the virtual network adapter you created above. (In my case it was named Local Area Connection 3). Click ok.
In the settings for the virtual machine, set the Network Adapter to be your virtual one created above.
That’s it!. Happy networking.
You may have seen this strange error when trying to install your MSI when you have developed a managed custom action DLL in Visual Studio 2005 / 2008?
If you execute the MSI with detailed logging, like this:
MSIEXEC /i "<YOURMSI>.msi" /L*v "InstallLog.txt"
You end up with an error message that is similar to this in the log file:
DEBUG: Error 2769: Custom Action _E3EBB591_EA21_438E_AEB9_4442A5A8C483.install did not close 1 MSIHANDLEs.
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2769. The arguments are: _E3EBB591_EA21_438E_AEB9_4442A5A8C483.install, 1,
Action ended 16:09:12: InstallExecute. Return value 3.
The thing is that you probably have set the Custom Action Data as follows:
The solution to the problem is to add a trailing backslash:
This is actually described in this MSDN article:
So you have come to the conclusion that you will need to debug custom actions in a MSI setup package?. How do you do it? Well, it’s very simple, just add the following line in your custom action code:
And now when you launch the MSI package, it will break and prompt you with the following dialog:
Just select the desired debugging environment and start debugging. It’s as simple as that!