Afternoon all, I'm hoping that someone will be able to help me with something. I've deployed SharePoint 2007, with all service patches onto a single server installation. The OS is Windows Server 2008 R2, SQL Server 2008 and IIS 7. I've also deployed PerformancePoint 2007 to the box. Now, I can access the central administration, which works for me as does getting into the SSP. The problem I'm having is that upon creating a new site collection and trying to access it via the URL, I get an error message stating that the site cannot be accessed. Please note that I don't return a http404 error message. Now, I've checked out what I can, and everything seems fine, but I can't access any site collection at all. I've created a new application and attached a site collection to this, with exactly the same issue. Checking the event viewer doesn't show anything to my eyes. Can anyone suggest anything that I may have missed? Many thanks, Stevenhttp://www.final-exodus.net

When you create the site collection, who are you making the site collection admin? Yourself? If you did not add yourself as a Primary/Secondary Site Collection Administrator then you won't have access. You can always go back to Central Administration and add yourself using Application Management -> Site Collection Administrators. Mike Smith TechTrainingNotes.blogspot.com

Also you can check ULS logs for any errors. Its in 12 Hive --Logs folder. Thanks & Regards Rakesh Narayan Lal

Have you added the DNS entries if necessary... Also, if you are accessing the WebApp from the Server have you modified the BackConnectionHostNames or DisableLoopbackCheck.. Reference http://support.microsoft.com/kb/896861 -IvanIvan Sanders My LinkedIn Profile, My Blog, @iasanders.

> I've also deployed PerformancePoint 2007 to the box. I'll leave this here for now as the addition of PerformancePoint seems to be an aside. Please note however that PerformancePoint 2007 has its own forums and questions on it go to one of those forums and not to a (pre-2010) SharePoint forum. (Moderator)2010 Books: SPF 2010; SPS 2010; SPD 2010; InfoPath 2010; Workflow etc. 2007 Books: WSS 3.0; MOSS 2007; SPD 2007; InfoPath 2007; PerformancePoint; SSRS; Workflow Both lists also include books in French; German; Spanish with even more languages in the 2007 list.

Just to respond to Mike Walsh, I've used the PerformancePoint forums for the appropriate questions and will continue to do so, I mention it here to be prudent. To the rest of the points: - (Mike Smith): I've given myself full site collection rights for this collection and another one. Neither rendered, I wasn't hitting the site in order for my permissions to be validated. (Ivan) Not sure on the DNS settings, I'm learning some of this as I go along. The diagnostic tool in IE advises that Windows can't find a device or computer called 'Application Name.' The alternate mappings have been set up up, it's within the trusted zone. Will giving the application an IP via the hosts file help here at all? http://www.final-exodus.net

Hi Steve, To keep it Simple: if you create a WebApp on a Port like http://YourServerName:9000 then create a Site Collection using the Collaboration Portal Temaplate on the new WebApp.. Are you able to access the site by going to the Http://YourServerName:9000 URL?? Information 1. IP Address are Added to the Network Adapter 2. DisableLoopBackProcessing http://support.microsoft.com/kb/896861 Is used to enable access to Hostnames other than the ServerName while testing on the Server 3. The Hosts file Maps Hostname to IP Addresses Maps HostNames to the IP Addresses of the Machine you are using. Developers sometimes use this when they do not have DNS # Hosts File example: # # 102.54.94.97 rhino.acme.com # source server # 38.25.63.10 x.acme.com # x client host 127.0.0.1 localhost 127.0.0.1 www.MyApp 127.0.0.1 MyApp 127.0.0.1 MyApp2 If you’re going to use HostsNames you will need to DisableLoopBack Processing and use the example above 127.0.0.1 YourAppName should map to your LocalMachine 127.0.0.1 -ivanIvan Sanders My LinkedIn Profile, My Blog, @iasanders.

Hi Ivan, I'll have a look at all of these. I'd made an amendment to the host file but didn't know about the LoopBack processing. As for the URL, I was going with http://WebApp/sites/sitename What I've done thus far is to edit the bindings in IIS to give it a shared port. SO, I can now access the site on http://localhost:PortNo/sites/sitename I'll give your suggestions a go though. Many thanks for your detailed responses.http://www.final-exodus.net