Networknet.nl Blog
Stay Connected
Posts tagged fix
SMS 2003: Error 25100
Mar 16th
I am still managing a SMS 2003 environment and last week we encountered following message on one of the SMS 2003 clients. The message appeared in Application Eventviewer and SMS client did not report back to our SMS Primary site:
Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 10005
Date: 3/10/2009
Time: 12:17:06 PM
User: NETWORKNET\Ivan
Computer: IVAN-VM01
Description:
Product: SMS Advanced Client — Error 25100. Setup was unable to create the WMI namespace CCM
The error code is 80041002
To fix the problem see my cmd script below which was used by the local IT contact:
@echo off
REM Ivan Versluis
REM Date: 2009/03/11
REM Description: FIX WMI Database for SMS Client
c:
cd %windir%\system32\wbem\
mofcomp cimwin32.mof
mofcomp cimwin32.mfl
net stop winmgmt
rmdir /s /q repository
rmdir /s /q Logs
mkdir Logs
net start winmgmt
rundll32 wbemupgd, UpgradeRepository
rundll32 wbemupgd, CheckWMISetup
rundll32 wbemupgd, RepairWMISetup
pause
WordPress: intranet and firewall
Mar 11th
I am huge fan of WordPress blogging platform. Recently I introduced the tool in a enterprise environment.
WordPress is running behind a restricted network and has no connection to the Internet. While installing and finalizing the virtual machine which is used to host WordPress I encountered one problem with it. WordPress was slow!
I download latest version of WordPress 2.7 and installed it on a Ubuntu JeOS 8.04 virtual machine appliance. The initial configuration went fine; but after I opened the admin area and the blog site it took ages before the pages were returned. WordPress was so slow within this Intranet environment that every action more than 30 seconds took.
Due to the fact virtual machine was sitting in a firewalled intranet environment the system could not connect to services sitting on the internet.
See my worklog how I got WordPress working and pages are loaded in less than a second:
- Goto ../wordpress/wp-includes and open http.php
- Search for “ function request( $url, $args = array() ) {“
- Add “return;” behind global. E..g “ return;global $wp_version;”
Well now I disabled all interactions to the Internet, but I don’t need them in this enviroment. For more information goto here.
Remove Active Directory without replication
Apr 27th
Couple minutes ago I initiated the remove of Active Directory and forced the demotion of a virtual machine domain controller. The domain controller exceed the 60day not being able to replicate and I was not able to get the replication working. It took me more than 90 minutes to troubleshoot and fix the problem. Since Windows 2003 there is option in the dcpromo tool to force the Active Directory removal.
1. By default, Windows Server 2003 domain controllers support forced demotion. Click Start, click Run, and then type the following command: dcpromo /forceremoval2. Click OK. 3. At the Welcome to the Active Directory Installation Wizard page, click Next. 4. At the Force the Removal of Active Directory page, click Next. 5. In Administrator Password, type the password and confirmed password that you want to assign to the Administrator account of the local SAM database, and then click Next. 6. In Summary, click Next. 7. Perform a metadata cleanup for the demoted domain controller on a surviving domain controller in the forest.
Reboot the server and cleanup the metadata with ntdsutil. I hate to use workaround like this, but there is not quick and dirty fix for me now. I am planning and testing to upgrade my Exchange 2007 server to SP1, but because the replication to the second dc did not take place for more than 60days the replication stopped.
One of the Errors on my primary domain controller. Demote didn’t work with force removal and option 3 also did not fix the problem when using the registry fix.
Event Type: Error
Event Source: NTDS Replication
Event Category: Replication
Event ID: 2042
Date: 4/27/2008
Time: 5:18:39 PM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: NET-DC-01
Description:
It has been too long since this machine last replicated with the named source machine. The time between replications with this source has exceeded the tombstone lifetime. Replication has been stopped with this source.
The reason that replication is not allowed to continue is that the two machine’s views of deleted objects may now be different. The source machine may still have copies of objects that have been deleted (and garbage collected) on this machine. If they were allowed to replicate, the source machine might return objects which have already been deleted.
Time of last successful replication:
2008-01-26 20:26:04
Invocation ID of source:
01dcf6c8-f6b8-01dc-0100-000000000000
Name of source:
e02a9b21-b7e0-4be6-9cc9-971b00325f65._msdcs.Networknet.nl
Tombstone lifetime (days):
60
The replication operation has failed.
User Action:
Determine which of the two machines was disconnected from the forest and is now out of date. You have three options:
1. Demote or reinstall the machine(s) that were disconnected.
2. Use the “repadmin /removelingeringobjects” tool to remove inconsistent deleted objects and then resume replication.
3. Resume replication. Inconsistent deleted objects may be introduced. You can continue replication by using the following registry key. Once the systems replicate once, it is recommended that you remove the key to reinstate the protection.
Registry Key:
HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Allow Replication With Divergent and Corrupt PartnerFor more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
For more information check the knowledge base article.
WordPress version 2.5 upgrade
Mar 31st
Two hours ago I upgraded Networknet.nl with WordPress version 2.5 and immediately after the php binaries and database were upgraded I hit my first problem. Within my Widgets Design Sidebar I have the Pages widget which shows all pages on the right side of my blog starting with “About me”.. VMware. For some topics I created pages instead of WordPress posts and linked those pages to a parent page; these two pages were excluded from “Pages Widget”. After the upgrade my pages widget become really huge showing 30+ pages. I did a search on WordPress support site and someone else already reported this problem; no response yet except me on this post.
I didn’t want to downgrade my new WordPress version and therefore I used this method to query the parent pages and exclude them manually without doing the PHP code research how to exclude them.
- Open phpmyadmin
- Select your wordpress database
- Open wp_posts and click SQL
- Paste this sql query
<p>SELECT id<br>FROM 'wp_posts'<br>WHERE 'post_type' = 'page'<br>AND 'post_parent' NOT LIKE '0' </p>
- Click GO button and click Export; I export to CSV to excel and copied all cells into Notepad.
- Paste these pages into the exclude for your pages widget.
Dirty solution but I solved my problem in less than 5 minutes for now…
