Dhiraj Moghe's - SharePoint World

SharePoint 2007 Alerts not triggered

Jardhi — Wed, 25 Jan 2012 03:56:33 GMT

Technorati Tags: MOSS,Alerts,Initial email,SMTP

Issue: Recently we saw a sudden rise in the issue where SharePoint 2007 alert emails are not being received by users including the the initial email that says you signed up for an alert. All other outgoing email functions are also not working. When you go ahead and subscribe for an alert and click OK, the alert page hangs while creating. You are able to send email using Telnet command to the SMTP server.

Cause: In our case it was the Sophos Antivirus on the SharePoint server, the new antivirus definition changes the Winsock order on the server. Here is how it looks when the issue occurs using the tool SPOrder.exe or if you use the command line tool : "netsh winsock show catalog" command, which would show the antivirus web scan intelligence sitting ahead of TCP.

Resolution: Change the winsock provider order with the sporder.exe tool & Make sure the MSAFD Tcpip [TCP/IP] is placed above any UDP providers.
sporder.exe is a GUI tool part of the windows platform SDK.

If you have x64 bit Operating System,change the order using the tool and then follow these steps and restart the system to apply the changes.

Backup the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\Protocol_Catalog9 registry hive with regedit.exe into winsock_backup.reg
Export HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters\Protocol_Catalog9\Catalog_Entries with subkeys to winsockproviderorderfix64.reg
Open winsockproviderorderfix64.reg in notepad and replace \Catalog_Entries\ with \Catalog_Entries64\ and in the 3rd line replace \Catalog_Entries with \Catalog_Entries64
Save the reg file and double click it to make the changes in the registry

More Info : https://support.microsoft.com/kb/2000689

Office 2010 Web Application Workshops and experts coming soon to a city near you…

Jardhi — Wed, 23 Feb 2011 14:16:48 GMT

Thinking about setting up Microsoft Office 2010 Web Applications in your environment? Curious about Excel, OneNote, PowerPoint and Word web applications?

If the answer to any of the above questions is yes, you should consider attending one of the Office 2010 Web Application workshops that will be delivered in cities around the country in the coming months.

The Office 2010 Web Applications workshop is designed to provide you with information regarding best practices on installation, manage, and usage of the Office web applications of PowerPoint, Word, Excel, and OneNote 2010.

Key Focus Areas:

· Setup of Office web applications

· Server Architecture

· The Companions

· Introduction to Excel Word, PowerPoint, and OneNote web applications

IT Professionals responsible for the deployment, maintenance, and troubleshooting of Office installations. Application-specific and/or help desk-type issues are not included in the scope of this offering.

Delivery Dates and Locations:
April 5-6, 2011 – Irving, TX
April 19-20, 2011 – Irvine, CA
May 3-4, 2011 – Downers Grove, IL
May 17-18, 2011 – New York, NY
June 1-2, 2011 – Tampa, FL
New dates and locations will be announced here as they become available.

Pricing:
$1000 USD per person

To register or for more information:

• To register online, visit https://www.microsoft.com/events, click the Find Events and Webcasts link, and perform an advanced search using the following EventIDs or keywords "Office 2010 Deployment":

o    Las Colinas: 1032479205
o    Irvine, CA: : 1032479318
o    Downers Grove, IL: 1032479319
o    New York, NY: 1032479324
o    Tampa, FL: 1032479329

• To register via email, send mail to ProfessionalServices@Microsoft.com and include the following information:

o    Company Name
o    Attendee Name
o    Physical Address
o    Phone Number
o    Number of Attendees
o    Desired Event Location/Date

• To register via phone, call 1-888-875-9071

• Email inquiries to ProfessionalServices@Microsoft.com

SharePoint 2010 : Unable to connect to the search service after Search Service Application restoration

Jardhi — Wed, 01 Dec 2010 00:40:50 GMT

Issue:

After restoring the Search service application from the SharePoint 2010 Central Administration site successfully. When you try to perform a search, it gives the following message : The search request was unable to connect to the Search Service.

Cause:

Check if you have the Search Application proxy restored successfully under the Search Service Application, if not then that’s where the problem lies.

So when you take a Search Service Application backup from Central Administration site. Ensure that you take the backup of the Search service application proxy separately.

