You may receive error message 302
when install windows update, Windows Live Messenger error ..., this
page contains some useful information to repair your
code 302, if you fixed this error from this help article, you can
email us (firstname.lastname@example.org ) give your feedback,
and we hope you can share this page to your friends if they need like you, thanks.
- When you install Microsoft
System Center Data Protection Manager (DPM) 2007 Protection
Agent on a target server, you may receive the following error
"The protection agent operation failed because it could not
access the protection agent on server
%FQDN_of_Production_Server%. The server
%FQDN_of_Production_Server% may be running DPM, or the DPM
protection agent may have been installed by another DPM
computer. (ID: Code 302)"
- How to fix?
This problem occur when the Service Principal Names (SPNs) for
the server are not consistent in Active Directory. The agent
installation may use the incorrect information to complete the
installation and connection. This problem can cause many
To resolve this problem, run the SetSPN tool and check the
Service Principal Names for the server that you cannot push the
Click here to learn more about "Setspn.exe support
tool update for Windows Server 2003"
Log on as a Domain Administrator.
At a command prompt, type the following command, and then press
setspn -L Servername
Note In this command, the placeholder Servername represents the
target server that you cannot deploy the DPM agent to.
The resulting output should resemble the following:
Registered ServicePrincipalNames for CN=TARGETSERVER,OU=Member
Notice that all the "HOST/" SPNs entries that are listed in the
output indicate that the primary DNS is set to
Incorrect_Servername, not Servername. When the agent is being
deployed, the DPM server is resolving the name
TARGETSERVER.SERVERNAME, and this is what is being used to build
the SPN that it is being requested at the time of agent
deployment. However, because the SPNs that are registered for
targetserver are for www.Incorrect_Servername, the Kerberos
connection attempt fails, and an attempt is made to establish an
anonymous connection. This may results in an event ID 6033
logged on the Exchange server.
Verify that there are no duplicate SPNs of the target server. At
a command prompt, type the following command, and then press
Examine the output for any duplicates of the desired SPN for the
To make sure that the Host SPNs are registered correctly, type
the following commands at a command prompt. Press ENTER after
setspn -a HOST/targetserver.Servername targetserver
setspn -a HOST/targetserver targetserver
Replicate the changes throughout Active Directory.
Redeploy the DPM protection agent to the affected servers.
to learn more information about the SetSPN tool
Read our site other related articles...
is we find the informations to Fix computer error 302 in
windows, hope our page is helpful to you, if you still need more
guide detail, please contact the
microsoft support for further help.
(Simple Steps:>>Download >>Install >>Free
Scan >>Repair. that's all.)
PC error? Windows error? Registry error? - Find and fix
on windowsxpregistrycleaner.com. Thanks for your visiting and we
wait for you using our site again in the future! :)
Search Computer Errors
on Our Site
Back to Top