Latest EX Build 4.81.1147

I just ran the upgrade on our host server which was also running 655.

No problems.

Followed the prerequisites (closing volumes and running HealthCheck to rebuild any broken indexes, etc).


Our clients are still running the 655 version along with the OWA support on our Exchange 2003 server. (Both will be updated soon).

ThI have this version, 1147, and I have no problem. I just have a problem with the queue index but I need a hotfix to repair it.at problem appear too in the 655 version.

Regards.

I upgraded to this version from 655 a week or so ago. I ran into a problem getting my volumes closed, but that was not related to the patch. I've had no problems so far.

We haven't upgraded the user Search plug-in or OWA shortcut support yet, but we are working to do so. Good luck!

Upgraded one of our lesser used clusters today. All the EX functions look good. Did run into some difficulties running the upgrade but, they were all cluster related issues.

The Search Tool seems much faster. Not sure it pulls data back faster just the search GUI seems "snappier". Shortcuts seemed pretty snappy as well.

Hopefully, 1147 will fix the exquery.exe/EXCH~1.EXE hangs we are experiencing.

I have reported an issue with 1147 running against a Domino 7 mail environment. Our client has two EX systems amd both have been upgraded from 655 to 1147. Following each upgrade, files started building up in the Payload and MsgCentre directories. These are a mix of .onm and .access files , hundreds of them being generated by the overnight archiving and shorcutting tasks. This wasnt happening under 655 and for the time being I have had to suspend the tasks. If you are running Domino , watch out for this.

Hi Mark,

Payload is used for EmailXtract jobs and MSGCENTER for both using EmailXtract and Real Time journaling. Depending upon which process has touched the data messages will be in one of the many directory structures.

Data will be cleared off from MSGCENTER when the containers that it belongs to are closed and index agent has finished working on it. Any wrong termination of services might can give unexpected results.

Data from Payload will be moved to another directory one its process by certain processes.

If backup job runs at night and EXSuspend utility suspends EX services you will see data in payload directories for long. Especially till all services resumes back and everything gone through MSMQ private queues. If EX never got chance to add to MSMQ due to any given reason then data might need to be processed manually which support will help you with.


I hope I make some sense.

Thanks,
Rajan