PWA not externally accesible

[Kevin]

After installing project server 2007 and Moss on server 2008, I'm not able to
access the PWA site from other boxes. After installing Project server, I'm
actually no longer able to access the local host on the server itself
anymore. Is there a service such as the search or project application that
may have knocked this out? (following the Microsoft Experts Implementation
and Administration book but it doesn't talk to Server 2008 nor MOSS)

What logging can I turn on for IIS to give me a hint as to what the problem
is? Or should I start disabling Moss services until local host works again?

I have Server 2008 with IIS 7 and IIS6 compatibility mode on.
Moss 2007 SP1 and Project Server 2007 SP1 are on this box. SQL 2005 is on
another box.

 

[Stephen Sanderlin]

The most likely answer is that your Alternate Access Mappings are
incorrectly configured. Read
http://blogs.msdn.com/sharepoint/ar...w-about-alternate-access-mappings-part-1.aspx
for more information about this feature.

--

Stephen Sanderlin

Principal Consultant

MSProjectExperts



For Project Server Consulting: http://www.msprojectexperts.com

For Project Server Training: http://www.projectservertraining.com



Read my blog at: http://www.projectserverhelp.com/

Join the community at: http://forums.epmfaq.com

 

[Kevin]

I’m just following the MS Experts book (Implementing and Administering Server
2007) and don’t see why I need to monkey around with host file info. I have:
a.Two Web Applications:
i. MOSS – 80 at http://dhrm-vmdev=prj0/
ii. PW SSP – DHRM-VMDEV-PRJ08 at http://dhrm-vmdev-prj0:8000
b.Two Site Collections
i. ssp/admin
ii. ssp1 (My Site)
c. Farm Shared Services
i. MOSS – 80
ii. PWA SSP – DHRM-VMDEV-PRJ08 (Administration site host)
d. Project Web Access Site
i. MOSS – 80 http://dhrm-vmdev-prj0/ (I have no idea if this is the
“Extended Web site†as mentioned on page 150. I followed the directions on
page 140 & 141 when I created it)
1. http//dhrm-vmdev-prj0/PWA (Provisioned)

I should be able to hit localhost on the server but I 404.

 

[Stephen Sanderlin]

I would guess that you don't see why you need to do it because you seem
to have a less than complete understanding of how Alternate Access
Mappings work.



For more information beyond the article I've already referenced, refer
to the Plan alternate access mappings page on TechNet
(http://technet.microsoft.com/en-us/library/cc288609.aspx).



Under the section entitled "Troubleshooting alternate access mappings"
the first item is called "Mistake 1: Assuming that you do not need to
configure alternate access mappings unless you are deploying SharePoint
in an unusual way". The second item under "Mistake 1" is entitled
"Localhost", where it states:

Localhost

Localhost is a special host name that enables you to type
http://localhost in your browser and reach the Web site hosted on your
local computer. However, because localhost is made available by
accessing the computer's hosts file, Windows SharePoint Services 3.0
cannot automatically take advantage of it. If you need http://localhost
to be a valid URL for Windows SharePoint Services 3.0, you need to enter
http://localhost as an alternate access mapping.

Therefore, if you have not configured localhost as an alternate access
mapping, your problem is likely with incorrectly configured alternate
access mappings.


--

Stephen Sanderlin

Principal Consultant

MSProjectExperts



For Project Server Consulting: http://www.msprojectexperts.com

For Project Server Training: http://www.projectservertraining.com



Read my blog at: http://www.projectserverhelp.com/

Join the community at: http://forums.epmfaq.com

 

[Kevin]

I confess that I have a less than complete understanding of AAM. What the
deal was is that my server name was truncated by the MOSS setup process. So
the external access worked right up to the point I created the new port 80
page. Then I had to go into AAM and edit the public url to contain the full
DNS name. Magically, everything started to work.

So the instructions in your companies book would have worked swimmingly had
my server name been shorter.

Thanks for putting me on the path.

 

[Stephen Sanderlin]

I'm really glad you were able to figure it out. Hopefully the remainder
of your work with PS/MOSS will be less troublesome )

--

Stephen Sanderlin

Principal Consultant

MSProjectExperts



For Project Server Consulting: http://www.msprojectexperts.com

For Project Server Training: http://www.projectservertraining.com



Read my blog at: http://www.projectserverhelp.com/

Join the community at: http://forums.epmfaq.com

 

[Gary L. Chefetz]

Kevin:

Thanks for the feedback, we'll make every effort to include your suggestion
in the next edition. By the way, the book was written well before Server
2008 was available in stable form.


----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com