locked
Microsoft Repair Install Help RRS feed

  • Question

  • I am trying to do a repair installation on Microsoft CRM 4 on a Windows 2003 R2 Server. The Async Service seems to not work because all the system jobs are in the waiting status. When the repair goes through the checklist, I get an error accessing url http://<Hostname>:88. the remote server returned an error: (401) Unauthorized. I don't exactly know what is going on here, but I do know that I can't access the CRM web site from within the CRM server. From the outside, I can see the CRM website. Please let me know if there is anything you can do to help.

    Thank you
    Wednesday, May 12, 2010 9:01 PM

Answers

  • Did you get this issue resolved.  If so, please post the resolution.  It seems quite odd that you wouldn't be able to open CRM from a web browser on the CRM server.  Sounds like a DNS issue.

    If this is not a production server, then you might want to consider a reinstall.


    Regards, Donna

            Windows Live Blog

    Thursday, May 20, 2010 8:41 PM
  • It seemed to be an issue with the anonymous authentication account that was used for the CRM site. For some reason someone put in a guest account from the local computer and not someone on the domain. This seemed to fix our issue. Thank you


    Friday, May 28, 2010 6:24 AM

All replies

  • Can you get to it from the server using http://locahost ?
    Jerry http://www.crminnovation.com
    Wednesday, May 12, 2010 9:12 PM
  • The CRM website is on port 88. I can access http://localhost/ but not http://localhost:88. I can access the crm website from outside the server. 
    Thursday, May 13, 2010 3:58 AM
  • Did you get this issue resolved.  If so, please post the resolution.  It seems quite odd that you wouldn't be able to open CRM from a web browser on the CRM server.  Sounds like a DNS issue.

    If this is not a production server, then you might want to consider a reinstall.


    Regards, Donna

            Windows Live Blog

    Thursday, May 20, 2010 8:41 PM
  • It seemed to be an issue with the anonymous authentication account that was used for the CRM site. For some reason someone put in a guest account from the local computer and not someone on the domain. This seemed to fix our issue. Thank you


    Friday, May 28, 2010 6:24 AM