Dev Team Assemble

Getting SharePoint 2010 Custom Site Template Code

Calvin — Wed, 02 May 2012 13:03:15 +0000

The other day I was looking for a way to get the site template code (STS#1, STS#0, etc) of a custom site template that I made and I couldn't find it anywhere. I am sure you can use powershell to do this but I couldn't figure it out so I thought I would use the cheating way

Go to the create new site web page and look at the value of the items in the "Custom" list...it should have it in the option element.
If you hae silverlight installed you may find that sharepoint is loading the silverlight console and not the page you need...if thats the case go to http://YOUR-SITE-URL/_layouts/newsbweb.aspx and use that page to do your investigation.
The template code you get back should be somethign like {GUID}#your-template-name

From here we can use this template code to create instances of that site via code or workflow actions like the iLoveSharePoint Create a Site Action (which is fantastic by the way).

Technorati Tags: SharePoint, SharePoint 2010, SP 2010

Getting SharePoint 2010 Version

Calvin — Thu, 19 Apr 2012 19:27:09 +0000

It seems finding the version number of SharePoint 2010 is different than in 2007. In 2007 you can just go to site settings and it appears at the top of the content area under Site information > version.

In 2010 it isnot there...where did it go you ask? Good question, you can access this information from:

Central admin under Central Admin > Servers in Farm
Powershell usig the following command : (Get-SPFarm).BuildVersion

Technorati Tags: SharePoint, SharePoint 2010, SP 2010

.NET Convert DataTable to JSON

Calvin — Fri, 16 Mar 2012 13:42:02 +0000

Here is a neat little method I found on the ASP.NET forums for converting a DataTable into JSON objects for use by web services : written by Chandra Prakash Andani. Its a little older now but its still good stuff.

public string GetJson(DataTable dt) { System.Web.Script.Serialization.JavaScriptSerializer serializer = new System.Web.Script.Serialization.JavaScriptSerializer(); List> rows = new List>(); Dictionary row = null;

foreach (DataRow dr in dt.Rows) { row = new Dictionary(); foreach (DataColumn col in dt.Columns) { row.Add(col.ColumnName, dr[col]); } rows.Add(row); } return serializer.Serialize(rows); }

The original article is located here:
http://forums.asp.net/t/1572961.aspx/1

Technorati Tags: .net, ASP.NET, Development, json

JDE BSSV Won’t Build…after package update…ummmm what?

Calvin — Mon, 06 Feb 2012 18:42:57 +0000

I have been working with jDeveloper and JDE (J.D.Edwards) for a little while. Mostly to build integration pieces for portals and custom applications. One of the strangest things happened to me after I did a package update (upgrade to local JDE application) the other day.

After the package update, I grabbed my project code from the OMW (object management workbench) and tried to go back to development. All of a sudden it had replaced my ValueObject classes with generated classes ( really...I have no idea why) and copied some other strange code articles to my computer.

This was really strange but good thing I managed to backup my code using an alternative source code control system just in case something bizarre like this happened....which of course it did. I copied my code back over the top of the JDE code and all was well, with the exception of some oracle.e1.bssvfoundation classes not working correctly (complaining that the method could not be found, etc). In order to build my code I needed to remove some new code (that showed up during the package build) in the c:\e812\dv812\java\source\oracle\e1\bssvfoundation folder. I think its safe to say you can delete that entire folder because it should not exist in your source code folder.

To try and make a confusing story short and understandable I guess what I am trying to say if you find that you have the folder c:\e812\dv812\java\source\oracle\e1\bssvfoundation you can delete it because you probably shouldn't have it....these are system functions that you don't need the source for, and chances are if you do have the source its not the right version :s. I am not sure why they are included in our package but they are.

If your still with me then I hope this helped...if you are confused then drop me a line and I will attempt to explain by adding more acronyms and file paths.

Calvin

Technorati Tags: J.D.E., JD Edwards, JDE, jDeveloper

JDE BSSV Error – E1AuthorizationException

Calvin — Tue, 17 Jan 2012 18:26:19 +0000

I have been doing some integration work with JD Edwards Business Services (aka BSSV) lately and I came across this error when trying to run my Published Business Service .

Internal Server Error (Caught exception while handling request: oracle.e1.bssvfoundation.exception.E1AuthorizationException: User is not authorized to invoke this published business service

Here is the article that led me to the answer I needed https://forums.oracle.com/forums/thread.jspa?threadID=867569 specifically ChrisWalsh's comment.

Essentially in order to run a published business service you need to have security to the object declared in JDE. This is done in the F00950 table (or file) and should probably be setup as *ALL for your dev team.

HTH

Technorati Tags: BSSV, Business Services, JDE

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

SharePoint Version Information

Calvin — Wed, 31 Aug 2011 13:27:39 +0000

Here are some great resources on finding and determining the different versions of SharePoint available:

All available versions on SharePoint

Microsoft Office SharePoint Server 2007

Microsoft SharePoint 2010

Here is the information that I really needed on SharePoint 2007 (I feel like I am stealing it but all props to the author of the first link for putting it together....thank you):

THE INFORMATION BELOW IS TAKEN DIRECTLY FROM (WORD FOR WORD) : All available versions on SharePoint

Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0

For additional download information and detailed descriptions visit the Updates Resource Center for SharePoint Products and Technologies and Update Center for Microsoft Office, Office Servers, and Related Products.

Using SharePoint Central Administration Web site SharePoint HTML Site Settings admin pages will show the following version numbers:

Note: Microsoft has released a WSS 3.0 SP1 Developer evaluation virtual machine on the Microsoft download site.

12.0.0.6557    WSS 3.0 or MOSS 2007¹ SP2 + Apr 11 cumulative Update (KB2512783 + KB2512782)
12.0.0.6554    WSS 3.0 or MOSS 2007¹ SP2 + Feb 11 cumulative Update (KB2475886 + KB2475885)
12.0.0.6550    WSS 3.0 or MOSS 2007¹ SP2 + Dec 10 cumulative Update (KB2458606 + KB2458605)
12.0.0.6548    WSS 3.0 or MOSS 2007¹ SP2 + Oct 10 cumulative Update (KB2412268 + KB2412267)
12.0.0.6545    WSS 3.0 or MOSS 2007¹ SP2 + Aug 10 cumulative Update (KB2276474 + KB2276472)
12.0.0.6539    WSS 3.0 or MOSS 2007¹ SP2 + June 10 cumulative Update (KB983311 + KB983310)
12.0.0.6535    WSS 3.0 or MOSS 2007¹ SP2 + April 10 cumulative Update (KB981043 + KB981042)
12.0.0.6529    WSS 3.0 or MOSS 2007¹ SP2 + February 10 cumulative Update (KB978396 + KB978395)
12.0.0.6524    WSS 3.0 or MOSS 2007¹ SP2 + December 09 cumulative Update (KB977027 + KB977026)
12.0.0.6520    WSS 3.0 or MOSS 2007¹ SP2 + October 09 cumulative Update (KB974989 + KB974988)
12.0.0.6514    WSS 3.0 or MOSS 2007¹ SP2 + August 09 cumulative Update (KB973400 + KB973399)
12.0.0.6510    WSS 3.0 or MOSS 2007¹ SP2 + June 09 cumulative Update (KB971538 + KB971537)
12.0.0.6504    WSS 3.0 or MOSS 2007¹ SP2 + April 09 cumulative Update (KB968850 + KB968851)
12.0.0.6421    WSS 3.0 or MOSS 2007¹ SP2 (KB953338 + KB953334)
[Updated 1st Aug 09: SP2 download now includes the hotfix (KB971620) that corrects the activation issue more information on the Microsoft SharePoint team blog]

If you are running SP1 after 13/Jul/2010 then you are running an un-supported environment, see "Be aware of upcoming SP1 retirement for WSS V3 and MOSS 2007"
12.0.0.6341    WSS 3.0 or MOSS 2007¹ February 09 cumulative Update (KB961755 + KB961756)
12.0.0.6335    WSS 3.0 or MOSS 2007¹ December 08 cumulative Update (KB960010 + KB960011)
12.0.0.6331    WSS 3.0 or MOSS 2007¹ October 08 cumulative Update (KB957691 + KB957693,KB958567 and KB958569)
12.0.0.6327    WSS 3.0 or MOSS 2007¹ August 08 cumulative update (KB956056 & KB956057)
12.0.0.6318    WSS 3.0 or MOSS 2007¹ Infrastructure Update (KB951695 & KB951297)
12.0.0.6303    WSS 3.0 or MOSS 2007¹ post-SP1 hotfix (KB948945)
12.0.0.6301    WSS 3.0 or MOSS 2007¹ post-SP1 hotfix (KB941274)
12.0.0.6300    WSS 3.0 or MOSS 2007¹ post-SP1 hotfix (KB941422)

12.0.0.6219    WSS 3.0 or MOSS 2007¹ SP1
12.0.0.6039 WSS 3.0 or MOSS 2007¹ October public update
12.0.0.6036    WSS 3.0 or MOSS 2007¹ August 24, 07 hotfix package
12.0.0.4518    WSS 3.0 or MOSS 2007¹ RTM
12.0.0.4407    WSS 3.0 or MOSS 2007¹Beta 2 TR
12.0.0.4017    WSS 3.0 or MOSS 2007¹ Beta 2
12.0.0.3111    Office 12 (PDC image - pre-beta) - This version of Office does not have a support link in the Add/Remove programs dialog box.

¹To confirm that a particular service pack/hotfix is install on SharePoint Server you must either check the version numbers of specific dlls as specified in the related Microsoft Knowledge Based article or:

On Server 2003, select the Show Updates check box in Add and Remove Programs.
On Server 2008, select View installed updates on the Control Panel/Programs and Features page

Version numbers of SharePoint Server 2007 can also be found:

Server 2003, go to Control Panel -> Add and Remove Programs
Select the product and then click: Click here for support.
Server 2008, go to Control Panel -> Program and Features
If the Version column is not visible, click Views -> Choose Details, and select Version, click OK.

The versions will be displayed as follows:

	Windows SharePoint Services 3.0	Microsoft Office SharePoint Server 2007
SP2		12.0.6425.1000
post-SP1 hotfix ( KB948945 )	12.0.6303.5000	12.0.6303.5000
SP1	12.0.6219.1000	12.0.6219.1000
RTM	12.0.4518.1016	12.0.4518.1016
Beta 2 TR	12.0.4407.1005	12.0.4407.1005
Beta 2	12.0.4017.1006	12.0.4017.1006

Back to the top

Execute Commands in Windows via .NET Application

Calvin — Thu, 26 May 2011 15:44:50 +0000

Heres a neat little snippit that comes in handy for running commands against the operating system.

Sourced directly from here: http://stackoverflow.com/questions/691716/running-cmd-commands-via-net ...but I like having the code here as well.

 
// Kills a process
  private static void ExecuteCommand(string command)
{
try
{
// create the ProcessStartInfo using "cmd" as the program to be run,
// and "/c " as the parameters. > tell the command to execute the command that follows
System.Diagnostics.ProcessStartInfo procStartUpInfo =
new System.Diagnostics.ProcessStartInfo("cmd", "/c " + command);
// The following commands are needed to redirect the standard output.
// This means that it will be redirected to the Process.StandardOutput StreamReader.
procStartUpInfo.RedirectStandardOutput = true;
procStartUpInfo.UseShellExecute = false;
// Do not create a window.
procStartUpInfo.CreateNoWindow = true;
// Now we create a process, assign its ProcessStartInfo and start it
System.Diagnostics.Process proc = new System.Diagnostics.Process();
proc.StartInfo = procStartUpInfo;
proc.Start();
// Get the output into a string
string result = proc.StandardOutput.ReadToEnd();
// Display the command output.
Console.WriteLine(result);
}
catch (Exception objException)
{
Console.WriteLine(objException);
}
}

Technorati Tags: .net, cmd, command, Development, Windows

Visual Studio 2005 – WSE 3.0 Settings not showing up

Calvin — Tue, 24 May 2011 14:16:40 +0000

- OLD SCHOOL ALERT -

I was setting up Visual Studio 2005 and Web Service Extensions 3.0. My problem was getting the WSE 3.0 Settings to appear on the context menu of the project. Turns out when you install it you need to select the Visual Studio Tools option in the installer.