Dev Team Assemble » Configuration

SQL Server Recovery Model – Modification Script

Calvin — Thu, 20 Oct 2011 15:59:41 +0000

I often find in my sharepoint development environments that I have issues with transaction logs filling up. This gives me the "Error" page with no indication of what the problem is...yes I can go and change the tag to set the customer errors mode to off and add the callstack to the page but it still doesn't address the problem. I whipped this script up because the dev sql server we are using has well over a hundred db's on it and I didn't fell like manually typing the ALTER DATABASE [xxx] SET RECOVERY SIMPLE for each one or doing the clickity click thing either. Now the solution below probably breaks lots of best practices and such but it works for what I wanted it to do....which is modify all existing db's recovery mode. To modify new db's recovery mode, just set the model db's option to simple and voila..you are ready to go.

Quick note: YOU PROBABLY DO NOT WANT TO EVER...I MEAN EVER...USE THIS ON A PRODUCTION SYSTEM.

*/


	Modify th recovery model for all databases on your server
*/
	DECLARE @lasterror int
	DECLARE @sql nvarchar(max)
	DECLARE @dbname nvarchar(100)
	DECLARE @dbid int
	DECLARE @recModel int
	-- cycle the log
	exec sp_cycle_errorlog 
	CREATE Table #dbInfo
	(
		database_id int NOT NULL,
		dbName nvarchar(100) NOT NULL,
		recoveryModel int
	)
	--SELECT database_id, [name], recovery_model FROM sys.databases order by database_id
	SELECT TOP 1 @dbid = database_id FROM sys.databases where database_id > 4  ORDER BY database_id asc;
	SELECT @dbname = [name] FROM sys.databases where database_id = @dbid;
	SELECT @recModel = recovery_model FROM sys.databases where database_id = @dbid;
	-- begin backup process
	WHILE @dbid > 0
	BEGIN
		INSERT INTO #dbInfo (database_id, dbName, recoveryModel) VALUES (@dbid, @dbname, @recModel);
		IF @recModel = 1
		BEGIN
			SELECT @sql = 'ALTER DATABASE [' + @dbname + '] SET RECOVERY SIMPLE'
			EXEC sp_executesql @sql
			SELECT @lasterror = @@ERROR
			IF @lasterror <> 0
				-- log the error to the message console
				PRINT 'ERROR: Changing the recovery mode for database : ' + @dbname + ' with error number ' + CAST(@lasterror as nvarchar(25))
			ELSE
				PRINT 'Recovery mode changed to simple (3) for database : ' + @dbname
		END
		-- get a new record
		SELECT @dbid = 0;
		SELECT TOP 1 @dbid =  database_id FROM sys.databases where database_id > 4 and
			database_id NOT IN (SELECT DISTINCT x.database_id FROM #dbInfo x);
		SELECT @dbname = [name] FROM sys.databases where database_id = @dbid;
		SELECT @recModel = recovery_model FROM sys.databases where database_id = @dbid;
	END	
	DROP Table #dbInfo
	SELECT database_id, [name], recovery_model FROM sys.databases order by database_id
	GO

Technorati Tags: Configuration, Development, moss 2007, SharePoint, SQL Server

SharePoint 2007 FBA- Upload Mutiple Documents Missing From Menu

Calvin — Mon, 17 Oct 2011 15:14:40 +0000

Scenario: Forms Based Authentication on an external facing portal. Users are having trouble (as in not able too) uploading multiple documents at once.

This was a pretty easy fix....Enable Client Integration for the given website zone in Central Administration.

Technorati Tags: Configuration, FBA, moss 2007, SharePoint

Windows 2008 Server GPO – Force Allow Remote Desktop Connections

Calvin — Wed, 29 Sep 2010 18:00:07 +0000

Neat thing I figured out today...which I am 100% certain I will forget...to force allow remote desktop connections on a windows 2008 domain you need to set the following

Set windows Firewall to have a exception for the remote connection : computer >> admin templates >> network >> network connections >> windows firewall >> domain profile >> windows firewall: allow inbound remote desktop exceptions
Set the remote desktop services to allow connections: : computer >> admin templates >> windows components >> remote desktop services >> remote desktop session host >> connections >> Allow users to connect remotely using remote desktop services

Technorati Tags: Configuration, GPO, group policy, remote desktop, Security, Windows, windows 2008 r2

SharePoint 2007 on Windows 2008 R2 x64

Calvin — Tue, 01 Dec 2009 16:11:00 +0000

I was trying to install install SharePoint 2007 onto Windows 2008 r2 and was getting a strange error referencing KB article 962935. Funny enough this article is not live yet so it left me a little unhappy. Apprarently Microsoft does not support the distributed SP1 installation package of SharePoint for this version of the OS. Turns out Jei Li posting on his msdn blog detailing how to go about creating a slipstreamed installation for SP2 on this server Click here for the article. Basically the steps are (pretty much word for word from Jei Li's blog):

Install .Net Framework 3.5 SP1 in the features applet
Copy the installtion media contents to a folder on the computer (c:\install)
Download the WSS x64 SP package and the MOSS 2007 SP2 x64
Delete everything inside Updates folder in the install folder you setup.
Open a command prompt, change directory to the folder you put the downloaded patches, and run the following two commands:
- wssv3sp2-kb953338-x64-fullfile-en-us.exe /extract:[Path to installation bits]\Updates /quiet
- officeserver2007sp2-kb953334-x64-fullfile-en-us.exe /extract: [Path to installation bits]\Updates /quiet
Delete the wsssetup.dll filein the updates dir. This is a very important step so please don’t miss it.
If you also need the Cumulative Updates to be applied when install SharePoint, download the latest Windows SharePoint Services 3.0 and SharePoint Server 2007 Cumulative Update packages and extract them into Updates folder like step 4.
Your slipstream build of SharePoint Server 2007 is done!
Go and install it on your Windows Server 2008 R2 box, after the installation, the site version will show 12.0.0.6421 or possibly a higher version.

Please reference Jei Li's post for furthur instuctions. I only posted all the steps here because things have a mysterious way of dissappearing or not appearing at all on Microsofts site.

After doing all of this everything seems to be fine...seems to be

Links

Technorati Tags: Configuration, server, SharePoint, Windows, windows 2008 r2, x64

Variations Failed: An error was encountered performing this operation. You may re-try the operation…

Calvin — Fri, 30 Oct 2009 20:16:27 +0000

So I got this error the other day when putting together a dev site collection usign varations:

An error was encountered performing this operation. You may re-try the operation, and you may need to clean up the half-created data first before re-trying. If the problem persists, please contact your system administrator

This was actually a fairly easy fix for me. I simply had to enable the publishing features in my site. Which is funny...because they should have been on but I must have overlooked that.

Technorati Tags: Configuration, error, moss 2007, SharePoint, variations

Lookup Fields and Content Types

Calvin — Wed, 09 Sep 2009 04:43:35 +0000

For the last little bit I have been working on learning how to package up all site infrastructure into a single feature. All of this is pretty straight forward and I didn't really have any issues.....UNTIL I tried to get lookup columns working.

Using CAML

I did some reading on the subject and apparently you can do all of this using CAML alone. I came across a post from Josh Gaffery supporting this claim, but I simply could not get this working...so i gave up after spinning my wheels on it for longer than I wanted to. Josh's approach is to use the list URL as opposed to the GUID that links the column to the source list and he has put up an update explaining it further. Nonetheless....didn't work for me.

Using Feature Receiver

I knew that at this point I would have to take the feature reciever approach and modify the fields in place or create them. I found two sources that both take different approachs to this problem.

Chris O'Brien has put together the a project on CodePlex that will create the lookup columns at activation time. This actully sounds like a pretty good approach but unfortunately it didn't work for me. I dont know if there is something wrong with my environment but I encountered a few errors doing this...things like the fields not rendering on the page layouts and getting the "The local device name is already in use. (Exception from HRESULT: 0x80070055)" error.
Waldek Mastykarz has a great post on creating the columns via code here.

Basically I took a hybrid approach to doing this by mixing the two approaches mentioned above. I created a custom XML file that I deploy into the layouts directory and then use a feature reciever to read the xml content and create lookup columns based on this. I also added a deactiving event to remove the fields when the feature is deactivated. Heres the feature reciever code:

public override void FeatureActivated(SPFeatureReceiverProperties properties)
        {
            using (SPSite site = properties.Feature.Parent as SPSite)
            {
                string contentTypes = null;
                string listName = null;
                string fieldName = null;
                string groupName = null;
                string staticName = null;
                string lookupFieldName = "Title";
                bool mult = false;
                bool required = false;
                string filePath = properties.Feature.Properties[
                   "ColumnDefinitionPath"].Value;
 
                XmlTextReader xReader = new XmlTextReader(
                  HttpContext.Current.Server.MapPath(@"~\_layouts\" + filePath));
                while (xReader.Read())
                {
                    if (xReader.LocalName == "Field")
                    {
                        #region Get values from attributes
                        if (xReader.MoveToAttribute("List"))
                        {
                            listName = xReader.Value;
                            xReader.MoveToElement();
                        }
                        if (xReader.MoveToAttribute("Name"))
                        {
                            fieldName = xReader.Value;
                            xReader.MoveToElement();
                        }
                        if (xReader.MoveToAttribute("StaticName"))
                        {
                            staticName = xReader.Value;
                            xReader.MoveToElement();
                        }
                        if (xReader.MoveToAttribute("Group"))
                        {
                            groupName = xReader.Value;
                            xReader.MoveToElement();
                        }
                        if (xReader.MoveToAttribute("LookUpField"))
                        {
                            lookupFieldName = xReader.Value;
                            xReader.MoveToElement();
                        }
                        if (xReader.MoveToAttribute("ExistInContentTypes"))
                        {
                            contentTypes = xReader.Value;
                            xReader.MoveToElement();
                        }
                        if (xReader.MoveToAttribute("Mult"))
                        {
                            bool.TryParse(xReader.Value, out mult);
                            xReader.MoveToElement();
                        }
                        if (xReader.MoveToAttribute("Required"))
                        {
                            bool.TryParse(xReader.Value, out required);
                            xReader.MoveToElement();
                        }
 
                        #endregion
 
                        SPFieldLookup lookup = CreateLookupField(
                          fieldName, groupName, required, mult, site.RootWeb,
                          site.RootWeb.Lists[listName], lookupFieldName, staticName);
                        if (contentTypes != null)
                            foreach (string s in contentTypes.Split(','))
                            {
                                LinkFieldToContentType(s.Trim(), (SPField)lookup);
                            }
                    }
                }
 
                xReader.Close();
 
            }
        }
 
        public static SPFieldLookup CreateLookupField(
          string fieldName, string group, bool required, bool allowMultipleValues,
          SPWeb w, SPList lookupList, string lookupField, string staticName)
        {
            w.Fields.AddLookup(fieldName, lookupList.ID,
               lookupList.ParentWeb.ID, required);
            SPFieldLookup lookup = (SPFieldLookup)w.Fields[fieldName];
            lookup.AllowMultipleValues = allowMultipleValues;
            lookup.LookupField = lookupField;
            lookup.StaticName = staticName;
            lookup.Group = group;
            lookup.Update(true);
            return lookup;
        }
 
        public static void LinkFieldToContentType(string contentType, SPField field)
        {
            using (SPSite site = SPContext.Current.Web.Site as SPSite)
            {
                SPContentType ct = site.RootWeb.ContentTypes[contentType];
                ct.FieldLinks.Add(new SPFieldLink(field));
                ct.Update(true); // will update children
            }
        }

As you can read from the above code the xml file would need to have a node like below for each lookup column:

 

         Type="Lookup"
         List="Access Type"
         Name="AccessTypeColumn"
         StaticName="Access_x0020_Type"
         Group="Infrastructure"
         ExistInContentTypes="THIS IS A COMMA DELIMITED LIST OF CONTENT NAMES"
         LookUpField="Title"
         Mult="TRUE"
         Required="FALSE"
        />

The Final Project

So here are all the pieces of my infrastructure project. Notice the placement of the lookupfields xml file...this is because the layouts directory is setup as a virtual directory for every sharepoint site and we can read files from there without a permissions problem.

12/TEMPLATES/FEATURES/myfeature/lists.xml	this contains the source lists for the lookup fields
12/TEMPLATES/FEATURES/myfeature/contenttypes.xml	this contains the content type definitions MINUS the lookup fields
12/TEMPLATES/FEATURES/myfeature/sitecolumns.xml	this contains all the other fields included in the content types
12/TEMPLATES/FEATURES/myfeature/feature.xml	the feature def
12/TEMPLATES/LAYOUTS/myfeature/lookupfields.xml	this contains all the lookup fields that need to be provisioned

Hopefully this helps anyone who's been having problems getting this going. And a big thanks to Waldek, Chris and Josh for their posts.

Technorati Tags: Configuration, content types, Development, lookup fields, SharePoint

GACUtil missing…Windows 2008/Visual Studio 2008 development machine

Calvin — Mon, 24 Aug 2009 17:26:44 +0000

Great post here with a fix/workaround. Essentially when you go to look in the windows .net framework directory that program is not there. In order to run this utility program you will need to use the Visual Studio command prompt that is in the Programs/Visual Studio menu.

Technorati Tags: Configuration, gac, gacutil, visual studio, Windows