Microsoft SharePoint

37K

Solutions

19K

Contributors

Microsoft Sharepoint is a software platform and family of software products used for collaboration and web publishing combined. These capabilities include developing web sites, portals, intranets, content management systems, search engines, wikis, blogs, and other tools for business intelligence and collaboration. SharePoint has a Microsoft Office-like interface, and it is closely integrated with the Office suite.

Share tech news, updates, or what's on your mind.

Sign up to Post

When using a search centre, I'm going to show you how to configure Sharepoint's search to only return results from the current site collection. Very useful when using Office 365 with multiple site collections.
0
New feature and membership benefit!
LVL 9
New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

A recent project that involved parsing Tableau Desktop and Server log files to extract reusable user queries for use in other systems. I chose to use PowerShell to gather the data, and SharePoint to present it...
1
In case you ever have to remove a faulty web part from a page , add the following to the end of the page url
?contents=1
2
These days socially coordinated efforts have turned into a critical requirement for enterprises.
1
I thought I'd write this up for anyone who has a request to create an anonymous whistle-blower-type submission form created using SharePoint 2010 (this would probably work the same for 2013). It's not 100% fool-proof but it's as close as you can get without Visual Studio which was a requirement.
1
One of the most challenging things I've run into as a SharePoint consultant is creating a visual sitemap of a SharePoint environment.  Visual maps are so much more effective when showing clients what their environment looks like and how it can be optimized when performing a migration, security review, or consolidation effort.  My inspiration for publishing this article is hoping it will provide others in the same position an easy way to get a visual overview of their SharePoint environment.
1.png*NOTE: The yellow colored objects were manually set. I try to get only 1 row of pages in Visio. If any go beyond 1 row, I put them in a different Visio sheet and uniquely identify that node by changing the color.
 
Run this PowerShell script.
  • By default it uses the local SharePoint environment so it should be run on the SP server itself.
  • If you want to specify a specific WebApplication, you can modify the script. 
  • This was written for WSS 3.0 and MOSS 2007 to run using PowerShell 1.0 because that's what many companies are migrating from.  For 2010 and 2013 I'm aware there are optimizations that could be made to the script
The script is commented but is pretty straight forward.
 
#clear the PowerShell window
cls

#Set or reset default properties
$ReportPath = "SPSiteReport.csv"
$Result=""
$Count=0

#Load the PowerShell commandlets for SharePoint using PowerShell 1.0 and MOSS 2007

Open in new window

2
This is just a little help to get you started with your first SharePoint site.
First things first, log into your Microsoft Office 365 Admin portal account at this link: https://portal.microsoftonline.com/admin/default.aspx.

Use your username and password to access your Office 365 Administrative portal site.  If you have trouble logging in, use the forgot password option to reset.  Once successfully logged in, select the drop down menu under Admin and select SharePoint. The next page that loads will be to administer your Sharepoint site information. Once loaded, you will be managing your site collections as Microsoft refers.  Think of this as the master and root destination to manage everything.

If you already have a few URLs listed, like, https://domainname.sharepoint.com then you are well on your way.
Want to create/check ownership of that domain created?  Select the domain in question and on there is a tab above that has a drop down entitled "Owners, " click it and choose Manage Administrators.  From here, you can check who is your primary site collection administrator as well as see who is your site collections administrator(s). In the event you want others to share the task of editing or managing the site collection with you, adding administrators will be the next task.

Simply do the following:
Select the URL you want to add administrator(s) to,…
0
 
LVL 1

Author Comment

by:teksolgreg
Comment Utility
I edited the article to include information on adding administrators for the sites not just primary site collection administrator.  Found this information helpful when a client had an admin leave a job and not give up some information on how to change and edit content.
I would like to follow up with more articles addressing issues they come across and how we solve them together as I feel it would be extremely helpful for the community and possibly attract more public views.
0
In SharePoint, you have the ability to set the number of versions to retain through the settings of the specific document libraries.  I was recently faced with a challenge where a company implemented a new global policy which mandated only 10 versions be retained.  The policy had be implemented by notice of the collection administrators after users were sufficiently notified of the change so I it had to be something that was run

