Problems Receiving Email OL 2007 / Exch 2007 / Server 2008
Only some of the users are not receiving email in our company. It seems that the users who are having a problem are the ones that use Outlook 2007. They can send with no problems, but cannot receive email. When they try to sign into OWA, they get the message I am posting below.This does not seem to be affecting OL 2003 users, or OWA-only users, only OL 2007 users. Email was working as recently as Friday 3/6/09, but sometime over the weekend, it seems to have stopped, and I cannot figure out why. The only change to the network / system was Daylight Savings over the weekend.Our Exchange Server is:Exchange 2007 SP1 (x64)Windows Server 2008 (x64)Here is the message the users with a problem are receiving with OWA:RequestUrl: https://webmail.emailserver.com:443/owa/default.aspxUser host address: INTERNAL IP ADDRESSExceptionException type: Microsoft.Exchange.Data.Storage.StoragePermanentExceptionException message: Cannot find row based on condition.Call stackMicrosoft.Exchange.Data.Storage.QueryResult.SeekToCondition(SeekReference reference, QueryFilter seekFilter) Microsoft.Exchange.Data.Storage.UserConfiguration.QueryConfigurations(Folder folder, SortBy[] sorts, String configurationName, UserConfigurationSearchFlags searchFlags, Int32 maxRow, PropertyDefinition[] columns) Microsoft.Exchange.Data.Storage.UserConfiguration.GetIgnoringCache(UserConfigurationManager manager, Folder folder, String configurationName, UserConfigurationTypes freefetchType) Microsoft.Exchange.Data.Storage.UserConfigurationManager.InternalGetUserConfiguration(StoreId folderId, String configurationName, UserConfigurationTypes freefetchDataType) Microsoft.Exchange.Clients.Owa.Core.UserOptions.GetUserConfiguration() Microsoft.Exchange.Clients.Owa.Core.UserOptions.Load(IList`1 properties) Microsoft.Exchange.Clients.Owa.Core.UserOptions.LoadAll() Microsoft.Exchange.Clients.Owa.Core.UserContext.Load(OwaContext owaContext) Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.CreateUserContext(OwaContext owaContext, UserContextKey userContextKey, UserContext& userContext) 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 ExceptionException type: Microsoft.Mapi.MapiExceptionJetErrorReadVerifyFailureException message: MapiExceptionJetErrorReadVerifyFailure: Unable to find table row. (hr=0x80004005, ec=-1018) Diagnostic context: Lid: 18969 EcDoRpcExt2 called [length=210] Lid: 27161 EcDoRpcExt2 returned [ec=0x0][length=326][latency=1] Lid: 23226 --- ROP Parse Start --- Lid: 27962 ROP: ropGetContentsTable [5] Lid: 27962 ROP: ropSetColumns [18] Lid: 27962 ROP: ropSortTable [19] Lid: 17082 ROP Error: 0xFFFFFC06 Lid: 27489 Lid: 21921 StoreEc: 0xFFFFFC06 Lid: 27962 ROP: ropExtendedError [250] Lid: 1494 ---- Remote Context Beg ---- Lid: 26426 ROP: ropSortTable [19] Lid: 3245 StoreEc: 0xFFFFFC06 Lid: 2989 StoreEc: 0xFFFFFC06 Lid: 10213 StoreEc: 0xFFFFFC06 Lid: 9189 StoreEc: 0xFFFFFC06 Lid: 1750 ---- Remote Context End ---- Lid: 27962 ROP: ropSeekRow [24] Lid: 27962 ROP: ropFindRow [79] Lid: 17082 ROP Error: 0xFFFFFC06 Lid: 23649 Lid: 21921 StoreEc: 0xFFFFFC06 Lid: 27962 ROP: ropExtendedError [250] Lid: 1494 ---- Remote Context Beg ---- Lid: 26426 ROP: ropFindRow [79] Lid: 21970 StoreEc: 0x8004010F PropTag: 0x668F0040 Lid: 14164 StoreEc: 0xFFFFFA1D PropTag: 0xE5E0003 Lid: 8660 StoreEc: 0x8004010F PropTag: 0xE5E0003 Lid: 21970 StoreEc: 0x8004010F PropTag: 0xE5E0003 Lid: 3245 StoreEc: 0xFFFFFC06 Lid: 2989 StoreEc: 0xFFFFFC06 Lid: 2221 StoreEc: 0xFFFFFC06 Lid: 10645 StoreEc: 0xFFFFFC06 Lid: 9381 StoreEc: 0xFFFFFC06 Lid: 13925 StoreEc: 0xFFFFFC06 Lid: 15653 StoreEc: 0xFFFFFC06 Lid: 46665 Lid: 11621 StoreEc: 0xFFFFFC06 Lid: 21484 Lid: 23788 StoreEc: 0xFFFFFC06 Lid: 1750 ---- Remote Context End ---- Lid: 26849 Lid: 21817 ROP Failure: 0xFFFFFC06 Lid: 29726 Lid: 18462 StoreEc: 0xFFFFFC06Call stackMicrosoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, Object objLastErrorInfo) Microsoft.Mapi.MapiTable.FindRow(Restriction restriction, BookMark bookmark, FindRowFlag flag) Microsoft.Exchange.Data.Storage.QueryResult.SeekToCondition(SeekReference reference, QueryFilter seekFilter)Thanks!
March 9th, 2009 8:30pm

