Tag Info

Hot answers tagged

6

According to Microsoft: You cannot use the period character at the end of a site name, a subsite name, or a site group name. You cannot use the period character at the end of a folder name. You cannot use the period character at the end of a file name http://support.microsoft.com/kb/905231/en-us Are you looking for a way to by-pass this directive?


3

I had this happen to me recently and its was because I failed to actually create the site collection. I did happen to create the webapp so all the IIS settings/db was there. In central admin verify you do have a site collection.


3

You need to Deactivate/activate the feature or if you wan't to do it the right way then use FeatureUpgrading with a ApplyElementManifests element for the elements.xml with the images and then make sure the feature is upgraded


3

Creating a template from Publishing sites is not supported as the templating function relies heavily on content types and other items that may not be available when you create a new site from the template. Like you I've tried the workaround from 2007 by navigating directly to the Template creation page, which does work, but I've never succeeded in then ...


2

You need to create a search center first, then in site collection settings (for your site from where you perform people search) set this search center URL (http://yoursite/search/pages - for example). You may also need to check your User Profile Service - does it import users from AD correctly?


2

There is a strong possibility that the application pool for central admin timed out before the application was created on the second node. To fix this: Delete the web application that did not provision on all WFE's On the server hosting Central Admin, open IIS manager. In the tree view, expand the server name and click on Application Pools. Locate the ...


2

Here is something to try : Deactivate the feature Retract the solution delete the solution Go into your site via Manage Content and Structure and verify that all of the new images are in fact deleted. If they are not gone, delete them manually. The goal is to completely eliminate all traces of the feature and to eliminate any manual tweaks that may have ...


2

I dont know if this has anything to do with it.... I thought that 60 was for SPS 2003 and WSS 2.0 files. It looks like you had a problem upgrading. Windows SharePoint Services uses a different strategy for upgrading a page depending on whether or not it has been customized (unghosted). Windows SharePoint Services tracks whether a Web site was ...


2

I have recently just come across the same problem. when it will upload every file except executable files once i had allowed them on the Sharepoint server. After checking and ensuring both Config files and max file size settings on the server are correct to accept the executable. This can be done by following the link directly below. ...


1

i presume from the reply that you want a custom 404 page? there are two methods. One is generic: To configure SharePoint Foundation server or SharePoint Server 2010 to point to a custom 404 error Web page, follow these steps. 1.Log on to the computer that is running SharePoint Server 2010 by using an account that has administrative permissions. ...


1

You could create a custom page not found page that would retrieve the URL of the Site Collection-specific page from for example the property bag of that specific Site Collection and redirect to that page.


1

Have you tried setting the value of the SPSite.FileNotFoundUrl property?


1

If you are seeing the IIS default page it means that SharePoint is not listening on the hostheader:port that you are requesting. Verify that the host header and port are correct both in IIS and in Central Administration-Alternate Access Mappings. Also, remember that restoring a site collection does not create the corresponding web application so you would ...


1

This is the natural behaviour of HttpContext When you try to redirect the page, the current thread will be aborted and the system will throw an exception. If you don't want the thread to abort, pass false to redirect method. response.Redirect(message, false);


1

60 hive is where WSS 2.0 or SPS 2003 files were stored. Did you upgrade to 2007/WSS 3.0 on the same machine or box?


1

Ensure that you have an Alternate Access Mapping set up for www.nextdocs.com and IIS has a binding for the host header. I've seen similar behaviour when a web has been created without the host header and IIS has been used to bind the address to the site but SharePoint has no knowledge of the host header.


1

404 means NOT FOUND; you have to check the Search settings under Site Actions > Site Settings. The URL there is where the user goes when Search is clicked. This is a common issue when you aren't using the default Search site (basic), someone has moved it or you deployed the enterprise search site. Simply check it by running a search and noting the URL - ...


1

Maybe someone (I mean a site owner at least) deleted your subsite and you got an orphan url. But as the above answer it is too little info


1

Check the properties for the files that are not being deployed/copied. Make sure that Copy To Output Directory is set to either "Copy Always" or "Copy if Newer" depending on your preference. Check that the Deployment Location is set to something like "{SharePointRoot}\ISAPI\".


1

First thing to look at would be the contents of your solution package (wsp). Perhaps the mapped ISAPI folder is not being included in the package. Within Visual Studio, open the Package.package file. 1.) In the design view, your ISAPI mapped folder should be in the right hand pane (Items in the package) 2.) If you switch to the manifest view, there should ...


1

For future reference, the error i described in my post is actually normal behaviour. I thought that when i created a web application with a site collection, it would automatically be served via all the WFE servers. This is true, but only on the root site collection, to access the other site collections on all WFE servers, I had to add an Alternate Acces ...


1

The "no addresses available" is because you have a service that is not started, most likely the subscription service, which is require for multi-tenancy.


1

I don't know if this could be the cause of your problem, but by looking at your code I noticed that you use the istruction SPFile page = web.GetFile(url); If this is the case (and it isn't a simple copy&paste error) be aware that you are breaking the elevation process. By looking at your code I would assume that you already know this, but you should be ...


1

You will also want to familiarize yourself with the search settings for your site collection. If you go to Site Settings, Site Collection Administration and select Search Settings you will see the different settings available to you for pointing to the search center and how the scopes should behave. If you are going to OSSSearchResults.aspx you are not ...


1

It sounds as though you have some content that has links to your test sites. Add a crawl rule that blocks those sites from being indexed. Then I suggest you reset your index and re-crawl.


1

Using SharePoint Manager (http://spm.codeplex.com/), check to see if the document library was actually deleted. Then in IIS, make sure there isn't any virtual directory or such that matches the name of the document library.


1

I believe it's not the actual userdisp.aspx throwing the 404, but it's trying to redirect to the MySite, which does not exist at the url it's trying to redirect to. Use Fiddler to confirm.


1

For 404's I generally check this Can anyone else access the page? Is the master page published? does the user have permissions to the user page? Is the page layout published? does the user have permissions to the page layout? any other resources, such as controls (ASCX) not available to the user with 404's For anonymous sites I will most often solve it ...



Only top voted, non community-wiki answers of a minimum length are eligible