Outlook 2007 : Scanpst.exe Errors

Outlook 2007 : Scanpst.exe Errors

When using scanpst.exe to check a Personal Folder (.pst file) you may be presented with the following error: “Internal errors were found in this file. They must be repaired for this file to work correctly.

This is actually a red-herring in some cases. Creating all of the standard Microsoft Outlook folders resolve the inconsistency errors requiring a repair with scanpst.exe.

These folders include:

  • Calendar
  • Contacts
  • Deleted Items
  • Drafts
  • Inbox
  • Journal
  • Notes
  • Outbox
  • Sent Items
  • Tasks

That-said, creating the folders is unnecessary as you needn’t be worried about the reported ‘errors.’

Windows : Re-installing the WMI Provider

Windows : Re-installing the WMI Provider

If you receive errors such as ‘SwbemLocator’ Critical Error 8004100A when running VBScripts, or applying GPO’s with WMI filters it may be necessary to re-install WMI.

Use WMIDiag.vbs to perform initial diagnosis (available here: http://www.microsoft.com/downloads/details.aspx?familyid=d7ba3cd6-18d1-4d05-b11e-4c64192ae97d&displaylang=en),
> Insert the slipstreamed Windows CD (including the current client Service Pack version) into the CDROM.
> Re-install WMI using the following command: rundll32.exe setupapi,InstallHinfSection WBEM 132 %windir%\inf\wbemoc.inf

You may be prompted for a file named ‘napclientprov.mof’ a non-corrupt version of this can be downloaded here.

Exchange 2007 : SendAs Bug

Exchange 2007 : SendAs Bug

I recently came across an issue where SendAs for a Resource (Shared) Mailbox appeared to be failing, despite specifically defined permissions granting this.The mailbox in question had several email addresses defined, and the SendAs function was using one of the secondary email addresses.

It would appear that it is impossible to SendAs using an email address other than the primary (reply) email address, or display name of any Exchange object.

Windows Server 2008 R2 : LookupAccountName Issues

Windows Server 2008 R2 : LookupAccountName Issues

When running Windows Server 2008 R2 x86/x64 that is a member of a Windows 2000 Domain you may encounter errors when installing applications that are similar to:

‘The trust relationship between this workstation and the primary domain failed’

I recently came across this error when installing SQL Server 2008 SP1 on a Windows Server 2008 R2 failover cluster, when selecting the service accounts from the domain I was presented with the error:

Error in User Account –   ‘The trust relationship between this workstation and the primary domain failed’

To resolve this error you must apply the following hotfix: http://support.microsoft.com/?id=976494

This issue affects Windows 7 and Windows Server 2008 R2, only when joined to a Windows 2000 domain. It is caused by a program that calls the LookupAccountName function to retrieve a security identifier (SID) for an account.

vSphere: Thin/TBZ disks cannot be opened in multiwriter mode

vSphere: Thin/TBZ disks cannot be opened in multiwriter mode

When using a ‘Virtual’ SCSI Bus Sharing controller on a VM Windows 2008 Cluster I was presented with the following error when creating disks via the vSphere Client:

Thin/TBZ disks cannot be opened in multiwriter mode.

Neither VM would power on with the new disk attached.

To resolve this, create the new vDisk from the shell using the command: vmkfstools -d eagerzeroedthick -c 20G -a lsilogic DISKNAME.vmdk

The important part of this command is eagerzeroedthick without this, or using thin or zeroedthick will result in the the same error being presented at power-on of the VM.