Optimize the Speed of Your PC and Fix Computer Errors!

 Windows 7 Error | Windows Vista Error | Windows XP Error | Registry Repair Help | PC Common Error

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Home   About Us   F.A.Q   SiteMap   Contact Us

You may receive error message 302 when install windows update, Windows Live Messenger error ..., this page contains some useful information to repair your computer error code 302, if you fixed this error from this help article, you can email us (windowsxpregistrycleaner@gmail.com ) give your feedback, and we hope you can share this page to your friends if they need like you, thanks.

 

Error 302 install DPM

Back to Top

  • When you install Microsoft System Center Data Protection Manager (DPM) 2007 Protection Agent on a target server, you may receive the following error message:

    "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 symptoms.

    To resolve this problem, run the SetSPN tool and check the Service Principal Names for the server that you cannot push the agent to.

    Click here to learn more about "Setspn.exe support tool update for Windows Server 2003"

    1. Log on as a Domain Administrator.

    2. At a command prompt, type the following command, and then press ENTER:
    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
    Servers,DC=<Servername>,DC=com:
    SMTPSVC/targetserver.<Servername>
    NtFrs-88f5d2bd-b646-11d2-a6d3-00c04fc9b232/targetserver.<Servername>
    HOST/targetserver.www.<Incorrect_Servername>/Incorrect_Servername
    HOST/targetserver.www.<Incorrect_Servername>
    exchangeMDB/targetserver.www.<Incorrect_Servername>
    SMTPSVC/targetserver.www.<Incorrect_Servername>
    HOST/targetserver.www.<Incorrect_Servername> /www.<Incorrect_Servername>
    exchangeRFR/targetserver.www.<Incorrect_Servername>
    exchangeRFR/targetserver.<Servername>
    exchangeMDB/targetserver.<Servername>
    exchangeRFR/TARGETSERVER
    exchangeMDB/TARGETSERVER
    SMTPSVC/TARGETSERVER
    HOST/TARGETSERVER
    ~~~~~~~~~~~~~~~~~~~~~~~~~~

    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.

    3. Verify that there are no duplicate SPNs of the target server. At a command prompt, type the following command, and then press ENTER:
    setspn -X

    Examine the output for any duplicates of the desired SPN for the target server.

    4. To make sure that the Host SPNs are registered correctly, type the following commands at a command prompt. Press ENTER after each command.

    setspn -a HOST/targetserver.Servername targetserver
    setspn -a HOST/targetserver targetserver


    5. Replicate the changes throughout Active Directory.

    6. Redeploy the DPM protection agent to the affected servers.

    Help link:
    Click here to learn more information about the SetSPN tool
     

Read our site other related articles...

 

Microsoft help links for windows 302 error

Back to Top

 

PC tool to fix error code 302

Back to Top

 

That 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.



 

www.pchealthadvisor.com

www.pchealthadvisor.com

(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

Error 302

Home > Categories > PC Common Errors - Update: April 14, 2010

>>> Repair PC Error 302
Copyright 2008 WindowsXPRegistryCleaner.com. All Rights Reserved.      

 

 Change Language

 

Subscribe Emails

PC Error Popular Articles 

PC Health Advisor Reviews
error 1706
Error 2753
ccSvcHst.exe
Error 2048
lsass.exe
Error 21
Csrss.exe
Error 2738

 

 PC Errors Categories 

Windows 7 Error
Windows Vista Error
Windows XP Error
Registry Repair Help
PC Common Error

 

 


 

This site provides the information as a service to the Internet community. We do not endorse any of the companies, products, or services
mentioned. Each product or service is the trademark of their respective company. All information is provided as opinions only.