RickJones012
asked on
Cannot create a DPM 2010 Protection Group on new exchange 2010 server.
DPM 2010 supports our current Exchange 2007. A Virtualized Exchange 2010 server was added to the domain. The agent loaded, but cannot create the protection group. Error “DPM could not enumerate application component Microsoft Exchange Server\Microsoft Information Store\RSC-EXCH2K10\182ff92
Still-having-issues-with-DPM-see.doc
Still-having-issues-with-DPM-see.doc
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Still working this issue, found additional articles pointing to a rollup for Exchanges SP2. Applied the rollup/patch, but error did not go away.
“(http://support.microsoft.com/kb/2664761/ -DPM protection agent service may stop responding on Exchange Server 2010 servers that are protected by System Center DPM 2010”
Just now looking at some new Application log errors.
“(http://support.microsoft.com/kb/2664761/ -DPM protection agent service may stop responding on Exchange Server 2010 servers that are protected by System Center DPM 2010”
Just now looking at some new Application log errors.
ASKER
I've requested that this question be closed as follows:
Accepted answer: 0 points for RickJones012's comment #a38487183
for the following reason:
The direction stipulated did not answer the question, but it put me on the correct path. According to a MS publication Exchange Roll Up #2 should correct the problem. Only issue with that is, the Roll up filed, but that’s another problem!
Accepted answer: 0 points for RickJones012's comment #a38487183
for the following reason:
The direction stipulated did not answer the question, but it put me on the correct path. According to a MS publication Exchange Roll Up #2 should correct the problem. Only issue with that is, the Roll up filed, but that’s another problem!
ASKER
The direction stipulated did not answer the question, but it put me on the correct path. According to a MS publication Exchange Roll Up #2 should correct the problem. Only issue with that is, the Roll up filed, but that’s another problem!
I did a couple hours of research on this, followed the above instructions, updates, and tried some other things as well. What finally worked for me was to dismount and remount the mail store in exchange. Once I did that, the error dissapeared. I hope this helps someone.
ASKER
I'm at a loos where to go from here.