Tuesday, November 9, 2010

Error message when an Exchange Server 2007 user or an Exchange Server 2010 user tries to log on to OWA

http://support.microsoft.com/kb/941146

when you see this long list of errors:

Request


Url: https://:443/owa/lang.owa

User host address:

Exception

Exception type: Microsoft.Exchange.Data.Storage.StoragePermanentException

Exception message: There was a problem accessing Active Directory.

Call stack

Microsoft.Exchange.Data.Storage.ExchangePrincipal.Save()

Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchLanguagePostLocally(OwaContext owaContext, OwaIdentity logonIdentity, CultureInfo culture, String timeZoneKeyName, Boolean isOptimized)

Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchLanguagePostRequest(OwaContext owaContext)

Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.PrepareRequestWithoutSession(O

waContext owaContext, UserContextCookie userContextCookie)

Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.InternalDispatchRequest(OwaContext owaContext)

Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchRequest(OwaContext owaContext)

System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()

System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Inner Exception

Exception type:

Microsoft.Exchange.Data.Directory.InvalidADObjectOperationException

Exception message: Property Languages cannot be set on this object because it requires the object to have version 0.1 (8.0.535.0) or later. Current version of the object is 0.0 (6.5.6500.0).

Call stack

Microsoft.Exchange.Data.Directory.PropertyBag.set_Item(PropertyDefinition key, Object value)

Microsoft.Exchange.Data.Directory.ADObject.set_Item(PropertyDefinition propertyDefinition, Object value)

Microsoft.Exchange.Data.Directory.ADObject.StampCachedCaculatedProperties(Boolean retireCachedValue)

Microsoft.Exchange.Data.Directory.ADObject.ValidateWrite(List`1 errors)

Microsoft.Exchange.Data.Directory.Recipient.ADRecipient.ValidateWrite(List`1 errors)

Microsoft.Exchange.Data.Directory.Recipient.ADUser.ValidateWrite(List`1 errors)

Microsoft.Exchange.Data.Directory.ADSession.Save(ADObject instanceToSave, IEnumerable`1 properties)

Microsoft.Exchange.Data.Storage.ExchangePrincipal.Save()

Thursday, October 28, 2010

How to Determine What Domain Controller Authenticated the User

How to Determine What Domain Controller Authenticated the User. In another words, which domain controller log you in?

You can do either at command prompt

set logonserver
echo %logonserver%

Thursday, July 29, 2010

VMware vSphere Host currently has no management network redundancy.

Resolution

This message appears if the Service Console does not have network redundancy configured properly and can be safely ignored.

To prevent this message from appearing and to comply with proper network redundancy, VMware recommends that you add a second service console on a different vSwitch and subnet. Alternatively, you can add a second vmnic to the service console vSwitch.

To suppress this message on ESX hosts in the VMware High Availability (HA) cluster or if the warning appears for a host already configured in a cluster, set the VMware HA advanced option das.ignoreRedundantNetWarning to true and reconfigure VMware HA on that host. This advanced option is available in VMware Virtual Center 2.5 Update 3 and later.

Note: If the warning continues to appear, disable and re-enable VMware High Availability in the cluster.

To set das.ignoreRedundantNetWarning to true:
  1. From VMware Infrastructure Client, right-click on the cluster and click Edit Settings.
  2. Select VMware HA and click Advanced Options.
  3. In the Options column, enter das.ignoreRedundantNetWarning.
  4. In the Value column, enter true.

    Note
    : Steps 3 and 4 create a new option.

  5. Click OK.
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004700

9 security suites: maximum protection, minimum fuss

9 security suites: maximum protection, minimum fuss

Cisco, VMware, NetApp claim first end-to-end FCoE configuration

Cisco, VMware, NetApp claim first end-to-end FCoE configuration