Installing SharePoint on Existing Web Server
I have a WSS 3.0 server running on rpt01. The plan is for that to be our new intranet site. I'm still working on it and there is not much content there yet at all. I have IIS7, asp.net 4 extentions and the Crystal Reports reporting engine installed on web102. Our current intranet site is on web101, only has asp.net 2 installed. What I would like to do is to install Sharepoint 2010 Foundation on web102 and build our new intranet out on the newer version of Sharepoint.
My question is, if I install Sharepoint 2010 Foundation on web102, will it affect the existing website that exists there now? The only site on that server is the reports web aspx pages that serve up our Crystal Reports. If I had to, I might could move the existing website to another server, but would have to make sure it has dotnet 4 and reporting engine installed. I'd like to keep them on the same server if possible.
My question is, if I install Sharepoint 2010 Foundation on web102, will it affect the existing website that exists there now? The only site on that server is the reports web aspx pages that serve up our Crystal Reports. If I had to, I might could move the existing website to another server, but would have to make sure it has dotnet 4 and reporting engine installed. I'd like to keep them on the same server if possible.
Ted Bouskill
SharePoint can share IIS with other standard web applications. The only conflict will arise if you try to use Port 80 on two sites that don't have a host header name set (a DNS entry for the web site)
ASKER
Okay I am making great progress on this project but am now stuck. I have my intranet reporting site installed on web102 and it's listed under <Sites> as <reports> and was running under port 80. It was working correctly with .net 4 extensions. It was accessible at http://sdwinweb102/. I have now installed SharePoint 2010 Foundation and it installs itself on port 80. Now when I go to http://sdwinweb102 the SharePoint site comes up and runs under .net 2.0 extensions. That's exactly how it should be. I have some web page part viewers in this site and am trying to reference reports that are under the reports website. I can't for the life of me figure out how to configure the host headers to allow both of these websites to run on port 80.This is what I have right now in Site Bindings IIS7:
site name: reports (.net 4)
type: http
host name: reports
port: 80
ip address: *
site name: sharepoint - 80
type: http
host name: (blank now, but if i put myaert2, it doesn't load)
port: 80
ip address: *
I want to be able to access the SharePoint site internally only by typing in http://myaert2 and then I want to be able to access the reports somehow - don't really care how, I'd just like them to be on port 80 also. Right now I can load sharepoint at http://sdwinweb102, but can't get reports load at all. If I take out the host header on reports and change the port, to say 82, the site loads fine under http://localhost:82/ and the reports run locally. But I need these to be accessible all over our network.
What do I need to do to accomplish what I want here?
site name: reports (.net 4)
type: http
host name: reports
port: 80
ip address: *
site name: sharepoint - 80
type: http
host name: (blank now, but if i put myaert2, it doesn't load)
port: 80
ip address: *
I want to be able to access the SharePoint site internally only by typing in http://myaert2 and then I want to be able to access the reports somehow - don't really care how, I'd just like them to be on port 80 also. Right now I can load sharepoint at http://sdwinweb102, but can't get reports load at all. If I take out the host header on reports and change the port, to say 82, the site loads fine under http://localhost:82/ and the reports run locally. But I need these to be accessible all over our network.
What do I need to do to accomplish what I want here?
ASKER
Part of this is accomplished. Server administrator got the pointer set up in DNS so that now http://myaert2 opens the default sharepoint site which is correct. Now I just need to get the reports website configured to open on port 80 also somehow.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I haven't figured out exactly how to do that. This is my current iis structure:
Sites
>Default Website
>>reports (can't get this to come up no matter what I do) .net 4
>>SharePoint - 80 (comes up by default to http://myaert2) .net 3.5
>>SharePoint Central Administration v4 (accessible by the servername:20143) .net 3.5
>>SharePoint Web Services
Can you point me to a link or tell me exactly what to search for that will show me how to get reports to show up on port 80 at http://myaert/reports? Or is that possible since reports is .net 4 and SP is .net 3.5?
Sites
>Default Website
>>reports (can't get this to come up no matter what I do) .net 4
>>SharePoint - 80 (comes up by default to http://myaert2) .net 3.5
>>SharePoint Central Administration v4 (accessible by the servername:20143) .net 3.5
>>SharePoint Web Services
Can you point me to a link or tell me exactly what to search for that will show me how to get reports to show up on port 80 at http://myaert/reports? Or is that possible since reports is .net 4 and SP is .net 3.5?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Okay - I finally got this working and tried this same method multiple times. I don't know why it didn't work earlier, but here's what is working:
SharePoint loads at http://myaert2 (which is good)
Reports loads now at http://sdwinweb102 (default) which I can handle.
Both are set to port 80 wit no host headers. The SharePoint site has an entry in DNS that points http://myaert2 to http://sdwinweb102.
I can load some the reports successfully. Others are failing, but that's not pertaining to this issue - it's got to do with Crystal Reports and .net 4 somehow.
SharePoint loads at http://myaert2 (which is good)
Reports loads now at http://sdwinweb102 (default) which I can handle.
Both are set to port 80 wit no host headers. The SharePoint site has an entry in DNS that points http://myaert2 to http://sdwinweb102.
I can load some the reports successfully. Others are failing, but that's not pertaining to this issue - it's got to do with Crystal Reports and .net 4 somehow.
ASKER
And I did use all the defaults - guess that was my problem to begin with.
ASKER
Thanks for the pointers. I'll know next time not to use the default settings. If I wasn't under a deadline to have the shell working by tomorrow, I would have taken your advice and uninstalled/reinstalled SharePoint.