• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2366
  • Last Modified:

Exchange 2K7 'Can't open this item' after reboot

For reasons unknown after a server reboot our Exchange 2007 mailboxes give error ('can't open this item') when opeing e-mails received post that-particular-reboot. Pre-that-particular-reboot e-mails can be opened. I have ran eseutil (against DB and logs) and isinteg and everything seems fine. I have tried with different mailboxes, also recreating outlook profiles. Tried from CAS and the same problem occurs and the error below is thrown. I've rebooted several times. In the server's event log I get no errors. I've had to move the mailboxes back to another server running EX2K3. I have not set any diagnostic logging 'cause I'm not sure what I should increase the logging for. I've also disabled the anti-virus software to no avail.

 Request
Url: https://webmail.company.com:443/owa/forms/premium/MessageView.aspx?ae=Folder&t=IPF.Note&a=
User host address: *.*.*.*
User: username
EX Address: /o=GIBTELECOM/ou=First Administrative Group/cn=Recipients/cn=user
SMTP Address: username@company.com
OWA version: 8.0.685.24
Mailbox server: server
Exception
Exception type: Microsoft.Exchange.Data.Storage.StoragePermanentException
Exception message: Failed to get properties.
Call stack
Microsoft.Exchange.Data.Storage.MapiPropertyBag.GetProperties(IList`1 propertyDefinitions)
Microsoft.Exchange.Data.Storage.StoreObjectPropertyBag.InternalLoad(PropertyDefinition[] properties, Boolean forceReload)
Microsoft.Exchange.Data.Storage.StoreObjectPropertyBag..ctor(StoreSession session, MapiProp mapiProp, Origin origin, PropertyDefinition[] autoloadProperties, Boolean canSaveOrDisposeMapiProp)
Microsoft.Exchange.Data.Storage.StoreObjectPropertyBag..ctor(StoreSession session, MapiProp mapiProp, Origin origin, PropertyDefinition[] autoloadProperties)
Microsoft.Exchange.Data.Storage.Item.InternalBindItem(StoreSession session, StoreObjectId itemId, Byte[] changeKey, ItemBindOption itemBindOption, PropertyDefinition[] allPropsToLoad)
Microsoft.Exchange.Data.Storage.Item.InternalBind[T](StoreSession session, StoreId id, ItemBindOption itemBindOption, PropertyDefinition[] allPropsToLoad)
Microsoft.Exchange.Data.Storage.Item.InternalBind[T](StoreSession session, StoreId id, PropertyDefinition[] allPropsToLoad)
Microsoft.Exchange.InfoWorker.Common.SingleInstanceItemHandler.GetItemContent(MailboxSession itemStore)
Microsoft.Exchange.InfoWorker.Common.OOF.UserOofSettingsStorage.LoadUserOofSettings(MailboxSession itemStore)
Microsoft.Exchange.Clients.Owa.Premium.MessageView.get_UserOofSettings()
Microsoft.Exchange.Clients.Owa.Premium.MessageView.ShouldShowOofDialog()
ASP.forms_premium_messageview_aspx.__Render__control1(HtmlTextWriter __w, Control parameterContainer)
System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)
System.Web.UI.Page.Render(HtmlTextWriter writer)
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Inner Exception
Exception type: Microsoft.Mapi.MapiExceptionCallFailed
Exception message: MapiExceptionCallFailed: Unable to get properties on object. (hr=0x80004005, ec=-1073151871) Diagnostic context: Lid: 18969 EcDoRpcExt2 called [length=468] Lid: 27161 EcDoRpcExt2 returned [ec=0x0][length=222][latency=46] Lid: 23226 --- ROP Parse Start --- Lid: 27962 ROP: ropOpenMessage [3] Lid: 27962 ROP: ropGetPropsSpecific [7] Lid: 17082 ROP Error: 0xC0090081 Lid: 26465 Lid: 21921 StoreEc: 0xC0090081 Lid: 27962 ROP: ropExtendedError [250] Lid: 1494 ---- Remote Context Beg ---- Lid: 26426 ROP: ropGetPropsSpecific [7] Lid: 21970 StoreEc: 0x8004010F PropTag: 0xE960102 Lid: 21970 StoreEc: 0x8004010F PropTag: 0x6708000B Lid: 21970 StoreEc: 0x8004010F PropTag: 0xE960102 Lid: 21970 StoreEc: 0x8004010F PropTag: 0x67760102 Lid: 25394 Lid: 19506 Lid: 27698 Lid: 11285 StoreEc: 0xC0090081 Lid: 5257 StoreEc: 0xC0090081 Lid: 10786 dwParam: 0x0 Msg: servername Lid: 1750 ---- Remote Context End ---- Lid: 26849 Lid: 21817 ROP Failure: 0xC0090081 Lid: 20385 Lid: 28577 StoreEc: 0xC0090081 Lid: 32001 Lid: 29953 StoreEc: 0xC0090081
Call stack
Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, Object objLastErrorInfo)
Microsoft.Mapi.MapiProp.GetProps(PropTag[] propTagsRequested)
Microsoft.Exchange.Data.Storage.MapiPropertyBag.GetProperties(IList`1 propertyDefinitions)
0
HHTH
Asked:
HHTH
  • 8
  • 6
1 Solution
 
ATIGCommented:
From the error it would appear the user is doing this in OWA

Can you provide as much detail as possible?

Have you deployed the 3 Exchange  2007 rollups yet?
0
 
HHTHAuthor Commented:
The error is from OWA (the CAS) but it only reflects the same problem as if the user were doing it from outlook. Except outlook actually dsiplays ('can't open this item'). I have not applied the 3 rollups but this server was running fine for 3 months. The only thing that changed was that we run some redundancy\high-availabiltiy software (double-take). This basically allows the store to failover to a redunant one in case of the live should fail. We have been testing this and everything seemed fine. We were failing over and failing back without problems. The last time we tried though, although mail was fine and things seemed OK we got these 3 errors in the event log when rebooting:

2007-08-03 02:00:59.000      Site folder could not be opened for duplicate message deletion on virtual machine VIKKI. The error number is 0x80004005.       Event ID: 8276 MSExchangeFBPublish
      
2007-08-03 05:07:59.000      OALGen encountered error 80004005 while cleaning the offline address list public folders under /o=GIBTELECOM/cn=addrlists/cn=oabs/cn=Default Exchange 2K7 Offline Address List. Please make sure the public folder store is mounted and replicas exist of the offline address list folders. No offline address lists have been generated. Please check the event log for more information. - Default Exchange 2K7 Offline Address List                Event ID: 9335 MSExchangeSA

2007-08-03 05:07:59.000      OALGen encountered error 80004005 (internal ID 50101ee) accessing the public folder store while generating the offline address list for address list '/'. - Default Exchange 2K7 Offline Address List 9331 MSExchangeSA      
0
 
HHTHAuthor Commented:
Sorry submited before ending. I got rid of these errors by adding back the Exchange 2K7 server in the Public folders\system folders replication tab in the 'Schedule+ Free Busy' and 'Offline Address Book'. During testing failover it must've disappeared from there. After this though all was fine and mail was still OK. Only after another reboot a couple off days later was I getting the problem
0
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.

 
HHTHAuthor Commented:
To add further information. I have just confirned it is not really a db problem. I dismounted\moved the original db\logs to a temp\backup location and then mounted\created a completely new store but the problem is still there. I have since put back the original db\logs.
0
 
ATIGCommented:
does this happen to all users or just individual ones?

I would also recommend the rollups they fix some known bugs
0
 
HHTHAuthor Commented:
All users.

I'll apply the roll-up and see what happens.
0
 
HHTHAuthor Commented:
I've applied the roll-up 2 both servers and the problem persists. Note I have a Hub\CAS running on one server and the Mailbox\hub running on another.
0
 
ATIGCommented:
You might want to look at a pss case for this one... since its happening to everyone it almost like the pointers are messaged up.

I know the first think you going to need to do is a trace and have someoen at MS go through it.
0
 
HHTHAuthor Commented:
Ok. I contacted MS and I've sent them the trace. Any idea how I can view it? I've searched and cannot find any tool. I did try Exmon (I know it's meant to be for EX2K3) but it doesn't return any data.
0
 
ATIGCommented:
hehe... no MS specific .. lets them look at the code
0
 
HHTHAuthor Commented:
I assumed that would be the answer. Well at least I tried.
0
 
ATIGCommented:
:)
0
 
HHTHAuthor Commented:
SMSMSE 6.0 at fault. Although I had stopped the service. This wasn't enough. A complete uninstall reasolved the issue. Onto Symantec now.
0
 
ATIGCommented:
interesting.....
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 8
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now