Saturday, November 3, 2012

Kerberos event ID 4 - KRB_AP_ERR_MODIFIED

A SBS 2008 server has been throwing this message recently, caused by one of the workstations on the network. This error was accompanied by numerous instances of DCOM event ID 10009 caused by the same PC.

After reviewing several articles on this, we realized this PC was removed and rejoined to the SBS domain on a previous occasion. When the machine was rejoined to the domain, it received a different IP address from the DHCP server on the SBS box.

All workstations are assigned a DNS "A" record when they are initially joined to the SBS domain. When a workstation is removed, the "A" record remains on the DNS server. After rejoining the workstation, a new IP address was assigned which did not match the existing "A" record.

Once we updated the DNS record on the server to reflect the new IP address assignment, both errors stopped.

Saturday, October 27, 2012

Windows 7 restore error 0x80070057

We had problems attempting to restore a machine using the Windows 7 Recovery Environment. Instead of using a DVD, we booted the PC using a USB flash drive. We also had a USB hard drive attached as it contained the Windows Backup image

After selecting the appropriate system image from the USB hard drive and starting the restore, the Recovery Environment displayed the following message:

Error: The parameter is incorrect
Code: 0x80070057

After some investigation, we found this post at Microsoft's site describing the solution. In short, the recovery disk must be removed before you select the recovery image. Once we did that, the image restored without incident.

Saturday, October 13, 2012

"Open with" context menu missing

A change to one of our client's machines caused the "Open with" context menu to disappear. This menu appears when you right click on a document or other data file that's not an executable or shortcut. After checking with Microsoft, we found the solution from MS MVP Daniel Martin:

1. Click Start, All Programs, Accesories, Notepad.

2. Copy and paste this text:

Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\*\shellex\ContextMenuHandlers\Open With]

3. Click File, Save As, name the file "OpenWith.reg" (WITH THE QUOTATION MARKS) and click OK.

4. Now double-click OpenWith.reg, click Continue, Yes, OK, and see if the problem is solved.

This registry addition resolved the issue perfectly. Thanks!

Saturday, August 25, 2012

WIndows Update cannot currently check for updates

This week, we could not run Windows Update on a server due to the following error:

“Windows Update cannot currently check for updates, because the service is not running. You may need to restart your computer.”

When we checked the Windows Update service, we found it was running!

We restarted the service with no results. Per the advice on Microsoft's Partner support site, we opened up an elevated command prompt and ran sfc /scannow.

We started Windows Update and it's running OK again.

Saturday, July 28, 2012

Outlook 2010 preview window won't work for Office docs

One of my colleagues came across this issue at a client site and we found the solution in Microsoft’s forums. Specifically, Outlook's preview pane displays the following message when attempting the view a Microsoft Office file:
“This file cannot be previewed because there is no previewer installed for it.”

This is a new PC with new Windows 7 and Office 2010 installations. He tried removing and reinstalling Office without any success. He also tried creating a new Outlook profile with no luck.

The solution, found here, is as follows:

Click on Start, Run, enter dcomcnfg and click OK.
This starts the Component Services applet.
  • Expand Component Services.
  • Expand Computers.
  • Right click on My Computer and go to Properties
  • Click on Default Properties tab.
  • Ensure the following options are set:
    • Default Authentication Level: Connect (not "None").
    • Default Impersonation Level: Identify
This resets the DCOM permissions so the preview pane will work properly.

Saturday, May 12, 2012

User cannot connect to SBS network remotely

A user reported they could not use RWW or the RDP gateway to connect to their PC at the office. Oddly enough, they were able to connect to another machine - just not theirs. Internally, we were able to RDP into the machine so we knew it was not a problem with the machine itself.

After some research, we found this article on the Official SBS blog and got the answer. The PC was a new unit and we named it using a machine name that was used for an older machine. When SBS adds a machine into the domain, it creates an A record in the internal DNS. When you remove the machine from the domain, that record is not deleted.

So, we updated the A record with the IP for the new machine and we were good to go!

Saturday, March 31, 2012

Timeslips error - "Could not start the database engine" Part 2

Previously, we came across this problem and determined it was a quick adjustment using the BDE Administrator applet in the Control Panel. We saw this error again recently and found the BDE Admin applet would not open at all.

A forum post on Sage's support site recommended reinstalling the Borland Database Engine which did the trick.