Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
microsoft dynamics crm was unable to add the web address of... RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    The full message is...

    "Microsoft Dynamics CRM was unable to add the Web Address of the Microsoft Dynamics CRM server to Trusted Sites.  This may cause it not to function correctly.  To add the Web address of the Microsoft Dynamics CRM server manually to the list of trusted sites, see the Internet Explorer Help for Trusted Site zones.  If you use CRM for Outlook with Offline Access, include the URL http://localhost as a trusted site."

    This popup will come up randomly, it has only occured since installing the crm for outlook plugin.  We are running version 4.0.   We host our own crm company files, and the internal url is crm.domainname.com.  All of the appropriate records have been created in DNS.  This is only happening on two of the workstations here.  Once you click ok to close the message everything continues to function normally with the CRM and the outlook plugin.  

    crm.domainname.com is listed in the trusted accounts list.  

    Any ideas are greatly appreciated.  Thanks in advance!
    Tuesday, February 9, 2010 3:24 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    The error states that the resident CRM client cannot input the site to the Trusted Sites list, not that it isn't there.  If a GPO is configured to populate the list, then nothing but the GPO will be allowed to specify the sites, and access to everything else restricted.  I would try removing the GPO configuration to see if that makes the problem go away.
    Dave Berry
    Thursday, May 27, 2010 12:35 AM
    Moderator

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    I should also mention that the trusted site security level is set to low.
    Tuesday, February 9, 2010 4:41 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Anyone have any ideas for this...?
    Tuesday, February 9, 2010 9:00 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    You can have a look at this post and see if it helps.
    Best Regards | Twitter: edwardsdna
    Thursday, February 11, 2010 3:15 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks Donna, that did not solve my problem.  I haven't been able to find anything on google.  The issue is spreading.  It seems that all users having this problem originally had the CRM plugin installed on a different computer.  The original CRM plugin had been uninstalled prior to reinstalling on the new computer.  
    Tuesday, February 16, 2010 9:16 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    You may want to open a support ticket with Microsoft as this seems like it is unique to your environment and they will more quickly be able to identify the issue.
    Best Regards | Twitter: edwardsdna
    Thursday, February 18, 2010 10:04 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I am receiving the exact same error, and I use the Crm Online version.  I have even tried using GPO to push the requested URLS to the Trusted Sites zone, which it does, but I still get the error.
    Wednesday, May 26, 2010 4:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    You can take a look at this post and see if there is anything helpful.  Also, completely uninstall any toolbars you have for IE including Yahoo, Google, Windows Live, etc. and then reboot your machine.

    Regards, Donna

            Windows Live Blog

    Thursday, May 27, 2010 12:21 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    The error states that the resident CRM client cannot input the site to the Trusted Sites list, not that it isn't there.  If a GPO is configured to populate the list, then nothing but the GPO will be allowed to specify the sites, and access to everything else restricted.  I would try removing the GPO configuration to see if that makes the problem go away.
    Dave Berry
    Thursday, May 27, 2010 12:35 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Check it out:  Update Rollup 11 is supposed to fix this issue:  http://support.microsoft.com/kb/982510/en-us

    Dave Berry
    Monday, June 7, 2010 11:55 PM
    Moderator