SQL Server Update KB948119 Service Pack 4 fails to install
If like me you're trying to install the SQL Service Pack 4 (KB948119) via Microsoft Update and it fails (without any obvious error) then here's a possible fix. I've found one reason may be if the MSSQL$SBSMONITORING service isn't running - at least this was the case for me when it failed on various Windows Small Business Servers.
Fix:
1) Go to Start - Run - type in Services.msc
2) Look for the MSSQL$SBSMONITORING service
3) If this is stopped or disabled then double click the service name to bring the properties window up
4) Within the properties either start the service or set it's startup type to Automatic and then start the service
5) Retry the Microsoft Update
Clearing Tunnel adapter Local Area Connection from ipconfig
I recently had to work on a machine that listed 100's of Tunnel adapter's in the ipconfig output which prevented getting the IP information I was after. Having hunted around here's how to clear them.
Problem:
Fix:
A few different google searches did come up with multiple answers, however here's the fix that worked for me running Windows Vista SP1. Be aware that messing with Network Connections if you are not familiar with what you are doing can cause serious problems!
1) Go into the Control Panel via Start - Control Panel
2) Go to System (may want to switch to Classic View via the link on the left hand side of the Control Panel to view all the icons)
3) Select Device Manager
4) In Device Manager click the View menu and Tick 'Show Hidden Devices'
5) Expand Network Adapters
6) You should now see a list of adapters starting with isatap, these are the adapters I removed and it then cleared down the Tunnel list in ipconfig.
7) There were also several 6TO4 adapters that I removed to help the clean up. These are related to the Teredo Tunneling and can also be disabled / removed - Full instructions can be found here to do this (but for those wanting the immediate solution run netsh interface teredo set state disabled from a CMD)
File Replication Service error Event ID 13508
Having set up a Server 2003 Domain Controller in a remote site we found the following error whilst trying to replicate between the two locations, Active Directory and DNS seemed to replicate correctly however the Sysvol folder remained empty, the error is below:
Event ID: 13508
Description:
The File Replication Service is having trouble enabling replication from to for
using the DNS name . FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name from this computer.
[2] FRS is not running on .
[3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
Fix:
In our case it was a firewall between the sites blocking the RPC traffic so once this was opened up between the two servers it replicated without any problems. Here's the article we found on Experts Exchange that helped us go through the quick checks:
1) Examine the FRS event ID 13508 to determine the machine that FRS has been unable to communicate with.
2) Determine whether the remote machine is working properly, and verify that FRS is running on it. Type the following command at a command prompt on the computer that logged the FRS event ID 13508 and press ENTER:
ntfrsutl version
If this fails, check network connectivity by using the Ping command to ping the fully qualified domain name (FQDN) of the remote domain controller from the computer that logged the FRS event ID 13508. If this fails, then troubleshoot as a DNS or TCP/IP issue. If it succeeds, confirm that the FRS service is started on the remote domain controller.
3) Determine whether FRS has ever been able to communicate with the remote computer by looking for FRS event ID 13509 in the event log and see if the FRS problem correlates to recent change management to networking, firewalls, DNS configuration, or Active Directory infrastructure.
4) Determine whether anything between the two machines is capable of blocking RPC traffic, such as a firewall or router.
5) Confirm that Active Directory replication is working. For more information about troubleshooting Active Directory replication, see Troubleshooting Active Directory Replication Problems in this guide.
Having gone through several articles we also found alot of users fixed this via a registry tweak. It's a D2 tweak on the 'secondary' server telling it to pull replication from the Primary DC and a D4 registry tweak on the 'primary' server telling it that it holds all of the master records to replicate out.
D2 - Non-Authoritative restore (pull from another DC)
D4 - Authoritative restore
Steps for setting D2/D4 are:
1) Stop File Replication service via Start - Run - type in CMD, click ok. In the Command Prompt window type 'net stop ntfrs' and press enter
2) Use RegEdit to edit "BurFlags" in the key "HKLM\System\CurrentControlSet\Services\Ntfrs\Parameters\Backup/Restore\Process at Startup"
* edit the dword key "BurFlags" in Hex format.
* change from 0 to D2 or D4
3) Start the File Replication service via Start - Run - type in CMD, click ok. In the Command Prompt window type 'net start ntfrs' and press enter
DNS error – Unable to open zone in the Active Directory
Having demoted a Windows 2003 Domain Controller and re-promoting into a different domain DNS began throwing the following error referencing the old domain name, which no longer existed:
Event ID: 4007
Source: DNS
Description: The DNS server was unable to open zone <zone> in the Active Directory from the application directory partition <partition name>. This DNS server is configured to obtain and use information from the directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and reload the zone. The event data is the error code.
Fix:
1) Open Regedit via Start - Run - type Regedit and click ok
2) Browse to HKLM\System\ControlSet\Services\DNS\Zones
(This may have been moved to HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\DNS Server\Zones)
3) Export and then delete the zones that are no longer needed
Checking zone information with ADSIEdit.msc may also be required however removing the above seems to have worked to us. In ADSI check - DC=DomainDNSZones,DC=(yourdomain),DC=local partition
Microsoft Update Error 0×80248007
Having just installed a clean Windows XP Service Pack 3 VMWare image the last thing you expect to see is Windows Update with an error (well being an MS product perhaps that's not entirely true!). Either way here's the quick fix:
Error Code: 0x80248007
Fix:
1) Stop the Automatic Update service,
Go to Start - Run - type in Services.msc and click ok,
Select the Automatic Update service and click the stop button.
2) Rename the SoftwareDistribution folder
Go to C:\Windows and rename the SoftwareDistribution to something suitable (e.g. SoftwareDistribution.old)
3)Start the Automatic Update service,
Go to Start - Run - type in Services.msc and click ok,
Select the Automatic Update service and click the start button.
4) Retry running Windows/Microsoft Update