I was not able to run the Configure E-mail and Internet Connection Wizard, it always failed at "Firewall Configuration".

I looked into the log file which is stored in C:\Program Files\Microsoft Windows Small Business Server\Support\icwlog.txt to see what the error was.

I was not able to run the Configure E-mail and Internet Connection Wizard, it always failed at "Firewall Configuration".

I looked into the log file which is stored in C:\Program Files\Microsoft Windows Small Business Server\Support\icwlog.txt to see what the error was.

03/08/2010 9:45 AM

C:\Program Files\Microsoft Windows Small Business Server\Networking\ICW\wizemail.dll, version 5.2.2893.0

calling CEmailCommit::ValidatePropertyBag ().

calling pdispPPPBag->QueryInterface (IPropertyPagePropertyBag, 0x6e50c).

Call to pdispPPPBag->QueryInterface () returned ok.

calling ReadInt4 (0x1884668, DB5E5E45-3598-4F1D-8FF7-0ED35B9EB6A4).

Call to ReadInt4 () returned ok.

The out param of ReadInt4() is -1.

calling CValidatePropertyUtil.ValidatePropertyInteger ().

Call to CValidatePropertyUtil.ValidatePropertyInteger () returned ok.

Call to CEMailCommit::ValidatePropertyBag () returned ok.

calling CNetCommit::Commit (25708136).

calling CNetCommit::ValidatePropertyBag ().

Call to Querying for the property bag () returned ok.

Property bag is not dirty, skipping validation

calling CNetCommit::Common ().

Call to Configuring the time service () returned ok.

Call to Notifying RWW for ISA () returned ok.

Call to CNetCommit::Common () returned ok.

Call to CNetCommit::Commit () returned ok.

calling CRFireCommit::CommitEx (0x1884668).

calling CRFireCommit::ValidatePropertyBag (0x1884668).

Call to This is a Router Single Nic configuration only Web Publishing will be configured, Basic Firewall will not be configured. () returned ok.

Call to Reading web publishing selection () returned ok.

Call to Reading OWA publishing selection () returned ok.

Call to Reading RUP publishing selection () returned ok.

Call to Reading Monitoring publishing selection () returned ok.

Call to Reading OMA publishing selection () returned ok.

Call to Reading RPC publishing selection () returned ok.

Call to Reading Companyweb publishing selection () returned ok.

Call to Reading ROOT publishing selection () returned ok.

Web publishing selections:

OWA publishing: 1

RUP publishing: 1

Monitoring publishing: 0

OMA publishing: 1

RPC publishing: 1

Companyweb publishing: 0

ROOT publishing: 0

Call to CRFireCommit::ValidatePropertyBag () returned ok.

Call to GetPrivateNICGuid () returned ok.

Call to GetIPAddress for private nic () returned ok.

Call to GetSubnetMask for private nic () returned ok.

RUP is published

Call to Fixing the inheritance for root dir () returned ok.

Call to Unpublishing the default web site () returned ok.

Call to Fixing the inheritance for companyweb dir () returned ok.

Call to Unpublishing companyweb () returned ok.

Call to Publishing /Exchange () returned ok.

Call to Publishing /ExchWeb () returned ok.

Call to Publishing /Public () returned ok.

Call to Publishing /ExAdmin () returned ok.

Call to Publishing RUP () returned ok.

Call to Publishing client help for RUP () returned ok.

Call to Publishing OMA () returned ok.

Call to Publishing ActiveSync () returned ok.

Call to Publishing RPC () returned ok.

Call to Configuring RPC over HTTP () returned ok.

Call to Notify RUP for OWA () returned ok.

Call to Notify RUP for Monitoring () returned ok.

Call to Notify RUP for RPC () returned ok.

Call to Notify RUP for Companyweb () returned ok.

Call to Restricting exhchangeoma to local server only () returned ok.

Call to Restricting ConnectComputer to local network only () returned ok.

Call to GetInternetServerName () returned ok.

Call to GetNetbiosDomainName () returned ok.

Call to NotifyProvisioning () returned ok.

Call to Limiting number of connections () returned ok.

Call to Sending RUP intro mail () returned ok.

Call to Saving web publishing selection () returned ok.

calling Set Web Publishing Rules (0x0).

Call to GetPrivateNICGuid () returned ok.

Error 0x80041002 returned from call to WMIGetIPAddress().

Error 0x80041002 returned from call to CRFireCommit::Commit().

calling GetBOConnector ().

Call to GetBOConnector () returned ok.

calling spADs->PutEx (ADS_PROPERTY_CLEAR, msExchSmtpOutboundSecurityPassword).

