According to Microsoft, exception 0xC0000142 (STATUS_DLL_INIT_FAILED) means that initialization of the  dynamic link library failed. It looks like some of dll's linked to e2010_bar are missing or not correctly registered.

1) In Windows 2012 environment .net framework 3.5 is not installed by default,  so please install it manually through ServerManager on all windows 2012 machines and after that try again to configure Exchange  integration. If configuration fails again, proceed with following steps.

Bob, is there an escalation on this issue?  We're in the same boat, Exchange admins are very worried about having to grant full blown access.  Have you tried incrementally enabling services to see what the baseline threshold is?   Thanks for any input.

Not only are there no Escalation on this issue, there is not even any lab cases open that I can file.  I did some 'google' searching, and did find a couple of things

http://h30499.www3.hp.com/t5/Data-Protector-Support-and-News/DP-6-11-Failing-to-Backup-Exchange-2010-via-VSS/td-p/4644566#.VRmshvnF8eo

Similar problem with 2003, turned out to be permissions on C:\exchsvr\bin\ and account not being exchange admin. But I tried an advanced backup using windows backup locally and I could see everything. So the problem was from the backup software. No Firewall so no problem with 5555. Agents installed ok, just no ntfs permissions.Even though path variable added. 

==============

This may also be a problem with Windows VSS function

http://blogs.technet.com/b/josebda/archive/2008/05/29/installing-the-vss-hardware-provider-for-the-microsoft-iscsi-software-target-on-windows-server-2008.aspx

I'm pushing the issue with HP, the documentation looks like it's two years behind the software.  This running with full permissions is too much of a security risk. 

For 1 and a half year I have the described problem with DP and exchange 2013 ( installed on Windows Server 2012 ).

It seems to me that DP-User's membership in the 'Organization management' cannot be verified reliable.

I have a multi domain environment and DP 9.03 is installed on a member server in a sub domain.

I've scheduled a task running every 15 minutes on a mailbox server with the following:

e2010_bar.exe -chkconf

The result changes every 12 hours ( or a multiple of 12 ):

MS Exchange 2010 Configuration check success

OR

Configured User dp-user is not a member of MS Exchange built-in group 'Organization Management'.

A year ago I opened a case with HP, it ended with the reference to the known MS article

http://support.microsoft.com/kb/969166/en-us

The following case with Microsoft showed that the file version of System.directoryservices.accountmanagement.dll

on my WS 2012 is higher ( 3.5.30729.6387 ) than in the article.

Any ideas?

Best regards,

Dirk

I have the same echo with same version , did you suceed to get a solution , the funny thing that backup is succeed some time without any error ?!!

No, I haven' got a solution yet.

As long as the 'Organization management' membership could not be verified reliable, the backup sometimes succeeded

and sometimes not.

All my DCs are Windows Server 2008 R2 , the functional domain level is also "Windows Server 2008 R2" , the DP Server is Windows Server 2008 x64 with DP 9.04

Because of the astonishing "multiple of 12 hours" it may be a relation with the timestamps of an access token or something else.

Best regards,

Dirk

I have opened a case at HP and I asked for the fix QCIM2A59113_TM1, it is a new powershell API DLL.

In the HP Blogs I found the following article where this fix is mentioned:

http://h30499.www3.hp.com/t5/Data-Protector-Support-and-News/Data-Protector-is-probably-not-configured-for-use-with-MS-Exchan/td-p/6755590#.ViXgiPn7NSF

Now the integration works fine!

I have opened a case at HP and I asked for the fix QCIM2A59113_TM1, it is a new powershell API DLL.

In the HP Blogs I found the following article where this fix is mentioned:

http://h30499.www3.hp.com/t5/Data-Protector-Support-and-News/Data-Protector-is-probably-not-configured-for-use-with-MS-Exchan/td-p/6755590#.ViXgiPn7NSF

Now the integration works fine!