Method 'Post' of object 'IOWSPostData' failed

The error message --Method 'Post' of object 'IOWSPostData' failed --appears when I import a spreadsheet in the Create -Import Spreadheet menu of MOSS 2007.
Importing lists from Excel 2007 returns a Method 'Post' of object 'IOWSPostData' failed dialog. The problem is not with the sharepoint but result of a failed Application.SharePointVersion() call in the Excel Add-In which results in Excel attempting to use the IOWSPostData.Post() method to publish the Excel range which is used with SharePoint Services.

By forcing the version lookup result variable to 2 or greater, Excel will use SOAP to communicate with SharePoint and the publish request will be successful.

To make this change, Please follow these steps:
1. open the Excel Add-In EXPTOOWS.XLA locate in

C:\Program Files\Microsoft Office\Office12\1033.

2. Press Alt+F11 to display the Visual Basic code editor and search (Ctrl+F) for the line lVer = Application.SharePointVersion(URL).

3. Comment out that line with a single quote and add the line lVer=2 so your Intialize() method should now look like this:

Sub Initialize(List, Title, URL, QuickLaunch)
strQuickLaunch = QuickLaunch
aTarget(iPublishURL) = URL
aTarget(iPublishListName) = List
aTarget(iPublishListDesc) = Title
'lVer = Application.SharePointVersion(URL)
lVer = 2
End Sub

If you have any doubts or queries regarding the above procedure then please let me know...
I hope the above information will helps you to resolve your issue..Thanks !!

Reff:http://social.technet.microsoft.com/forums/en-US/sharepointgeneral/thread/75b2be6b-44df-4389-bf34-c7a01c12372c/

Authenticated Users get Access Denied when Browsing to Site- 403 Forbidden

When NT Authority\Authenticated users were added to a windows sharepoint services 3.0 site, users other than the users directly permissioned to site, or Site Collection Admins would receive a 403 Forbidden error when they woudl try to browse to the Default.aspx page.

ULS Logs would show:
============================================================
Access Denied for /default.aspx.
StackTrace: Microsoft.SharePoint.Utilities.SPUtility:Void
HandleAccessDenied(System.Exception), Microsoft.SharePoint.SPGlobal:Void
HandleUnauthorizedAccessException(System.UnauthorizedAccessException),
Microsoft.SharePoint.SPWeb:System.String GetWebPartPageContent(System.Uri,
Microsoft.SharePoint.WebPartPages.PageView, System.Web.HttpContext, Boolean,
Boolean, Boolean, Boolean, Boolean ByRef, Byte ByRef, System.String ByRef,
System.Guid ByRef, Int64 ByRef, System.Guid ByRef, UInt32 ByRef, System.String
ByRef, Byte ByRef, System.Object ByRef, UInt32 ByRef, System.Object ByRef,
Microsoft.SharePoint.SPWebPartCollectionInitialState ByRef, System.Object ByRef,
System.String ByRef, Boolean ByRef, System.Guid ByRef),
Microsoft.SharePoint.ApplicationRuntime.SPRequestModuleData:System.String
FetchWebPartPageInformationForInit(System.Web.HttpContext,
Microsoft.SharePoint.SPWeb, Boolean, System.String, Boolean, Boolean ByRef, Byte
ByRef, System.Guid ByRef, UInt32 ByRef, System.String ByRef,
Microsoft.SharePoint.SPFileLevel ByRef, System.String ByRef, System.String ByRef,
System.String ByRef, System.String ByRef, System.Guid ByRef, System.Object ByRef,
Microsoft.SharePoint.SPWebPartCollectionInitialState ByRef, System.String ByRef,
System.String ByRef, System.Object ByRef, Boolean ByRef, System.Guid ByRef, Int64
ByRef), Microsoft.SharePoint.ApplicationRuntime.SPRequestModuleData:Void
GetFileForRequest(System.Web.HttpContext, Microsoft.SharePoint.SPWeb, Boolean,
System.String), Microsoft.SharePoint.ApplicationRuntime.SPRequestModule:Void
InitContextWeb(System.Web.HttpContext, Microsoft.SharePoint.SPWeb),
Microsoft.SharePoint.WebControls.SPControl:Microsoft.SharePoint.SPWeb
SPWebEnsureSPControl(System.Web.HttpContext),
Microsoft.SharePoint.WebControls.SPControl:Microsoft.SharePoint.SPWeb
GetContextWeb(System.Web.HttpContext),
Microsoft.SharePoint.ApplicationRuntime.SPRequestModule:Void
PostResolveRequestCacheHandler(System.Object, System.EventArgs),
System.Web.HttpApplication+SyncEventExecutionStep:Void
System.Web.HttpApplication.IExecutionStep.Execute(),
System.Web.HttpApplication:System.Exception ExecuteStep(IExecutionStep, Boolean
ByRef), System.Web.HttpApplication+ApplicationStepManager:Void
ResumeSteps(System.Exception), System.Web.HttpApplication:System.IAsyncResult
System.Web.IHttpAsyncHandler.BeginProcessRequest(System.Web.HttpContext,
System.AsyncCallback, System.Object), System.Web.HttpRuntime:Void
ProcessRequestInternal(System.Web.HttpWorkerRequest), System.Web.HttpRuntime:Void
ProcessRequestNoDemand(System.Web.HttpWorkerRequest),
System.Web.Hosting.ISAPIRuntime:Int32 ProcessRequest(IntPtr, Int32),
==================================================================

after detailed analysis and debug of the w3wp process, we found two columns with non standard settings in the content database. In the AllList table the columns called tp_readsecurity and tp_writesecurity, for the “User Information List” have the values set to 2 & 4 respectively. The default value for both columns is 1.

Tp_readsecurity

Value="1">read all items
Value="2">read only my items
Value="4">read none


Tp_writesecurity

Value="1”>write all items
Value="2">write only my items
Value="4">write none

The value 2 for tp_readsecurity will only allow a user to read their own items. So reading the items does not occur because it is trying to read the items in the “user Information list” that are not their own. The value 4 for tp_writesecurity does not allow write to this list so you will not be able to add users. Since they have not or cannot be added into the list, there was an exception being thrown and this is the reason for the 403 Forbidden.

RESOLUTION/WORKAROUND:
===========================
1. Open the site you are having trouble with, but make sure you open the site
with site collection admin/owner rights.
2. Browse to the URL:
http://portal/sites/site/_layouts/advsetng.aspx?list={GUID}
3. This List ID will vary.
4. You can also get to this list by Browsing to the root of your site, Site
Actions> Site Settings> Advanced Permissions> Click on the All People link
in qiuck launch> Then select List Settings, then Advanced Settings
5. This method will also get you to the above URL and probably easier than
having to poke thru the DB to find the GUID of that list.
6. Change the Read Access Value to “All Items”
7. Change the Edit Access to “All Items”
7. This will modify those values in the database back to 1 and 1
8. Authenticated Users should now be able to access the site.

I hope the above information will helps you to resolve this issue !! Thanks !!!

Access Denied when attempting to create a new page

When attempting to create a page by clicking Site Actions Create Page, the user immediatly receives an Access Denied. This occurs even if the user is a member of the Site Owners group with Full Control.

