We have seen other posts with similar issues so we have tried the following:
1. Removed the agent and the registry entries
2. Numerous reboots after attempting reinstallation of agent
No dice. Then we attempted to do a manual install of the agent. Here is the
log:
=== Verbose logging started: 10/8/2007 10:09:01 Build type: SHIP UNICODE
3.01.4000.3959 Calling process: d:\0aacafa0d98b5abe658b2b\installagent.exe
===
MSI (c) (70:8C) [10:09:01:444]: Resetting cached policy values
MSI (c) (70:8C) [10:09:01:444]: Machine policy value 'Debug' is 0
MSI (c) (70:8C) [10:09:01:444]: ******* RunEngine:
******* Product: d:\0aacafa0d98b5abe658b2b\dw20shared.msi
******* Action:
******* CommandLine: **********
MSI (c) (70:8C) [10:09:01:444]: Client-side and UI is none or basic: Running
entire install on the server.
MSI (c) (70:8C) [10:09:01:444]: Grabbed execution mutex.
MSI (c) (70:8C) [10:09:01:459]: Cloaking enabled.
MSI (c) (70:8C) [10:09:01:459]: Attempting to enable all disabled priveleges
before calling Install on Server
MSI (c) (70:8C) [10:09:01:475]: Incrementing counter to disable shutdown.
Counter after increment: 0
MSI (s) (24:88) [10:09:01:475]: Grabbed execution mutex.
MSI (s) (24:90) [10:09:01:490]: Resetting cached policy values
MSI (s) (24:90) [10:09:01:490]: Machine policy value 'Debug' is 0
MSI (s) (24:90) [10:09:01:490]: ******* RunEngine:
******* Product: d:\0aacafa0d98b5abe658b2b\dw20shared.msi
******* Action:
******* CommandLine: **********
MSI (s) (24:90) [10:09:01:490]: Note: 1: 2203 2:
d:\0aacafa0d98b5abe658b2b\dw20shared.msi 3: -2147287038
MSI (s) (24:90) [10:09:01:490]: MainEngineThread is returning 2
MSI (c) (70:8C) [10:09:01:490]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (70:8C) [10:09:01:490]: MainEngineThread is returning 2
=== Verbose logging stopped: 10/8/2007 10:09:01 ===
Here is the fun part. Every time we attempt to push this agent to this
server, it causes the other domain controller with the agent already
installed to stop communicating with the DPM server. We then have to run the
'setdpmserver' command on it. Once we do, communication resumes. Weird.
All of these servers had the previous Beta 2 agent installed on them. All
were backing up successfully. It is as if there is something which is
affecting DCs where the agent was installed. Has anyone else had this issue?
We need to get this resolved asap. Please advise.
Thanks for your feedback. It looks like there is DC replication enabled on
your setup. Does your DC acts as parallel domain controller?
Could you please paste the error details from details pane from DPM Agents
UI?
Thanks,
krisnaru
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"rixmix" <rix...@discussions.microsoft.com> wrote in message
news:12B404E4-6D24-469F...@microsoft.com...
Install protection agent on 2k3mail.d2inet.net failed:
Error 347: An error occurred when the agent operation attempted to create
the DPM Agent Coordinator service on 2k3mail.d2inet.net.
Error details: Unknown property
Recommended action: Review the error details, take the appropriate action,
and then retry the agent operation.
Please advise.
On the DPM computer, from the DPM Management Shell (shortcut on desktop and
Program Files) prompt, type Attach-ProductionServer.ps1 <DPM server name>
<production server name> <user name> <password> <domain>.
--
Thanks,
Kapil
This posting is provided "AS IS" with no warranties, and confers no rights.
"rixmix" <rix...@discussions.microsoft.com> wrote in message
news:2B5C0E62-90A0-4ADD...@microsoft.com...
2. The manual adding of the server to the DPM server via the DPM Shell
worked well, however, it obviously has issues communicating with the 2k3mail
server.
You need to install agent on two domain controllers since replication
happens in regular intervals. On replications, domain groups get recreated.
That creates problems.
Please follow below steps install agents on parallel DCs.
The protection agent installations cannot occur simultaneously on the domain
controllers that are in parallel replication mode. Wait for the replication
to occur between the domain controllers before you install the protection
agent on the second domain controller. You can also force the replication by
doing the following:
From the command prompt, type repadmin /syncall.
The repadmin is a utility that you install with the Windows Server 2003
support tools.
Note Two or more
Please let me know if you face any problems further.
Thanks,
krisnaru
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"rixmix" <rix...@discussions.microsoft.com> wrote in message
news:A583933F-9D73-4690...@microsoft.com...
Please advise. I respect your knowledge, however, I am unclear how the above
is going to resolve the issue. Looking for your response.
You are right.You have already successfully installed agent on 2k3data
server. Make sure that agent communication is proper between DPM and
production server from DPM UI, if not do the setdpmserver on production
server.
After that install agent on second DC by steps: 5, 6 and 7 steps.
Thanks,
krisnaru
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"rixmix" <rix...@discussions.microsoft.com> wrote in message
news:BFB1F200-407B-47E8...@microsoft.com...
It looks like AD replication caused agent install to fail.
Lets do the below steps and let me know the result.
> > 1. Uninstall the agent from 2k3data
> > 2. Remove reg entries
> > 3. Manually install agent on 2k3data
> > 4. Run DPM shell command to add 2k3data to DPM server
> > 5. Run manual DC sync
> > 6. Manually install agent on 2k3mail
> > 7. Run DPM shell command to add 2k3mail to DPM server
Please send me the DPMAgentInstall.log under system temp folder incase
failure happens.
Thanks,
krisnaru
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"rixmix" <rix...@discussions.microsoft.com> wrote in message
news:7EDD4998-D29C-4189...@microsoft.com...
Thanks,
krisnaru
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"rixmix" <rix...@discussions.microsoft.com> wrote in message
news:19079222-444D-498B...@microsoft.com...
Thanks,
krisnaru
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Krishna Manohar Narukulla [MSFT]" <kris...@online.microsoft.com> wrote in
message news:u2OSM0ID...@TK2MSFTNGP04.phx.gbl...
Greg