Unfortunately, with the first library they updated, they noticed when you changed the version retention number, the libraries did not automatically remove the older versions.  Only when you performed a future update of the document, did the older versions get trimmed off.  

After a little research, I couldn't find anything online which offered the solution I was looking for.  In the end I wrote a simple but very fast, effective, and powerful PowerShell script.

if((Get-PSSnapin | Where {$_.Name -eq "Microsoft.SharePoint.PowerShell"}) -eq $null) {
    Add-PSSnapin Microsoft.SharePoint.PowerShell;
}
# 2 variables which need to be set
$siteCollection = "http://SharePoint/Sites/SiteCollection"
$documentRetentionCount=10

# get site collection
$site = new-object Microsoft.SharePoint.SPSite($siteCollection)

# loop through each subsite
foreach ($web in $site.AllWebs)
{
   write-host $web.url

   # loop through all lists in each subsite
   foreach ($list in $web.Lists)
   {
      # examine if BaseType of list is a Document Library and if 

Open in new window

1
For some time, our SharePoint Site had been suffering from performance issues. The users of the site were always quick to point out any performance issues, and it finally came to a head.

I had tried all types of things from app pools ( "Recycling" page ), registry hacks, adding CLR's to the sharepoint server, modifying the local host file, adding additional RAM, adding web gardens, re-indexing the SQL tables, troubleshooting SQL, Ensure there is no Disk or Bandwidth issues between the DB and SharePoint. While all good things to do in principle, still no joy.

Then, onto further tests and checks for network speed, re-schedule crawling jobs to run outside of regular business hours, enabled object caching , ensured compression is enabled too!

Actually, compression is a good tip... For lower bandwidth users SharePoint sends a large amount of CSS information to users that compresses down to 1/10th it's size if compression is enabled, ensure internal DNS is working correctly.

TechNet has some good best practices here. It is very thorough and will help you narrow down the problem.

But, nothing I did provided the performance boost we were looking for.

What I eventually found to improve slow performance in SharePoint 2007 worked for us, and continued the search. I finally came across a post about "closed web parts".  These tips were found here.
1
SharePoint Administration and the PoSH

Background – I started in SharePoint as a contractor Support Engineer for the company that created the product, which after years as a UNIX guy, left me confused and intrigued.

After I relocated to a new state, I tried getting back into the UNIX/Linux world but with such tight competition, it was difficult.

So, I ended up selling a client on a small SharePoint farm to help organize and share their massive collection of stock photographs, while giving them the ability to assign metadata and sort by company and job number.  

This basically was the first time I really got into PowerShell with SharePoint since it required a set of scripts for automating site provisioning…. So lets start from the beginning….

PoSH = PowerShell.  I will repeatedly use this interchangeably

Variables:

These are simply an object that contains something.  Variables can be identified by a preceding $, such as the “new” variable that follows:
$new

We populate variables with the = sign.  The following instantiates (creates an instance of) a SharePoint web object (called an SPWeb object in the Server Object Model vernacular):
$newSPweb = get-spweb http://url.to/my/subsite

Open in new window

You can name your variables pretty much whatever you like, though there are rules – google them if you are curious, since .Net object naming conventions are slightly out of the scope of this document.

The SharePoint Server Object Model
0
Office 365 Training for IT Pros
LVL 2
Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Sharepoint 2013 Server and Office Web Apps 2013 Server should work well together, so, what is with : 'Sorry there was a problem word cannot open..' and 'You do not have permission while opening PowerPoint App'. Well, that is what happened in one project, and thought I would share my findings.

The main purpose of this project was to make the office web apps like ‘word, powerpoint, Excel, one note’ to work with sharepoint 2013.  My test environment was working fine where I used ‘http’ to access my sharepoint and office web apps 2013.  For my test environment I followed ‘http://stevemannspath.blogspot.ca/2012/10/installing-office-web-apps-server-for.html‘.  

The day I started to use the SSL with both sharepoint 2013 and Office web apps 2013, I could no longer see my web apps work.  I had followed all the "nice" articles:
 
- http://technet.microsoft.com/en-us/library/ff431687.aspx
- http://blogs.msdn.com/b/sowmyancs/archive/2012/10/29/install-configure-amp-monitor-office-web-apps-2013-for-sp-2013.aspx
 
But, everytime I opened the web app from sharepoint 2013 (documents) I got few Errors namely:
 
- Word ran into problem, can’t open the file, try opening the file with Microsoft word.
- Sorry there was a problem, word can’t open the file.
- While opening power point.  You do not have permissions….
 
I checked the logs from office web apps server under  ‘C:\ProgramData\Microsoft\OfficeWebApps\Data\Logs\ULS’ and found many logs of …
1
Are these one of the scenarios you faced in your environment?
You don't have space in default C drive and always wanted to move Inetpub to D drive.
By mistake someone configured few webservers on C drive and couple of them on D drive, in farm environment it caused issues while deploying the code base.
One of your environment is already configured in C drive long back and now you have a policy/scripts which will only work in D drive. You want to move to D drive and make this environment similar to your production/cob environment.

If you answered yes to any one of the above, then you are reading the right article. Lets follow the below steps to move Inetpub with sharepoint websites from C drive to D drive.

Step 1: Backup the current registry and Change all the registry settings as below.

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\ContentIndex\Catalogs\Web]
"Location"="D:\\Inetpub"  

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\ContentIndex\Catalogs\Web]
"Location"="D:\\Inetpub"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ContentIndex\Catalogs\Web]
"Location"="D:\\Inetpub"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\InetStp]
"PathWWWRoot"="D:\\Inetpub\\wwwroot"