Call to spADs->PutEx () returned ok.

calling spADs->SetInfo ().

Call to spADs->SetInfo () returned ok.

Near the bottom you can see the error message: Error 0x80041002 returned from call to WMIGetIPAddress().

I was also getting the following error recorded in the application log:

Event Type:  Error
Event Source:    MSExchangeSA
Event Category:   Monitoring
Event ID:   9097
Description:The MAD Monitoring thread was unable to connect to WMI, error '0x8004100e'. 

For more information, click http://www.microsoft.com/contentredirect.asp.

The solution is below:

Step 1: Please take the steps according to the article below:

Error "0x8004100e" and event ID 9097 occur when you run the System Attendant

Note: The Exwmi.mof file is located in the following folder of SBS 2003 CD 3: CD_drive_letter:\Exchsrvr65\Setup\I386\Exchange

Step 2: The problem occurs when wbem repository might be corrupted

1. Stop and disable the Windows Management Instrumentation service.

a) Click Start, Run, type "services.msc" and press Enter.
b) Right click the "Windows Management Instrumentation" service and click Properties.
c) On the General tab, set "Startup type" to "Disable" and click OK.
d) Right click the "Windows Management Instrumentation" service and click Stop.

2. Delete all the files in the %windir%\system32\wbem\Repository directory.

3. Start the Windows Management Instrumentation service.
a) Click Start, Run, type "services.msc" and press Enter.
b) Right click the "Windows Management Instrumentation" service and click Properties.
c) On the General tab, set "Startup type" to "Automatic" and click OK.
d) Right click the "Windows Management Instrumentation" service and click Start.

