What would be the best way/ steps to create a SHAREPOINT 2007 SITE which any one can browse through in our situation?
We already have a web application in our production which is used as a authoring site and a extended application for that site collection, were the public can access it without authentication.
Can I create another SITE COLLECTION under the current web application and then create a required web page in it?
Thanks
Jag
You can create many site collections per web application. Just go to the Central Administration console and under Sharepoint Site Management, (Under Application Management), click Create site collection. You will then be asked to select the web application under which you want to create it.
Note too that the url will appear something like webappname/sites/sitecollection
hope this helps,
sivilian
Related
I have an Azure Logic App which I use to connect to a couple of different SharePoint lists within the company I work for. I have been granted access to another SharePoint list within the company (access confirmed using browser), but this new SharePoint list does not show up in my Logic App SharePoint connector.
All of the Azure resources mentioned are in the same domain.
What could be preventing this one SharePoint list from showing up in my connector?
I test it in my side, I can access to the site but also can't see the site in my logic app. But, since we have the access to the site, so we can just copy the link to the logic app. Please refer to the steps below:
Go to the site page in browser and copy the site link.
Click "Enter custom value" and paste the link which we copied just now.
Then we can select the file under this site.
There are two SharePoint sites, each based on its own SharePoint installation.
Both are in the same domain.
The first site is for a document flow.
The second site is for a knowledge base.
I need to put a set of web parts (search, search results, indexed document library) from the second site in the master page of the first site.
The services and data will stay on the second site but they would be available in the first site.
I tried to apply the Page Viewer Web Part but it’s impossible to avoid using the second site’s master page layout.
Question
What other ways exist to solve this task?
You can index content of first SharePoint farm with search service application in another SharePoint farm.
You should configure search service application and add new website content source in search service application setting.
In this scenario you dose not need to move any thing and SharePoint crawl your content periodically.
This isn't a programming issue base on sharepoint, as a common user, I just created a web application in sharepoint central administration v4 in windows server 2012. After that the site was set up in IIS but I couldn't browse it in IE.
I think there should be an empty website base on existing template when generating in sharepoint, it should be show normally even if I didn't edit the website content.
This is the first time that I deploy it, how should I config it next step?
Please help, thanks!
As a normal user you cannot create a web application. People with access to the central administration are called administrators ;)
So SharePoint did not create a Sitecollection for you. No Problem. Create one yourself. Either in Central administration or on Powershell. If there is no Sitecollection on your root path http://yourservername, you should be able to create one there.
#assuming you want to create the SiteCollection on your root path.
$template = Get-SPWebTemplate "STS#0"
New-SPSite -Url "http://yourserverurl/" -OwnerAlias "domain\user" -Template $template
/EDIT:
I have just created a WebApplication myself to recreate your problem and as it turns out, this is not a problem.
If this is the first time that you have used this application pool
with a SharePoint Web application, you must wait until the Internet
Information Services (IIS) Web site has been created on all servers.
By default, no new SharePoint site collections are created with the
Web application. If you have just created a Forms Based Authentication
(FBA) Web application, then before creating a new site collection, you
will need to perform some additional configuration steps.
This is what you can read after yuor WebApplication has been created. So you definitly need to create a SiteCollection under your WebApplication yourself, before you can start browsing. If you do not create a Sitecollection prior to calling the URL to your WebApplication, the best result you can get is:
HTTP/1.1 200 OK
Server: Microsoft-IIS/7.5
Date: Wed, 21 May 2014 07:47:38 GMT
Connection: close
Kind regards.
Our team has a sharepoint website and I need to maintain the shared documents on our site. Problem is, it was designed by someone else and I was just given the link to the team website. I have tried using search and setting alerts and both of these don't work. i googled trying to find out what's happening and everyone keeps asking me to go to central administrator. I don't see central administrator anywhere in the website(I have full access). I am thinking I have to go to the server where sharepoint is running from. How do I figure out where it is running from? Sorry, I'm new to sharepoint.
Central Admin is the website that SharePoint creates when you install the software. It generally runs on your main SharePoint web frontend. If you RDC to your main web front end and then click on Start, All Programs and then click on the SharePoint folder, you'll see Central Administration. Click on that and the website will appear. You must be a farm admin to be able to access the site.
It sounds like you may not be a farm admin though. Depending on the permissions you have, you should be able to see your team site's Shared Documents or other document libraries under All Site Content, which you can either see by clicking on Site Actions or find it on the bottom left of the web page (again depends on what modifications have been created).
You need to assign the sign-in user account the permission to check the Shared Documents and you need to get at least Contribute permission level to maintain the Shared Doc on the site.
For Central Administrator, you can either RDC to the Web Front End server where the SharePoint was intalled or visit that server IP:port or computer name:port(80 by default).
Hope this may help!
First of all,the link you got may not be a Central Administration link.It is probably a common site collection.If you have full control permission over this site collection, you should be able to maintain Shared Document.
About the question that where SharePoint is running from?
SharePoint must be installed in a server. Generally, only farm admin can access this machine. If you want to know or learn about it, and if you don't have farm account to access the server, you can contact your farm administrator.
Central Administration is also a site.But it is different. You can manage all web applications and site collections in Central Administration.So you can manage or modify your team site in Central Administration
Hope this helps.
I am trying to implement personalization (WebPartManager and WebParts) on ASP.NET application deployed to SharePoint as application pages (Separate application and aspx pages deployed to _layouts).
I'd like to take advantage of SharePoint personalization provider, so I can just wire up the provider to WebPartManager in the ASP.NET application. However SharePoint seems to call SPRequest object to perform these tasks, and does not have a provider for personalization.
The second option I tried was to use SharePoint WebPartManager on these pages but it does not seem to work because application pages are not uploaded pages inside the SharePoint content database, so I receive errors when I try to add/personalize a webpart.
Does anyone know a clean way to utilize SharePoint personalization on application pages?
Normally, application pages are not tied to a specific site. And the webpart manager keeps the personalization values with the page in the site the page comes from.
You can probably accomplish what you are trying to do by using ASP.NET personalization. But then you have to use the ASp.NET personalization infrastructure which [I think] wants to use SQL Server by default.
Of course, the drawback to this is that you will have 2 personalization infrastructures implmented. This could mean deployment headaches.
Roger Williams
Franklin Laboratory
You may want to use page layouts with publishing pages instead of application pages.
Application Pages are ment to be shared across the Application in the Farm and doesnt support personalization. You need to deploy them as the Publishing pages to make use of the Personilization. You can try upload these files using features and as the Ghostable. So that you dont need to place them in the Pages Library you can have it in any web folder you want . For more information refer this link