Open in new window


Step 2: Goto C:\winnt\system32\Inetsrv. Make sure IIS is stopped. Take a backup of metabase.xml under Inetsrv.  Do find/replace from C:\Inetpub to D:\Inetpub for all references.

Now copy C:\inetpub directory to D drive and give the same permission for the directory similar to C:\inetpub.

Step 3: Login to Server which contains sharepoint databases. Run the below query against sharepoint configuration database. This will give all the webapplications which are created in C drive.

select * from objects where properties like '%C:\inetpub\wwwroot\wss\virtualdirectories\%'

Open in new window


Now we need to update all these references to D drive as we are moving from C drive.

Step 4: We need to run the below powershell script to update the configuration database.

Open in new window

2
 
LVL 15

Administrative Comment

by:Eric AKA Netminder
Comment Utility
pramodsk40,

Congratulations; your article has now been published.

ericpete
Page Editor
0
Getting the private properties of a user's profile was one of the problems that I faced at my work. This was a very serious problem and finally I came up with a solution that helped me getting the required objectives.

I am still looking forward if there are any other better way for this. Meanwhile I would just like to share what I have done and understood throughout.

Please suggest or comment where you think there are better ways, or any improvements.

My college and I had lot of discussion about getting those values displayed. Most of them suggested changing the visibility of the current property.  When you change the visibility of the property to all and access the user profile service through elevated privileges then it would work as desired.

But here is the catch we have the legal compliance with the client that didn't allowed us to change the visibility of the property to public from private. We tried to educate our client about the implementation and making the property visible to preserve the security compliance.

But they never agreed with our approach. So Finally, I came up with a solution which helps me getting the values as I desired.

