SBS An error occurred while configuring a component error message when you run the Configure E-mail and Internet Connection Wizard in Windows Small Business Server 2003 fixed by enabling WMI Server
Thursday, May 1, 2008, 12:55 PM
I thought this one might be helpful to others. I got this error: "An error occurred while configuring a component", running the Configure E-mail and Internet Connection Wizard on an SBS box for a client. Doing some googling, I came to MS KB ID #875421, which was actually for a different problem. But it did reference \Program Files\Microsoft Windows Small Business Server\Support\Icwlog.txt
There I found the following two lines:
Error 0x80070422 returned from call to WMIGetIPAddress().
Error 0x80070422 returned from call to CRFireCommit::Commit().
And obviously the first one points to a problem obtaining the local IP address via WMI. So I looked at the services and sure enough WMI Service was stopped & disabled. I think this was done either by myself or an employee in the past when troubleshooting some lock-ups. In any case, WMI Service is usually a good thing to have running (and by default it is always running). So I set the startup type back to automatic, started it up, reran the SBS CEACIC wizard, and ta-da!
Problem fixed.
[ add comment ] | permalink |
( 2.9 / 879 )Saturday, March 22, 2008, 08:18 PM
This post is long overdue. Within a month of the previous post, I did fix the problem. I finally ended up being able to fix it, by first downloading from Microsoft the SUS 1.x installer, reinstalling it right on top of itself, and then the uninstall in add/remove programs finally worked. At that point I was able to upgrade the WSUS 2.0 install to 3.0.
I don't know why I didn't try this earlier. I thought I did, but it didn't work. Maybe so, but I am not positive. In any case, it has been working well running WSUS 3.0 now for months.
No thanks to Microsoft for making one of my original posts in their WSUS discussion group disappear. I honestly think that they removed it because they couldn't figure out an answer to it, and I was the only one person out of thousands of users who was having the problem. I've seen this once before too. What gives? I was able to pull my original post up in the Google Groups cache of that Microsoft newsgroup. But in searching the actual microsoft group, it was nowhere to be found. This is the second time that I have seen such behavior. And the other time it was not with one of my own posts, but instead with a MS Office problem that several other people were reporting, in which they were kind of criticizing Microsoft, and for which Microsoft hadn't been able to provide a solution.
I really hope that the disappearance of these threads was just a coincidence, but so far, it doesn't seem that way. In any case, it's pretty sad...
[ 1 comment ] ( 37 views ) | permalink |
( 3 / 695 )Thursday, September 13, 2007, 03:56 PM
I receive the following errors upon trying to uninstall SUS 1.0 (remember this machine currently also has WSUS 2.0 installed, although I don't know whether this makes any difference).
First Error:
============
There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personell or package vendor.
Second Error:
=============
Fatal error during installation
*Then the installer quits
In the application log we find the following errors, which all occur within a few seconds of eachother:
First Error: Event ID 1004 Source MsiInstaller
============
Detection of product '{AFF0D9D3-6F0D-437E-9327-98108B4A8644}', feature 'WU', component '{D31B2119-C240-4F8B-B13C-20EF38B2E070}' failed. The resource 'D:\SUS\wusync\WUSyncSvc.exe' does not exist.
Second Error: Event ID 1001 Source MsiInstaller
=============
Detection of product '{AFF0D9D3-6F0D-437E-9327-98108B4A8644}', feature 'WU' failed during request for component '{D31B2119-C240-4F8B-B13C-20EF38B2E070}'
Third Error: Event ID 1004 Source MsiInstaller
============
Detection of product '{AFF0D9D3-6F0D-437E-9327-98108B4A8644}', feature 'WU', component '{D31B2119-C240-4F8B-B13C-20EF38B2E070}' failed. The resource 'D:\SUS\wusync\WUSyncSvc.exe' does not exist.
Fourth Error: Event ID 1001 Source MsiInstaller
=============
Detection of product '{AFF0D9D3-6F0D-437E-9327-98108B4A8644}', feature 'WU' failed during request for component '{D31B2119-C240-4F8B-B13C-20EF38B2E070}'
Fifth Error: Event ID 1004 Source MsiInstaller
============
Detection of product '{AFF0D9D3-6F0D-437E-9327-98108B4A8644}', feature 'WU', component '{D31B2119-C240-4F8B-B13C-20EF38B2E070}' failed. The resource 'D:\SUS\wusync\WUSyncSvc.exe' does not exist.
Sixth Error: Event ID 1001 Source MsiInstaller
============
Detection of product '{AFF0D9D3-6F0D-437E-9327-98108B4A8644}', feature 'WU' failed during request for component '{D31B2119-C240-4F8B-B13C-20EF38B2E070}'
Seventh Error: Event ID 1004 Source MsiInstaller
==============
Detection of product '{AFF0D9D3-6F0D-437E-9327-98108B4A8644}', feature 'WU', component '{D31B2119-C240-4F8B-B13C-20EF38B2E070}' failed. The resource 'D:\SUS\wusync\WUSyncSvc.exe' does not exist.
Eighth Error: Event ID 1001 Source MsiInstaller
=============
Detection of product '{AFF0D9D3-6F0D-437E-9327-98108B4A8644}', feature 'WU' failed during request for component '{D31B2119-C240-4F8B-B13C-20EF38B2E070}'
Nineth Error: Event ID 11721 Source MsiInstaller
=============
Product: Microsoft Software Update Services -- Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor. Action: WUSyncRemove, location: D:\SUS\wusync\WUSyncSvc.exe, command: /unregserver
Tenth Error: Event ID 11725 Source MsiInstaller
=============
Product: Microsoft Software Update Services -- Removal failed.
[ add comment ] | permalink |
( 3 / 715 )Wednesday, April 25, 2007, 09:18 PM
Well, after the 3.2 update, just about all of our problems were fixed. We applied it within the first week of April. But I think it may have introduced a new issue. We have a Windows Small Business Server 2003 Std R2 server that we use for VPN connections. It is a virtual machine on our XenExpress server. Ever since the update, we can no longer connect to other VMs on our XenExpress server over the VPN. We can connect to other systems in the office over the VPN, but not any other VMs on the XenExpress server. The VMs can communicate with eachother fine via IP. It just seems to be the VPN connections that are unable to communicate with the XenExpress VMs. I have looked at the firewalls and I don't think it is a firewall issue.
Again, it seems that it was clearly introduced at the time that we upgraded from 3.1 to 3.2.
We are VERY pleased with the XenExpress server overall, but this little issue would increase our productivity, and allow us to NOT move backward from the solutions and technology we've been using. XenSource is of course a big leap forward in other ways. Did I mention that we like it?? :-)
[ 1 comment ] ( 16 views ) | permalink |
( 3.3 / 12 )Monday, March 26, 2007, 05:28 PM
We are really enjoying using XenExpress on our new Dell PowerEdge 1950 Quad-core Xeon. It's extremely fast now with 4 virtual servers running on our Xen server. I am ready to plop down the $700.00 to purchase the XenEnterprise version, which will allow us to have unlimited VMs, but before I do, I need answeres to few problems we've experienced.
1.) Xen Virtual Machine crash - We have 2 linux VMs running Debian Sarge, and 2 Windows VMs, one running Windows Small Business Server 2003 Premium R2, and the other running Server 2003 R2. I use a Mac, and so I connect to the Server 2003 R2 VM via RDP to do a lot of Windows work. One of the things that I do there is administer the Xen server. We have the Xen Administration program loaded onto that VM. It generally works fine administering the VMs that way. However, about an hour ago I was logged onto our Server 2003 R2 machine and running the Xen Administration program, when suddenly my RDP session stopped working. I reconnected about a minute later, only to find that the VM had rebooted. Just a moment later, a colleauge mentioned that the other Windows VM had just restarted unexpectedly. Upon logging back into both, we were prompted with Microsoft's window which asks why the computer was unexpectedly shut down. I then logged into the linux VMs, and ran the uptime command to find that one reported being up for over 4 days, and the other over 5 days. So only the Windows servers were rebooted. I SSH'd into the Xen Server & checked out the /var/log/messages & /var/log/xen/xend.log log files, as well as others that I thought may give helpful information. Those two were the only ones that really seemed to tell much about the unexpected Xen problem. I have a pretty good hunch as to what caused the problem with the server I was using (Server 2003 Standard R2), but I have no idea why it took the 2nd Windows server down with it. (By the way, the VMs are running fine now).
Here's exactly what I was doing at the time of the VM crashes:
I was connected to the Windows Server 2003 Standard R2 via RDP on the console connection. And I think the console fact is the important one here. The reason being is because the last thing I did before the servers crashed was open the Xen Administration program, select the Server 2003 Std R2 VM from the list in the upper-pane, then click on the "Graphical Console" tab down below. I am thinking that because I was remotely connected to the server's graphical console via RDP, the Xen Administration program didn't like the idea of me viewing the graphical console from it, from within the graphical console. I've had similar issues w/ VNC connecting to the local host, only to get an endless loop of embedded screens. Hmmm. This is absolutely the only reason why I can imagine that this happened.
So, perhaps for now, a lesson learned is to be more careful with that. But perhaps in the meantime, XenSource can implement an if-then statement in their software to check before hand as to whether allowing their software to do something (try to do, anyway) is going to cause problems.
I think the big problem here however, is that my 2nd Windows VM was taken down with the other. I think this is totally unacceptable. Just a passing detail that may help in solving this problem is that one or two other times, I have had problems connecting to the Xen server from the Xen Administration program, so I SSH'd into the Xen server & restarted the XenAgentD process (service xenagentd restart), only to find that it also killed & restarted my Windows VMs unexpectedly, while leaving the linux VMs unscathed.
As previously stated, I am ready to pay the $700.00 for XenEnterprise, but not until I get a good answer to what caused this, and get a permanent fix.
As far as I am concerned, I am very excited about Xen. I love to see Open Source software actually make some money and develop into a strong competing business to proprietary software companies. That is why I chose Xen over VMWare for virualization.
I don't think that most people using Xen have problems like this. The very fact that Xen is marketed & often reviewed as a strong competitor to VMWare all the more confirms to me that this is probably not a common problem. Also, the founder of XenSource (Ian Pratt), stated in July 2006 that there were very few outstanding bugs in Xen at that time (this was in a PDF titled "The Xen Roadmap"). And I'm thinking that coming from this guy being a very experienced professional programmer, this probably refers to issues that are so small that I probably wouldn't even notice them (although I may be overzealous here).
Also, HP and I think IBM are strongly backing Xen, and sell servers preloaded with it. HP has published whitepapers in conjunction with XenSource stating how great Xen is and posting benchmarks running on their systems. I really don't think they would do this, if my problems were commonly experienced.
So what I'm trying to say is that I don't think that Xen is a buggy solution that shouldn't be used on production servers. We've actually been very, very impressed with it overall. But there is obviously something wrong here, and I need to be reassured that we're making the right decision by virtualizing with Xen, before I commit to invest in it. And once that we really are convinced that it is the right way to go, we will continue to invest in it, and work to steer our clients the same way. Once that we commit ourselves, then we want them to be successful, and so will gladly pay them in doing our part to help them have the financial resources needed to continue to improve & be successful.
As for now, I am posting this with a request for help. I have placed the relevant portions of the log files here: http://www.kgotsi.com/static.php?page=s ... s-20070326
Please provide assistance, and also contact someone in the Xen sales division and let them know that you are sending them another buyer, whose problems you just fixed.
Thanks a lot!
--
Doug Mortensen
Network Consultant
Impala Networks Inc.
doug----at----impalanetworks----dot----com
CCNA, MCP, A+, Linux+, MS Small Business Specialist
[ add comment ] | permalink |
( 2.8 / 69 )Back Next