By default, the backup UI from Central Administration site, allows you to only take one at a time. Which means that you have to perform backup twice. One for
1. Search Service Application
2. Search Service Application Proxy

So if you have deleted the Search Service Application from the UI before taking the Search service application proxy backup, then you can create the proxy using PowerShell.

Workaround:

The below command will fetch the name of the Search service application in the variable, it is useful when you have multiple Search service application and was a specific SSA has an issue:

$getsearchapp = get-spenterprisesearchserviceapplication ""

This command provided the name of the proxy to the associated with the Search service application.
$setproxy = new-spenterprisesearchserviceapplicationproxy -name "Name of the Search Service Application Proxy" -Uri $getsearchapp.uri.absoluteURI

Verify the search service application proxy is online. It should be online by default.
$setproxy.status

If it's not online, you can run the following command to change the status:
$proxy.status = “online”

Hope this helps.

Migrate users and permissions from MOSS 2007 FBA to SharePoint 2010 FBA

Jardhi — Mon, 09 Aug 2010 08:03:59 GMT

This article will help you to migrate MOSS 2007 FBA to SharePoint 2010 claims based web application configured with FBA and successfully access the MOSS 2007 FBA site in SharePoint 2010 after migration.

If you have a MOSS 2007 FBA site using ASPNetMemberShip provider, for migrating to SharePoint 2010, you need to update the STS web.config file as mentioned in my earlier blog.

After successfully attaching the content database to the Claims based SharePoint 2010 FBA site, you will be able to add the users (NT users and the FBA users) through the Central Admin site. But when you try to browse to the site, you get access denied using both the NT users and the FBA users.

This is because the users trying to login to the Claims based SharePoint 2010 FBA site are not claims aware and the hence you will need to convert the existing Web applications to claims authentication and then migrate users and permissions from SharePoint Server 2007 to SharePoint Server 2010.

Convert the existing Web applications to claims authentication, follow the steps below :

1. On the Start menu, click All Programs.
2. Click Microsoft SharePoint 2010 Products.
3. Click SharePoint 2010 Management Shell.
4. From the Windows PowerShell command prompt, type the following:

    $w = Get-SPWebApplication "https://>/"
    $w.UseClaimsAuthentication = 1
    $w.Update()
    $w.ProvisionGlobally()

For migrating users and permissions from SharePoint Server 2007 to SharePoint Server 2010, follow the below steps:

1. On the Start menu, click All Programs.
2. Click Microsoft SharePoint 2010 Products.
3. Click SharePoint 2010 Management Shell.
4. From the Windows PowerShell command prompt, type the following:

$w = Get-SPWebApplication "https://>/"
$w.MigrateUsers(1)

These steps are echoed from the following TechNet article :

Configure forms-based authentication for a claims-based Web application (SharePoint Server 2010)

For more information, please refer Configure the security token service and Brokered Authentication: Security Token Service (STS)

Configure Forms Based Authentication(FBA) using ASPNetMembershipProvider for Claims based web applications in SharePoint 2010

Jardhi — Wed, 04 Aug 2010 07:30:00 GMT

This article willl help you to configure FBA using ASPNetMembership provider on a claims based web application. Here are the steps that are needed to configure SQL for MemberShip store:

Create SQL database
Create SQL User in the SQL database

To Create SQL Database for the SQLMembershipProvider

1. Install and then open the Visual Studio 2008

2. Select new website, select template as ASP.NET web site and select language as C#

3. Once you have the website created, click on Website menu and select the ASP.NET configuration..

4. Once you click on it, it will take you to : \&applicationUrl=/websitename">https://localhost:53663/asp.netwebadminfiles/default.aspx?applicationPhysicalPath=C:\\&applicationUrl=/websitename

5. Click on Providers and Click the Select a different provider for each feature (advanced)

6. Test both the Membership Provider & Role Provider and ensure that it is successful.

7. Now click on the Security tab and Select authentication type under Users
8. Select the option “From the internet" and click on Done.
9. Click on Create User and enter all the field required and click on “Create User”.
10. Once you have created the user, right on the website that we created in the VS 2008 and click on the refresh folder, you will now see the following database : ASPNETDB.MDF
11. Close the web site from VS 2008 and browse to the location where you created the web site like C:\\App_Data
12. Copy the MDF and LDF files and rename if required and then paste it in the directory where you have the SQL server databases.
13. Attach the database to the SQL database server using SQL Management Studio with whatever name you wish you have.