ERROR MESSAGE: Access Denied

CAUSE:
===========
The access denied was a result of the user not being a part of the Style Resource Readers group. According to technet, this group allows a user to read the Master Page Gallery and Restricted Read the Style Library. By default, this group contains only the NT AUTHORITY\Authenticated Users group. This will allow all users who have authenticated to the site to read the Master Page gallery and Style Library.

RESOLUTION:
====================
1) Open the site you are having issues with
2) Click Site Actions Site Settings
3) In the Users and Permissions section, click People and Groups
4) Click Groups
5) Click Style Resource Readers
6) Click New Add User
7) In the Add Users section, click the Add all authenticated users link
8) Click OK

I hope the above information will helps you to resolve this issue !! Thanks !!

no Next in list of users and groups

Groups.aspx will not display more than 100 groups !!

We have a site collection with many users and groups. It consist of approximately 745 groups created with different depts. When I go to see a list of users and groups, I only see the first page i.e. 100 groups only !! this is actually very strange as i compared with other site collections that are running in our farm, those sites are not facing this wierd issue... The next arrows are gone, we can't advance through the list.

After digging a lot, we were able to resolve this issue and i would like share this resolution with all of u !!!!
--The page on which we can see all the created groups is called as "User Information List"
--or we can add that one as a User Information List web part.
--Every List has the option of "Modify this View" but for this list i.e. "User Information List", this view is hidden (by default).. Microsoft hide this view from the consideration, just to avoid messing !! i can guess :-)
--When we will go inside that view then we have enable these following options:-

1. User Information List.
2. Click Edit > Modify this view
3. Count section
4. Make sure the Item Limit is set to 100 and Display items in batches of the specified size is checked.

Now the question arises as How to go inside that list ?? Dont Worry, Please follow these steps:

-> That page is called as ViewEdit.aspx

->You need to pass the Guid for both the list and view to this page, like this:
->http://MOSS2007.com/_layouts/ViewEdit.aspx?List={00000000-0000-0000-0000-000000000000}&View={00000000-0000-0000-0000-000000000000}

-> You can get the Guid for the User Information List using the GetListCollection web method on /_vti_bin/Lists.asmx.

-> You can get the Guid for the View by passing the Guid for the list to the GetViewCollection web method on /_vti_bin/Views.asmx

I hope the above information will helps u to resolve this issue..Thanks !!

File Conversion in Process, Converter Failed To Save File

On some machines, when a user opens an Excel file from SharePoint and checks out for edit and -does not- use the local drafts folder, yousee a dialog with "File Conversion In Progress", then "ConverterFailed To Save File" message, but the file is checked out to the user and will not open in the Excel. It never opens the application and I'm returned to the document library. If I already have the application it doesn't generate the error.

The fix is to do the following:

- Open Word
- Click the Office button (Top-left in the window)
- Click Word Options
- Click Resources
- Click the Diagnose button
- Click through the wizard until it’s finished
- Close all browser windows

That’s fixed all of our issues…

I hope the above information will helps u to resolve the issue !! Thanks !!

Error: Library Not Registered

On our main Sharepoint page, we've got this drop-down-button in our main navigation that shows other sites and lets you click on them to access them. I believe it uses ActiveX controls. We've got one user (that we know of) who when she loads up the main page, that drop-down won't work for it...it just does nothing. At the bottom-left of the page, IE shows an "error on page." When I double click on it to get the error, it says the following:

Line: 1936
Char: 4
Error: Library not registered.
Code: 0
URL: (the url of the page)

The fix is to do the following:

- Open Word
- Click the Office button (Top-left in the window)
- Click Word Options
- Click Resources
- Click the Diagnose button
- Click through the wizard until it’s finished
- Close all browser windows

That’s fixed all of our issues…

If you are using Office-2003 then please follow the below mentioned steps:

-Word 2003
- Help
-detect and repair
- check discard my customized settings and restore default settings

I hope the above information will helps u to resolve the issue !! Thanks !!

How to find out the List GUID in sharepoint !!

As the document libraries and lists are the most commonly used entities in sharepoint, or we can say sharepoint starts with list and libraries !! So, there are so many problems or issues we face on day to day basis...Among all these problems, some required list id's.

Please follow these as how to find out the list guid:
1.Navigate to the SharePoint list using the browser.

2.Select the Settings + List Settings menu command.

3.Copy the Url from the browser address bar into Notepad.

It will look something like: http://moss2007/adminX/_layouts/listedit.aspx?List=%7B26534EF9%2DAB3A%2D46E0%2DAE56%2DEFF168BE562F%7D

4.Delete everying before and including “List=”.

5.Change “%7B” to “{”

6.Change all “%2D” to “-“

7.Chnage “%7D” to “}”

8.You are now left with the Id:{26534EF9-AB3A-46E0-AE56-EFF168BE562F}

That's it-issue resolved !!!!!!

I hope the above information will helps you to find the list guid..thanks !!

Uploading Spreadsheets into SharePoint Lists

By having the data from the spreadsheet in a SharePoint list it makes it easier to filter the data, display the data to the right audiences, search the data, add new records to the list and most importantly it is easier for people to have access to the data. so what is the right process to upload spreadsheets into sharepoint list ????

1. Open up the SharePoint site where you want to create the new SharePoint list that will contain the data from your spreadsheet.

2.Click Site Actions – Create.

3.Then from the column Custom List you will find Import Spreadsheet .

4.Enter a ‘Name’ for the List and a Description.

5.Then in the ‘Import from Spreadsheet’ section browse to your spreadsheet.

6.Next click the ‘Import’ button.

7.You will now get the ‘Import Windows SharePoint List’ screen as well as your Excel spreadsheet.

8.Cell A1 is highlighted but you can’t select all the cells until you change the dropdown ‘Range of Cells’ and then click in the bottom box ‘Select Range’.

9.Now you can click on cell A1 hold the mouse button down and drag to the last cell in your spreadsheet so that all cells including the column titles are selected.

10.Now click the ‘Import’ button and after a few seconds you will have a neatly presented SharePoint list with all the columns and data from your spreadsheet now displaying.

Risk-List Uniqueness !!

This is regarding with one of the unique Sharepoint issues that we successfully resolved today. By using out-of-settings, it is not possible to resolve this issue and anybody can consider that it a SharePoint By-Default behaviour.

ISSUE:

-In a Project Tracking Workspace Template, there is one list which comes by default named "Risk List".

-If we want to create one more same list then you will not find the option under View All Site Content->Create-> Custom List

-If we try to save the Risk List as Template then it will successfully saved in the List Gallery but you will not find that list under the Create List Section (Path mentioned above)

STEPS TAKEN FOR RESOLUTION:

-Taken backup of all the folders for the below mentioned steps in which i have made modification !!

-Checked C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\FEATURES

-Inside the Features Folders->PWSRISKS Folder(Which is part of Project Tracking Workspace Template)

-Inside the PWSRISKS Folder->List Templates->pwsrisk.xml

-Opened the XML file in notepad->Made Modification as -> DontSaveInTemplate="FALSE" (It was True before)

-Opened Feature.XML for the Risk List-> made Modification as -> Hidden="FALSE" (It was true Before)

-That's it..Issue resolved !!

SharePoint Designer Cache

Clearing SharePoint Desinger Web Part Cache:
After deploy the new assembly to the server you might see that new properties are not reflected in SharePoint Designer. You can correct the issue by clearing the C:\Documents and Settings\[User]\Local Settings\Application Data\Local\Microsoft\WebsiteCache

Clearing the Assembly Cache for SharePoint Designer:
There might be issue with loading workflow with custom activities that you have deployed for SPD workflows, which will result in "Failed to load the workflow" !!
Getting rid of cached file from:C:\Documents and Settings\[user]\Application Data\Microsoft\SharePoint Designer\ProxyAssemblyCache\. Then delete the folder (12.x.x.xxxx)

How to disable Contributor Settings in SharePoint Designer

When you install Microsoft Office SharePoint Server 2007 (MOSS 2007), By Default the Contributor Settings will be enabled on your site(s). You will notice this in the SharePoint Designer task pane.

This is because your account is present in the Content Authors group, wich may “restrict the use of some features” as the task pane mentions.This behavior can be modified if you turn off the "Contributor Settings" in SPD.

How to get this above window:

1. Open The site in SharePoint Designer

2. Site Menu

3.choose Contributor Settings.

4.Click on Disbale Contributor settings

5. Refresh the page and U will not see that message again !!!!

An error has occured in Approval

I think, Workflow is the easiest part of SharePoint for anybody to use and especially the out-of-box workflows. Yesterday, One of the user in my project reported an error regarding workflow. The scenario was he set an approval workflow for himself and when he tried to approve it then he got an error message as follows:




When we set up an workflow for the document library and list, We usually follow these process :

-Go to Settings->Workflow Settings->Add Workflow
-Choose the Approval workflow from the list, make it start on item creation go to the second workflow page.
-Select the approvers asper your requirement and check "Update the approval status (use this workflow to control content approval)"
-Finish and the workflow has been set !!

And now the mystery begins and you will get an error as mentioned above. and now You will ask,why? So the keyword is "Approval" !!

This is an approval workflow which should among getting the approvals update the approval status of the document so, if you missed one tiny little step like setting the approval for the document library this simple task will fail at the end.

Resolution:-
-Just go to the document Library Settings
-Versioning Settings Page
-Set "Require content approval for submitted items to?" to yes and everything should be fine.

I hope the above information will helps you to overcome the above mentioned error message!!
Thanks!!!

How to find the template name of sharepoint site?

It is really very difficult to find out the name of the template after the site has been created but not now.. After lots of searching & googling, I found out one great post belongs to Mr.SP Raj who written this code and it is very successfull as i have tried this and i am able to find the names of the templates used by the site.

Please Follow this link and your issue will be Resolved:
http://social.technet.microsoft.com/Forums/en-US/sharepointgeneral/thread/721bec39-2d32-4bbc-9094-a021a0d06dcb

List of MOSS 2007 Template ID Information
0 - GLOBAL (SetupPath=global) - "Global template"
1 - STS - "windows SharePoint Services Site", "Team Site", "Blank Site", "Document Workspace"
2 - MPS - "Basic Meeting Workspace", "Blank Meeting Workspace", "Decision Meeting Workspace", "Social Meeting Workspace", "Multipage Meeting Workspace"
3 - CENTRALADMIN - "Central Admin Site"
4 - WIKI - "Wiki Site"
7 - BDR - "Document Center"
9 - BLOG - "Blog"
20 - SPS (OBSOLETE) - "SharePoint Portal Server Site"
21 - SPSPERS - "SharePoint Portal Server Personal Space"
22 - SPSMSITE - "Personalization Site"
30 - SPSTOC (OBSOLETE) - "Contents area Template"
31 - SPSTOPIC (OBSOLETE) - "Topic area template"
32 - SPSNEWS (OBSOLETE) - "News area template"
33 - SPSNHOME (SubWebOnly) - "News Home template"
34 - SPSSITES - "Site Directory area template"
36 - SPSCOMMU (OBSOLETE) - "Community area template"
38 - SPSREPORTCENTER - "Report Center Site"
39 - CMSPUBLISHING (SetupPath=SiteTemplates\PUBLISHING) - "Publishing and Team Collaboration Site"
40 - OSRV (SetupPath=SiteTemplates\OSRV) - "Shared Services Administration Site"
47 - SPSPORTAL - "Corporate Intranet Site"
50 - SRCHCEN - "Search Center"
51 - PROFILES - "Profiles"
52 - BLANKINTERNETCONTAINER - "Internet Presence Web Site"
53 - BLANKINTERNET - "Publishing Site", "Press Releases Site", "Publishing Site"
54 - SPSMSITEHOST - "My Site Host"
90 - SRCHCENTERLITE (SetupPath=SiteTemplates\SRCHCENTERLITE) - "Search Center Lite"
6221 - PWA (SetupPath=SiteTemplates\PWA) - "Project Web Access Site"
6215 - PWS (SetupPath=SiteTemplates\PWS) - "Project Workspace"
14483 - OFFILE - "Records Repository", "Records Repository"

I Hope the above information will helps u to find the template name but if you face any problem then please let me know... Thanks!!!

Error message when you try to edit an Office document in a document library: "'Edit Document' requires a Windows SharePoint Services-compatible applic

When you try to edit a Microsoft Office document that is stored in a document library of a Microsoft Windows SharePoint Services Web site, you may receive one of the following error messages, depending on the version of Office that you are running.

2007 Microsoft Office suites:
'Edit Document' requires a Windows SharePoint Services-compatible application and Microsoft Internet Explorer 6.0 or greater.

Microsoft Office 2003 and earlier versions of Office :
'Edit Document' requires a Windows SharePoint Services-compatible application and Microsoft Internet Explorer 5.0 or greater.

you experience these symptoms if you click a Microsoft Word document in the document library, and then click Edit in Microsoft Office Word. Additionally, when you click New Document in the document library, you may receive the following error message:

The document could not be created. The required application may not be installed properly, or the template for this Document Library cannot be opened. Please try the following:

1. Check the General Settings for this Document Library for the name of the template, and install the application necessary for opening the template. If the application was set to install on first use, run the application and then try creating a new document again.

2. If you have permission to modify this Document Library, go to General Settings for the library and configure a new template.

This issue may occur if one or more of the following conditions are true:
-Microsoft Office XP or later is not installed on the computer.

-Office XP or a later version of Office is installed on the computer. However, the SharePoint support component that is included in Office Tools is not installed on the computer. That is, either Microsoft SharePoint Support or Windows SharePoint Services Support (as appropriate to your version of Office) is not installed on the computer.

-The Owssupp.dll file is not registered correctly in Microsoft Windows.

To resolve this issue, use one of the following methods, as appropriate for your situation.

If Office 2003 is installed on the computer, follow these steps:
-Click Start, and then click Control Panel.
-Click Add or Remove Programs.
-In the list of currently installed programs, click Microsoft Office 2003, and then click Change.
-Click Add or Remove Features, and then click Next.
-Click to select the Choose advanced customization of application check box, and then click Next.
-In the Choose update options for applications and tools box, expand Office Tools, click the down arrow next to Windows SharePoint Services Support, and then click Run from My Computer.
-Click Update.

If a 2007 Office suite is installed on the computer, follow these steps:
-Click Start, and then click Control Panel.
-Click Add or Remove Programs.
-In the list of currently installed programs, click Microsoft Office suite 2007, and then click Change.
-Click Add or Remove Features, and then click Continue.
-Expand Office Tools.
-Click the down arrow next to Windows SharePoint Services Support, and then click Run from My Computer.
-Click Continue.

Method 3: Register the Owssupp.dll file
Note For Office 2003 and Office 2007 an error occurs in steps 4 and 6. This error is benign and the appropriate modifications have occurred. The error message reads similarly to: "DllRegisterServer in C:\Program Files\Microsoft Office\OFFICE11OWSSUPP.DLL failed. Return code was: 0x80070716.

-Repair or reinstall Office 2003 or the individual Office 2003 program that is experiencing this issue.

For more information about Windows SharePoint Services, visit the following Microsoft Web site: http://technet.microsoft.com/windowsserver/sharepoint/default.aspx

Your client does not support opening this list with Windows Explorer.

When you try to open a folder in a Microsoft Windows SharePoint Services 3.0 document library in Explorer View, the folder does not open.

Specifically, this problem occurs when you connect to a document library in a Windows SharePoint Services 3.0 Web site by using Microsoft Internet Explorer. You browse a folder in the document library, and then you click Open with Windows Explorer on the Actions menu. However, nothing happens. Or, you receive the following message:
Your client does not support opening this list with Windows Explorer.

This issue occurs if the following conditions are true:
-You are using Microsoft Internet Explorer 6.
-The path of the folder contains more than 100 characters.

