Paawan
asked on
New SSP Administration link shows 404 error
I created a first SSP in a new MOSS 2007 installation, but the new Shared Services Administration link shows HTTP 404 error-Not found.
The creation of SSP was complete and it showed the services in the SSP.
I am using IIS7 on Windows 2008 Server.
What can be going wrong?
The creation of SSP was complete and it showed the services in the SSP.
I am using IIS7 on Windows 2008 Server.
What can be going wrong?
Ted Bouskill
When you created the SSP did you create both the web application and the site collection for it?
ASKER
After I configured the search and query service in the farm I created SSP in the following order.
1. New SSP
2. In the New SSP page I used the links in there to create the two new application. (No site collection was created)
3. New SSP Created successful message got displayed with all those services running.
4. On the central admin site as I click the new SSP under "Shared Services Administration" on the left menu
It says "Server Error is Application : Default Web site" HTTP Error 404.0 - Not Found
I am using Windows Server 2008, IIS 7
Another issue is eventhough the Search Services displayed as started, the log issues with propogation, so I restarted again and now I ensured its working. But during the creation of SSP I doubt it was not working properly.
1. New SSP
2. In the New SSP page I used the links in there to create the two new application. (No site collection was created)
3. New SSP Created successful message got displayed with all those services running.
4. On the central admin site as I click the new SSP under "Shared Services Administration" on the left menu
It says "Server Error is Application : Default Web site" HTTP Error 404.0 - Not Found
I am using Windows Server 2008, IIS 7
Another issue is eventhough the Search Services displayed as started, the log issues with propogation, so I restarted again and now I ensured its working. But during the creation of SSP I doubt it was not working properly.
ASKER
Few more things to add on to the discussion...
I have three servers with complete installation of MOSS
Server A - With Search Service + Central Admin
Server B - Query Service and Excel
Server C - Query Service and Excel
From the Central Admin as I create SSP and Applications, I can see the applications are created in Server B and Server C.
My requirement is to Create an SSP in this farm with host header http://intranet.cbs.in
Thanks
I have three servers with complete installation of MOSS
Server A - With Search Service + Central Admin
Server B - Query Service and Excel
Server C - Query Service and Excel
From the Central Admin as I create SSP and Applications, I can see the applications are created in Server B and Server C.
My requirement is to Create an SSP in this farm with host header http://intranet.cbs.in
Thanks
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 already enabled the ports and it worked out well for a new SSP.
But the old SSP whose sites are on Port 80 still didnt work, I guess even though the ssp creation displayed successful due to the firewall I suspect it didnt create the web applications.
Also let me know how the host header works? Do we need to configure the DNS server as well or just by providing the intranet.cbs.in in the host header field while creating the application will work?
But the old SSP whose sites are on Port 80 still didnt work, I guess even though the ssp creation displayed successful due to the firewall I suspect it didnt create the web applications.
Also let me know how the host header works? Do we need to configure the DNS server as well or just by providing the intranet.cbs.in in the host header field while creating the application will work?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You MUST create a site collection for the SSP web application. Without it there are no pages to display.
Plus you cannot create an SSP central administration site at the root. It will always be http://<host header>/SSP/Admin/...
Yes it sucks but that is the way Microsoft did it.
Plus you cannot create an SSP central administration site at the root. It will always be http://<host header>/SSP/Admin/...
Yes it sucks but that is the way Microsoft did it.
ASKER
from what irinuc: comment, i really dont know why Port 80 cannot be used.
But I succeeded in using a different port and its now working fine.
Thanks for the suggestions.
But I succeeded in using a different port and its now working fine.
Thanks for the suggestions.
ASKER
Eventhough I was not clear about the reasons of why not? I created the applicaions on different port other than Port 80.