You can create the ASP.NET membership database using this method:

1. On the SQL server, open Windows Explorer.
2. Navigate to the path %System Drive%\Windows\Microsoft.NET\Framework\v2.0.50727.
3. To start the ASP.NET SQL Server Setup Wizard, double-click aspnet_regsql.exe.
4. Start the wizard by clicking Next, and then complete the wizard :

5. Click Configure SQL Server for application services, and then click Next.

6. In the Server box, type aspnetdb for the database name, and then click Next

7. Confirm that the data you typed is correct, and then click Next

8. The database is created and the final status information is displayed. Click Finish to complete the wizard

To perform the tasks such as creating users and groups and managing passwords, you can use the tool named MembershipSeeder. The tool and source code are available on CodePlex from the MemberShipSeeder page. You can use the MembershipSeeder tool as is for simple user and role management, or you can use the source code as a base on which to create your own tool; however, Microsoft does not provide support for this tool.

Before you create users from the MembershipSeeder tool

Start the MembershipSeeder tool. Click Configure.
In the dialog box that opens, type the name of the computer running SQL Server that hosts your SQL membership database.
Save your changes, and then restart MembershipSeeder so that it will use the new server name.

To create users for testing purposes

In the User Prefix field, type a value.
In the Password field, type the password you want each user to have.
In the # of Users field, select the number of users to create.
Click Create to create users where the user name is the value of the User Prefix field with an incrementing number added to the end.

You can also refer the following : https://msdn.microsoft.com/en-us/library/bb975136(office.12).aspx

Now that we have created the users, lets create the web application by selecting the authentication as Claims Based Authentication:

Select the Claims Authentication Type as shown below, you can either use “NTLM” or “Negotiate(Kerberos or NTLM)” for Windows Authentication.I have selected NTLM in this example

Once the web application is created, we will need to edit 3 web.config files for enabling claims:

1.The web.config file of the Central Administration site.
2.The web.config file of the Web Application.
3.The web.config file of the STS (SecurityTokenService) Application. This is important because it is this service that will ensure claims tokens are being passed correctly between the SQL provider and the Central Admin and the Web Application.

Central Administration web.config changes:

Place the below snippet between & in the web.config

In the Web Application web.config changes:

Place this between & in the web.config

Place this between &

In the following location : C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebServices\SecurityToken

Place the below code between : &

NOTE: ensure that you have taken the backup of the web.config file before making changes.

Now go ahead and add a user by going to User Policy ribbon option in the Web Applications Management page having selected the web application. Hit Add Users in the Policy for Web Application dialog. Use the Browse button in the Choose Users people picker control. You will now see sections like Active Directory, All Users, Forms Auth & Organizations. When you search for users, it would now tell you if its AD or Forms Auth as seen below.

Add the user to the site and browse to the site. You should be able to successfully login to the site.

Hope this helps!!!

How to manually uninstall the Microsoft SharePoint Server 2007

Jardhi — Sat, 19 Jun 2010 17:15:53 GMT

Technorati Tags: Manual,uninstall,SharePoint 2007,MOSS 2007

Sometimes you might have to re-install the SharePoint binaries again on the server trying to fix some corruption.

When you click on the uninstall or change button in the Add/Remove program, you get error message like :

“This product installation has been corrupted. Run setup again from the CD, DVD, or other original installation source.”

Before you begin the manual uninstall procedure, ensure that you have taken a working backup of the databases and the farm and that you disconnect the SharePoint server from the existing farm either by:

>> Running the “SharePoint Products and Technologies Configuration Wizard” and disconnecting the SharePoint server OR
>> By running the following command: psconfig –cmd configdb -disconnect

Steps to uninstall SharePoint 2007
--------------------------------------------
- Disable and Stop the following services:
    Microsoft Single Sign-on Service
    Windows SharePoint Services Administration
    Office SharePoint Server Search
    Windows SharePoint Services Search
    Windows SharePoint Services Timer
    Windows SharePoint Services Tracing
    Windows SharePoint Services VSS Writer

- Note the following registry keys:
From HKLM\Software\Microsoft\Office Server\12.0
InstallPath (default is C:\Program Files\Microsoft Office Servers\12)

From HKLM\Software\Microsoft\Shared Tools\Web Server Extensions\12.0
Location (default is C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12)

- Take a Registry hive backup and then delete the following registry hives:

    HKLM\Software\Microsoft\Office Server\12.0
    HKLM\Software\Microsoft\Shared Tools\Web Server Extensions\12.0
    [x32] - HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\OSERVER
    [x64] - HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\OSERVER

- Then delete the following folders:
The value of the InstallPath key
The value of the Location key

- If you are unable to delete the folder, due to any dll /file in used / locked , you can either reboot the server or use Process Explorer tool
https://technet.microsoft.com/en-us/sysinternals/bb896653.aspx

- After Deleting the above folders successfully, Uninstall SharePoint using Windows Installer Cleanup utility:
Download the tool from https://support.microsoft.com/kb/290301

- Select the entries that start with
“Microsoft Office SharePoint *.*” ,“Microsoft SharePoint Service *.*” and “Microsoft.Office*.*” having the same binaries version as the Server and select remove.

NOTE:

If you have any other Microsoft Office product (like Project server, PerformancePoint) installed on the server, you will find these Products also to remove. Carefully select ONLY the ones having the same binaries version as the SharePoint Server and not the other ones.

- You can run the binaries again and ensure that it is successfully, now you can again try to do a clean uninstall from the Add/Remove program and in supported state.

Hope this helps.

Demos and training for Office SharePoint Server 2007

Jardhi — Mon, 31 May 2010 01:21:42 GMT

Hello All,

Here is another set of videos and training material for Office SharePoint Server 2007.

Demo: Prepare to back up Office SharePoint Server 2007
https://technet.microsoft.com/en-us/library/cc811605(office.12).aspx

Demo: Back up and restore farms and site collections by using built-in tools
https://technet.microsoft.com/en-us/library/cc424947(office.12).aspx

Demo: Add a library to a Records Center site
https://technet.microsoft.com/en-us/library/cc263523(office.12).aspx

Demo: Deploy an administrator-approved form template
https://technet.microsoft.com/en-us/library/cc263365(office.12).aspx

Demo: Enable Excel Services and data connections for a SharePoint team site
https://technet.microsoft.com/en-us/library/cc263352(office.12).aspx

Demo: Configure a SharePoint Server 2007 site to receive e-mail
https://technet.microsoft.com/en-us/library/cc263459(office.12).aspx

SharePoint Server demos
https://office.microsoft.com/en-us/sharepointserver/CH102066971033.aspx

The last link gives you opportunity to view 36 various demos and video related to SharePoint 2007 Server.

Hope you all enjoy these demos and video and have a good learning experience.

Enjoy the reading!!!

Training videos for SharePoint Enterprise search

Jardhi — Mon, 31 May 2010 01:03:58 GMT

Building and implementing enterprise search solutions
--------------------------------------------------------

The presentations provide details about key enterprise search capabilities in Microsoft Office SharePoint Server 2007.