Hi, First please try to check if all these outlook 2007 users are in the different mailbox store from Outlook 2003 users. If yes, then please try to run ExBPA to has a health check. I suspect it could be a database related issue. Then please check if legacyexchangedn has been right set. 1. Run ADSIedit.msc from a command prompt. 2. Navigate to domain and then expand to user to find the outlook 2007 users. 3. Right click on it and select to Properties. 4. There please try to find value on legacyexchangedn. 5. Compare it to the alias, it should be the same as alias. Besides, please try to check event log and then post the error event here for further troubleshooting. Regards, Xiu
Free Windows Admin Tool Kit Click here and download it now
March 10th, 2009 11:25am

Hello Xiu - all of the users are on the same Exchange 2007 store (for almost a year now). When I looked at the user's properties in ADSIedit, the value on 'legacyexchangedn' value is the same for all of the users (in the format of "/o=DOMAIN/ou=first administrative group/cn=Recipients/cn=USER" This is the same for the users who are having the problem, as well as the users who are not. The 'Alias' as listed in the EMC is simply their username. Again, this is the same for all users, even the ones who are not on OL 2007.Are you saying that I need to change the OL 2007 users to have the above value match the alias? For example, if there is a user with an email address of 'jsmith@domain.com' and their existing legacyexchangedn shows as "/o=DOMAIN/ou=first administrative group/cn=Recipients/cn=jsmith" In EMC, their alias would list as 'jsmith'There was nothing in the event logs on this issue.Thanks.
March 11th, 2009 4:11pm

Also - a workaround we have done is create a rule in OL 2007 that moves anything destin for the 'Inbox' to a temporary inbox. So, email is still flowing in, but it is not showing up in the OL inbox. The problem with OWA still exists though.
Free Windows Admin Tool Kit Click here and download it now
March 11th, 2009 6:16pm

consulvation said: Hello Xiu - all of the users are on the same Exchange 2007 store (for almost a year now). When I looked at the user's properties in ADSIedit, the value on 'legacyexchangedn' value is the same for all of the users (in the format of "/o=DOMAIN/ou=first administrative group/cn=Recipients/cn=USER" This is the same for the users who are having the problem, as well as the users who are not. The 'Alias' as listed in the EMC is simply their username. Again, this is the same for all users, even the ones who are not on OL 2007.Are you saying that I need to change the OL 2007 users to have the above value match the alias? For example, if there is a user with an email address of 'jsmith@domain.com' and their existing legacyexchangedn shows as "/o=DOMAIN/ou=first administrative group/cn=Recipients/cn=jsmith" In EMC, their alias would list as 'jsmith'There was nothing in the event logs on this issue.Thanks.Yes, value on legacyexchangedn should be the same as display name.
March 12th, 2009 6:19am

When I did that, the user stopped receiving email, and I actually got a NDR when I tried to send one. Every other userhas a legacyexchangedn value listed in AD notation ('o=DOMAIN/ou=first administrative group/cn=Recipients/cn=USER'), and there are only 3 people having this problem.
Free Windows Admin Tool Kit Click here and download it now
March 12th, 2009 3:46pm

Hello - is there any update to this issue? I am willing to accept that Microsoft does not have a fix at this time, and I need to re-create the mailbox, but I just need to hear that from a MSFT/TEchnet staff member.Thank you.
March 16th, 2009 4:57pm

Hi,Sorry for the delay,since the issue only occur to these three user,I recommned you tonew mailbox account to fix the problem.Regards,Xiu
Free Windows Admin Tool Kit Click here and download it now
March 17th, 2009 11:35am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics