<atom:id>tag:blogger.com,1999:blog-896451408200852359</atom:id>
<lastBuildDate>Fri, 30 Aug 2024 02:53:21 +0000</lastBuildDate>
<category>MOSS</category>
<category>error resolution</category>
<category>Tip</category>
<category>WSS</category>
<category>Reporting Services</category>
<category>Virtual Machines</category>
<category>Dot Net Framework 3.0</category>
<category>SharePoint List</category>
<category>SharePoint designer</category>
<category>backup and recovery</category>
<category>stsadm</category>
<category>workaround</category>
<category>Document Libraries</category>
<category>Excel Services</category>
<category>Installing MOSS</category>
<category>Kerberos</category>
<category>SQL Server Management Studio</category>
<category>Task Lists</category>
<category>workflow</category>
<category>Daylight Savings time</category>
<category>Email Enabled Document Libraries</category>
<category>Email reminders</category>
<category>How To</category>
<category>IIS</category>
<category>Installation</category>
<category>JavaScript</category>
<category>MOSS Service Pack 1</category>
<category>Microsoft Office 2007</category>
<category>SPS 2003</category>
<category>SQL 2000</category>
<category>SQL Log Shipping</category>
<category>SQL Server</category>
<category>SSO</category>
<category>SSRS</category>
<category>SharePoint 2010</category>
<category>SharePoint 2013</category>
<category>SharePoint Dataview webpart</category>
<category>Single SIgn On</category>
<category>Troubleshooting</category>
<category>Uninstall SPS 2003</category>
<category>Windows Support Tools</category>
<category>XML</category>
<category>XPATH</category>
<category>XSLT</category>
<category>asp.net</category>
<category>batch scripting</category>
<category>hotfix</category>
<category>jQuery</category>
<title>SharePoint Fortress</title>
<description/>
<link>http://sharefort.blogspot.com/</link>
<managingEditor>noreply@blogger.com (Faisal Akhtar)</managingEditor>
<generator>Blogger</generator>
<openSearch:totalResults>38</openSearch:totalResults>
<openSearch:startIndex>1</openSearch:startIndex>
<openSearch:itemsPerPage>25</openSearch:itemsPerPage>
<item>
<guid isPermaLink="false">tag:blogger.com,1999:blog-896451408200852359.post-6541386786222941974</guid>
<pubDate>Mon, 04 Aug 2014 16:22:00 +0000</pubDate>
<atom:updated>2014-08-05T11:56:08.362-07:00</atom:updated>
<category domain="http://www.blogger.com/atom/ns#">How To</category>
<category domain="http://www.blogger.com/atom/ns#">JavaScript</category>
<category domain="http://www.blogger.com/atom/ns#">jQuery</category>
<category domain="http://www.blogger.com/atom/ns#">SharePoint 2010</category>
<category domain="http://www.blogger.com/atom/ns#">SharePoint List</category>
<category domain="http://www.blogger.com/atom/ns#">Tip</category>
<title>How to Calculate Date Difference Between Today and a Date Column in SharePoint - Javascript solution using content editor web part</title>
<description><h3>
Requirement</h3>
<br />
I have had this request come up repeatedly in the past but I never really got around to it. The typical customer request that comes to me is as follows<br />
<br />
"I have a date column in my list that I would like to compare to todays date and display the difference in days in the view"<br />
<br />
Usually the requirement is for a task list in which the column should indicate how many days an item is overdue or a review date in which the difference indicates how long ago the review was conducted.<br />
<br />
<h3>
The Solution</h3>
<br />
My restrictions in developing this quick code snippet was that I was not allowed to deploy a solution to the farm nor could I touch the page with SharePoint Designer (bummer I know). So I decided to put together a script that I can inject in to a content editor web part. and use that code to calculate and display the date difference.<br />
<br />
Here is how you can use the code to calculate date difference on your list views<br />
<br />
<ol>
<li>Create a view of the list / library view while making sure that the column that you would like to compare to today is displayed in that view.</li>
<li>Create a calculated column in the library and set it to any calculated value you like. We will remove that value from the view using JavaScript code.</li>
<li>Add the column you created in step 2 to the view you created in step 1 and note the position of the column (in my example I am calling the column "CalculatedDateDiff" as can be seen in the screenshot)<br /><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjbP81jtAJnrrANdmnfzU0VITyhUpviOxEGXBEofXmCooOdn2ZevrJZS2bwopCUOuGnbjnhnUIDk7PiIeBIXAsOgQp52dHl8X1SuVQ19yCYiVni-2H-J-9dw2s2XeJ8w7ZCNrkuaCGxpqVW/s1600/BloggerDateDifference.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjbP81jtAJnrrANdmnfzU0VITyhUpviOxEGXBEofXmCooOdn2ZevrJZS2bwopCUOuGnbjnhnUIDk7PiIeBIXAsOgQp52dHl8X1SuVQ19yCYiVni-2H-J-9dw2s2XeJ8w7ZCNrkuaCGxpqVW/s1600/BloggerDateDifference.png" height="112" width="640" /></a></li>
<li> Edit the view page using the site actions menu</li>
<li>Add a content editor web part to the page</li>
<li>Edit the HTML source of the content editor web part and paste the following code in there<br /><br /><br />
<!-- HTML generated using hilite.me --><div style="background: rgb(255, 255, 255); border: solid gray; overflow: auto; padding: 0.2em 0.6em; width: auto;">
<table><tbody>
<tr><td><pre style="line-height: 125%; margin: 0px;"> 1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115</pre>
</td><td><pre style="line-height: 125%; margin: 0px;"><span style="color: #333333;"><</span>script language<span style="color: #333333;">=</span><span style="background-color: #fff0f0;">"javascript"</span> src<span style="color: #333333;">=</span><span style="background-color: #fff0f0;">"http://ajax.googleapis.com/ajax/libs/jquery/1.6.4/jquery.min.js"</span> type<span style="color: #333333;">=</span><span style="background-color: #fff0f0;">"text/javascript"</span><span style="color: #333333;">><</span><span style="background-color: #ffaaaa; color: red;">/script><script language="javascript" type="text/javascript"></span>
$(<span style="color: #007020;">document</span>).ready(<span style="color: #008800; font-weight: bold;">function</span> () {
<span style="color: #008800; font-weight: bold;">function</span> datedifference(date1,date2 ) {
<span style="color: #888888;">//Get 1 day in milliseconds</span>
<span style="color: #008800; font-weight: bold;">var</span> one_day<span style="color: #333333;">=</span><span style="color: #0000dd; font-weight: bold;">1000</span><span style="color: #333333;">*</span><span style="color: #0000dd; font-weight: bold;">60</span><span style="color: #333333;">*</span><span style="color: #0000dd; font-weight: bold;">60</span><span style="color: #333333;">*</span><span style="color: #0000dd; font-weight: bold;">24</span>;
<span style="color: #888888;">// Convert both dates to milliseconds</span>
<span style="color: #008800; font-weight: bold;">var</span> date1_ms <span style="color: #333333;">=</span> date1.getTime();
<span style="color: #008800; font-weight: bold;">var</span> date2_ms <span style="color: #333333;">=</span> date2.getTime();
<span style="color: #888888;">// Calculate the difference in milliseconds</span>
<span style="color: #008800; font-weight: bold;">var</span> difference_ms <span style="color: #333333;">=</span> date2_ms <span style="color: #333333;">-</span> date1_ms;
<span style="color: #888888;">// Convert back to days and return</span>
<span style="color: #008800; font-weight: bold;">return</span> <span style="color: #007020;">Math</span>.round(difference_ms<span style="color: #333333;">/</span>one_day);
};
<span style="color: #888888;">// the table and table rows containing the data </span>
<span style="color: #008800; font-weight: bold;">var</span> myListTable <span style="color: #333333;">=</span> $(<span style="background-color: #fff0f0;">".ms-listviewtable"</span>).find( <span style="background-color: #fff0f0;">".ms-itmhover"</span> );
<span style="color: #888888;">// number of rows in the list view</span>
<span style="color: #008800; font-weight: bold;">var</span> myListTableLength <span style="color: #333333;">=</span> mylisttable.length;
<span style="color: #888888;">// set current date</span>
<span style="color: #008800; font-weight: bold;">var</span> currentDate <span style="color: #333333;">=</span> <span style="color: #008800; font-weight: bold;">new</span> <span style="color: #007020;">Date</span>();
<span style="color: #888888;">// number of items in the header row containing column names</span>
<span style="color: #008800; font-weight: bold;">var</span> viewHeadeRowLength <span style="color: #333333;">=</span> $(<span style="background-color: #fff0f0;">".ms-viewheadertr"</span>).find(<span style="background-color: #fff0f0;">"th"</span>).length;
<span style="color: #888888;">// alert(viewHeadeRowLength);</span>
<span style="color: #888888;">// most important. This is column name that dtermines what column date difference will calculated from</span>
<span style="color: #008800; font-weight: bold;">var</span> columNname <span style="color: #333333;">=</span> <span style="background-color: #fff0f0;">"Date Reviewed"</span>;
<span style="color: #888888;">// declare but do not set the value</span>
<span style="color: #008800; font-weight: bold;">var</span> dataColumnPos;
<span style="color: #008800; font-weight: bold;">for</span> (i <span style="color: #333333;">=</span> <span style="color: #0000dd; font-weight: bold;">0</span>; i <span style="color: #333333;"><</span> viewHeadeRowLength; i<span style="color: #333333;">++</span>) {
<span style="color: #888888;">// for each item in the table header find the inner html and check if it contains the column name</span>
<span style="color: #008800; font-weight: bold;">var</span> myInnerHTML <span style="color: #333333;">=</span> $(<span style="background-color: #fff0f0;">".ms-viewheadertr"</span>).find(<span style="background-color: #fff0f0;">"th"</span>)[i].innerHTML
<span style="color: #008800; font-weight: bold;">if</span> (myInnerHTML.indexOf(columnName) <span style="color: #333333;">></span> <span style="color: #333333;">-</span><span style="color: #0000dd; font-weight: bold;">1</span>) {
dataColumnPos <span style="color: #333333;">=</span> i;
}
<span style="color: #888888;">// alert(dataColumnPos);</span>
};
<span style="color: #888888;">// Important which column the date difference result will be displayed in</span>
<span style="color: #008800; font-weight: bold;">var</span> resultColumnPos <span style="color: #333333;">=</span> <span style="color: #0000dd; font-weight: bold;">5</span>;
<span style="color: #888888;">// alert(myListTableLength);</span>
<span style="color: #008800; font-weight: bold;">for</span> (i <span style="color: #333333;">=</span> <span style="color: #0000dd; font-weight: bold;">0</span>; i <span style="color: #333333;"><</span> myListTableLength; i<span style="color: #333333;">++</span>) {
<span style="color: #888888;">// select the current table row</span>
<span style="color: #008800; font-weight: bold;">var</span> myListtTR<span style="color: #333333;">=</span> myListTable[i];
<span style="color: #888888;">// var mylisttrinnerhtml = mylisttr.innerHTML;</span>
<span style="color: #888888;">// select all cell in the current row</span>
<span style="color: #008800; font-weight: bold;">var</span> myListTD <span style="color: #333333;">=</span> $(myListTR).find( <span style="background-color: #fff0f0;">"td"</span> );
<span style="color: #888888;">// find the text of the cell that contains the data column you would like to compare</span>
<span style="color: #008800; font-weight: bold;">var</span> myText <span style="color: #333333;">=</span> myListTD[dataColumnPos].innerText;
<span style="color: #888888;">// find the position of the space</span>
<span style="color: #008800; font-weight: bold;">var</span> spacePos <span style="color: #333333;">=</span> mytext.search(<span style="background-color: #fff0f0;">" "</span>);
<span style="color: #888888;">// select the date text before the space position</span>
<span style="color: #008800; font-weight: bold;">var</span> mydate <span style="color: #333333;">=</span> myText.substr(<span style="color: #0000dd; font-weight: bold;">0</span>, spacePos);
<span style="color: #888888;">// find the position of the first slash </span>
<span style="color: #008800; font-weight: bold;">var</span> firstSlashPosition <span style="color: #333333;">=</span> mydate.search(<span style="background-color: #fff0f0;">"/"</span>);
<span style="color: #888888;">// month is the text before the first slash</span>
<span style="color: #008800; font-weight: bold;">var</span> myMonth <span style="color: #333333;">=</span> myDate.substr(<span style="color: #0000dd; font-weight: bold;">0</span>, firstSlashPosition)<span style="color: #333333;">-</span><span style="color: #0000dd; font-weight: bold;">1</span>;
<span style="color: #888888;">// find the positon of the second slash</span>
<span style="color: #008800; font-weight: bold;">var</span> secondSlashPos <span style="color: #333333;">=</span> myText.substr(firstSlashPosition,spacePos).substr(<span style="color: #0000dd; font-weight: bold;">1</span>,spacePos).search(<span style="background-color: #fff0f0;">"/"</span>);
<span style="color: #888888;">// day is the text between the firs slash and second slash</span>
<span style="color: #008800; font-weight: bold;">var</span> myDay <span style="color: #333333;">=</span> myText.substr(firstSlashPosition,spacePos).substr(<span style="color: #0000dd; font-weight: bold;">1</span>,spacePos).substr(<span style="color: #0000dd; font-weight: bold;">0</span>,secondSlashPos);
<span style="color: #888888;">// year is the text between the second slash and the space</span>
<span style="color: #008800; font-weight: bold;">var</span> myYear <span style="color: #333333;">=</span> myText.substr(firstSlashPosition,spacePos).substr(<span style="color: #0000dd; font-weight: bold;">1</span>,spacePos).substr(secondSlashPos<span style="color: #333333;">+</span><span style="color: #0000dd; font-weight: bold;">1</span>,<span style="color: #0000dd; font-weight: bold;">4</span>);
<span style="color: #888888;">// set time in the middle of the date hence all the 12s</span>
<span style="color: #008800; font-weight: bold;">var</span> compDate <span style="color: #333333;">=</span> <span style="color: #008800; font-weight: bold;">new</span> <span style="color: #007020;">Date</span>(myYear, myMonth, myDay, <span style="color: #0000dd; font-weight: bold;">12</span>,<span style="color: #0000dd; font-weight: bold;">12</span>,<span style="color: #0000dd; font-weight: bold;">12</span>,<span style="color: #0000dd; font-weight: bold;">12</span>);
<span style="color: #888888;">// use date differene function to calculate number of days between the returned date and today</span>
<span style="color: #008800; font-weight: bold;">var</span> daysDiff <span style="color: #333333;">=</span> dateDifference(compDate,currentDate);
<span style="color: #888888;">// set the inner HTMl of the result column to the result returned from the function</span>
myListTD[resultColumnPos].innerHTML <span style="color: #333333;">=</span> daysDiff;
<span style="color: #888888;">// alert(daysDiff);</span>
<span style="color: #888888;">// alert("Year " + myyear + " month "+ myMonth + " day " + myDay + " myDate " + myDate );</span>
}
<span style="color: #888888;">// alert(mylisttablelength);</span>
<span style="color: #888888;">// alert(mylisttable);</span>
<span style="color: #888888;">// alert(JSON.stringify(mylisttable));</span>
<span style="color: #888888;">// console.log(mylisttable);</span>
});
<span style="color: #333333;"><</span><span style="background-color: #ffaaaa; color: red;">/script></span>
</pre>
</td></tr>
</tbody></table>
</div>
<br />
<br />
</li>
<li>Modify the code snippet to fit your need. The two important lines that are commented with the IMPORTANT comments are the name of the column you would like to calculate the difference from today and the column position where you would like to display the result. The result column position will be the position you noted in step 3.</li>
</ol>
<h3>
Limitations</h3>
<ol>
<li>I have not tested this snippet with date only columns</li>
<li>This solution works only on a page where the code is injected so it is limited to a page / list view</li>
<li>You cannot export that calculated difference to a spreadsheet because this calculation occurs on the front end</li>
<li>I may be cleaner to inject HTML to the page instead of creating a calculated column and then removing the value of that column</li>
<li>I only tested this code with a date and time column and did not test it with a date only column</li>
</ol>
<h3>
<a href="https://www.blogger.com/null" name="codex"></a>Code Example Disclaimer</h3>
I grant you a nonexclusive copyright license to use all programming code examples from which you can generate similar function tailored to your own specific needs.<br />
<br />
All sample code is provided for illustrative purposes only. These examples have not been thoroughly tested under all conditions. I therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.<br />
<br />
All programs contained herein are provided to you "AS IS" without any warranties of any kind. The implied warranties of non-infringement, merchantability and fitness for a particular purpose are expressly disclaimed.<br />
<br />
<br /></description>
<link>http://sharefort.blogspot.com/2014/08/how-to-calculate-date-difference.html</link>
<author>noreply@blogger.com (Faisal Akhtar)</author>
<media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjbP81jtAJnrrANdmnfzU0VITyhUpviOxEGXBEofXmCooOdn2ZevrJZS2bwopCUOuGnbjnhnUIDk7PiIeBIXAsOgQp52dHl8X1SuVQ19yCYiVni-2H-J-9dw2s2XeJ8w7ZCNrkuaCGxpqVW/s72-c/BloggerDateDifference.png" height="72" width="72"/>
<thr:total>0</thr:total>
...</item>
<item>
<guid isPermaLink="false">tag:blogger.com,1999:blog-896451408200852359.post-267823910126629419</guid>
<pubDate>Thu, 09 May 2013 18:04:00 +0000</pubDate>
<atom:updated>2013-05-09T11:05:22.824-07:00</atom:updated>
<category domain="http://www.blogger.com/atom/ns#">Installation</category>
<category domain="http://www.blogger.com/atom/ns#">SharePoint 2013</category>
<category domain="http://www.blogger.com/atom/ns#">Troubleshooting</category>
<title>Installing and configuring SharePoint 2013 on Windows Server 2013 Development Environment</title>
<description>After surfing the net recently and finding a number of guides on how to install SharePoint 2013 on a VM, I decided that another detailed guide will likely be pointless. However, I have found that the blog posts that address specific errors encountered have been most helpful for me in the past. Therefore, I am only writing a quick guide with all the errors / bumps I encountered.<br />
<br />
Obviously, the first thing you will need is the software and hardware necessary for the development environment. I am running VMware for Mac on my MacBook pro. You can find <a href="http://www.vmware.com/products/fusion/overview.html">VMWare for Mac on the VMWare web site.</a><br />
<br />
I don't want to go into the how to of creating a Mac hosted Windows VM but for more information, you can <a href="http://partnerweb.vmware.com/GOSIG/Windows_Server_2012.html">view the installation instruction from VMware</a><br />
<br />
<br />
When I created the Virtual Machine for Windows Server 2012, I ran in to the problem of "No Images are available". <a href="http://jontriphan.com/windows-8-error-there-are-no-images-available-on-wmware/">Here is the resolution</a>. It was simply a matter of disconnecting the floppy from the VMWare virtual machine settings.. <br />
<br />
The Windows Server 2012 installation proceeded without any bumps but when attempting to install SQL server 2012, an error was thrown<br />
<br />
<em>Error while enabling Windows feature : NetFx3, Error Code : –2146498298 , Please try enabling Windows Feature : NetFx3 from Windows management tools and then run setup again.</em><br />
<br />
<br />
<a href="http://garvis.ca/2013/01/04/installing-netfx3-on-windows-server-2012/">I found this excellent blog post on how to resolve this error</a> and afterwards, the SQL Server 2012 installation proceeded normally when I reinstalled.<br />
<br />
When Installing SharePoint 2013 pre requisites, an error was thrown. There was an error during installation the toll was not able to download MS SQL server 2008 R2 Sp1 native client. This was because at the time, I was not connected to the Internet. After I connected to the Internet and attempted the install again, the installation proceeded normally.<br />
<br />
After that I ran the configuration wizard which resulted in a shiny new SharePoint 2013 development environment. I am so happy. :)</description>
<link>http://sharefort.blogspot.com/2013/05/installing-and-configuring-sharepoint.html</link>
<author>noreply@blogger.com (Faisal Akhtar)</author>
<thr:total>1</thr:total>
...</item>
<item>
<guid isPermaLink="false">tag:blogger.com,1999:blog-896451408200852359.post-5397191233032893307</guid>
<pubDate>Tue, 04 Sep 2012 18:58:00 +0000</pubDate>
<atom:updated>2012-09-04T11:58:28.448-07:00</atom:updated>
<title>How to Prevent Certain Users from Reading Draft Version of some Documents in a SharePoint Document Library</title>
<description><span style="font-family: Arial, Helvetica, sans-serif;">A customer recently asked me to configure a document library in his environment. His scenario was that some users were creating certain document while other users were creating other documents. All documents existed at the root level of the library which meant that all contributors to the library were able to read draft versions of every document.</span><br />
<span style="font-family: Arial, Helvetica, sans-serif;"></span><br />
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span>
<div style="border-bottom: medium none; border-left: medium none; border-right: medium none; border-top: medium none;">
<span style="font-family: Arial, Helvetica, sans-serif;">What my client wanted was to configure the library such that only the people authorized to modify a document be able to view draft versions of that document while every other user should only be able to see the latest published major version of the document. The catch was that it needed to be done in a single library. </span></div>
<div style="border-bottom: medium none; border-left: medium none; border-right: medium none; border-top: medium none;">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div style="border-bottom: medium none; border-left: medium none; border-right: medium none; border-top: medium none;">
<span style="font-family: Arial, Helvetica, sans-serif;">I solved the problem by putting the documents in folders in the library, setting appropriate permissions on the folders, turning on major minor versioning and allowing only contributors to view minor versions of the documents. Here is how</span></div>
<div style="border-bottom: medium none; border-left: medium none; border-right: medium none; border-top: medium none;">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<ol><div class="separator" style="clear: both; text-align: center;">
</div>
<div class="separator" style="clear: both; text-align: center;">
</div>
<div style="border-bottom: medium none; border-left: medium none; border-right: medium none; border-top: medium none;">
<br /></div>
<li style="border-bottom: medium none; border-left: medium none; border-right: medium none; border-top: medium none;"><span style="font-family: 'Calibri','sans-serif'; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="font-family: Arial, Helvetica, sans-serif;">Create the necessary folders by clicking the new button and selecting “New Folder”<span style="mso-no-proof: yes;"> </span></span></span></li>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhkhyphenhyphenkTS1G7El9FNBySgXqDEdpEJ_9hgMSqxSPsS1f58_ZdkXHmOxLkPx1pSC5ZOKS8g6R5JK4ci8A_PdeWAUGpXz1TcYC9txys4zh_CiFJJYsSIe8ecYd8jIOylemfekHUXRfMHYHMt2m3/s1600/1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" hea="true" height="123" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhkhyphenhyphenkTS1G7El9FNBySgXqDEdpEJ_9hgMSqxSPsS1f58_ZdkXHmOxLkPx1pSC5ZOKS8g6R5JK4ci8A_PdeWAUGpXz1TcYC9txys4zh_CiFJJYsSIe8ecYd8jIOylemfekHUXRfMHYHMt2m3/s320/1.png" width="320" /></a></div>
<li style="border-bottom: medium none; border-left: medium none; border-right: medium none; border-top: medium none;"><span style="font-family: 'Calibri','sans-serif'; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="mso-no-proof: yes;"><span style="font-family: 'Calibri','sans-serif'; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="font-family: Arial, Helvetica, sans-serif;">Upload your documents to each folder as necessary</span></span></span></span></li>
<div class="separator" style="border-bottom: medium none; border-left: medium none; border-right: medium none; border-top: medium none; clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgwObhDS8Pdbsld4ydMvy4KRzTy2nZOktzOiIZ6UzFI7w646oBWAI8SEz4J4eEwc2Np931m5RkWMLMwxvAqFVsLP8FIrRsvejdtaZepg17O7S27NGP8VcbMA30eU_XUbp3m1DFT76D0jB6v/s1600/2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" hea="true" height="90" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgwObhDS8Pdbsld4ydMvy4KRzTy2nZOktzOiIZ6UzFI7w646oBWAI8SEz4J4eEwc2Np931m5RkWMLMwxvAqFVsLP8FIrRsvejdtaZepg17O7S27NGP8VcbMA30eU_XUbp3m1DFT76D0jB6v/s320/2.png" width="320" /></a><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjTUder09WVErugANlh65Oq0KaMEFj1nwwwK19YuS0Z9uweBt2RwEhBZPz6BtQmPzu0xEdXdsJ9HQUAmTi0QPwsRq31cQHdsiIOXRdMaangBA_4wRfcQ9mGNSg_WlpaY8snvB7foA2Q-otA/s1600/3.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" hea="true" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjTUder09WVErugANlh65Oq0KaMEFj1nwwwK19YuS0Z9uweBt2RwEhBZPz6BtQmPzu0xEdXdsJ9HQUAmTi0QPwsRq31cQHdsiIOXRdMaangBA_4wRfcQ9mGNSg_WlpaY8snvB7foA2Q-otA/s1600/3.png" /></a></div>
<div style="border-bottom: medium none; border-left: medium none; border-right: medium none; border-top: medium none;">
<br /></div>
<li style="border-bottom: medium none; border-left: medium none; border-right: medium none; border-top: medium none;"><span style="font-family: 'Calibri','sans-serif'; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="mso-no-proof: yes;"><span style="font-family: 'Calibri','sans-serif'; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="font-family: 'Calibri','sans-serif'; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="font-family: Arial, Helvetica, sans-serif;">Select the folders and break permissions inheritance for each folder from the parent library.</span></span></span></span></span></li>
<div class="separator" style="border-bottom: medium none; border-left: medium none; border-right: medium none; border-top: medium none; clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgGiEC_kxY_0owFXuJ84MPVN2Nxlf_kzEnFDZBS-I1BsULtCKMEv1PhqYxxBlE_lHkv6qzhPhjUYR383P1Z3YsFB6aVWyJFq5Dif7LpJV-nb0Zn__083as7TFsnZSWiiePuHvRNVEaDeHbc/s1600/4.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" hea="true" height="121" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgGiEC_kxY_0owFXuJ84MPVN2Nxlf_kzEnFDZBS-I1BsULtCKMEv1PhqYxxBlE_lHkv6qzhPhjUYR383P1Z3YsFB6aVWyJFq5Dif7LpJV-nb0Zn__083as7TFsnZSWiiePuHvRNVEaDeHbc/s320/4.png" width="320" /></a><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg6SkW4tIwMcp2VoFmsHZXmzN4LMquX5JCUDYoqwBa2GTpAyFa2L6K3GRcMDuJG2IvMnI0TspXA_jDeVg0ztyvXjIuTAwsfb6IysZuUYC4CTw_i4ybakErizmrpP0ljoD3DZv7Dw-w8dK6G/s1600/5.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" hea="true" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg6SkW4tIwMcp2VoFmsHZXmzN4LMquX5JCUDYoqwBa2GTpAyFa2L6K3GRcMDuJG2IvMnI0TspXA_jDeVg0ztyvXjIuTAwsfb6IysZuUYC4CTw_i4ybakErizmrpP0ljoD3DZv7Dw-w8dK6G/s1600/5.png" /></a></div>
<li style="border-bottom: medium none; border-left: medium none; border-right: medium none; border-top: medium none;"><span style="font-family: 'Calibri','sans-serif'; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="mso-no-proof: yes;"><span style="font-family: 'Calibri','sans-serif'; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="font-family: 'Calibri','sans-serif'; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="font-family: 'Calibri','sans-serif'; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="font-family: Arial, Helvetica, sans-serif;">Give only users with the authority to see the draft versions of the documents “Contribute” permissions on the folder while making sure all other users get “Read” permissions only. Repeat these steps for each folder.</span></span></span></span></span></span></li>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhbrQDJOAkM0KGD83AJ6sHhHU_nf0UwCCUz3OFYD4BDdYvKWUETihCRIVzAqBZq5XJJ4SFTJdlyOdecRejEea1UnYph9Uxp8XUmPKlWBQnCOt0MWEqkB7yhw7hGnkZBi72sSO1b1dXzr8yS/s1600/6.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" hea="true" height="70" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhbrQDJOAkM0KGD83AJ6sHhHU_nf0UwCCUz3OFYD4BDdYvKWUETihCRIVzAqBZq5XJJ4SFTJdlyOdecRejEea1UnYph9Uxp8XUmPKlWBQnCOt0MWEqkB7yhw7hGnkZBi72sSO1b1dXzr8yS/s320/6.png" width="320" /></a></div>
<div style="border-bottom: medium none; border-left: medium none; border-right: medium none; border-top: medium none;">
<br /></div>
<li style="border-bottom: medium none; border-left: medium none; border-right: medium none; border-top: medium none;"><span style="font-family: 'Calibri','sans-serif'; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="mso-no-proof: yes;"><span style="font-family: 'Calibri','sans-serif'; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="font-family: 'Calibri','sans-serif'; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="font-family: 'Calibri','sans-serif'; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="font-family: 'Calibri','sans-serif'; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="font-family: Arial, Helvetica, sans-serif;">Go to the document library settings and under general settings, select “Versioning Settings”. </span></span></span></span></span></span></span></li>
<div class="separator" style="border-bottom: medium none; border-left: medium none; border-right: medium none; border-top: medium none; clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEicDDCcE7ZdHSwQPXmVrWjR5xRMCbTb4tVAV2A51sZYJvcGXJxCjUQDWF9t4BzOcOdkKBhv114oH0FQwoRN8_CJ9xhfUyz-fHemd8-7TEMpGjSEB4Qk44_vYukRjLL7XTDIUirBieYNUJIq/s1600/7.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" hea="true" height="141" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEicDDCcE7ZdHSwQPXmVrWjR5xRMCbTb4tVAV2A51sZYJvcGXJxCjUQDWF9t4BzOcOdkKBhv114oH0FQwoRN8_CJ9xhfUyz-fHemd8-7TEMpGjSEB4Qk44_vYukRjLL7XTDIUirBieYNUJIq/s320/7.png" width="320" /></a></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg_U2Ec3m6e7YdCz1N0T96yCcBt4Oyfax4liTEfcy9KI6QX2iDsLVDkG4plrQFD7ETaeclmwNllRL5Ovct8TAc-TlFp3EoqY2lbdzpjODuaALorMyD9H4lgDA-owdA51ewgntTIzOmVPzpn/s1600/8.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" hea="true" height="252" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg_U2Ec3m6e7YdCz1N0T96yCcBt4Oyfax4liTEfcy9KI6QX2iDsLVDkG4plrQFD7ETaeclmwNllRL5Ovct8TAc-TlFp3EoqY2lbdzpjODuaALorMyD9H4lgDA-owdA51ewgntTIzOmVPzpn/s320/8.png" width="320" /></a></div>
<li style="border-bottom: medium none; border-left: medium none; border-right: medium none; border-top: medium none;"><span style="font-family: 'Calibri','sans-serif'; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="mso-no-proof: yes;"><span style="font-family: 'Calibri','sans-serif'; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="font-family: 'Calibri','sans-serif'; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="font-family: 'Calibri','sans-serif'; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="font-family: 'Calibri','sans-serif'; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="font-family: 'Calibri','sans-serif'; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="font-family: Arial, Helvetica, sans-serif;">Under versioning settings, select “Create major and minor (draft) versions” and under “Who should see draft items in this document library?” select “Only users who can edit items” and click ok.</span></span></span></span></span></span></span></span></li>
</ol>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj9mA7-IHqGqCJm3PTIc5KEj2bRTSmU5umjTFFea_Eq8nEgDvqhpKBWtgviTRyEXdFDWx6k2R74XAQUAcOtXmZlsfLmWvNJl5H_hENyc_BqY_CYUhe-cQ74X6PFM2id-pzmkCKmBDvbh3Yp/s1600/9.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" hea="true" height="216" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj9mA7-IHqGqCJm3PTIc5KEj2bRTSmU5umjTFFea_Eq8nEgDvqhpKBWtgviTRyEXdFDWx6k2R74XAQUAcOtXmZlsfLmWvNJl5H_hENyc_BqY_CYUhe-cQ74X6PFM2id-pzmkCKmBDvbh3Yp/s400/9.png" width="400" /></a></div>
<div style="border-bottom: medium none; border-left: medium none; border-right: medium none; border-top: medium none;">
<span style="font-family: 'Calibri','sans-serif'; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="mso-no-proof: yes;"><span style="font-family: 'Calibri','sans-serif'; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="font-family: 'Calibri','sans-serif'; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="font-family: 'Calibri','sans-serif'; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="font-family: 'Calibri','sans-serif'; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="font-family: 'Calibri','sans-serif'; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="font-family: Arial, Helvetica, sans-serif;">For more information, please read</span></span></span></span></span></span></span></span></div>
<div style="border-bottom: medium none; border-left: medium none; border-right: medium none; border-top: medium none;">
<br /></div>
<div style="border-bottom: medium none; border-left: medium none; border-right: medium none; border-top: medium none;">
<span style="font-family: 'Calibri','sans-serif'; font-size: 11pt; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="mso-no-proof: yes;"><span style="font-family: 'Calibri','sans-serif'; font-size: 11pt; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="font-family: 'Calibri','sans-serif'; font-size: 11pt; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="font-family: 'Calibri','sans-serif'; font-size: 11pt; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="font-family: 'Calibri','sans-serif'; font-size: 11pt; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><span style="font-family: 'Calibri','sans-serif'; font-size: 11pt; line-height: 115%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><a href="http://office.microsoft.com/en-us/windows-sharepoint-services-help/introduction-to-versioning-HA010021576.aspx"><span style="font-family: Arial, Helvetica, sans-serif; font-size: small;">Introduction to versioning</span></a></span></span></span></span></span></span></span></div>
<span style="font-family: Arial, Helvetica, sans-serif; font-size: small;"></span><br />
<div style="border-bottom: medium none; border-left: medium none; border-right: medium none; border-top: medium none;">
<a href="http://office.microsoft.com/en-us/sharepoint-server-help/overview-RZ010233806.aspx?section=1"><span style="font-family: Arial, Helvetica, sans-serif; font-size: small;">SharePoint document libraries III: Work with version history</span></a></div>
<div style="border-bottom: medium none; border-left: medium none; border-right: medium none; border-top: medium none;">
<a href="http://office.microsoft.com/en-us/windows-sharepoint-services-help/working-with-sharepoint-document-libraries-HA001141287.aspx"><span style="font-family: Arial, Helvetica, sans-serif; font-size: small;">Working with SharePoint document libraries</span></a></div>
<div style="border-bottom: medium none; border-left: medium none; border-right: medium none; border-top: medium none;">
<a href="http://office.microsoft.com/en-us/sharepoint-server-help/manage-permissions-for-a-list-library-folder-document-or-list-item-HA010021564.aspx?CTT=3"><span style="font-family: Arial, Helvetica, sans-serif; font-size: small;">Manage permissions for a list, library, folder, document, or list item</span></a></div>
<div style="border-bottom: medium none; border-left: medium none; border-right: medium none; border-top: medium none;">
<a href="http://office.microsoft.com/en-us/sharepoint-server-help/permission-levels-and-permissions-HA010100149.aspx?CTT=3"><span style="font-family: Arial, Helvetica, sans-serif; font-size: small;">Permission levels and permissions</span></a></div>
<span style="font-family: Arial, Helvetica, sans-serif; font-size: small;"></span><br />
<div style="border-bottom: medium none; border-left: medium none; border-right: medium none; border-top: medium none;">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /><span style="font-size: small;"></span></span></div>
<span style="font-family: Arial, Helvetica, sans-serif; font-size: small;"></span><br />
<br /><div style="border-bottom: medium none; border-left: medium none; border-right: medium none; border-top: medium none;">
<span style="font-family: Arial, Helvetica, sans-serif; font-size: small;"></span><br />
<br /><span style="font-family: Arial, Helvetica, sans-serif; font-size: small;"></span><br />
<br /><span style="font-family: Arial, Helvetica, sans-serif;"><br /><span style="font-size: small;"></span></span><span style="font-family: Arial, Helvetica, sans-serif; font-size: small;"></span></div>
<br />
<img height="42" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEicDDCcE7ZdHSwQPXmVrWjR5xRMCbTb4tVAV2A51sZYJvcGXJxCjUQDWF9t4BzOcOdkKBhv114oH0FQwoRN8_CJ9xhfUyz-fHemd8-7TEMpGjSEB4Qk44_vYukRjLL7XTDIUirBieYNUJIq/s320/7.png" style="filter: alpha(opacity=30); left: 362px; mozopacity: 0.3; opacity: 0.3; position: absolute; top: 1282px; visibility: hidden;" width="96" /></description>
<link>http://sharefort.blogspot.com/2012/09/how-to-prevent-certain-users-from_4.html</link>
<author>noreply@blogger.com (Faisal Akhtar)</author>
<media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhkhyphenhyphenkTS1G7El9FNBySgXqDEdpEJ_9hgMSqxSPsS1f58_ZdkXHmOxLkPx1pSC5ZOKS8g6R5JK4ci8A_PdeWAUGpXz1TcYC9txys4zh_CiFJJYsSIe8ecYd8jIOylemfekHUXRfMHYHMt2m3/s72-c/1.png" height="72" width="72"/>
<thr:total>0</thr:total>
...</item>
<item>
<guid isPermaLink="false">tag:blogger.com,1999:blog-896451408200852359.post-6534452558051223113</guid>
<pubDate>Thu, 05 Jul 2012 18:58:00 +0000</pubDate>
<atom:updated>2012-07-05T11:58:00.025-07:00</atom:updated>
<title>Visual guide to Windows Live ID authentication with SharePoint 2010</title>
<description>I found this blog post very hellful in setting up my SharePoint dev environment to use windows live ID for authentication.<br /><br /><a href="https://www.nothingbutsharepoint.com/sites/devwiki/articles/Pages/Visual-guide-to-Windows-Live-ID-authentication-with-SharePoint-2010---part-1.aspx">Visual guide to Windows Live ID authentication with SharePoint 2010</a></description>
<link>http://sharefort.blogspot.com/2012/07/visual-guide-to-windows-live-id.html</link>
<author>noreply@blogger.com (Faisal Akhtar)</author>
<thr:total>0</thr:total>
...</item>
<item>
<guid isPermaLink="false">tag:blogger.com,1999:blog-896451408200852359.post-6280344283885568056</guid>
<pubDate>Fri, 27 Apr 2012 19:44:00 +0000</pubDate>
<atom:updated>2012-04-27T12:44:59.180-07:00</atom:updated>
<title>Pursuing My Next SharePoint Certification</title>
<description>I am currently pursuing my next ShareP{oint certification.
Here is a link to the lesson plan for both the developer certification and the admin certification.
<a href="http://www.microsoft.com/learning/en/us/certification/cert-sharepoint-server.aspx">Microsoft SharePoint Server Certifications
</a>
The lessson plan contains all necessary plans and labs for the certfication.</description>
<link>http://sharefort.blogspot.com/2012/04/pursuing-my-next-sharepoint.html</link>
<author>noreply@blogger.com (Faisal Akhtar)</author>
<thr:total>0</thr:total>
...</item>
<item>
<guid isPermaLink="false">tag:blogger.com,1999:blog-896451408200852359.post-6537892258620051473</guid>
<pubDate>Wed, 11 Jan 2012 17:22:00 +0000</pubDate>
<atom:updated>2012-01-11T09:27:30.021-08:00</atom:updated>
<title>Another day, another error</title>
<description>I installed SharePoint 2010 on my macbook running VMWare Fusion last night and after running the configuration wizard, I got the following error.<br /><br />Error during SP2010 configure - Failed to create sample data <br /><br />After a cursory Google search, it appears that the error is commong but from the sound of it, the error does not appear to be a show stopper. The central admin site collection is up and running and I am now in the process of creating additional sites. If I experience any more trouble with this error, I'll post details.</description>
<link>http://sharefort.blogspot.com/2012/01/another-day-another-error.html</link>
<author>noreply@blogger.com (Faisal Akhtar)</author>
<thr:total>0</thr:total>
...</item>
<item>
<guid isPermaLink="false">tag:blogger.com,1999:blog-896451408200852359.post-2901498990107880726</guid>
<pubDate>Mon, 09 Jan 2012 17:25:00 +0000</pubDate>
<atom:updated>2012-01-09T09:26:50.759-08:00</atom:updated>
<title>Installing VM Ware Fusion for MAC OSX</title>
<description>Installing Installing VM Ware Fusion for MAC OSX was surpisingly easy. I was able to install and run Windows Server 2008 with incredible ease. Now I am moving on to installing SQL Server, and other necessary software to implement SharePoint 2010.</description>
<link>http://sharefort.blogspot.com/2012/01/installing-vm-ware-fusion-for-mac-osx.html</link>
<author>noreply@blogger.com (Faisal Akhtar)</author>
<thr:total>0</thr:total>
...</item>
<item>
<guid isPermaLink="false">tag:blogger.com,1999:blog-896451408200852359.post-1615250916452021321</guid>
<pubDate>Fri, 06 Jan 2012 21:31:00 +0000</pubDate>
<atom:updated>2012-01-06T13:33:19.715-08:00</atom:updated>
<category domain="http://www.blogger.com/atom/ns#">SharePoint List</category>
<category domain="http://www.blogger.com/atom/ns#">SQL Server</category>
<category domain="http://www.blogger.com/atom/ns#">SSRS</category>
<title>Tutorial: Connecting SQL Reporting Services to a SharePoint List</title>
<description>Great video on how to use SSRS (SQL Reporting Services) to connect to SharePoint list<br /><br /><br /><iframe width="420" height="315" src="http://www.youtube.com/embed/udn8dj_8UKY" frameborder="0" allowfullscreen></iframe></description>
<link>http://sharefort.blogspot.com/2012/01/tutorial-connecting-sql-reporting.html</link>
<author>noreply@blogger.com (Faisal Akhtar)</author>
<media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://img.youtube.com/vi/udn8dj_8UKY/default.jpg" height="72" width="72"/>
<thr:total>0</thr:total>
...</item>
<item>
<guid isPermaLink="false">tag:blogger.com,1999:blog-896451408200852359.post-6428228198422235282</guid>
<pubDate>Fri, 23 Dec 2011 16:53:00 +0000</pubDate>
<atom:updated>2011-12-23T08:54:53.072-08:00</atom:updated>
<title>New Macbook Pro</title>
<description>I finally jumped on the macbook bandwagon and am now the owner of a brand new macbook pro. I will be installing SharePoint 2010 on the machine and I will post my misadventures here. It's good to finally have something to post on this blog.</description>
<link>http://sharefort.blogspot.com/2011/12/new-macbook-pro.html</link>
<author>noreply@blogger.com (Faisal Akhtar)</author>
<thr:total>0</thr:total>
...</item>
<item>
<guid isPermaLink="false">tag:blogger.com,1999:blog-896451408200852359.post-1933877224472541495</guid>
<pubDate>Tue, 21 Apr 2009 17:23:00 +0000</pubDate>
<atom:updated>2009-06-05T12:21:44.869-07:00</atom:updated>
<category domain="http://www.blogger.com/atom/ns#">hotfix</category>
<category domain="http://www.blogger.com/atom/ns#">SharePoint designer</category>
<category domain="http://www.blogger.com/atom/ns#">Tip</category>
<category domain="http://www.blogger.com/atom/ns#">workflow</category>
<title>Pause For Duration or Pause Until Date Activity Not Working in SharePoint Designer</title>
<description>I recently experienced a problem with some <span class="blsp-spelling-error" id="SPELLING_ERROR_0">SharePoint</span> designer activities. These activities include the "Pause For Duration" activity and the "pause until Date" activity. Basically, whenever I requested a <span class="blsp-spelling-error" id="SPELLING_ERROR_1">workflow</span> to pause for either a duration or pause until a date, even after that time the <span class="blsp-spelling-error" id="SPELLING_ERROR_2">workflow</span> failed to start again and the pausing continued. After doing some Googling, I came <span class="blsp-spelling-corrected" id="SPELLING_ERROR_3">across</span> this <span class="blsp-spelling-error" id="SPELLING_ERROR_4">MSDN</span> thread.<br /><br /><a href="http://social.msdn.microsoft.com/forums/en-US/sharepointworkflow/thread/9f5784de-b666-4dbc-8cea-ce9d5c221f2d/">http://social.msdn.microsoft.com/forums/en-US/sharepointworkflow/thread/9f5784de-b666-4dbc-8cea-ce9d5c221f2d/</a><br /><br />So this is a known issue that can be <span class="blsp-spelling-error" id="SPELLING_ERROR_5">fixed</span> by the following <span class="blsp-spelling-corrected" id="SPELLING_ERROR_6">hot fix</span>.<br /><br /><a href="http://www.microsoft.com/downloads/details.aspx?FamilyID=6096ce0f-d21e-47ac-afe2-d4e1c2fce670&displaylang=en">http://www.microsoft.com/downloads/details.aspx?FamilyID=6096ce0f-d21e-47ac-afe2-d4e1c2fce670&<span class="blsp-spelling-error" id="SPELLING_ERROR_7">displaylang</span>=en</a><br /><br />The <span class="blsp-spelling-error" id="SPELLING_ERROR_8">MSDN</span> thread describes the steps to <span class="blsp-spelling-corrected" id="SPELLING_ERROR_9">install</span> this <span class="blsp-spelling-corrected" id="SPELLING_ERROR_10">hot fix</span>. A word of caution to all hot fix users.<br /><br />1) <span class="blsp-spelling-error" id="SPELLING_ERROR_11">Hot fixes</span> can break more things than they fix, make sure a support ticket is open with Microsoft to let them know you are applying the <span class="blsp-spelling-corrected" id="SPELLING_ERROR_12">hot fix</span> and there is a log of the <span class="blsp-spelling-corrected" id="SPELLING_ERROR_13">hot fix</span>.<br />2) Document the application of the <span class="blsp-spelling-corrected" id="SPELLING_ERROR_14">hot fix</span>, when it was applied and why so in case you have to apply more <span class="blsp-spelling-corrected" id="SPELLING_ERROR_15">hot fixes</span>, you will be able to go back to your release notes for your MOSS <span class="blsp-spelling-corrected" id="SPELLING_ERROR_16">installation</span> in case two <span class="blsp-spelling-corrected" id="SPELLING_ERROR_17">hot fixes conflict or a service pack conflicts</span>.<br /><br />Now, there may be instances, in which the above hotfix won't resolve your problem. This may be due the fact that there are three timer jobs that run with with every web application in order for custom workflows to work and those timer jobs may not be running for your web application. The three timer jobs are<br /><br />1) Workflow<br />2) Workflow failover<br />3) Workflow failover auto cleanup<br /><br />Go into central administration and check to see if these three timer jobs show under timer jobs definitions. If they do, make sure they are running for the web application under which you have your workflows published. There maybe multiple instances of the timer jobs depending on how many web applications you have deployed but you have to be certain that they are running for the web application that contains your workflow. if they are not running, then you have to figure some way out to start them. I was not able to locate an STSADM command to forecefully start them but I do know a workround.<br /><br />1) Create a new web application and a new content database attached to that web application.<br />2) Take a backup of your site collection that is running under your old web application and restore it to the new web application you just created.<br />3) Test if your workflows are running in the new web application.<br /><br />If they are, you can then go ahead and change the port numbers and alternate access mapping settings along with any host header settings to point all URLs to the new web application and you can then delete the old web application.</description>
<link>http://sharefort.blogspot.com/2009/04/pause-for-duration-or-pause-until-date.html</link>
<author>noreply@blogger.com (Faisal Akhtar)</author>
<thr:total>2</thr:total>
...</item>
<item>
<guid isPermaLink="false">tag:blogger.com,1999:blog-896451408200852359.post-7423200398154784103</guid>
<pubDate>Tue, 17 Feb 2009 17:31:00 +0000</pubDate>
<atom:updated>2009-02-17T09:43:04.811-08:00</atom:updated>
<category domain="http://www.blogger.com/atom/ns#">Email reminders</category>
<category domain="http://www.blogger.com/atom/ns#">SharePoint designer</category>
<category domain="http://www.blogger.com/atom/ns#">Task Lists</category>
<category domain="http://www.blogger.com/atom/ns#">Tip</category>
<category domain="http://www.blogger.com/atom/ns#">workflow</category>
<title>Secondary Workflow Fails to Start and Task Reminder Email in MOSS</title>
<description>So I created a document library and published a <span class="blsp-spelling-error" id="SPELLING_ERROR_0">workflow</span> to it using <span class="blsp-spelling-error" id="SPELLING_ERROR_1">SharePoint</span> designer. I needed a secondary <span class="blsp-spelling-error" id="SPELLING_ERROR_2">workflow</span> to kick off on a task list that <span class="blsp-spelling-corrected" id="SPELLING_ERROR_3">would</span> allow the task list to send a reminder email when a task was due.<br /><br />Many people have asked me if there is a way to send an email when a task is due. <a href="http://www.sharepointace.com/Blog/post/2008/06/SharePoint-Designer-Workflow-ndash;-Send-Email-Reminder-X-days-prior-to-a-Date.aspx">Oscar Median has an excellent post</a> showing how to do exactly that.<br /><br />Now I needed my task list reminder <span class="blsp-spelling-error" id="SPELLING_ERROR_4">workflow</span> to kick off when a document was entering review. This <span class="blsp-spelling-error" id="SPELLING_ERROR_5">workflow</span> would send a reminder 3 days before the task was due. I <span class="blsp-spelling-corrected" id="SPELLING_ERROR_6">created</span> the <span class="blsp-spelling-error" id="SPELLING_ERROR_7">workflow</span> and published it to the task list but a<span class="blsp-spelling-error" id="SPELLING_ERROR_8">ny</span> time I created a document and ran the review <span class="blsp-spelling-error" id="SPELLING_ERROR_9">workflow</span> from the primary list, the secondary <span class="blsp-spelling-error" id="SPELLING_ERROR_10">workflow</span> refused to start automatically.<br /><br /><span class="blsp-spelling-corrected" id="SPELLING_ERROR_11">Finally</span>, I found <a href="http://office.microsoft.com/en-us/sharepointdesigner/HA102376561033.aspx">this post from Office Online</a> detailing how primary and secondary <span class="blsp-spelling-error" id="SPELLING_ERROR_12">workflows</span> interact but this little blurb fixed my problem.<br /><br />"Also note that even if a <span class="blsp-spelling-error" id="SPELLING_ERROR_13">workflow</span> was designed in Office <span class="blsp-spelling-error" id="SPELLING_ERROR_14">SharePoint</span> Designer 2007, its actions will still not trigger a secondary <span class="blsp-spelling-error" id="SPELLING_ERROR_15">workflow</span> if the user who started the <span class="blsp-spelling-error" id="SPELLING_ERROR_16">workflow</span> has signed in by using the system account. A <span class="blsp-spelling-error" id="SPELLING_ERROR_17">workflow</span> running under the system account cannot trigger a secondary <span class="blsp-spelling-error" id="SPELLING_ERROR_18">workflow</span>. "<br /><br />As it turns out, I was logging in as the system account. I logged in with a user account and the secondary <span class="blsp-spelling-error" id="SPELLING_ERROR_19">workflow</span> worked.</description>
<link>http://sharefort.blogspot.com/2009/02/secondary-workflow-fails-to-start-and.html</link>
<author>noreply@blogger.com (Faisal Akhtar)</author>
<thr:total>0</thr:total>
...</item>
<item>
<guid isPermaLink="false">tag:blogger.com,1999:blog-896451408200852359.post-482744564004150684</guid>
<pubDate>Wed, 11 Feb 2009 15:53:00 +0000</pubDate>
<atom:updated>2009-02-11T08:09:00.724-08:00</atom:updated>
<category domain="http://www.blogger.com/atom/ns#">error resolution</category>
<category domain="http://www.blogger.com/atom/ns#">Installing MOSS</category>
<title>An Error has Occurred...</title>
<description>Well, I was recently doing an installation of MOSS in my test environment and this error came up.<br /><br /> “Microsoft Office <span class="blsp-spelling-error" id="SPELLING_ERROR_0">SharePoint</span> Server 2007 encountered an error during setup.”<br /><br />Not very descriptive as to what is causing the error and nothing was found in the event logs. So I tried Google and found <a href="http://tiredblogger.wordpress.com/2007/11/16/fixing-a-broken-moss-2007-installation/">an excellent blog post by David <span class="blsp-spelling-error" id="SPELLING_ERROR_1">Longnecker</span></a>. However, after following David instruction and looking for a ghost of a <span class="blsp-spelling-error" id="SPELLING_ERROR_2">SharePoint</span> installation past, i was still unsuccessful. I then rebuilt the server from scratch formatting the hard drive. That made sure that there couldn't possibly be a lingering installation of <span class="blsp-spelling-error" id="SPELLING_ERROR_3">SharePoint</span>. Still, the same error <span class="blsp-spelling-corrected" id="SPELLING_ERROR_4">occurred</span> when I tried the installation.<br /><br />One last thing I tried was I copied the installation files to a local C drive folder and that seems to have done the trick. Now the installation proceeds normally. I was originally trying to do the <span class="blsp-spelling-corrected" id="SPELLING_ERROR_5">installation</span> from a network drive but that may have been what was causing the error. So <span class="blsp-spelling-corrected" id="SPELLING_ERROR_6">lessons</span> learned are as follows:<br /><br />If you get an error such as<br /><br /> “Microsoft Office <span class="blsp-spelling-error" id="SPELLING_ERROR_8">SharePoint</span> Server 2007 encountered an error during setup.”<br /><br />Try the following<br /><br />1) David's advice and look for a bad <span class="blsp-spelling-corrected" id="SPELLING_ERROR_9">installation</span> of <span class="blsp-spelling-error" id="SPELLING_ERROR_10">SharePoint</span> and remove it.<br />2) Format the server hard drive and reinstall to OS to make sure there is no <span class="blsp-spelling-error" id="SPELLING_ERROR_11">SharePoint</span> installation<br />3) Copy your setpup files from your network drive to a local C drive folder and then do the installation from there.<br /><br />That last one really stumps me because I have done plenty of installations using network drives and they have never given me trouble.</description>
<link>http://sharefort.blogspot.com/2009/02/error-has-occurred.html</link>
<author>noreply@blogger.com (Faisal Akhtar)</author>
<thr:total>5</thr:total>
...</item>
<item>
<guid isPermaLink="false">tag:blogger.com,1999:blog-896451408200852359.post-2274908980372529449</guid>
<pubDate>Mon, 12 Jan 2009 18:28:00 +0000</pubDate>
<atom:updated>2009-01-12T11:28:45.289-08:00</atom:updated>
<category domain="http://www.blogger.com/atom/ns#">error resolution</category>
<category domain="http://www.blogger.com/atom/ns#">MOSS</category>
<title>Your Friendly Neighborhood 401 Error</title>
<description>Well, I installed MOSS in a single server virtual environment for development and applied my service packs. After the creation of a site collection, I got the following error when trying to access the top level site.<br /><br /><br /><br />"You are not authorized to view this page"<br /><br /><br /><br />This is not a <span class="blsp-spelling-error" id="SPELLING_ERROR_0">SharePoint</span> error as the usual <span class="blsp-spelling-error" id="SPELLING_ERROR_1">SharePoint</span> background and logos were missing. So this is an <span class="blsp-spelling-error" id="SPELLING_ERROR_2">IIS</span> or <span class="blsp-spelling-corrected" id="SPELLING_ERROR_3">file system</span> error. Some Google searches revealed that the authentication might be set to <span class="blsp-spelling-error" id="SPELLING_ERROR_4">Kerberos</span> when it shouldn't be. So I went to application management and under application security clicked authentication providers and selected my web application. Sure enough, <span class="blsp-spelling-error" id="SPELLING_ERROR_5">Kerberos</span> was checked instead of <span class="blsp-spelling-error" id="SPELLING_ERROR_6">NTLM</span>. I <span class="blsp-spelling-error" id="SPELLING_ERROR_7">changed</span> it and everything was great.</description>
<link>http://sharefort.blogspot.com/2009/01/your-friendly-neighborhood-401-error.html</link>
<author>noreply@blogger.com (Faisal Akhtar)</author>
<thr:total>0</thr:total>
...</item>
<item>
<guid isPermaLink="false">tag:blogger.com,1999:blog-896451408200852359.post-6410535092325736306</guid>
<pubDate>Thu, 08 Jan 2009 21:04:00 +0000</pubDate>
<atom:updated>2009-01-08T13:16:10.879-08:00</atom:updated>
<category domain="http://www.blogger.com/atom/ns#">Virtual Machines</category>
<category domain="http://www.blogger.com/atom/ns#">WSS</category>
<title>Another WSS Search Service Problem</title>
<description>I was running a MOSS (No service Pack) enviornment on a virtual PC with Windows Server 2003 SP2 and kept running into trouble when trying to start the WSS search service. <a href="http://sharefort.blogspot.com/2008/07/windows-sharepoint-services-search.html">I had another problem earlier with the service </a>but in this one, when I tried starting the search service, I recieved the following error<br /><br /><br /><br />"Could not access the Search service configuration database"<br /><br /><br /><br />Quick google search led to <a href="http://www.sharepointblogs.com/stopcollaborateandlisten/archive/2008/11/11/cannot-start-the-wss-search-service-amp-office-sharepoint-search-not-working-same-sql-amp-wss-moss-server.aspx">this article</a>. I did as advised in the article and reconnected to the farm and tried restarting the service but got this error.<br /><br /><br /><br />"WSS_Search_develop.virtual.dev on develop.virtual.dev contains user-defined schema. Databases must be empty before they can be used. Delete all of the tables, stored procedures and other objects or use a different database."<br /><br /><br /><br />This likely holds true for the WSS search service and the MOSS search service. Which means,<br /><br /><br /><br />1) Lesson 1, do not use FQDN for the database server if you have the configuration listed in <a href="http://www.sharepointblogs.com/stopcollaborateandlisten/archive/2008/11/11/cannot-start-the-wss-search-service-amp-office-sharepoint-search-not-working-same-sql-amp-wss-moss-server.aspx">this article</a><br /><br />2) lesson 2, you will likely have to recreate your search databases when you reconnect to the farm.<br /><br /><br /><br />This problem may have been fixed in the service pack but I don't feel like investigating. Post below if you know otherwise.</description>
<link>http://sharefort.blogspot.com/2009/01/another-wss-search-service-problem.html</link>
<author>noreply@blogger.com (Faisal Akhtar)</author>
<thr:total>0</thr:total>
...</item>
<item>
<guid isPermaLink="false">tag:blogger.com,1999:blog-896451408200852359.post-966088085809874432</guid>
<pubDate>Mon, 06 Oct 2008 14:25:00 +0000</pubDate>
<atom:updated>2008-10-06T07:30:53.688-07:00</atom:updated>
<category domain="http://www.blogger.com/atom/ns#">Document Libraries</category>
<category domain="http://www.blogger.com/atom/ns#">error resolution</category>
<title>Changing the Document Name Field</title>
<description>I was attempting to give some of my users the ability to modify the document name field of a given document library. I modified the permissions of the document library but whenever a user attempted to modify the name field, the were given an access denied error. Another thing of note was that I did not want these same user to be able to remove document from the library (no deletion priviliges) so I had to create a custom permission level and take the delete items privilige out of the permission set.<br /><br />Doing this however also removed my users' ability to change a document name. I gave my users the delete item privilige and they were then able to modify the document name field. Any one else experience this? Anyone know why this happens?</description>
<link>http://sharefort.blogspot.com/2008/10/changing-document-name-field.html</link>
<author>noreply@blogger.com (Faisal Akhtar)</author>
<thr:total>0</thr:total>
...</item>
<item>
<guid isPermaLink="false">tag:blogger.com,1999:blog-896451408200852359.post-163227238452783732</guid>
<pubDate>Mon, 25 Aug 2008 20:44:00 +0000</pubDate>
<atom:updated>2008-08-25T13:52:25.275-07:00</atom:updated>
<category domain="http://www.blogger.com/atom/ns#">backup and recovery</category>
<category domain="http://www.blogger.com/atom/ns#">error resolution</category>
<category domain="http://www.blogger.com/atom/ns#">stsadm</category>
<title>After Farm Level Restore ....</title>
<description>When doing a farm level restore from <span class="blsp-spelling-error" id="SPELLING_ERROR_0">stsadm</span>, the prompt window asks for all credentials the farm will need in order to be restored. It will ask for all application pool identities, all search service account etc. However, one thing I don't remember it asking for is the <span class="blsp-spelling-error" id="SPELLING_ERROR_1">SSP</span> service <span class="blsp-spelling-corrected" id="SPELLING_ERROR_2">credentials</span> accounts. A farm level restore will <span class="blsp-spelling-corrected" id="SPELLING_ERROR_3">restore</span> your <span class="blsp-spelling-error" id="SPELLING_ERROR_4">SSP</span> but will not restore the credentials for the <span class="blsp-spelling-error" id="SPELLING_ERROR_5">SSP</span> timer service. After you do the <span class="blsp-spelling-corrected" id="SPELLING_ERROR_6">restore</span>, you will notice umpteen number of errors being thrown in your application event viewer such as<br /><br /><br />he Execute method of job definition Microsoft.Office.Server.Administration.ApplicationServerAdministrationServiceJob (ID 9c686e41-73d7-4<span class="blsp-spelling-error" id="SPELLING_ERROR_7">eb</span>0-866f-1f6d3c30270a) threw an exception. More information is included below.<br />Value cannot be null.<br />Parameter name: <span class="blsp-spelling-error" id="SPELLING_ERROR_8">userName</span><br />For more information, see Help and Support Center at <a href="http://go.microsoft.com/fwlink/events.asp">http://go.microsoft.com/fwlink/events.asp</a>.<br /><br />and<br /><br /><br />An exception occurred while executing the Application Server Administration job.<br />Message: Value cannot be null.<br />Parameter name: <span class="blsp-spelling-error" id="SPELLING_ERROR_9">userName</span><br /><span class="blsp-spelling-error" id="SPELLING_ERROR_10">Techinal</span> Support Details:<br />System.<span class="blsp-spelling-error" id="SPELLING_ERROR_11">ArgumentNullException</span>: Value cannot be null.<br />Parameter name: <span class="blsp-spelling-error" id="SPELLING_ERROR_12">userName</span><br />at Microsoft.SharePoint.Administration.SPProvisioningAssistant.ProvisionIisApplicationPool(String name, <span class="blsp-spelling-error" id="SPELLING_ERROR_13">ApplicationPoolIdentityType</span> <span class="blsp-spelling-error" id="SPELLING_ERROR_14">identityType</span>, String <span class="blsp-spelling-error" id="SPELLING_ERROR_15">userName</span>, <span class="blsp-spelling-error" id="SPELLING_ERROR_16">SecureString</span> password, <span class="blsp-spelling-error" id="SPELLING_ERROR_17">TimeSpan</span> <span class="blsp-spelling-error" id="SPELLING_ERROR_18">idleTimeout</span>, <span class="blsp-spelling-error" id="SPELLING_ERROR_19">TimeSpan</span> <span class="blsp-spelling-error" id="SPELLING_ERROR_20">periodicRestartTime</span>)<br />at Microsoft.SharePoint.Administration.SPMetabaseManager.ProvisionIisApplicationPool(String name, Int32 <span class="blsp-spelling-error" id="SPELLING_ERROR_21">identityType</span>, String <span class="blsp-spelling-error" id="SPELLING_ERROR_22">userName</span>, <span class="blsp-spelling-error" id="SPELLING_ERROR_23">SecureString</span> password, <span class="blsp-spelling-error" id="SPELLING_ERROR_24">TimeSpan</span> <span class="blsp-spelling-error" id="SPELLING_ERROR_25">idleTimeout</span>, <span class="blsp-spelling-error" id="SPELLING_ERROR_26">TimeSpan</span> <span class="blsp-spelling-error" id="SPELLING_ERROR_27">periodicRestartTime</span>)<br />at Microsoft.Office.Server.Administration.SharedWebServiceInstance.CreateSharedWebServiceApplicationPool(SharedResourceProvider <span class="blsp-spelling-error" id="SPELLING_ERROR_28">srp</span>)<br />at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean <span class="blsp-spelling-error" id="SPELLING_ERROR_29">isAdministrationServiceJob</span>)<br />For more information, see Help and Support Center at<br /><a href="http://go.microsoft.com/fwlink/events.asp">http://go.microsoft.com/fwlink/events.asp</a>.<br /><br />These events will all be in one minute <span class="blsp-spelling-corrected" id="SPELLING_ERROR_30">intervals</span> of each other. To resolve, go into your restored <span class="blsp-spelling-error" id="SPELLING_ERROR_31">SSP</span> and provide the <span class="blsp-spelling-error" id="SPELLING_ERROR_32">SSP</span> time service account. Your errors will go away.<br /><br />Go under <span class="blsp-spelling-error" id="SPELLING_ERROR_33">SSP</span> administration, select edit properties. Provide a valid domain account for the <span class="blsp-spelling-error" id="SPELLING_ERROR_34">SSP</span> timer service and <span class="blsp-spelling-corrected" id="SPELLING_ERROR_35">click</span> <span class="blsp-spelling-corrected" id="SPELLING_ERROR_36">OK</span>.</description>
<link>http://sharefort.blogspot.com/2008/08/after-farm-level-restore.html</link>
<author>noreply@blogger.com (Faisal Akhtar)</author>
<thr:total>0</thr:total>
...</item>
<item>
<guid isPermaLink="false">tag:blogger.com,1999:blog-896451408200852359.post-5963944080345551088</guid>
<pubDate>Wed, 13 Aug 2008 20:31:00 +0000</pubDate>
<atom:updated>2008-08-13T13:56:33.543-07:00</atom:updated>
<category domain="http://www.blogger.com/atom/ns#">backup and recovery</category>
<category domain="http://www.blogger.com/atom/ns#">batch scripting</category>
<category domain="http://www.blogger.com/atom/ns#">IIS</category>
<category domain="http://www.blogger.com/atom/ns#">Tip</category>
<title>STSADM Farm Recovery</title>
<description>The STSADM command is indeed a very handy tool. When creating a farm level backup, I created the following batch file using the stsadm command<br /><p>rd /s /q <a href="file://ServerName/Backup/FarmBackup">\\ServerName\Backup\FarmBackup</a></p><p>cscript.exe c:\windows\system32\iisback.vbs /s servername.domainname /backup <a href="file://servername/Backup">\\servername\Backup</a> /b WeeklyBackup /v NEXT_VERSION /e password</p><p>md <a href="file://servername/Backup/FarmBackup">\\servername\Backup\FarmBackup</a></p><p>move C:\WINDOWS\system32\inetsrv\MetaBack\WeeklyBackup.MD0 <a href="file://servername/Backup/FarmBackup">\\servername\Backup\FarmBackup</a></p><p>move C:\WINDOWS\system32\inetsrv\MetaBack\WeeklyBackup.SC0 <img alt="Add Image" src="http://www.blogger.com/img/gl.photo.gif" border="0" /><a href="file://servername/Backup/FarmBackup">\\servername\Backup\FarmBackup</a></p><p>cd C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BINstsadm -o backup -directory <a href="file://servername/Backup/FarmBackup">\\servername\Backup\FarmBackup</a> -backupmethod full -overwrite</p>Now let's break it down.<br /><br />The first line actually deletes the backup taken last night as these backups are transfered to tape every night in my case. If i need an earlier backup, I can recover it from tape.<br /><br />The second line creates a backup of the IIS meta base. Why do the work when you can steal from others right? :) Thanks Ben, you da man. <a href="http://mindsharpblogs.com/ben/archive/2006/09/19/1292.aspx">Excellent post on this script by Ben Curry here</a>.<br /><br />The third line recreates the backup directory in which the backups will go. Notice that the servername\backup directory is the <a href="http://sharefort.blogspot.com/2008/08/stsadm-and-farm-level-backups.html">root directory I talked about configuring in this post</a>.<br /><br />The fourth and fifth line actually move the metabase backup files to the newly created backup folder while the fifth actually takes the backup of the farm.<br /><br /><a href="http://blogs.msdn.com/joelo/archive/2008/02/24/navigating-sharepoint-server-backup.aspx">Joel Oleson has an excellent list</a> of the stuff you have to backup in order to recover your installation in case of disaster. Now this farm level back does cover all my content databases but depending n your requirements, you may not want to create a farm level batch process that runs every day. Maybe your recovery time and recovery point objectives for different content is different so use your judgement in when to use farm level and when to use content database level backups.<br /><br /><a href="http://support.microsoft.com/kb/948725">Now, the configuration database cannot be backed up</a>. Among your options to recover your configuration database is<br /><br />1) Use Microsoft data protection manager (I haven't done this)<br />2) Create a well tested silent installer file (Follow Joel's and Ben's advice, those guys seem to know thier stuff but I am currently in the process of doing this.)<br />3) Document all your settings and simple redo the installation<br /><br />The third option was easiest for me so that where I went.<br /><br />In case of disaster, you should reinstall MOSS, recreate the configuration database and then restore the farm using your command line tool and your application will come back.</description>
<link>http://sharefort.blogspot.com/2008/08/stsadm-farm-recovery.html</link>
<author>noreply@blogger.com (Faisal Akhtar)</author>
<thr:total>0</thr:total>
...</item>
<item>
<guid isPermaLink="false">tag:blogger.com,1999:blog-896451408200852359.post-3901073978792195425</guid>
<pubDate>Thu, 07 Aug 2008 19:06:00 +0000</pubDate>
<atom:updated>2008-08-07T12:11:20.349-07:00</atom:updated>
<category domain="http://www.blogger.com/atom/ns#">error resolution</category>
<category domain="http://www.blogger.com/atom/ns#">MOSS</category>
<category domain="http://www.blogger.com/atom/ns#">stsadm</category>
<title>Unable to backup content database using stsadm</title>
<description>Interesting problem I ran into with stsadm. I was unable to backup my content database using the stsadm command. it kept failing telling me to check the backup log file. Finally, I found a blog post here<br /><br /><a href="http://dhunter-thinkingoutaloud.blogspot.com/2007/07/sharepoint-2007-backup-failed.html">http://dhunter-thinkingoutaloud.blogspot.com/2007/07/sharepoint-2007-backup-failed.html</a><br /><br />on how to fix this problem. You have to make sure the MSSQLSERVER service is running under a domain account. Mine was running under local system. After i changed the identity, I restarted the service and reset IIS and was then able to perform my content database backup.</description>
<link>http://sharefort.blogspot.com/2008/08/unable-to-backup-content-database-using.html</link>
<author>noreply@blogger.com (Faisal Akhtar)</author>
<thr:total>0</thr:total>
...</item>
<item>
<guid isPermaLink="false">tag:blogger.com,1999:blog-896451408200852359.post-1352112711078981960</guid>
<pubDate>Thu, 07 Aug 2008 16:19:00 +0000</pubDate>
<atom:updated>2008-08-07T09:58:50.860-07:00</atom:updated>
<category domain="http://www.blogger.com/atom/ns#">backup and recovery</category>
<category domain="http://www.blogger.com/atom/ns#">error resolution</category>
<category domain="http://www.blogger.com/atom/ns#">MOSS</category>
<category domain="http://www.blogger.com/atom/ns#">stsadm</category>
<category domain="http://www.blogger.com/atom/ns#">Tip</category>
<title>stsadm and Farm Level Backups</title>
<description>As most <span class="blsp-spelling-error" id="SPELLING_ERROR_0">SharePoint</span> administrators know, <span class="blsp-spelling-error" id="SPELLING_ERROR_1">stsadm</span> is a really handy <span class="blsp-spelling-error" id="SPELLING_ERROR_2">tool</span> for creating scheduled tasks for backups of a <span class="blsp-spelling-error" id="SPELLING_ERROR_3">SharePoint</span> farm. I was setting up such a scheduled task today and while i was testing my batch script, I ran into two problem.<br /><br />The first problem <span class="blsp-spelling-corrected" id="SPELLING_ERROR_4">occurred</span> whenever I tried to execute the following command.<br /><br /><strong><span class="blsp-spelling-error" id="SPELLING_ERROR_5">stsadm</span> -o backup -directory "<span class="blsp-spelling-error" id="SPELLING_ERROR_6">servername</span></strong><a href="file://Test/"><strong>\Test</strong></a><strong> Backups" -<span class="blsp-spelling-error" id="SPELLING_ERROR_7">backupmethod</span> full</strong><br /><br />Whenever i attempted to execute this command, I <span class="blsp-spelling-error" id="SPELLING_ERROR_8">recieved</span> the following error,<br /><br /><strong>Access to the path '<span class="blsp-spelling-error" id="SPELLING_ERROR_9">servername</span></strong><a href="file://Test/"><strong>\Test</strong></a><strong> Backups\<span class="blsp-spelling-error" id="SPELLING_ERROR_10">spbrtoc</span>.<span class="blsp-spelling-error" id="SPELLING_ERROR_11">xml</span>' is denied.</strong><br /><br />I went to the directory and right clicked and selected security<br /><br /><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgt11M_Ba0tiTxRGlq6TkRrbJqtmdM7Ui6b85ljERLsGNV3zDKdfElAbV-jHXSJ31jqWHYDDrj21AwQK2AuodZhGpYWgVwlYVBdkOrXrcJJ15scPW5wqMxE4_R8MO_m8XuMXuoEySMSNQ90/s1600-h/stsadmproblem.JPG"><img id="BLOGGER_PHOTO_ID_5231817380587494690" style="FLOAT: left; MARGIN: 0px 10px 10px 0px; CURSOR: hand" alt="" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgt11M_Ba0tiTxRGlq6TkRrbJqtmdM7Ui6b85ljERLsGNV3zDKdfElAbV-jHXSJ31jqWHYDDrj21AwQK2AuodZhGpYWgVwlYVBdkOrXrcJJ15scPW5wqMxE4_R8MO_m8XuMXuoEySMSNQ90/s320/stsadmproblem.JPG" border="0" /></a><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br />The account with which I was logged in had full control so that was not the issue, I then noticed the sharing tab. In the sharing tab, there is a button called permissions, when i checked the permissions there, my account did not have any permissions. So I added my account to that area and attempted the command again and it worked.<br /><br />The second error I encountered was that when the command was done running, it encountered 8 errors. When I checked the log, apparently one of my search databases had failed to be backup during the farm backup.<br /><br /><strong>Error: Backup failed for Object <span class="blsp-spelling-error" id="SPELLING_ERROR_12">WSS</span>_Search_<span class="blsp-spelling-error" id="SPELLING_ERROR_13">ServerName</span> failed in event <span class="blsp-spelling-error" id="SPELLING_ERROR_14">OnBackup</span>. For more information, see the error log located in the backup directory.</strong><br /><strong></strong><br />Now the funny thing is, that database seems to be the least critical database as that is the database that stores the search content for the help section of <span class="blsp-spelling-error" id="SPELLING_ERROR_15">SharePoint</span>. It is easy enough to recreate in case of a failure but I was still puzzled. So I attempted the backup on another <span class="blsp-spelling-corrected" id="SPELLING_ERROR_16">file share</span> with the following name<br /><br /><a href="file://servername/Backupstest">\\<span class="blsp-spelling-error" id="SPELLING_ERROR_17">servername</span>\<span class="blsp-spelling-error" id="SPELLING_ERROR_18">Backupstest</span></a><br /><br />Then my command looked like this<br /><br /><strong><span class="blsp-spelling-error">stsadm</span> -o backup -directory <span class="blsp-spelling-error" id="SPELLING_ERROR_20">servername</span></strong><strong>\B</strong><strong><span class="blsp-spelling-error" id="SPELLING_ERROR_21">ackuptest</span> -<span class="blsp-spelling-error" id="SPELLING_ERROR_22">backupmethod</span> full</strong><br /><br />Notice I don't need quotes around my directory name as there are no spaces in the <span class="blsp-spelling-corrected" id="SPELLING_ERROR_23">directory name</span>. When I attempted this command, the farm backup completed successfully without errors.<br /><br />So remember, check permissions and rename your file share location if you want your backups to run properly.</description>
<link>http://sharefort.blogspot.com/2008/08/stsadm-and-farm-level-backups.html</link>
<author>noreply@blogger.com (Faisal Akhtar)</author>
<media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgt11M_Ba0tiTxRGlq6TkRrbJqtmdM7Ui6b85ljERLsGNV3zDKdfElAbV-jHXSJ31jqWHYDDrj21AwQK2AuodZhGpYWgVwlYVBdkOrXrcJJ15scPW5wqMxE4_R8MO_m8XuMXuoEySMSNQ90/s72-c/stsadmproblem.JPG" height="72" width="72"/>
<thr:total>0</thr:total>
...</item>
<item>
<guid isPermaLink="false">tag:blogger.com,1999:blog-896451408200852359.post-1239283022474919575</guid>
<pubDate>Thu, 31 Jul 2008 19:14:00 +0000</pubDate>
<atom:updated>2008-07-31T12:26:37.780-07:00</atom:updated>
<category domain="http://www.blogger.com/atom/ns#">error resolution</category>
<category domain="http://www.blogger.com/atom/ns#">MOSS</category>
<category domain="http://www.blogger.com/atom/ns#">Tip</category>
<category domain="http://www.blogger.com/atom/ns#">workaround</category>
<title>Windows SharePoint Services Search Service Not Starting</title>
<description><div>Slightly annoying problem I ran into. I was trying to get the Windows SharePoint Services Search Service started on my farm but no matter what, I couldn't get it to start. Finally, I tried changing the indexing schedule and it worked<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhAXHl29Wh9EvUjy-7QEk8Zg-1bvR2CbXjjbXR5W7hC9jp4IjtjKaFc3SlufpvQERKe_VkUUnouLOUwDTYDaCCDRdpm8Gzs_4_V42ltX7zDIbuc0WTq8nd8zwm7oINpnKT_VwnMbWGuhiK-/s1600-h/SearchServiceNotworking.JPG"><img id="BLOGGER_PHOTO_ID_5229260637810287090" style="FLOAT: left; MARGIN: 0px 10px 10px 0px; CURSOR: hand" alt="" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhAXHl29Wh9EvUjy-7QEk8Zg-1bvR2CbXjjbXR5W7hC9jp4IjtjKaFc3SlufpvQERKe_VkUUnouLOUwDTYDaCCDRdpm8Gzs_4_V42ltX7zDIbuc0WTq8nd8zwm7oINpnKT_VwnMbWGuhiK-/s320/SearchServiceNotworking.JPG" border="0" /></a></div><div> </div><div> </div><div> </div><div> </div><div> </div><div> </div><div> </div><div> </div><div> </div><div> </div><div> </div><div> </div><div> </div><div> </div><div> </div><div>Notice the red arrow. Do not let the indexer run every five minutes as this will cause the service not to start. </div><div> </div><div>For those of you who don't know, Windows SharePoint Services Search Service is the service SharePoint uses to index the content in the help section of SharePoint. On the top right corner of everypage, there is a question mark that takes you to SharePoint help. If you don't have this service configured, you won't be able to search for any content in the help section. Also, be sure to use a domain account for the content access and the service account.</div></description>
<link>http://sharefort.blogspot.com/2008/07/windows-sharepoint-services-search.html</link>
<author>noreply@blogger.com (Faisal Akhtar)</author>
<media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhAXHl29Wh9EvUjy-7QEk8Zg-1bvR2CbXjjbXR5W7hC9jp4IjtjKaFc3SlufpvQERKe_VkUUnouLOUwDTYDaCCDRdpm8Gzs_4_V42ltX7zDIbuc0WTq8nd8zwm7oINpnKT_VwnMbWGuhiK-/s72-c/SearchServiceNotworking.JPG" height="72" width="72"/>
<thr:total>0</thr:total>
...</item>
<item>
<guid isPermaLink="false">tag:blogger.com,1999:blog-896451408200852359.post-1901563343796549102</guid>
<pubDate>Wed, 30 Jul 2008 14:52:00 +0000</pubDate>
<atom:updated>2008-07-31T07:44:59.551-07:00</atom:updated>
<category domain="http://www.blogger.com/atom/ns#">error resolution</category>
<category domain="http://www.blogger.com/atom/ns#">SPS 2003</category>
<category domain="http://www.blogger.com/atom/ns#">SQL 2000</category>
<category domain="http://www.blogger.com/atom/ns#">Uninstall SPS 2003</category>
<title>Uninstalling SPS 2003</title>
<description>First, the client had a SPS 2003 installation that they wanted to get rid of. They asked me to upgrade but the application was so badly hosed that I recommended we scratch the installation altogether and start over. So then they wanted the fiels in that SPS 2003 environment to be saved to a network drive. I then created a network place and copied all fields from SPS 2003 on to my network drive. Now I am ready to uninstall SPS 2003. Since SPS 2003 is on the ABC box and I am to utilize the ABC box as my test / dev environment for MOSS, I need to uninstall SPS 2003 first. A great writeup on how to uninstall SPS 2003 from Microsoft <a href="http://office.microsoft.com/en-us/sharepointportaladmin/HA011605181033.aspx">can be found here</a>.<br /><br /><br />Now notice that in the article, they say that uninstalling the WMSDE or SQL server won't get rid of the databases that SPS 2003 created such as the content and config database. In order to get rid of the databases, I log in to SQL enterprise manager but I see "No Items" under the SQL server group. Apparently you have to create a new SQL server registration for the account with which you are logged in. <a href="http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=3194930&SiteID=1">Excellent MSDN discussion details the steps here</a>. Deepak is the man as he has helped me in the past as well.<br /><br /><br />After you have created your registeration, then go about uninstalling in this order<br /><br />1) Uninstall SPS 2003<br />2) Uninstall WSS 2.0<br />3) Delete all databases that SharePoint created through enterprise manager<br />4) Uninstall SQl Server or WMSDE<br /><br />The fourth step is optional as you might have other applications running on that instance of SQL server. After that, your server should be in a state for you to go about preparing it for the installation of MOSS.</description>
<link>http://sharefort.blogspot.com/2008/07/uninstalling-sps-2003.html</link>
<author>noreply@blogger.com (Faisal Akhtar)</author>
<thr:total>0</thr:total>
...</item>
<item>
<guid isPermaLink="false">tag:blogger.com,1999:blog-896451408200852359.post-5511970830326839382</guid>
<pubDate>Wed, 30 Jul 2008 14:02:00 +0000</pubDate>
<atom:updated>2008-07-30T07:12:34.290-07:00</atom:updated>
<category domain="http://www.blogger.com/atom/ns#">MOSS</category>
<category domain="http://www.blogger.com/atom/ns#">SQL Log Shipping</category>
<title>Next Project Please</title>
<description>Ok, I am in Chesapeake VA working on my next project. I will keep a log of all events and problems on this blog. For now, there are three servers in the farm<br /><br />ABC, DEF, GHI<br /><br />I cannot even disclose the last three digist of the IP as this is a sensitive installation. ABC will be my test server while DEF and GHI will be my productions servers. Where DEF will be the application and webfront end and GHI will be my database backend. Here is a cool thing that client asked whether is possible. Say the DEF server also had a SQL server instance, can we replicate all production data to the DEF server from GHI server so in case the GHI server ever got blown away, we could manually switch our DEF application instance to the DEF SQL instance and everything would come back up? Also, can we use the GHI server as a backup application server where if the DEF server ever got blown away, we could switch the GHI SQL instance to use the GHI application instance and bring MOSS back?<br /><br />Way cool scenario but I have yet to come accross anyone who has done it. I am using MOSS 2007 Standard with SQL 2000 as the back end. This should be fun...</description>
<link>http://sharefort.blogspot.com/2008/07/next-project-please.html</link>
<author>noreply@blogger.com (Faisal Akhtar)</author>
<thr:total>0</thr:total>
...</item>
<item>
<guid isPermaLink="false">tag:blogger.com,1999:blog-896451408200852359.post-5577084726911503893</guid>
<pubDate>Wed, 30 Apr 2008 12:28:00 +0000</pubDate>
<atom:updated>2008-04-30T05:41:26.928-07:00</atom:updated>
<category domain="http://www.blogger.com/atom/ns#">error resolution</category>
<category domain="http://www.blogger.com/atom/ns#">MOSS</category>
<category domain="http://www.blogger.com/atom/ns#">workaround</category>
<category domain="http://www.blogger.com/atom/ns#">WSS</category>
<title>Navigation Editing problem</title>
<description><div>Recently, one of my users asked to change the name and URL of his site. I was naieve in thinking that perhaps editing the URL from the site settings and Title and Description settings will do the trick. However, be warned that as soon as you change the site URL, the quick launch bar will malfunction. After changing , the subheadings in the quicklaunch will stop working. For example<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj0Kiw2oU6EbDfvV0NI_Jdd_FmiynWFmfd1SU5k3Fv7wqGnj0rt10JLAcnZyv3n_WD1SSrh5D5686jT-aTrVdSW_H_AJrCeiSubP5laxyZYSey5ecxLwbgov8RkftGzmXexIBUQsWuI1skH/s1600-h/NavProblem.jpg"></a></div><br /><div></div><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhcM2Bnb4T2HZlT7XrIpujcbuTh2GOlXMB-Zg5uIxLVDG1cYIJYGmxYnxRrP-KUCMysqfgGWPv_Zhz1VxPN_sp5Am92eOdvTxFkb6vcm14lsji24HEuHSZuXUKmhbcIzL20M3yjHIytHX33/s1600-h/NavProblem.jpg"><img id="BLOGGER_PHOTO_ID_5195016890414769122" style="FLOAT: left; MARGIN: 0px 10px 10px 0px; CURSOR: hand" alt="" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhcM2Bnb4T2HZlT7XrIpujcbuTh2GOlXMB-Zg5uIxLVDG1cYIJYGmxYnxRrP-KUCMysqfgGWPv_Zhz1VxPN_sp5Am92eOdvTxFkb6vcm14lsji24HEuHSZuXUKmhbcIzL20M3yjHIytHX33/s320/NavProblem.jpg" border="0" /></a><br /><div></div><br /><div><br /><br /><br /><br /><br /><br /><br /><br /><br />The documents and pictures subheadings will stop working and will give you page not found errors. Also, if you try to add any additional items to the quick launch, the quick launch will totally malfunction and you will start seeing multiple enterie for Documents, Lists and / or Pictures. This has not been fixed in SP1 as the environment in which this problem occurred had SP1. There are good blog posts and discussion boards discussing this problem <a href="http://paulgalvin.spaces.live.com/Blog/cns!1CC1EDB3DAA9B8AA!202.entry">here</a> and <a href="http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1691577&SiteID=1">here</a>.<br /><br />It is frustrating that a simple thing like this could cause so much trouble. Is anyone from Microsoft listening?</div></description>
<link>http://sharefort.blogspot.com/2008/04/navigation-editing-problem.html</link>
<author>noreply@blogger.com (Faisal Akhtar)</author>
<media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhcM2Bnb4T2HZlT7XrIpujcbuTh2GOlXMB-Zg5uIxLVDG1cYIJYGmxYnxRrP-KUCMysqfgGWPv_Zhz1VxPN_sp5Am92eOdvTxFkb6vcm14lsji24HEuHSZuXUKmhbcIzL20M3yjHIytHX33/s72-c/NavProblem.jpg" height="72" width="72"/>
<thr:total>0</thr:total>
...</item>
<item>
<guid isPermaLink="false">tag:blogger.com,1999:blog-896451408200852359.post-7980351278983217428</guid>
<pubDate>Thu, 27 Mar 2008 23:23:00 +0000</pubDate>
<atom:updated>2013-05-16T10:22:42.135-07:00</atom:updated>
<category domain="http://www.blogger.com/atom/ns#">Document Libraries</category>
<category domain="http://www.blogger.com/atom/ns#">Task Lists</category>
<category domain="http://www.blogger.com/atom/ns#">Tip</category>
<title>Using the Me filter in SharePoint</title>
<description>Many users are unaware of the [me] filter inside SharePoint that is a very powerful filter. You can use this filter to personalize views of a document library and even dataview webparts. Say you want to show on the main page of a team website all tasks a person is responsible for, the documents that were created by them or the documents that were last updated by them. You can do so by using the [me] filter.<br />
<br />
<br />
First, the me filter applies only to fields that contain people picker values. It cannot be applied to other fields. For example, some Kosher fields for the filter are<br />
<br />
<ol><br />
<li>Created by</li>
<br />
<li>Modified by</li>
<br />
<li>Assigned to</li>
<br />
<li>Any custom field that contains people picker data</li>
</ol>
<br />
Other fields cannot use this filter.<br />
<br />
I will address the two most common application of this filter that I have used in SharePoint. <br />
<br />
<ol><br />
<li>In a tasks list to show what tasks are assigned to me</li>
<br />
<li>In a document library to show what documents were created or modified by me.</li>
</ol>
<br />
<br />
<strong>Task List</strong><br />
<br />
Whenever a new task list is created in SharePoint, it comes with a default view in it that is called the my tasks view. This view uses the [me] filter on the assigned to field in order to show those items that are assigened to an individual that is logged in. From the view menu, select modify view on the my tasks view and in the filter section you will see how a SharePoint task list uses the me filter. <br />
<br />
<strong>Document Library</strong><br />
<br />
In most documents libraries that I work with, I like to create a personal view called the my documents view that contains all the documents that I have created or modified. This view helps me keep track of documents that I am interested in a large document set.<br />
<br />
<ol><br />
<li>Select create view from the settings menu of the document library.</li>
<li>You can call it the "My Documents" view.</li>
<li>Navigate down to the filter section and sepcify the "created by" field on the "Show the items when column". Specify "is equal to" in the comparison and in the filter type [me].</li>
<li>Select or for the next column and sepcify the "modified by" field on the "Show the items when column". Specify "is equal to" in the comparison and in the filter type [me].</li>
</ol>
There you have it. When you see the documents in these views, you will see only those items that are either created or last modified by you.</description>
<link>http://sharefort.blogspot.com/2008/03/using-me-filter-in-sharepoint.html</link>
<author>noreply@blogger.com (Faisal Akhtar)</author>
<thr:total>6</thr:total>
...</item>
<item>
<guid isPermaLink="false">tag:blogger.com,1999:blog-896451408200852359.post-3700530987754528579</guid>
<pubDate>Fri, 21 Mar 2008 13:24:00 +0000</pubDate>
<atom:updated>2008-03-21T12:01:37.344-07:00</atom:updated>
<category domain="http://www.blogger.com/atom/ns#">error resolution</category>
<category domain="http://www.blogger.com/atom/ns#">SharePoint List</category>
<category domain="http://www.blogger.com/atom/ns#">workaround</category>
<title>MOSS: List Schema Error</title>
<description>I have run into this bug within SharePoint multiple times. Whenever I attempt to export some list to a spreadsheet, I get the following error<br /><br />"Cannot get the list schema column property from the SharePoint list"<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEifeAKeGyYS1tFZmA76It8OMH1go_DFijEdUyj85b2ZsNktWzg1khjhx-6eiglXN_gJy7VnbpaDiq9wqvpnmsheMmJCJCB5j8Bzyq7oNpf9VkU9n8q1EE_bLf6nzM5MuZyfCeyRcAyiwJE_/s1600-h/ListSchemaError1.jpg"><img id="BLOGGER_PHOTO_ID_5180185942273708322" style="FLOAT: left; MARGIN: 0px 10px 10px 0px; CURSOR: hand" alt="" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEifeAKeGyYS1tFZmA76It8OMH1go_DFijEdUyj85b2ZsNktWzg1khjhx-6eiglXN_gJy7VnbpaDiq9wqvpnmsheMmJCJCB5j8Bzyq7oNpf9VkU9n8q1EE_bLf6nzM5MuZyfCeyRcAyiwJE_/s320/ListSchemaError1.jpg" border="0" /></a><br /><br /><br /><br /><br /><br /><br />This problem is caused by some malformed date fields. I don't exactly know what causes this problem but I do know two workarounds. to it.<br /><br /><ol><li>Export the list to an Excel 2007 spreadsheet</li><li>Read below</li><br /></ol><br /><p>So in order to do the second work around, I recommend that you take a backup<br />of your list before you go any further in case something breaks</p><ol><li>Go the list settings of the list that is giving you this error, and select create view <a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjgxRNGvTdkHWpY8KPGxhMuooqEBZLqG6OWFwAk7xd45Pum-B0shtpWwiTTmOyyBZALaedkerZuqjcnGI6ZFN7S0mv2tdTQt_OMfddl-r3fFn-dlDvGrg7bIPkn37bEdsWiR_XvVUp2rWUf/s1600-h/ListSchemaError9.jpg"><br /><img id="BLOGGER_PHOTO_ID_5180189180679049698" style="MARGIN: 0px 10px 10px 0px; CURSOR: hand" alt="" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjgxRNGvTdkHWpY8KPGxhMuooqEBZLqG6OWFwAk7xd45Pum-B0shtpWwiTTmOyyBZALaedkerZuqjcnGI6ZFN7S0mv2tdTQt_OMfddl-r3fFn-dlDvGrg7bIPkn37bEdsWiR_XvVUp2rWUf/s320/ListSchemaError9.jpg" border="0" /></a></li><li>Create a personal view that contain only one field that is a simple text field. </li><br /><li>Export this view to a spreadsheet. If you are successful in your export, select modify this view from the view menu and add one field to the view at a time and continue exporting until you find the fields that cause the error. </li><br /><li>After you know what fields are causing the error, select list setting from the list menu<br /><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg6SFPgBkAEEzPvMntNEFF7nZn_K3YzVei63NO6S5cGZ7i2r_h4_YcyNyKVPNtQsNlY5EPsdF71un0T2OYEjsylnYHq9oIK3N0wFGDoxQro-nxGbGl4EJf9MrmhpUh6qGx55OqdOATbf4ms/s1600-h/ListSchemaError2.jpg"><img id="BLOGGER_PHOTO_ID_5180188892916240738" style="MARGIN: 0px 10px 10px 0px; CURSOR: hand" alt="" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg6SFPgBkAEEzPvMntNEFF7nZn_K3YzVei63NO6S5cGZ7i2r_h4_YcyNyKVPNtQsNlY5EPsdF71un0T2OYEjsylnYHq9oIK3N0wFGDoxQro-nxGbGl4EJf9MrmhpUh6qGx55OqdOATbf4ms/s320/ListSchemaError2.jpg" border="0" /></a></li><li>Under the columns section select a field that you identified in steps 1,2 and 3<br /><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhqmOQyCUfmGjc9jN8aIRFUSwlx9sJBOF2BklHS8C2HGWeeZ15kncpJM0_D64tHwgQzK5Fpv0egyDdcZUA-6_gWOu_KkTYfFayr-jMu4HF5W0msnSBgxbB4Hs1mmJmhdUN1C8Q3gacLuReV/s1600-h/ListSchemaError3.jpg"><img id="BLOGGER_PHOTO_ID_5180189043240096114" style="MARGIN: 0px 10px 10px 0px; CURSOR: hand" alt="" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhqmOQyCUfmGjc9jN8aIRFUSwlx9sJBOF2BklHS8C2HGWeeZ15kncpJM0_D64tHwgQzK5Fpv0egyDdcZUA-6_gWOu_KkTYfFayr-jMu4HF5W0msnSBgxbB4Hs1mmJmhdUN1C8Q3gacLuReV/s320/ListSchemaError3.jpg" border="0" /></a></li><br /><li>Change the field type from date field to single line of text and click ok.<br /><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiB2KiF6GVRTFtAsARplTpUdu7UIzFMKsn4BwJ8zCIXL7EDEDa0P3xxuJ-5D-lnydKxCenFXN1_UF1NGbXPFVXzBVxZYVjKxFHlKtoL1iD4nCVQf_K9PHcFF_rnEAIxNKM6YSzU1JBaKzsL/s1600-h/ListSchemaError4.jpg"><br /><img id="BLOGGER_PHOTO_ID_5180189043240096130" style="MARGIN: 0px 10px 10px 0px; CURSOR: hand" alt="" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiB2KiF6GVRTFtAsARplTpUdu7UIzFMKsn4BwJ8zCIXL7EDEDa0P3xxuJ-5D-lnydKxCenFXN1_UF1NGbXPFVXzBVxZYVjKxFHlKtoL1iD4nCVQf_K9PHcFF_rnEAIxNKM6YSzU1JBaKzsL/s320/ListSchemaError4.jpg" border="0" /></a></li><br /><li>If you are prompted with a warning, click ok.<br /><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiGziUHYZSxIRioHWohNaZtaKn1yeW_tP7Q-TuiE0IkRQTXyTxg07jsF3aDWl3f_n3nEEKlOOL0GmhdEli4Qes1U0xxvtArrdt3NAbpIvpeVPQ9enc2ok94GVPvqOv1TQKbvf-FB4Vl1P7k/s1600-h/ListSchemaError8.jpg"><br /><img id="BLOGGER_PHOTO_ID_5180189176384082386" style="MARGIN: 0px 10px 10px 0px; CURSOR: hand" alt="" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiGziUHYZSxIRioHWohNaZtaKn1yeW_tP7Q-TuiE0IkRQTXyTxg07jsF3aDWl3f_n3nEEKlOOL0GmhdEli4Qes1U0xxvtArrdt3NAbpIvpeVPQ9enc2ok94GVPvqOv1TQKbvf-FB4Vl1P7k/s320/ListSchemaError8.jpg" border="0" /></a><br /></li><li>Click on the same field again, this time it will say "Single line of text" as the field type<br /><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjNXCuEClRe3WaJNOSEl2xIgjSlxkGQAvSozhAUArcVw1Qnv946NyjOUMC57n8AYDzVUwUjk4eTpjl_nygfG1fbe0yzYl0CKH1h-l38PT1Ef6478ajk2QO4fmscCC9SSqJvv5aRtA1quu6m/s1600-h/ListSchemaError6.jpg"><img id="BLOGGER_PHOTO_ID_5180189047535063458" style="MARGIN: 0px 10px 10px 0px; CURSOR: hand" alt="" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjNXCuEClRe3WaJNOSEl2xIgjSlxkGQAvSozhAUArcVw1Qnv946NyjOUMC57n8AYDzVUwUjk4eTpjl_nygfG1fbe0yzYl0CKH1h-l38PT1Ef6478ajk2QO4fmscCC9SSqJvv5aRtA1quu6m/s320/ListSchemaError6.jpg" border="0" /></a></li><br /><li>Change it to date time format and click ok<br /><br /><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg_JLjGjT2dKQGg1aVxxtxnhkcx4BQF-fNjhyphenhyphenN8CmGdQmLJEQsYjLPzTyuOzLFCApKdgzRs2egf6-SlQV441-Aq2tXg2eWQkdSH_2OasYU_tgpzuuwtzFz2dGUUs-xwwg8pR-yaXYPT5yfU/s1600-h/ListSchemaError7.jpg"><br /><img id="BLOGGER_PHOTO_ID_5180189172089115074" style="MARGIN: 0px 10px 10px 0px; CURSOR: hand" alt="" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg_JLjGjT2dKQGg1aVxxtxnhkcx4BQF-fNjhyphenhyphenN8CmGdQmLJEQsYjLPzTyuOzLFCApKdgzRs2egf6-SlQV441-Aq2tXg2eWQkdSH_2OasYU_tgpzuuwtzFz2dGUUs-xwwg8pR-yaXYPT5yfU/s320/ListSchemaError7.jpg" border="0" /></a></li><br /><li>If you are prompted with a warning, click ok.<br /><br /><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiGziUHYZSxIRioHWohNaZtaKn1yeW_tP7Q-TuiE0IkRQTXyTxg07jsF3aDWl3f_n3nEEKlOOL0GmhdEli4Qes1U0xxvtArrdt3NAbpIvpeVPQ9enc2ok94GVPvqOv1TQKbvf-FB4Vl1P7k/s1600-h/ListSchemaError8.jpg"><br /><img id="BLOGGER_PHOTO_ID_-2147483648" style="MARGIN: 0px 10px 10px 0px; CURSOR: hand" alt="" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiGziUHYZSxIRioHWohNaZtaKn1yeW_tP7Q-TuiE0IkRQTXyTxg07jsF3aDWl3f_n3nEEKlOOL0GmhdEli4Qes1U0xxvtArrdt3NAbpIvpeVPQ9enc2ok94GVPvqOv1TQKbvf-FB4Vl1P7k/s320/ListSchemaError8.jpg" border="0" /></a></li><br /><li>Repeat these steps for all fields that were causing the error to occur and you should eliminate the problem. Next time your export to Excel should work.</li></ol><br /><br /><br /><br /><p></p></description>
<link>http://sharefort.blogspot.com/2008/03/moss-list-schema-error.html</link>
<author>noreply@blogger.com (Faisal Akhtar)</author>
<media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEifeAKeGyYS1tFZmA76It8OMH1go_DFijEdUyj85b2ZsNktWzg1khjhx-6eiglXN_gJy7VnbpaDiq9wqvpnmsheMmJCJCB5j8Bzyq7oNpf9VkU9n8q1EE_bLf6nzM5MuZyfCeyRcAyiwJE_/s72-c/ListSchemaError1.jpg" height="72" width="72"/>
<thr:total>0</thr:total>
...</item>