Module 1: Workshop Overview
(https://go.microsoft.com/fwlink/?LinkId=115635&clcid=0x409)

Module 2: Enterprise Search Overview
(https://go.microsoft.com/fwlink/?LinkId=115636&clcid=0x409)

Module 3: SharePoint Search 2007 Walkthrough
(https://go.microsoft.com/fwlink/?LinkId=115637&clcid=0x409)

Module 4: Search Architecture and Deployment Scenarios
(https://go.microsoft.com/fwlink/?LinkId=115638&clcid=0x409)

Module 5: Crawl and Query Processes
(https://go.microsoft.com/fwlink/?LinkId=115639&clcid=0x409)

Module 6: Relevance Ranking
(https://go.microsoft.com/fwlink/?LinkId=115640&clcid=0x409)

Module 7: Customizing the End-User Experience
(https://go.microsoft.com/fwlink/?LinkId=115641&clcid=0x409)

Module 8: Developing Search Solutions
(https://go.microsoft.com/fwlink/?LinkId=115642&clcid=0x409)

Module 9: Business Data Catalog Search
(https://go.microsoft.com/fwlink/?LinkId=115643&clcid=0x409)

Module 10: Extensibility and Integration for Search
(https://go.microsoft.com/fwlink/?LinkId=115644&clcid=0x409)

Module 11: Search Administration
(https://go.microsoft.com/fwlink/?LinkId=115646&clcid=0x409)

Module 12: Security for Search
(https://go.microsoft.com/fwlink/?LinkId=115647&clcid=0x409)

Module 13: Performance Scalability and Capacity Planning for Search
(https://go.microsoft.com/fwlink/?LinkId=115648&clcid=0x409)

Module 14: Search Operations
(https://go.microsoft.com/fwlink/?LinkId=115649&clcid=0x409 )

Hope these videos are helpful for understanding the SharePoint Search!

Search Service is Offline… when clicked on Search Settings page of Shared Services Provider

Jardhi — Thu, 07 Jan 2010 07:52:40 GMT

BEHAVIOR:

On MOSS 2007 SharePoint Farm, You might sometime land on the following messages:

1. When clicked on the Search Settings page of the Shared Services Administration: The search service is currently offline. Visit the Services on Server page in SharePoint Central Administration to verify whether the service is enabled. This might also be because an indexer move is in progress

2. When you try to Reset All Crawled content, you get the following message : Exception from HRESULT: 0x80040D1B or

3. Event ID : 6482 ; “Reason: Exception from HRESULT: 0x80040D1B” or

4. Event ID : 6398; “Exception from HRESULT: 0x80040D1B”

ENVIRONMENT:

MOSS 2007 (single or multi server farm)

RESOLUTION: You will need to follow the step given below:

Stsadm –o osearch –action stop on the Index server

Stsadm –o osearch –action stop on the Query server

The above command will remove all the indexes that were already built by previous crawl. I have seen that even after performing the above command and resetting the crawled contents from the SSP, the indexes are still on the disk.

So the best way to go ahead is to set a new Index location on the Index server and the Query server.

On the Index server box, run the following stsadm command to enable Index role :

stsadm –o osearch -action start -role Index -farmcontactemail -farmserviceaccount] -farmservicepassword –defaultindexlocation

On the Query box, run the following stsadm command to enable Query role :

stsadm -o osearch -action start -role Query -defaultindexlocation

Then run the following stsadm command on the Query server to enable the share:

stsadm -o osearch –propagationlocation

Details : https://technet.microsoft.com/en-us/library/cc262920.aspx

Once you have successfully completed the command, you will be able to access the Search Administration page and may see the following :

Server status shows status as “Error” and Crawl Status also shows status as “Error”

Follow the steps provided in the KB article https://support.microsoft.com/kb/962928 and run the below command:

selfssl /s:951338967 /v:1000

The Server status no longer shows “Error” message and shows the actual Query server location size.

When you click on the Search Setting page, you may still not able to open the page and get the 403 forbidden error message.

Follow the KB article https://support.microsoft.com/kb/926959

Now you should be able to access the Search Administration page as well as the Search Settings page of the Shared Services Provider without any error message.

Hope this was helpful.

Troubleshooting Solution (.wsp) Deployment

Jardhi — Sat, 03 Oct 2009 13:11:16 GMT

This article help you troubleshoot issue while deploying solution package and successfully complete the solution deployment:

Once you have got your solution (.wsp) package for deployment, you will have to add the solution to the solution store using the command:

stsadm -o addsolution -filename

Details : https://technet.microsoft.com/en-us/library/cc263162.aspx

Once the solution is added to configuration database, you have to deploy it to the individual front-end Web servers in the farm. You have a choice to either deploy from the GUI of Central Administration page or from the command line.

If you are going to deploy from command line, use the following command:

stsadm -o deploysolution -name [-url]

[-allcontenturls] [-time] [-immediate] [-local]

[-allowgacdeployment] [-allowcaspolicies] [-lcid] [-force]

Details : https://technet.microsoft.com/en-us/library/cc262459.aspx

If you are facing issue like the status is showing as “deploying” then you will need would like to know where is it stuck? Enable verbose logging for all or for the following categories : Timer and Topology. Most likely it would be timer service stuck or waiting for a job to complete.

Try using the command : stsadm – o execadmsvcjobs

If the solution is still hung state, you can cancel the deployment of the solutions by using the following commands:

1. stsadm -o enumdeployments

It will list out the Windows SharePoint Services Solution Package (*.wsp) and Web Part packages located in the solution store of the farm. along with the deployment IDs.

2. stsadm -o canceldeployment -id

This will retract the solution package deployment.

3. stsadm -o deletesolution -name

Hope this will help you!