I am putting the code here so that anyone interested can use it and may be make it more efficient.

 public void DisplayLoginDate()
        {
            SPUser AdminUser = SPContext.Current.Site.SystemAccount;
            var superToken = AdminUser.UserToken;
            HttpContext con = 

Open in new window

0
How do you keep your CDs sorted to quickly find what your looking for? In alphabetical order, based on popularity, genre or just a nice organized chaos?  A search in Sharepoint 2010 usually lists the search results after the built-in relevancy order. According to Microsoft, it's based on BM25 . If it's true or what it really means is hard to know. Since we don't want to blindly rely on Microsoft, we have tested to create our own sort order. The advantage is that we know how it is supposed to act. We have chosen to weight very high if the search keyword is in the name of the document, and then weighted our properties based on what we feel is most relevant. We're evaluating this right now but so far we are pretty pleased.

It was hard to find any good description of how to go about building custom order of relevance, but I hope the following description will still be pretty accurate:

In SharePoint 2007 there was a nice tool for weight our search results according to your properties. The tool is available here: http://searchrelevancy.codeplex.com/

In 2010, you have to fix this yourself. What you do is creating an XML with instructions on how the search should be weighted. With the help of the XML you then create a custom ranking model that is added to Sharepoint as possible choices. One can then choose whether to use any of the Sharepoint default ranking models or our own.

How do you do that? Well, here is a template on how the xml should look like. It looks like …
0
 
LVL 15

Administrative Comment

by:Eric AKA Netminder
Comment Utility
Congratulations!

Your article has been published. Thanks again for your submission.

ericpete
Page Editor
0
 
LVL 6

Author Comment

by:einarbrown
Comment Utility
Thanks!
0
In a Microsoft Windows IIS environment that is load balanced, the external load balancing hardware needs to know which servers, in the pool of servers, are available to send http traffic to for a particular website.

The rule, shown below, is a built in rule that requires each IIS Website on each IIS Web Server to have a http://healthcheck host header.

The load balancer will check each website using the http://healthcheck host header and look for an alive.html web page. Upon being able to access that alive.html web page, the load balancer will continue routing traffic to that particular website on that particular web server for another 60 seconds.

Using this built in rule administrators only have to add a healthcheck host header to each IIS Website.

This built in rule eliminates any need for administrators to create a separate and distinct set of rules for each IIS Website  on each Server using the websites own distinct name.

http_alove lb monitor
Now, enters SharePoint 2010 and how it is incompatible with this rule.

For the sake of an easy example, let us declare that we have three Windows 2008 R2 Servers that are running SharePoint 2010 Standard Server.

We will call them SPServer1, SPServer2, SPServer3, and they are configured as follows.
SPServer1 runs the Central Administration Console, and contains all SharePoint Websites. But end users never Access the SharePoint Websites here.
SPServer2 contains all SharePoint Websites
0
My developers created a sandbox code and uploaded it to a site collections under  site Actions--Site settings--Galleries--Solutions  for which the url is "/_catalogs/solutions/Forms/AllItems.aspx".

Once uploaded, they were trying to "Activate" the solution by highlighting the solution and then clicking "Activate" on the ribbon but they were getting below error message.


Error
The site collection containing this sandboxed solution has exceeded its daily resource usage quota.

Troubleshoot issues with Microsoft SharePoint Foundation.

Correlation ID: 1364ec53-0c27-426a-b298-164267001df7

Date and Time: 7/31/2012 12:58:38 PM

Sandbox Error

In order to troubleshoot and fix the problem, below are the steps which was tried by me on the sharepoint environment:

RESOLUTION:

I Checked the site quota showing for sandbox solution at site Actions--Site settings--Galleries--Solutions, it was showing the message as:

Your resource quota is 0 server resources. Solutions can consume resources and may be temporarily disabled if your resource usage exceeds your quota.

Sandbox storage Resource Allocation1

I uploaded the same solution on a test site, newly created in SP2010 and tried to activate it but got the same error


I checked the site resource quota on the server and found following information:
Limit maximum usage per day to:   0 points
Send warning e-mail when usage per day reaches:  0 points

I checked the settings for other sites in the farm but they all has same settings

0
We had a requirement to extract data from a SharePoint 2010 Customer List into a CSV file and then place the CSV file into a directory on the network so that the file could be consumed by an AS400 system. I will share in Part 1 how to Extract the Data and save it in a csv file.  In Part2, I will explain how to schedule it on a periodic basis.  

After some research I found Roi Kolbinger's blog "I Will Share my Point: Export SharePoint 2010 List to Excel with PowerShell.  The problem with this is that it will only extract the Title field.  I was able to create a PowerShell script to extract the data using Roi's script as the base for my script and with a little help from a developer, named Miguel Wood,  who told me "Yes.  The .Items will only export the Title column.  To export the list, try creating and using a PSObject."  
Now that we have some background information, let’s create a SharePoint Management Shell script to extract the data from a SharePoint 2010 List and into a csv file.

1.  Open notepad and paste the following code customizing it for your environment.
$MyWeb = Get-SPWeb "http://sitename"
$MyList = $MyWeb.Lists["ListName"]
$exportlist = @()
$Mylist.Items | foreach {
$obj = New-Object PSObject -Property @{
            “Column1” = $_["Column Name in SharePoint"]
           "Column2" = $_["Column Name in SharePoint"]                  
}
$exportlist += $obj
$exportlist | Export-Csv -path 'C:\FilePath\Filename.csv'
}
*Notes:   Http://sitename is the url to the…
4
 

Expert Comment

by:JamesHeathcote1981
Comment Utility
Hi Miguel

Thank you for your article, I will be attempting shortly.

I wondered if the following was also possible as we need to export our job data into a csv file for our accounting software which is Soloman.

We would need to filter items which have a tick box placed next to ready for invoice in the list.

Further to that, we need a column which is called invoiced which gets selected once the export has run so that duplicate entries don't get sent to the csv file.

Is this possible?
0
 
LVL 4

Author Comment

by:Eldrick Vance
Comment Utility
Hello James. Thanks for taking time to read my article.  Unfortunately I do not know how to make the script do what you need.  I will do some research and see if I can assist.  

Thanks,
Eldrick
0

The vision:

A MegaMenu for a SharePoint portal home page

The mission:

Make it easy to maintain. Allow rich content and sub headers as well as standard links. Factor in frequent changes without involving developers or a lengthy Dev/Test/Prod release cycle. The personal assistant of the marketing boss should be able to make changes on the fly. Instantaneous. Without any knowledge of HTML or CSS, so editing code is out. If it’s more complicated than filling in a time sheet, it won’t fly. And do all that with just the browser interface and SharePoint Designer. No Visual Studio, no custom code.

What’s a MegaMenu, anyway?
There are quite a few sites out there describing how to create impressive MegaMenus if you Bingle a bit. Rave reviews of the concept from Jacob Nielsen. Flashy sites from developers strutting their stuff. JavaScript, jQuery – the choice is yours. Most of them even work.

None of those take into account a SharePoint background, though. The MegaMenu content is always somehow “there already”, nicely configured in a nested construct of UL and LI tags, with hard-coded <A href> tags and titles. Not something the Marketing Assistant will want to get his head around if he wants to add a few items and a flashy “Hot and new” icon to a new menu entry.

So, to achieve the vision and make the mission possible, we need to come up with some practicable steps.

Here’s the plan:

Create a SharePoint list that stores all the items to feature in the MegaMenu
4
 
LVL 50

Author Comment

by:Ingeborg Hawighorst (Microsoft MVP / EE MVE)
Comment Utility
Köbes? Eine Runde für Tolomirs Tisch!
0
 
LVL 50

Author Comment

by:Ingeborg Hawighorst (Microsoft MVP / EE MVE)
Comment Utility
As is the way with the internet, sites get created, sites get abandoned. Links die.

The link in my above article to the demo of the MegaMenu has died.

Fear not. The Wayback machine comes to the rescue. Here are the links to the content that does not work anymore from the links above.

MegaMenu Demo

Background on the MegaMenu CSS and HTML structure

cheers, teylyn
0
SharePoint Designer 2010 has tools and commands to do everything that can be done with web parts in the browser, and then some – except uploading a web part straight into a page that is edited in SPD. So, can it be done?

Scenario

For a recent project I created a Content Query Web Part (CQWP). To fine-tune the data presentation I used customised XSL templates. Good practice suggests that these templates should not be stored in the default ItemStyle.xsl and ContentQueryMain.xsl, but in separate files. I did that and then exported the web part and edited the .webpart file to link to the custom XSL files. Then I uploaded the .webpart file to a web part page via the browser interface for testing. All good so far.

As a next step I wanted to integrate this customised web part into a Page Layout, so that new pages created with that layout would always include the customised CQWP. I did not want to use a web part page, for the following reasons:

Users with edit rights would be able to accidentally delete the web part from the page
I wanted the ability to quickly create new pages with the same layout and CQWP, without having to manually upload it into every new page
I did not want to store custom scripts calling CSS and jQuery functions in a Content Editor Web Part, but integrate them in the page header instead.

So, off we go: fire up SharePoint Designer 2010. Create a new Page Layout, create a structure with …
4
 
LVL 50

Author Comment

by:Ingeborg Hawighorst (Microsoft MVP / EE MVE)
Comment Utility
Thanks, younghv.
0
 

Expert Comment

by:Aymanit
Comment Utility
good , and Thanks
0
Want to be a Web Developer? Get Certified Today!
LVL 9
Want to be a Web Developer? Get Certified Today!

Enroll in the Certified Web Development Professional course package to learn HTML, Javascript, and PHP. Build a solid foundation to work toward your dream job!

Summary

In SharePoint 2010 it is easy to create custom color themes to jazz up a site. Theme colors can also be created in PowerPoint 2010 with a few clicks. But how do the chosen colors actually look in the SharePoint site? The attached PowerPoint has a preview of all the main elements of a SharePoint 2010 site with the selected color theme.

Detail

Using Office Themes for SharePoint 2010 sites is easy, but can be time consuming. You need to create new theme colors in PowerPoint, save the file as an Office Theme with the .thmx extension, upload that theme to your SharePoint site collection gallery, and select it in the site via Site Settings > Site Theme.

The Site Theme page has a preview button where the site landing page is then displayed in the new theme colors, but there are a few drawbacks:

chances are that this page does not show all the site elements that are affected by the theme changes
you cannot click through to another page of the site to check the new colors there
the preview is slow to generate
some site elements, for example the list form backgrounds, use shades of the main accent colors, and you could end up with a lot of trial and error time until you finally arrive at the desired color effects for all site elements
the preview is buggy (it often throws an error in my environment and also often just does not display the correct colors)

3
Pimping Sharepoint 2007 without Server-Side Code

Part 1

One of my biggest frustrations with Sharepoint 2007 in the corporate world is that while good-intentioned managers lock down the more interesting capabilities of Sharepoint programming in the name of sustainable code, they often kill innovation in the process.  Over the last several years, I have had the opportunity to find ways around this strict no-code policy to achieve a user experience that is reasonable while getting all the benefits of Sharepoint 2007.

In this series, I will show you how I have leveraged the existing infrastructure of Sharepoint along with the out-of-the-box  Content Editor Web Part and jquery to give Sharepoint a much nicer look and feel, users more natural access to the data, and ultimately design freedom within the walls of a Sharepoint installation.

I will be making a lot of assumptions about the reader’s experience with Sharepoint and jquery.  You should be able to make and manage lists, created libraries, and all the other “normal” Sharepoint administrative tasks that occur through the interface.  You should also have a pretty strong working knowledge of the jquery core.  If neither of those are in your wheelhouse, this article might not be for you.

Getting Started
You must have Sharepoint 2007 installed and have Full Control on a site collection.  If neither of these is true, stop reading now.  The rest of this article won’t matter to you.  

We’re going to …
6
 
LVL 51

Administrative Comment

by:Mark Wills
Comment Utility
No worries.

I can see your question : http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/MS-SharePoint/Q_27275890.html

Hope you also have a great weekend...
0
 
LVL 16

Author Comment

by:Steve Krile
Comment Utility
Was just reading through this article a few weeks ago and it bothered me how aged it had become. I've learned a ton about this approach and am now using Sharepoint 365. Also, writing articles is really time-consuming so I'm switching to an episodic video format. You can check it out here.
0
Microsoft SharePoint Foundation 2010 and Microsoft SharePoint Server 2010 do not offer the option to configure the location of the SharePoint diagnostic trace log files during installation.  This can, however, be configured through Central Administration or through a simple PowerShell command after installation.  

With the default SharePoint configuration, the SharePoint diagnostic trace logs are stored in the 14 HIVE on the local hard drive of each SharePoint server in a SharePoint farm (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS).  If you are not going to store the diagnostic trace log files on a different drive, it is recommended to leave the default location.  However, you may wish to store them on a different local hard drive for storage space or other considerations.  

When deciding where to place the SharePoint diagnostic trace log files, it is important to remember that they must be stored on a local hard drive.  SharePoint does not support storing the diagnostic trace log files on network storage.  Also note that the specified directory location must exist in the same place on all SharePoint servers in the farm.

To configure the SharePoint diagnostic trace log location through Central Administration:

1

Open Central Administration for the SharePoint farm you wish to change the storage location for

2

In Central Administration, browse to Monitoring and then to Configure Diagnostic Logging under Reporting

3

0
 
LVL 1

Expert Comment

by:nsitsupport
Comment Utility
Hi,

I found you can change the INDEX LOCATION during installation.
SharePoint Index File Location During Install
However, the DIAGNOSTIC LOGGING.....I haven't found. This seem to be done after only.

Regards

Ian
0
For SharePoint sites, particularly public-facing ones, there are times when adding JavaScript, Meta Tags, CSS Styles or other content to the page <head> section is more practical than modifying master pages.  For instance, you could add the jQuery library to the head of every page.  If adding tags to the page <head> section is the only customization being made side-wide, doing so programmatically instead of modifying and un-ghosting the default master pages will increase the performance of the site.  (Un-ghosting a page means that SharePoint is no longer grabbing the master page from the local hard drive and is instead grabbing it from the Content Database.  This adds another call to the database that isn't necessary unless you have a fully branded master page).

To demonstrate how to accomplish this programmatically using the AdditionalPageHead Content Place Holder, we will make a SharePoint solution in Visual Studio 2010 that adds a custom JavaScript file and a custom CSS file.  This solution could be further extended to dynamically add different content based on configurable settings, however for this demonstration we will keep it simple.

1

Open Visual Studio 2010 on a computer running SharePoint 2010.

2

Select File > New Project.

3

Make sure .NET Framework 3.5 is selected.

4

Under Visual C# > SharePoint >2010, select Empty SharePoint Project.

5

Provide a name and location for the solution, for the demonstration we are using CustomPageHead.

6

0
There is one common problem that all we SharePoint developers share: custom solution deployment.

This topic can't be covered fully in this short article, so all I want to do in this one is to review it from a development-to-operations perspective.

This is the problem statement:
You have your SharePoint solution developed and ready to be delivered to the production environment (I'm intentionally skipping all the QA steps here). All you have is one or more WSPs (as you may know, WSP is a CAB-based package containing solution files and XML manifest with instructions to SharePoint how to deploy solution files) and some features of different scope inside. But in my experience, this is not enough to get your solution deployed even on a test environment.


Most of us, old-school SharePoint developers, used to write STSADM-based batch files to automatically deploy, install and activate; but this approach is not very convenient: no logging, no UI, and too much preconditions to have it successfully completed.

Almost the same experience is regarding PowerShell. Please note that I'm referring only deployment automation aspects of using PowerShell. No doubt that PowerShell is a great tool for a lot of IT tasks, but it gives almost the same user experience when used for SP deployment automation.

The next approach is usually to write a proprietary tool to take care of deployment.  If used for many different solutions, such a tool could become …
0
I used to be SharePoint evangelist in our company, so my Outlook always full of questions about how to do this, or where I can find that. One day I found such an email with the following question: "how to attach 3-State workflow (one of the workflows available "Out-of-the-Box") to the Wiki Library".

Looks like a good idea for business users, especially if they need to control wiki content contribution. I have to mention that their department use small isolated SharePoint farm based on MOSS 2007 Standard.

As usual, I sent her simple step-by-step manual from the MS TechNet (or someone’s blog article, I don't remember the exact source).

She has successfully attached workflow to the library, assigned column with state values, and managed to start the workflow without any problems. Although all the workflow instances she started have never been finished successfully. That became interesting for me so I visited her servers myself. After some diving into logs I found the following exception:

System.ArgumentException: Value does not fall within the expected range.     
at Microsoft.SharePoint.SPFieldCollection.GetField(String strName, Boolean bThrowException)     
at Microsoft.SharePoint.SPListItem.GetValue(String strName, Boolean bThrowException)     
at Microsoft.SharePoint.SPListItem.GetValue(String strName)     
at Microsoft.SharePoint.SPListItem.get_Title()     
at Microsoft.SharePoint.Workflow.Application.IssueTracking.OnWorkflowActivated(Object sender, 

Open in new window

2

Microsoft SharePoint

37K

Solutions

19K

Contributors

Microsoft Sharepoint is a software platform and family of software products used for collaboration and web publishing combined. These capabilities include developing web sites, portals, intranets, content management systems, search engines, wikis, blogs, and other tools for business intelligence and collaboration. SharePoint has a Microsoft Office-like interface, and it is closely integrated with the Office suite.