Workaround:
To work around this issue, use one of the following methods:
-Apply hotfix 325355 for Internet Explorer 6. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
325355 (http://support.microsoft.com/kb/325355/ ) You cannot access Word documents by using Outlook Web Access on a server that is running SharePoint Portal Server

-Use Windows Internet Explorer 7. For more information about Windows Internet Explorer 7, visit the following Microsoft Web site:
http://www.microsoft.com/windows/ie/default.mspx

I hope the above information will helps you to resolve your problem... Thanks!!!

The document could not be opened for editing. A Windows SharePoint Services compatible application could not be found to edit the document.

One of the user from my project reported that he was not able to edit as well as check out the office documents. When i tried to follow the same procedure (i.e. Edit, check-in, check-out) and strange thing was me also got the same error message. When i started my troubleshooting, I found out user created document library with multiple nested folders.

When we go to third or fourth level of the folder and try to edit any file with office application, we are getting an error – The document could not be opened for editing. A Windows SharePoint Services compatible application could not be found to edit the document. However if we try to edit the document uploaded on the root of the document library, we can edit it properly.

I tried reproduced the issue 2-3 times and found out one common thing and that is: You cannot edit the office document once the URL path reaches characters limit 340. You can edit the documents only till URL path length is up to 339 characters. You can open the documents, you can upload documents but you can't edit them by right click on document and click on "edit in Microsoft Word". Even this behavior is same with non-office documents also like text documents.

Workaround:

The only workaround possible is - open the file directly from the folder, modify and save it as a new file. Every time you need to save it as a new file. It won’t allow to save in the existing file. Or, Move the file one level up and you will be able to do all the operations like edit, check-in and check-out too.

I hope the above information helps you to resolve your problem and time also!! Thanks!!

Summary Links Web Part (Error 0x80070002)

Today, We faced one wierd error message regarding Summary Links Webpart.
Due to some requirement, one of the user in my project demanded me the replication of one of the site collections. So, Itried to take the export and imported it one to a new one with blank site template. Export and import both were successfull and replication has been done properly but the problem starts now, when we open the site and we found out one error message related to Summary Link Webpart.

Unable to add selected web part(s). Could not load XSL file. The system cannot find the file specified.(Exception from HRESULT: 0x80070002).
Solution:
This error is usually raised when you try to add a publishing-related web part (such as Summary Links) into a non-publishing site. You have to either add it into a site built with a publishing template (Collaboration Portal or Publishing Portal), or to activate the publishing features manually:

-Activate Office SharePoint Server Publishing Infrastructure feature in site collection features, in Site Collection Administration section of Site Settings page
-Activate Office SharePoint Server Publishing feature in destination site features, located on Site Administration section of Site Settings page

SharePoint Server 2010 Preliminary System Requirements

Very Soon, Microsoft will release the new version of SharePoint and that is Microsoft Office SharePoint Server 2010 i.e. Office 14

SharePoint Server 2010 Preliminary System Requirements
1.SharePoint Server 2010 will be 64-bit only.
2.SharePoint Server 2010 will require 64-bit Windows Server 2008 or 64-bit Windows Server 2008 R2.
3.SharePoint Server 2010 will require 64-bit SQL Server 2008 or 64-bit SQL Server 2005.

Microsoft also announced some important requirements regarding SharePoint Server 2010 browser compatibility:
-To ensure the best possible experience across multiple browsers, Microsoft is focusing on SharePoint 2010 engineering efforts on targeting standards based browsers (XHTML 1.0 compliant) including Internet Explorer 7, Internet Explorer 8 and Firefox 3.x. running on Windows Operating Systems.
-In addition, Microsoft also planning to increased level of compatibility with Firefox 3.x and Safari 3.x on non-Windows Operating Systems.
-Due to this focus Internet Explorer 6 will not be a supported browser for SharePoint Server 2010.

You can find additional information on Microsoft’s Support Lifecycle Policy including specific dates, product information and support offerings here: http://support.microsoft.com/gp/lifepolicy.

Advantages of 64-bit hardware and software (Office SharePoint Server 2007)
http://technet.microsoft.com/en-us/library/dd630764.aspx

Migrate an existing server farm to a 64-bit environment (Office SharePoint Server 2007)
http://technet.microsoft.com/en-us/library/dd622865.aspx

Columns in Edit in Datasheet View are read-only

Few Days before, we encountered a weird error message, not error we can say but normal properly working list or document library turned out to be readable only and we were not able to edit anything by using datasheet.

In standard view, it worked properly but our users wanted to use datasheet view only because they are more comfortable with that view and also it is more flexible to apply the metadata for multiple documents in datasheet view. I tried to reproduce the issue and strange thing is i am also facing the same behavior.

After lots to research and troubleshooting, we are able to find out the cause as well as resolution.

CAUSE:

User was using Office 2003 and then later installed an Office 2007 component so the Windows SharePoint Service Support tool portion of Office defaulted to using the Office 2007 version. Office 2007 will by default use Access instead of Excel for opening lists in Datasheet view. The types of columns that were being used in the list did not translate correctly to Access from Excel and so were changed to read-only.

This issue is by design and Microsoft is working on this one:

http://msdn.microsoft.com/en-us/library/bb462636(office.11).aspx#Office2007SynchronizeSharePointListfromExcel_Updating

WORKAROUND:

This will in effect remove the Office 2007 integration with SharePoint and change it back to using Office 2003 integration.

On the client machine:-

1.   Go to Add/Remove Programs

2.   Select the Office 2007 component, if there are more than one, do this for each of them.

3.   Select “Change” and then Add or Remove Features Expand the Office Tools section and

4.   Change the install state for Windows SharePoint Service Support to Not Available (Right click on it and choose “not available”) Continue through the wizard.

5.   Reboot

Go to Add/Remove programs --> Select Office 2003 -->Select Change and then Repair-->Continue through the wizard.

I hope the above steps helps you to resolve your problem and you are able to use the data view properly. If you face any issues after applying the above steps then please let me know!! Thanks!!

unable to connect to database or unable to connect the configuration database

Issue with SharePoint after installating the hotfix which solve DNS issue

If you install the DNS fix (KB 953230) and experience SharePoint trouble – such as error message which says unable to connect to database or unable to connect the configuration database.

You can follow the steps below if you're using Windows Internal Database/MSDE:
• Download and install SQL Management Studio Express (http://www.microsoft.com/downloads/details.aspx?FamilyId=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=en) if you don't have any SQL 2005 management tool available
• Connect the server using the following information
oServer: \\.\pipe\mssql$microsoft##ssee\sql\query
o Windows authentication
• Detach the SharePoint configuration database
• Reattach the SharePoint configuration database
• Restart your SharePoint server

Your issue should have been solved!!!

‘g_InstanceID’ is undefined

How to fix: Recurring Meeting Workspace error: ‘g_InstanceID’ is undefined
After changing the master page on a Meeting Workspace site, the recurring meeting workspace hyperlinks under “Select a date from the list below” do not work and throw a JavaScript error.

Please follow these steps to to overcome this error message "‘g_InstanceID’ is undefined "
1. At the top level of the site collection:- Browse to Site actions -> Site Settings -> Modify all site settings.
2.- Under the Galleries section, click 'Master pages and page layouts' to access the Master Page Gallery
3.Select 'Upload'. Browse to 12 hive\TEMPLATE\GLOBAL and select mwsdefault.master.
4.The 'Edit Item' page for the gallery will open. It's best to give this mwsdefault.master a new name in order to distinguish it from the original mwsdefault.master. Then click 'Check In'.
5.Publish the newly uploaded copy by selecting 'Publish a major version' from the item's dropdown box on the Master Page Gallery.
6.Approve the newly uploaded master page by selecting 'Approve/reject' from the item's dropdown box, selecting the Approved box, and clicking OK.

Back on the problem Meeting Workspace page:
-Select 'Site Actions' -> 'Site Settings' -> and then 'Master page' under the Look and Feel section
-Select the newly uploaded version of the mwsdefault.master in the Site Master Page and System Master Page dropdown boxes, and then click OK.
-the JavaScript controls on the Meeting Workspace will now work without producing the JavaScript error, making the other event dates browsable again.

I hope the above steps helps you to overcome this javascript error message and your meeting workspace template will work properly and never face this problem again. Thanks!!!

Cannot open file: it does not appear to be a valid archive. If you downloaded this file, try downloading the file again.

After you download a .ZIP file from a Microsoft Windows SharePoint Services document library, and then you try to open the .ZIP file, you may receive the following error message:
Cannot open file: it does not appear to be a valid archive. If you downloaded this file, try downloading the file again.

CAUSE
This problem may occur if HTTP compression is turned on in the Web Sites properties of Microsoft Internet Information Services (IIS) on the SharePoint virtual server. When you download a .ZIP file, IIS encodes the file as GZIP. However, the browser client passes the file directly to the unZIP program, without GZIP decoding the file. To determine if HTTP compression is turned on, follow these steps:
1. Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
2. Expand the server (local computer) tree, where server (local computer) is the name of your IIS server.
3. Right-click Web Sites, and then click Properties.
4. Click the Service tab to view the HTTP compression properties.

Resolution:

change the MIME type for the .ZIP file from application/x-zip-compressed to application/octet-stream . To change the MIME type, follow these steps:

1. Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
2. Right-click the server (local computer) tree, where server (local computer) is the name of your IIS server, and then click Properties.
3. Click MIME Types.
4. Scroll down the registered MIME type list to find the .zip entry.
5. Click the .zip application/x-zip-compressed entry, and then click Edit.
6. Change the MIME type value to application/octet-stream .
7. Stop and then restart the IIS Admin Service to apply the change to the MIME type.

The file that you selected could not be found

Few Days before, in our project, one of the user faced wierd error message which was never seen by my team. First of all lets focused the whole error message:
"The file that you selected could not be found. Check the spelling of the file name and verify that the location is correct."

When trying to open the sample dashboard in MOSS 2007 Enterprise Report Center site as an user with Read Only rights, we got this error message.
While troubleshooting, we compared two document libraries and reproduced the scenario.
After the excat replication of error message on a new document library,we found out the resolution which is quite simple.

Resolution:-
1. Go to your reports library where the workbooks are stored.
2. On the Settings menu, click Document Library Settings.
3. Under General Settings, click versioning settings.
4. Disable versioning.

I hope the above steps helps you to resolve your issue.
Thanks...

Usage Analysis Processing - Server Out of Memory error

In our company's project, We have Two enviornments Windows SharePoint Services and Microsoft office SharePoint Server 2007. Both are classified into 3 stages as Tes, QA and Production. In WSS 3.0 Test enviornment, when we tried to enable Usage Analysis processing, we got an error message :
"Server Out Of MemoryThere is no memory on the server to run your program. Please contact your administrator with this problem."

I can't find anything in the EVENT LOGS on the server that indicate an issue with this.
After doing lots of troubleshooting for more than 2 days, we found out the resolution.You can't believe it but the resolution is very simple and straightforward.

We found out that the application pool account was running under Network Service. We changed it to Domain admin account and after that did IISRESET.

Issue Resolved.
Cheers !

Note:-
The domain account should have the following rights as follows:-
1. It should be present in the WSS_WPG,WSS_ADMIN_WPG and IIS_WPG and Administrator group.
2.It should be present in the SQL SERVER Logins Section.
3. It should have DBCREATOR & SECURITY ADMIN Permissions in the SQL SERVER.

The application pool identity is essentially what the ASP .Net code of the site will be executing as. The user account used here must have the standard rights in order to run an application pool, and must obviously have rights to read and write to the SQL Server databases for the site.

Thanks...

How to configure Usage Analysis Processing on a Web server that is running Windows SharePoint Services 3.0

To turn on Windows SharePoint Services usage logging in an Office SharePoint Server farm, you must first turn on Usage Analysis Processing in Windows SharePoint Services 3.0, and then turn on Advanced Usage Analysis Reporting service in Shared Services Administration. To do this, follow these steps:

1.Click Start, point to All Programs, point to Administrative Tools, and then click SharePoint 3.0 Central Administration.
2.On the Central Administration page, click Operations.
3.On the Operations page, under Logging and Reporting, click Usage Analysis Processing.
4.In the Logging Settings section, click to select the Enable logging check box.
5.In the Log file location box, type the location where you want to store the log file.The default location for the log file is \Program Files\Common Files\Microsoft Shared\Web Server Extension\12\Logs.
6.In the Number of log files to create box, type a number between 1 and 30. In general, use a number that is one to three times the number of database servers in your server farm, with a maximum number of 30 log files.
7.In the Processing Settings section, click to select the Enable usage analysis processing check box.
8.Under Run processing between these times daily, specify the range of times to start the usage analysis log processing.In the Start box, select the earliest time of day to start running log processing. In the End box, select the latest time to start running log processing.
9.Click OK.

Refferance:-
http://support.microsoft.com/kb/825541

How to configure Usage Analysis Processing on a Web server that is running Windows SharePoint Services 2.0

Usage analysis processing is set up through SharePoint Central Administration. To do this, follow these steps:

-Click Start, point to All Programs, point to Administrative Tools, and then click SharePoint Central Administration.
-Under Component Configuration, click Configure usage analysis processing.
-In the Logging Settings section, click to select the Enable logging check box.
-In the Log file location box, type the location where you want to store the log file.The default location for the log file is c:\Windows\system32\LogFiles\STS.
-In the Number of log files to create box, type a number between 1 and 30. In general, use a number that is one to three times the number of database servers in your server farm, with a maximum number of 30 log files.
-In the Processing Settings section, click to select the Enable usage analysis processing check box.
-Under Run processing between these times daily, specify the range of times to start the usage analysis log processing.In the Start box, select the earliest time of day to start running log processing. In the End box, select the latest time to start running log processing.
-Click OK.

Refferance:-
http://support.microsoft.com/kb/825541

Move, Lock, and Delete Site Collections

Microsoft has recently released an update to the Central Administration site that makes it easy to move a Site Collection between different Content Databases. The Batch Site Manager can be very handy if you need to break up your content across multiple Content Databases – possibly sitting on different SQL Servers.

Batch Site Manager is a feature that is designed to be used by SharePoint farm administrators to manage and administrate bulk operations that involve moving, locking or deleting one or more site collections within a single Web application. To access the Move, Lock, and Delete Multiple Site Collections page, click the Move, Lock, and Delete Site Collections link located on the Application Management page of Central Administration. The same tool also allows you to lock and delete site collections:

http://technet.microsoft.com/en-us/library/cc508852(TechNet.10).aspx

Download Microsoft SharePoint Administration Toolkit

Move site collections
Lock site collections
Delete site collections
Batch Site Manager files

How to rename a SharePoint Server machine name.

Renaming a MOSS server is tough job. If anything goes wrong along the way chances are that you need to reconfigure your whole MOSS environment.

Here are the steps to take, and the order in which to take them if you want to rename a server that has MOSS already installed and configured on it:

1.Change each alternate access mapping for your MOSS/WSS deployment in Central Administration:

-Open Central Administration, "Operations" Tab, "Alternate access mappings" link -Modify each mapping item to reflect your newly chosen server name

2.Use stsadm.exe to invoke the "renameserver" command option:

-Open a command prompt window

-cd "C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN"

-stsadm -o renameserver -newservername -oldservername

3.Rename your Server via Change Name Operation in Windows Server 2003: Start Menu Control Panel System, "Computer Name" tab, "Change" button.

4.Input your new server name

5.Reboot the server NOW.

6.After reboot, open command prompt
-cd C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN -stsadm -o updatefarmcredentials -userlogin -password -iisreset /noforce

7.Check all application pool identities in IIS, update where the old machine name is still there.

8.If you already have a search index drop this, and rebuild it.

Your server is now renamed.

Limit SharePoint Designer to Certain Users

For this post, I am going to concentrate on using security permissions to limit access to SPD.

Below is a quick way to limit only certain users the ability to SPD.
-Out-of-the-box, users who have Full Control and Contribute security permissions can open SPD and make changes.
-Assuming you want only users with Full Control access to have access to SPD, the easiest way is to turn off access to the site from SPD for users under the Contribute permission level.
-Open the site
-Select Site Actions > Site Settings.
-Under the “Users and Permissions” group, click the “Advanced permissions” link.
-Select Settings > Permission Levels from the toolbar.
-Click on the Contribute link.
-Under Site Permissions, uncheck the “Use Remote Interfaces - Use SOAP, Web DAV, or SharePoint Designer interfaces to access the Web site.” option.
-Click OK

The issue with the above steps is now any user with Contribute access cannot use SPD. You may have some users who you still want access to SPD but do not want to give Full Control to. For that scenario, you could create a new permission level.

-Open the site
-Select Site Actions > Site Settings.
-Under the “Users and Permissions” group, click the “Advanced permissions” link.
-Select Settings > Permission Levels from the toolbar.
-Click on the Contribute link.
-Scroll to the bottom and click the “Copy Permission Level” button.
-For the Name, type in “Contribute (With SPD)” (without the quotes).
-For the Description, type in “Can view, add, update, and delete. With SPD support.” (without the quotes).
-Under Site Permissions, check the “Use Remote Interfaces - Use SOAP, Web DAV, or SharePoint Designer interfaces to access the Web site.” option.
-Click Create

Now the out-of-the-box Contribute permission level can contain all the users who need contribute access but no SPD. For those users you want to give SPD access to, they can be added to the “Contribute (With SPD)” group. One caveat is if you have other applications access the SharePoint web services for the site, they will no longer work.

This web site has been configured to disallow editing with FrontPage. Contact your web site administrator for more information

To prevent users from changing a Windows SharePoint Services 3.0 site or a SharePoint Server 2007 site, disable the authoring feature in SharePoint Designer 2007 by editing the Onet.xml file. By default, the Onet.xml file for Windows SharePoint Services 3.0 and for SharePoint Server 2007 is in the following folder:
\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\SiteTemplates\\xml

Note: Replace the placeholder with the name of the Windows SharePoint Service that is installed on the server.

For example, if the English (United States) version of Windows SharePoint Services is installed on the server, the SharePoint Team Site site template is located in the following folder:
Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\SiteTemplates\XML

To do this, follow these steps:
1.On the server that is running Windows SharePoint Services 3.0 or SharePoint Server 2007, locate the site template that you want to modify. Site templates are located in the following folders on the server:
-SharePoint Team Site: Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extentsions\12\Template\SiteTemplates\XML.-Meeting Workspaces: Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extentsions\12\SiteTemplates\MPS\XML

Note Replace the Drive placeholder with the drive where Windows is installed.

2.Right-click the Onet.xml file, click Open With, and then click Notepad.

3.Locate the Project Title tag, and then add the following line:

DisableWebDesignFeatures=wdfopensiteThen, click Save.
The complete Project Title tag is as follows:

4.Restart Internet Information Services (IIS). To do this, follow these steps:

-Click Start, click Run, type cmd, and then click OK.
-At the command prompt, type iisreset computer_name /restart, and then press ENTER.

Note: Replace the computer_name placeholder with the name of the computer that is running IIS.

After you follow these steps, users who try to open a site that is based on the site template that has the DisableWebDesignFeatures=wdfopensite attribute will receive the following message:
 
This web site has been configured to disallow editing with FrontPage. Contact your web site administrator for more information.
 
Warning: Do not edit a Windows SharePoint Services 3.0 site or a SharePoint Server 2007 site by using Microsoft Office FrontPage 2003. If you do this, you run a major risk of corrupting the site. Instead, always use SharePoint Designer 2007 to edit the site.

Server Error in '/' Application. The resource cannot be found.

Few Days before, in our project, we faced one issue while browsing the site. Don’t know, what gone wrong but got error message as mentioned below:-

Server Error in '/' Application.

HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly
The resource cannot be found.

Even if you have activated the possibility to see errors and trace in SharePoint (Web application web.config --> callstack="true", customerror="off", debug="true") you won't have a precise indication of what ressource is missing.

How to troubleshoot this error message? Here is the answer...

There are two ways by which you can resolve this error message:-

Method: 1

Just right click your page and choose "view source"

Method: 2

Under the root path in IIS configuration, under "Home Directory"under the field "local path". "c:\inetpub\mywebsite\" is not the same as "c:\inetpub\mywebsite" apparently now.

My site came back alive as soon as I removed the trailing backslash so that the path now says "c:\inetpub\mywebsite"

If you have any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Error Scheduling Crawls: Access is Denied (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

When you set up your SSPs one of the things you will come across is Crawl Scheduling. This comes under Search Settings and allows you to configure Incremental Crawls and Full Crawls to the frequency you would like. For example, Full crawl once a day, Incremental Crawl every 5 minutes of each day.

When we tried to set the schdule incremental crawl, we faced this error message. When we filled out all the information and tried to click on Ok.

When I hit Ok I received the error:
ACCESS is DENIED. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

Resolution:-
To fix this you need to add the account WSS_WPG to the C:\Windows\Tasks folder on your Index server and apply modify rights.

If you cannot see the Security tab on the Tasks folder you need to open a command prompt and type is:
attrib -s %windir%\tasks

When you right click on the tasks folder having done this you should be able to see the Sharing & Security option.

To remove the option once you have applied the changes to the folder open command prompt again and type:
attrib +s %windir%\tasks

I hope the above steps helps you to resolve this issue. All the Best!

.swf Files Won't Play in IE7

Few days before, when i tried to put shockwave pages (.SWF files) in pageviewer webparts, it did not work. After doing some research and troubleshooting, i compare my two systems: one was using IE 6.0 and other was using IE 7.0

The .SWF files are working fine in the machine where IE 6.0 is present but the problem is with the IE 7.0. I understand this arises from a security "feature" in IE7 that blocks "Cross-Domain" shockwave objects.

I found there's a registry hack that disables this "feature."

Solution for this as mentioned below:-

Create a key named HKLM\Software\Microsoft\Internet Explorer\Main\Feature Control\FEATURE_BLOCK_LMZ_SCRIPT and add a REG_DWORD value to the key of 0 which should show up as 0x000000 (0)

Now my page views with .swfs in them work just fine.

Cheers!!!

Happy SharePoint to all of you…

Post Mortem of SharePoint Content Database + common queries that we can run against the content databases

Conttent Database plays a very important role in SharePoint.There are some cases when we need to look into and read from the content databases.

NOTE: Never update any SharePoint database directly. Always use the SharePoint API (Object Model) for any updates.

Before beginning the postmortem of sharepoint content database, lets focused on basic sharepoint tables as how excately they function.
Features:Table that holds information about all the activated features for each site collection or site.
Sites:Table that holds information about all the site collections for this content database.
Webs:Table that holds information about all the specific sites (webs) in each site collection.
UserInfo:Table that holds information about all the users for each site collection.
Groups:Table that holds information about all the SharePoint groups in each site collection.
Roles:Table that holds information about all the SharePoint roles (permission levels) for each site.
AllLists:Table that holds information about lists for each site.
GroupMembership:Table that holds information about all the SharePoint group members.
AllUserData:Table that holds information about all the list items for each list.
AllDocs:Table that holds information about all the documents (and all list items) for each document library and list.

Here are some common queries that we can run against the content databases.
--Query to get all the top level site collections
SELECT SiteId AS SiteGuid, Id AS WebGuid, FullUrl AS Url, Title, Author, TimeCreatedFROM dbo.WebsWHERE (ParentWebId IS NULL)

--Query to get all the SharePoint groups in a site collection
SELECT dbo.Webs.SiteId, dbo.Webs.Id, dbo.Webs.FullUrl, dbo.Webs.Title, dbo.Groups.ID AS Expr1, dbo.Groups.Title AS Expr2, dbo.Groups.DescriptionFROM dbo.Groups INNER JOINdbo.Webs ON dbo.Groups.SiteId = dbo.Webs.SiteId

--Query to get all the users in a site collection
SELECT dbo.Webs.SiteId, dbo.Webs.Id, dbo.Webs.FullUrl, dbo.Webs.Title, dbo.UserInfo.tp_ID, dbo.UserInfo.tp_DomainGroup, dbo.UserInfo.tp_SiteAdmin, dbo.UserInfo.tp_Title, dbo.UserInfo.tp_EmailFROM dbo.UserInfo INNER JOINdbo.Webs ON dbo.UserInfo.tp_SiteID = dbo.Webs.SiteId

--Query to get all the members of the SharePoint Groups
SELECT dbo.Groups.ID, dbo.Groups.Title, dbo.UserInfo.tp_Title, dbo.UserInfo.tp_LoginFROM dbo.GroupMembership INNER JOINdbo.Groups ON dbo.GroupMembership.SiteId = dbo.Groups.SiteId INNER JOINdbo.UserInfo ON dbo.GroupMembership.MemberId = dbo.UserInfo.tp_ID

--Query to get all the sites where a specific feature is activated
SELECT dbo.Webs.Id AS WebGuid, dbo.Webs.Title AS WebTitle, dbo.Webs.FullUrl AS WebUrl, dbo.Features.FeatureId, dbo.Features.TimeActivatedFROM dbo.Features INNER JOINdbo.Webs ON dbo.Features.SiteId = dbo.Webs.SiteId AND dbo.Features.WebId = dbo.Webs.IdWHERE (dbo.Features.FeatureId = '00BFEA71-D1CE-42de-9C63-A44004CE0104')

-- Query to get all the users assigned to roles
SELECT dbo.Webs.Id, dbo.Webs.Title, dbo.Webs.FullUrl, dbo.Roles.RoleId, dbo.Roles.Title AS RoleTitle, dbo.UserInfo.tp_Title, dbo.UserInfo.tp_LoginFROM dbo.RoleAssignment INNER JOINdbo.Roles ON dbo.RoleAssignment.SiteId = dbo.Roles.SiteId AND dbo.RoleAssignment.RoleId = dbo.Roles.RoleId INNER JOINdbo.Webs ON dbo.Roles.SiteId = dbo.Webs.SiteId AND dbo.Roles.WebId = dbo.Webs.Id INNER JOINdbo.UserInfo ON dbo.RoleAssignment.PrincipalId = dbo.UserInfo.tp_ID

--Query to get all the SharePoint groups assigned to roles
SELECT dbo.Webs.Id, dbo.Webs.Title, dbo.Webs.FullUrl, dbo.Roles.RoleId, dbo.Roles.Title AS RoleTitle, dbo.Groups.Title AS GroupNameFROM dbo.RoleAssignment INNER JOINdbo.Roles ON dbo.RoleAssignment.SiteId = dbo.Roles.SiteId AND dbo.RoleAssignment.RoleId = dbo.Roles.RoleId INNER JOINdbo.Webs ON dbo.Roles.SiteId = dbo.Webs.SiteId AND dbo.Roles.WebId = dbo.Webs.Id INNER JOINdbo.Groups ON dbo.RoleAssignment.SiteId = dbo.Groups.SiteId AND dbo.RoleAssignment.PrincipalId = dbo.Groups.ID

These are just some of the common queries that I have used against the content database.

Enjoy!!!

Office Server Search Service cannot be started because it does not exist.(Object reference not set to an instance of an object)

Office Server Search Service cannot be started because it does not exist.
Few Days before, I tried to setup my lab and after the installation, i tried to start the search service but mystery is here, when i checked CA-operations-services on server-OSEARCH is not there. I have the right key , the right CD and the latest fixes.I installed it and it is simply not there.
As you can probably guess, there’s nothing wrong with your PC or Cd or key, you simply did not installed the server in the correct way to receive all the services.

Please check:-
regedit and check the value under the following key :
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\WSS\
ServerRole
Possible options:
WFE
APPLICATION
SINGLESERVER

Each option means :
WFE - Windows SharePoint Services Web Application (no search , no excel, no ssp, just web server)
APPLICATION –Everything (and you can add the server to a farm)
SINGLESERVER –Everything (but you cannot add the server to a farm , and most probably you have MSDE or SQL Server Express on the box too)

To change the installation mode for the server (even if you managed to create webapplications and set-up your sharepoint config db), here’s the procedure:
-Detach the server from the farm
-Uninstall Sharepoint
-Reboot the server
-Re-install Sharepoint in Advanced mode and select your desired server role.
-Run the configuration wizard and re-attach the server to the original farm (config_db)
You should get the applications back and everything else in place, as they were but with new services in the farm.

This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms‏

After you upgrade from Microsoft ASP.NET 1.1 to Microsoft ASP.NET 2.0, some ASP.NET-based applications may not function correctly. Additionally, when you access ASP.NET Web pages that have ViewState enabled, you may receive the following error message:
[InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.]

This problem occurs when the following conditions are true:
-The HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\fipsalgorithmpolicy registry subkey is set to 1.
-ASP.NET 2.0 uses the RijndaelManaged implementation of the AES algorithm when it processes view state data. The ReindaelManaged implementation has not been certified by the National Institute of Standards and Technology (NIST) as compliant with the Federal Information Processing Standard (FIPS). Therefore, the AES algorithm is not part of the Windows Platform FIPS validated cryptographic algorithms.
Resolution:-
http://support.microsoft.com/kb/911722

Note:-Please follow each step carefully within this document and the issue will be definately resolved.

I hope the above document helps you to overcome the above mentioned error message. Thanks!

Move the SharePoint data from c:\ drive to d:\ drive

=Opened Central administration page and checked for no of web applications & system account (administrator) which is used for those web applications.

=Stopped all SharePoint related IIS web sites

=The following Services had set to Manual:
-Windows SharePoint Services Administration
-Windows SharePoint Services Timer
-Windows SharePoint Services Search
-Windows SharePoint Services Tracing
-Office Document Conversions Launcher Service
-Office Document Conversions Load Balancer Service
-Office SharePoint Server Search
-Indexing services
-IIS Admin Service

= Opened SQL Server Management Studio
= Expanded the Databases section
= For each SharePoint database we need to move, we must perform the following:
-Right clicked on the database
-Clicked on Properties
- Selected Files from the left hand pane
-Make note of the Path
-Clicked on Cancel
-Right clicked again on the database
-Selected Tasks -> Detach..
-Clicked the checkbox for Drop Connections. By default, the checkbox for keep Full Text Catalogs should be checked. Make sure that is true.
-Clicked OK
-For each additional database we need to move, perform the detach method for each
= Once we have detached all the databases, opened a Explorer window, and browse to the database location that was noted in the Properties task
= Selected the databases to be moved
= Right clicked, and selected Copy
= Browse to the new location for the databases
= Right clicked, and selected paste
= Go back to SQL Server Management Studio
= Right clicked on Database and selected Attach
= Clicked on Add..
= Browse to the new location for the databases and selected a database
= We have added each database one at a time
= reset all the services you set to manual in Step 2 to Automatic and started services.
= Turned on all IIS websites that we have stopped
= Browse to your central administration site; we were able to browse all sites correctly.
I hope the above steps will helps you to move your sharePoint databases from one drive to another drive. Thanks!

Moving documents between document libraries in MOSS 2007

There are several ways to move documents between SharePoint document libraries and one of the simplest ways to do this is to use the explorer view.

Here's a step by step reference on how to use the explorer view feature to migrate documents between document libraries.

Open the source and destination document libraries in two separate Internet Explorer windows.

Now select the explorer view

Now copy the source file by simply right clicking the mouse and selecting copy, then paste the file in the destination document library. It's important to remember that when you move documents between document libraries you lose the document version history.

Some users may experience an annoying popup when copying and pasting.

The way to turn this off is to make a change to the client's Internet Explorer:

-Open Internet Explorer

-Click "Tools", then "Internet Options"

-Select the "Security" tab

-Choose the appropriate zone

-Click the "Custom level" button

-Select "Enable" for the "launching programs and files in the IFRAME" option

-Click the "OK" button

-Click "Yes" when prompted to change the settings

-click the "OK" button

-Restart IE.

If you have any queries/questions regarding the above mentioned information then please let me know.

I would be more than happy to help you as well as resolves your issues, Thank you

Microsoft Office SharePoint Server (MOSS 2007) Versions

How do you find out what version of SharePoint you are running?

The first approach is to open a web browser and got to the site settings page (Site Actions > Site Settings > Modify All Settings).

The second approach is against the databases. Open SQL Server Management Studio, Connect to the server, new query, run the following:
SELECT [VersionId]
,[Version]
,[Id]
,[UserName]
,[TimeStamp]
,[FinalizeTimeStamp]
,[Mode]
,[ModeStack]
,[Updates]
,[Notes]
FROM [SharePoint_Config].[dbo].[Versions]
WHERE VersionId = '00000000-0000-0000-0000-000000000000'
ORDER BY Id DESC
This returns :-

The top row is the latest version. The query is performed on the SharePoint Configuration database. If you have called this database something instead of "SharePoint_Config" change the query to reflect this.
You can also look at the versions for Content Databases, by changing the database name. For example: FROM WSS_Content_MySites.[dbo].[Versions]

WSS SP1:- Download

MOSS SP1:- Download

MOSS 2007 post SP1 hotfix KB941422

MOSS 2007 post SP1 hotfix KB941274

MOSS 2007 post SP1 hotfix KB948945

MOSS 2007 Infrastructure Update KB951695 & KB951297

MOSS 2007 Cumulative update KB956056 & KB956057