Question : Microsoft Project Server will not respond to requests for fully qualified domain names

Project Server 2007 SP2 running in a server farm configuration:
Sharepoint Service 3.0 SP2 running on Windows Server 2003 R2 Standard X64
and  
SQL Server 2005 Standard running on Windows Server 2003 Standard x86

Neither Project Web Access nor connections from MS Project 2007 client app will connect to the server if you use a fully qualified domain name.  If you enter just a hostname in the URL string it works fine.  

ex.
http://myserver.mydomain.me/PWA
-fails to open in a web browser with an "unexpected error has occurred"
-returns "Login Failed.  Project could not connect to server  Please check your username and password and try again." if you attempt to connect from the MS Project client application

http://myserver/PWA
-opens to the PWA page for the user logging in
-connects to project server without issues

I do not recall having this issue when I first deployed Project Server or if it only showed up after the installation of SP1 or SP2,  it might be that I just never tried using a FQDN before.

All other Sharepoint Services sites respond properly to a URL containing the FQDN, it is only the Project Web Access and connections to PWA from the Project client that fail with the use of the FQDN instead of just the hostname.  

Does anyone have any ideas of what might be causing this?  I suspect something in the provisioning of the PWA site but I am not sure where to look or what to look for.  Any help will be greatly appreciated.  Thank you.

Answer : Microsoft Project Server will not respond to requests for fully qualified domain names

It's very likely that the "Alternate Access Mappings" (AAM) in SharePoint aren't set up to handle the FQDN.

http://technet.microsoft.com/en-us/library/cc263208.aspx

Make sure that the default web site, or the site hosting PWA has an entry with the FQDN.


James Fraser