Issue with Journal Task Failing : Possible Bug?

[Bruce_Cranksh1]

Hi All

I have a customer on EV 10 in the Middle East that I am finishing off the last outstanding deliverables on an EV project that is targeting an Exchange 2010 environment.

I have an issue where the Journal Task fails to start on the EV Journal Cluster and the error it gives, see below, doesn't make sense as I have confirmed that Outlook is on 2007 sp2 with all relevant Hotfixes. The Deployment Scanner passes this server and Mailbox Archiving is working fine in the Exchange 2010 environment. I have  done the following
 

• Reinstalled Office with all SP and Hotfixes
• Reinstalled the Journal Target and Journal Task
• Confirmed that both nodes on the Journal Cluster are configured with the same versions of Office. The Journal Task fails on either node.

I have read that there may be a known bug about this error and why EV won't start the Journal Task but I can't find anything around this. Any idea's

[JesusWept3]

Get a DTrace and a procmon and see where and how EV is trying to determine the version of outlook

[TonySterling]

Have you tried just using Outlook 2007 sp 3?  It is supported with the foot note to set a registry key.

1. SettheregistryentriesdescribedintheMicrosoftKnowledgeBasearticle http://support.microsoft.com/kb/952295. The recommended registry value is 0xFFFFFFFF.

[Bruce_Cranksh1]

Hi Guys

Thanks for the responses

I logged a call with Support due to time constraints. This is a weird one. We did analysis and Support thinks its a WMI corruption  in the OS or .NET

I have confirmed WMI is consistent so tomorrow we try to reinstall .Net ,

The issue seems to be that EV is unable to determine the Outlook version, even though deployment scanner works the Journal Task operates differently. This is  apparently done through WMI and .Net connections.

Will give an update tomorrow

[JesusWept3]

I had WMI corruption on one of my machines, I had to delete the entire WMI cache folder and reboot, after that worked like a charm

[JesusWept3 · Accepted solution]

http://windowsxp.mvps.org/repairwmi.htm

[Bruce_Cranksh1]

@ JesusWept

Thanks thats very helpful. I ran the commands below and it seemed to find no issues but your link seems more comprehensive :) I'll run that as well tomorrow

sc config winmgmt start= disabled
net stop winmgmt
Winmgmt /salvagerepository %windir%\System32\wbem
Winmgmt /resetrepository %windir%\System32\wbem
sc config winmgmt start= auto
net start winmgmt