Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 899
  • Last Modified:

Problems getting Out of Office Assistant working Outlook 2007 & Exchange 2008

Hello everyone,

A user who is out of town told me that they couldn't get their Out of Office Assistant (OOA for now) working. Since I'm not sure of how to do this from the Exchange backend, I logged into their local machine (shame on them for changing their password back to  the default password) and when I launched Outlook 2007 to set the OOA, I got this message: "Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later."
In troubleshooting the issue, I found this article: http://technet.microsoft.com/en-us/library/cc411327.aspx?ppud=4 that mentions using OWA to fix things. When I went to OWA, I get the following error logging in:

        A problem occurred while trying to use your mailbox. Please contact technical support for your organization.
Show details


Request
Url: https://exchange.[companyurl].[com]:443/owa/lang.owa
User host address: 192.168.***.***

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(OwaContext 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.ADOperationException
Exception message: Active Directory operation failed on data.girlscoutssdi.org. This error is not retriable. Additional information: Insufficient access rights to perform the operation. Active directory response: 00002098: SecErr: DSID-03150A45, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0

Call stack
Microsoft.Exchange.Data.Directory.ADSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRequest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer)
Microsoft.Exchange.Data.Directory.ADSession.ExecuteModificationRequest(ADRawEntry entry, DirectoryRequest request, ADObjectId originalId)
Microsoft.Exchange.Data.Directory.ADSession.Save(ADObject instanceToSave, IEnumerable`1 properties)
Microsoft.Exchange.Data.Storage.ExchangePrincipal.Save()

Inner Exception
Exception type: System.DirectoryServices.Protocols.DirectoryOperationException
Exception message: The user has insufficient access rights.

Call stack
System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, ResultAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)
System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)
Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOperation)
Microsoft.Exchange.Data.Directory.ADSession.ExecuteModificationRequest(ADRawEntry entry, DirectoryRequest request, ADObjectId originalId)


***Before I wrap up, a note: yesterday I finished moving users from my old Exchange 2003 server to my Exchange 2008 server, this user included. I'm not sure if this has anything to do with it***

Any help for getting this setup is appreciated!
0
biofishfreak
Asked:
biofishfreak
  • 3
  • 2
3 Solutions
 
dmwynneCommented:
The first thing I would do is to either restart the server or Exchange services and see if it works.
0
 
biofishfreakAuthor Commented:
Well I'd prefer not to restart the service, but if I don't hear from anyone else soon (by around 4pm PST) I'll do that.
0
 
biofishfreakAuthor Commented:
Just kidding, I got impatient. I restarted most of the exchange services individually (wasn't sure which one) and each time nothing happened (I restarted outlook before trying too.)

Looking at the OWA error, I found the MSKB article: http://support.microsoft.com/kb/941146 and followed that through but Exchange console returned that no values were changed.
0
 
dmwynneCommented:
Is this happening for just the one user or everyone?  Have you verified autodiscover is working properly from inside the domain and externally.
0
 
biofishfreakAuthor Commented:
Digging some more, I found this: http://technet.microsoft.com/en-us/library/bb885050.aspx . Sure enough that fixed the problem.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now