IPM.Note.EnterpriseVault.PendingArchive.ArchiveMe

[jprknight-oldax]

Has anyone seen this before? Every now and again a user comes to me saying their emails are not archived overnight. When I use DocMessageClass to look at the mailbox folder classes the pending items have the class of IPM.Note.EnterpriseVault.PendingArchive.ArchiveMe instead of IPM.Note.EnterpriseVault.PendingArchive.

I then cancel off the pending items, and archive the same items from the server as a test, and they archive overnight as usual.

We are currently running on EV 7.5 SP5, but still have the 7.5 SP1 client running on our clients.

Thanks,

Jeremy.

[JesusWept3]

.ArchiveMe and .RestoreMe are generated by the Lite Clients, so there is some communication issues when it goes to call http://EVServer/EnterpriseVault/Clientaction.asp and the item isn't being cancelled properly.

As always though, suggest using latest client

[jprknight-oldax]

The ArchiveMe message class is set when the user is archiving from the desktop PC. So would this suggest communication issues with EV server? MAPI problems with EV / Exchange?

Thanks,

Jeremy.

[JesusWept3]

Well what happens is the following

1. using lite client you hit Store in Vault
2. It changes the Item to IPM.Note.EnterpriseVault.ArchiveMe
3. It then calls http://yourEVServer/EnterpriseVault/clientaction.asp?
4. In that call it passes along the archiveID and also the shortcutaccessor
5. ClientAction.asp then calls AgentClientBroker and then archives the item
6. It then uses the Shrotcutaccessor to locate where the archiveme item is and then post processes it as needed

So it could be anything inbetween, end result though is whatever is happening there is a communication failure either to change it back to IPM.Note or to post process it

[TonySterling]

So to try and narrow down the point of failure:

Are the items actually in the archive and just left pending? If they are in the Archive then it would seem the request makes it to EV and gets archived but EV isn't able to post process like JW2 wrote in step 6.

Are your queues clean when this happens?

I would be curious to look at the modified time of the pending item and check what might be going on with the EV Server during that time. 

Do you see any errors or warnings in the EV log?

[jprknight-oldax]

Thanks JW,

Checked your connect inbox? What do you think of my question?

Jeremy.

[JesusWept3 · Accepted solution]

good point tony, i forgot to mention the actiontimestamp, any lite client functionality (archiveme, restoreme and public folder stuff) will stamp the item with a timestamp and then put that as part of the URL request to client action

Then when EV goes back to do anything, it wants to check to see if its been modified or not before doing anything with it, if the timestamps are off, it will cancel the operation
and actually now that i'm thinking about it, in public folders the items remain pending in that scenario

[Rob_Wilcox1]

 There were some bugs around the ActionTimeStamp attribute and what is passed to the server being "off" when it comes to checking against the timestamp on the messages.  They're fixed in later EV 2007 clients, but can't remember whether they were fixed for 2007 SP 1.

Also, with regards to public folders...  are these public folders replicated?  Could it be that the client machine is talking to ReplicaA, but you're archiving task normally archives from ReplicaB?  In which case you are out of luck, as this is never going to work.  The client machine will have updated ReplicaA's copy of the message, but the archiving task will look on ReplicaB.. find that the timestamps don't match (remember even in the same site replication can take UP TO 15 minutes in Exchange)... and since the timestamps don't match, the item stays pending.  (It's filed as a bug to address at some point in the future, to include the name of the Exchange or some other mechanism for the task to "do the right thing")

[JesusWept3]

public folders were my example mr rob, of other pieces of the client that use lite client functionality no matter what
i.e you can have a normal functionality DCOM client, but it will act as HTTP Only when performing Public Folder operations and will use the ArchiveMe and RestoreMe

[jprknight-oldax]

Hi guys,

To follow up, the messages are not in the archive.

erm...

J.

[Rob_Wilcox1]

 Yes that's right they won't be  .. because they were/are pending, but the archive task didn't process them, so they won't be archived.  You'd have to cancel them, and archive them again and/or troubleshoot what happens if they end up in this state again.

Hope that helps,