This blog post is from mickyj.com (but I couldn't figure out how to link to it!):

Can not reinstall SharePoint.
Ok, My clients SharePoint is dead. I have the database files but the SharePoint as I know it is dead. Under Add/Remove in Control panel I tried to run "Windows Small Business Server Setup" and run maintenance and reinstall or install the Intranet component. It fails. There are many other steps to take. I tried to used the maintenance wizard to install, it failed, I went back in, it said it was installed, so I uninstalled again and then reinstalled, it failed. I tried everything I could think of. I spent 6 hours trying to get SharePoint back onto the system.

I tried Microsoft KB 829114 "How to remove and how to install the Windows Small Business Server 2003 SharePoint Services 2.0 companyweb Web site"
(This involves stopping the services, deleting the SharePoint website and application pools in IIS, editing the registry removing MSDE instance of companyweb and removing the MSDE data). This also failed.

I threw caution to the wind and downloaded the Windows SharePoint Services 2 SP2 from the web. The version for Windows 2003 server (Non SBS). I installed it flawlessly. I then uninstalled it, again it went perfect. I then run the wizard for maintenance in Add/Remove "Windows Small Business Server Setup" and the Intranet installed first time. It shows you how valuable a gut feel can be sometimes.

Why did I have to reinstall Sharepoint ?
I removed the MSDE instance for Companyweb in Add/Remove in preparation to move the databases to SQL 2005 Workgroup edition. Due to other issues, we could not continue with the SQL 2005 install so we ended up with no Companyweb. We could not install SQL 2005 in a way that we needed for the upgrade as the workstation components (Management studio) etc would not install. The repair suggested is to run a "change" on the existing SQL 2005 instance in Add/Remove in control panel and restrospectively install the tools. This did not work for us in this situation. I have seen this previously. Backup Exec 12d includes SQL 2005 Express. It does not include the tools. If this is installed before you try andinstall SQL 2005 Workgroup, there seems to be no way to install the missing tools. I have tried uninstalling Backup Exec and SQL 2005, and then reinstalling but I can't seem to get the tools to install.

From Microsoft "You may be unable to install the Client Components when you update the SQL Server Desktop Engine instance to SQL Server 2005. This behavior may occur if this is not the first instance of SQL Server 2005 that is installed on the server and if you did not install the Client Components together with the first SQL Server 2005 instance. If this is the case, SQL Server Setup displays a message that states that the Client Components have already been installed."

In my case the error was sompthing like .. a newer version of the tools has previously been installed, please exit the installation and from the comand line perform an upgrade ..... Nothing I read on the internet seemed to work.

Take a look at this link

It then dawned on me. The SQL 2005 interface and Management tool runs across the network. I had the software installed on a secondary PC. I could use that one to manage and make the changes to this database as SQL 2005 had installed on this server, Just minus the tools. It worked like a dream.

SharePoint recovery ?
how can you recover SharePoint ?
You can do it from the flat files, if you have them (The Ldf and MDF files). You can do it from a stsadm backup or from your backup tool if it supports a SQL Agent. All are valid recovery methods.

If all you want is the document libraries, you could also mount the companyweb under "My Network places" as a Network place (http://companyweb) and simply copy the data out.
It might be helpful to backup C:\inetpub\companyweb (If you have modified it) and have an IIS metadatabase backup handy.

You can recover to the same server and same AD or a new server with the same server name. You do this using different methods. Look at this article for help.

I had the situation where I needed to do a recovery from the Ldf and MDF files into a fresj MSDE instance. I reinstalled the Intranet onto the same server and AD. I stopped the services, replaced the Ldf and MDF files with the backup and restarted the databases. I then was told (in Internet Explorer) it was a foreign database "The Web site that is referenced here is not in the configuration database". Here is how I fixed it.
Start the companyweb Web site
(Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager. In IIS Manager, expand server_name (local computer), and then expand Web Sites.Under Web Sites, right-click companyweb, and then click Start.

Now remove Windows SharePoint Services 2.0 from thr CompanyWeb intranet site.
(Click Start, point to Administrative Tools, and then click SharePoint Central Administration (http://localhost:8081). Under Virtual Server Configuration, click Configure virtual server settings. On the Virtual Server List page, click the virtual server that you want to configure. In this example, click the companyweb virtual server. Under Virtual Server Management on the Virtual Server Settings page, click Remove Windows SharePoint Services from Virtual Server. On the Remove Windows SharePoint Services from Virtual Server page, click Remove without deleting content databases.Click OK. You will receive the following error message.
"The virtual server that is referenced here is not in the configuration database "

Extend the CompanyWeb intranet site by using Windows SharePoint Services 2.0.
(Click Start, point to Administrative Tools, and then click SharePoint Central Administration (http://localhost:8081). On the Central Administration page under Virtual Server Configuration, click Extend or upgrade virtual server.On the Virtual Server List page, click the name of the virtual server to extend. In this case, click companyweb. On the Extend Virtual Server page under Provisioning Options, select Extend and map to another virtual server. Under Server Mapping, click companyweb.Under Application Pool, click Use an existing application pool, and then click DefaultAppPool (NT AUTHORITY\NETWORK SERVICE). Click OK.)

For further information look here

Web Part Error: This page has encountered a critical error
After restoring my site I had this error. You can also get it after installing .Net Framework 2.0. You may have to change the .Net Framework back to 1.1.4322 on the site or virtual directories. Please do as following:

1. Open the IIS management snap-in.
2. Go to the properties of companyweb.
3. Go to the ASP.NET tab.
4. On the ASP.NET version select the drop-down and change from the 2.0.50727 to 1.1.4322.
5. Apply and close out the properties.
6. Browse companyweb.


Run Company Web on ASP.Net 2
If you want to run companyweb on ASP.NET 2.0.50727 you will need to upgrade run the following SharePoint command:

stsadm.exe -o upgrade -forceupgrade -url http://companyweb

SBS server 2003 WSS2- Everyone can edit my Company web ?
I have a client whose companyweb seems to ignore the permisisons supplied. Anyone can edit the companyweb, move webparts around and delete items. Even those whom have no account linked to the MSDE instance and do not appear in the users list. It has a strange "log in" button floating where the "Modify Shared Page" should be on the right hand side. It turns out that the reason is someone has played in the AD. The "SBS SP Admins" group is set and used by Sharepoint to allow people to edit and play with Sharepoint. It is in the Active Directory and in this case, someone added "Domain Users" to the Membership. Removing the "Domain Users" fixed the problem.

My Sharepoint has all my data in it, it is my life....
... Then you should consider an additional backup for it. Use the commandline in a batch file
"C:\Program files\Common files\Microsoft shared\Web server extensions\60\Bin\STSADM.EXE" -o backup -url http://Companyweb -filename C:\Backup\companyweb -overwrite

Today I installed SP2 for WSUS on my SBS 2008 server. In the SBS Console under "Network Essentials Summary" the Updates section reported: The software update configuration has been modified and no longer meets the recommended configuration

To fix this run through the following procedure:

1. Start
2. MMC
3. File
4. Add/Remove Snap-in
5. Update Services
6. Add
7. OK
8. Expand Update Services
9. Expand 'SERVER'
10. Options
11. WSUS Server Configuration Wizard
12. Next, Next, Next
13. Start Connecting
14. Next
15. Next (only English selected here)
16. Select All Products
17. Verify selection of Critical Updates, Definition Updates, Security Updates, Service Packs, Update Rollups (all others are unselected)
18. Next, Next, Next, Next, Finish
19. Close MMC
20. Open Windows SBS Console and Updates work once again (no error)

Updates through Windows Update do not write to user-specific registry keys, so it shouldn't be necessary to install them while the system is in install mode.

That said, it doesn't hurt to do so.

Whatever you do, do *not* configure the server for automatic windows updates!

I did a P2V (Physical to Virtual) migration of an SBS 2003 server. It was running on physical hardware but now it is running in Hyper-V. I removed the device drivers for things that were no longer connected to the SBS; this is standard practice in P2V migrations.

I started getting error 7000 logged in the event viewer, complaining that the Parallel port driver service failed to start.

Event Type:    Error
Event Source:    Service Control Manager
Event Category:    None
Event ID:    7000
Description:
The Parallel port driver service failed to start due to the following error: 
The service cannot be started, either because it is disabled or because it
has no enabled devices associated with it. 

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

How to fix it

The parallel port has already been removed from the device manager, and there are no related services that I can see.The only fix is to open up Registry Editor (regedit) and change the start value from 3 to 4, as shown below:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Parport]
"Start"=dword:00000004

As always, be careful in the registry!

Suppose you wanted to insert Google Ads half way through your article in Joomla. There is no pre-existing module position for that, so you'll have to make one.

In the Module Manager, there is a drop-down called "Position". Click inside the drop-down and you can type your own position name. I called mine "ad".

Now in your Joomla article you can put the following:

For much more information: http://www.yireo.com/tutorials/joomla/joomla-administration/343-load-a-module-within-your-joomla-articles

Source: http://www.busyboo.com/2008/10/26/joomla-jce-styles-dropdown/

Create a new CSS file and place it in your template CSS folder. Call it editor_content.css, for example. In the Administrator section of your site, go to Components > JCE Administration > JCE Configuration. Change the ‘Template CSS Classes’ value to ‘No’ and below it enter editor_content.css and that’s it. no / or template/ or any other full path.

Now, keep in mind that every css class you added to editor_content.css must also be in your template_css.css for it to show in the frontend of your site (hp template and inner template, if you’ve got one).

Now, here is the buggy part; don’t ask me why – just try this:

1. You have to have a title or some text in your content item before testing the Styles box.
2. Clicking the down-arrow for the Styles drop-down doesn’t seem to work on XP/FF, XP/IE7, and Ubuntu/FF; you have to first click the actual drop-down box first. Clicking right on the word “Styles” will work, and then the down-arrow works subsequently {…Cheers, linux4me}
3. Oh, and another thing… always do Refresh and/or clear your browser’s cache to see results.

What happens when you run out of licenses in SBS 2003?

First, you'll get a warning in the event logs that you are nearing the limit, followed by a warning that you have reached the limit.

Event Type:      Warning
Event Source:    LicenseService
Event Category:  None
Event ID:        221
Description:
License usage for product Windows Server is nearing the maximum number 
of per server licenses purchased. Consult Licensing from the 
Administrative Tools folder for more information.

Event Type:      Warning
Event Source:    LicenseService
Event Category:  None
Event ID:        222
Description: License usage for product Windows Server is at the maximum number
of  per server licenses purchased. New license requests may not be granted.
Consult Licensing from the Administrative Tools folder for more  information

After that you'll get an error that you have reached the limit. I believe there may be a grace period of a few weeks in this condition, but that will only help you if someone is actually monitoring the event logs.

Event Type:      Error
Event Source:    LicenseService
Event Category:  None
Event ID:        201
Description:
No license was available for user DOMAIN\USER using product FilePrint .  
Use Licensing from the Administrative Tools folder to ensure that you 
have sufficient licenses.

What to do?

The obvious answer is to make sure you have enough licenses. If you have run out, you'll need to buy more.

Remember that SBS licenses are NOT concurrent. You must have a CAL (Client Access License) for each user listed in the Server Management console. More info: http://www.microsoft.com/WindowsServer2003/sbs/evaluation/faq/licensing.mspx

How to I check?

Open up the Server Management console. In the menu at the left, go to Licensing. There you will see "Installed licenses" and "Maximum usage".

What can I do right now?

This may creep up on you, and you have bought CALs but they will be delivered tomorrow. If the boss is breathing down your neck because he is being denied access to the server, there is a temporary workaround. Reboot the server or restart the SBS License Logging service. Be warned that another user may be kicked out when you reset the server, and I believe it will be on a first-come first-serve basis.