By the way...

Go to the application you are deploying your feature to, and open web.config and make following changes in the given sections (CustomeErrors, compilation and SafeMode sections are already there): <customErrors mode="Off" /> <compilation debug="true"… <SafeMode CallStack="true"… Now press F5 and it should start debugging your projects/features/solutions created with VSeWSS.

I faced this issue after installing VSeWSS (Visual Studio Extensions for Windows SharePoint Services) V1.3. O/S was Windows Server 2003 SP2 and I was trying to package my solution for SharePoint in Visual Studio 2008 when it kept failing by giving following errors: “The HTTP request is unauthorized with client authentication scheme 'Negotiate'. The authentication header received from the server was 'Negotiate,NTLM'."" and (at times when I was trying different things) the following error: “The HTTP request is unauthorized with client authentication scheme 'Negotiate'. The authentication header received from the server was 'Negotiate,NTLM'.” Do the following to resolve, go to (try after each step in order): 0. If you are using domain account, make sure you are connected to that domain otherwise user (against which the VSeWSS site application pool is running) will not be able to authenticate. 1. Follow this article and make sure IIS en...

I am assuming that you already have WSS/MOSS installed on your system and you are using Visual Studio 2008. 1. Download and install VSeWSS (Visual Studio Extensions for WSS) http://www.microsoft.com/downloads/en/details.aspx?FamilyID=B2C0B628-5CAB-48C1-8CAE-C34C1CCBDC0A&displaylang=en 2. Create new project and select SharePoint group on the left. Then select Empty from the templates (make sure SharePoint group of template is selected). Name the project "MyTest". (that means, this is also going be your assembly name). Select "Partial Trust" when it asks. 3. Add new class, say "MyNewHandler". 4. Inherit the new class from "System.Web.IHttpHandler". 5. Right click on the "System.Web.IHttpHandler" and click "Implement". 6. Modify your code to look like the following: public bool IsReusable { get { return false; } } public void ProcessRequest(HttpContext context) { context.Response.Writ...

If you want to move a MOSS 2007 databases over to a new DB server, do the following: 1. Run SharePoint configuration wizard (on the web server) 2. Disconnect from existing configuration database (on web server) 3. Move the SITE database over to the new database server (on DB server) 4. Run configuration wizard again and create a new farm (on web server) 5. Give NEW database server and NEW configuration database (on web server) 6. After configuration wizard is finished, create web application by going in the SharePoint Cetral Admin (on web server) 7. Give it any web site name. Here you'll specify the New database server and OLD SITE db name. Hit OK. That's it. So only the combination of New DB server and Old Database name are important to specify in all this scenario. Now open web browser and open the site with same URL that it had been running before. You can also follow other processes like descriped on "Ron Grzywacz's Blog"

In Upgrade.log file generated after running upgrade by clicking "Begin Upgrade" in central administration of MOSS, I found following errors in log when upgrading from SharePoint 2003 to MOSS 2007. "[ProfileDatabaseSequence] [ERROR] [12/21/2008 3:07:31 AM]: Action 12.0.18.0 of Microsoft.SharePoint.Portal.Upgrade.ProfileDatabaseSequence failed. [ProfileDatabaseSequence] [ERROR] [12/21/2008 3:07:31 AM]: The statistics 'SectionName' is dependent on column 'SectionName'. ALTER TABLE DROP COLUMN SectionName failed because one or more objects access this column." I used following query to find table having column "SectionName" in the database, since i didnt know which table had it: SELECT name FROM sysobjects WHERE id IN ( SELECT id FROM syscolumns WHERE name = 'SectionName') It returned "ProfileUI" table name. I expanded the "ProfileUI" table in SPS2003's Profile DB and then explanded "Statistics". T...

I created a web service in .NET and placed it in the "_layouts" folder and created Application in IIS. Somehow, the application pool of it was not the same as of SharePoint site's App Pool in which it was placed. It caused following error: An error occurred loading a configuration file: Failed to start monitoring changes to "<your virtual directory here>" because access is denied. Changing the App pool of the web application for the web service to the one SharePoint site had fixed the problem.

I created a batch file that every time I have to update my particular feature, it eases the job. One can create such file to speed up the development process: My Installfeature.bat contents look like this: set folderpath = "C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\" %folderpath%BIN\stsadm -o deactivatefeature -name MyProject -url http://test.mysharepintsite.com %folderpath%BIN\stsadm -o uninstallfeature -name MyProject %folderpath%BIN\stsadm -o installfeature -name MyProject %folderpath%BIN\stsadm -o activatefeature -name MyProject -url http://test.mysharepintsite.com iisapp.vbs /a "DefaultAppPool" /r