Feeds:
Posts
Comments

Archive for the ‘Automation’ Category

Dear readers,

I have decided to discontinue this blog and not further publish posts on SharePoint. Thank you for more than 160,000 visits!

I am now writing a blog on algorithms and science, which is hosted at http://www.scilogs.com The blog is called Algoworld:

Algoworld is all about algorithms, mathematical and computer models and how they influence and shape our daily lives. They are either inspired by science, or they are aiding it.
The models and algorithms you will find here deal with the prediction of hurricanes, earthquakes, health and crime (and many more to come!), but also with solving engineering problems like traffic jam optimization. Many of these algorithms are strongly interwoven with the analysis of scientific “big data” – hence they are also facing its implied problems.

You can find it here: Algoworld – algorithms meet science.

I hope to see you there!

Best wishes,
Martin W. Angler

Read Full Post »

UPDATED: Find the new Youtube Link below!

Dear all,

episode 4 of SP5 is ready! This time it is dealing with the topic of moving site collections from one content database to another. Click below to watch the video (UPDATED):

Remark: If you want to create a new site collection using a specific content database, you need to use PowerShell, specifically the New-SPSite cmdlet:

New-SPSite –ContentDatabase <DBName>

This cannot be done from within Central Administration.

The involved cmdlets are:

Get-SPSite (lists site collections)
Get-SPContentDatabase (list content databases)
Move-SPSite (list content databases)
New-SPSite (create new site collection, specify content DB)

Important: After moving a site collection from one content DB to another, an iisreset is required. Be aware that this will cause a service disruption for some time (depending on your server’s configuration). Be sure to execute this only if you are fully aware that this will cause all websites to be inaccessible for some time.

Disclaimer: All tutorials are provided as is. You are responsible for any changes undergoing your system that derive from following this tutorial. It is hence recommended to consult your administrators and verify that the changes cannot harm your IT environment in any way.

Stay tuned till the next time!

Martin

Read Full Post »

Dear all,

The developer dashboard is a very handy tool in Microsoft SharePoint Server 2010, when it comes to analyzing how your site is loading and finding potential bottlenecks. It displays information about databases, webservices, the current page itself and so on. You can see an example of the developer dashboard here. Once enabled, it can be found scrolling at the bottom of the page you want to analyze.

The Developer Dashboard

There are three states the developer dashboard can be in:

  • On: Displayed
  • Off: Not displayed
  • On Demand: Can be toggled by the user.

And you have three possibilities of turning it on or off:

  • STSADM.exe
  • PowerShell
  • SharePoint COM

In this post, we’ll just focus on the STSADM.exe method, since it is the fastest one. STSADM.exe is located in the HIVE folder of SharePoint 2010 (usually “C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\”, and there in the “BIN” folder).

The STSADM.exe Method:

On:  stsadm -o setproperty -pn developer-dashboard -pv on

Off:  stsadm -o setproperty -pn developer-dashboard -pv off

On Demand:  stsadm -o setproperty -pn developer-dashboard -pv ondemand

Turning it on “On Demand” creates a new button in the menu, which is shown in the following picture:

On Demand Developer Dashboard Toggle Button

On Demand Developer Dashboard Toggle Button

That’s it! The command takes a few seconds to run and then quits with a “Operation successful” message.

Best regards and stay tuned till the next time,

Martin

Read Full Post »

Dear all,

 

There is a new tool out to deal with the variety of ULS logs that get generated and are hardly accesible.

As part of the Microsoft SharePoint 2010 Administration Toolkit v2.0, the SharePoint Diagnostic Studio is delivering the following information into a single graphical user interface:

 

  • Base
  • Capacity
  • Performance
  • Availability
  • Usage

Fig. 1: SharePoint 2010 Diagnostic Studio UI. Source: http://sharepoint.microsoft.com/blog/Pages/BlogPost.aspx?pID=971

 

Hence, it is allowing to assess performance issues in a single graphical representation, showing possible problems at a glance.

 

Moreover, it features integrated search capabilities, snapshots and a context sensitive help.

 

Not bad for a 1.9M download!

 

If you are interested in further details, you might also want to have a look at the following links:

Blog post from SharePoint Team Blog: http://sharepoint.microsoft.com/blog/Pages/BlogPost.aspx?pID=971

SharePoint 2010 Administration Toolkit v2.0 DL: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=718447d8-0814-427a-81c3-c9c3d84c456e&displaylang=en

 

Enjoy and till next time,

Martin

Read Full Post »

Dotnet DevCon-Speakerbanner

Dear all,

As I am preparing my session for the .NET DevCon conference in Nuremberg, I’d like to give you a idea of what I’m going to talk about. It’ll feature Visual Studio Add-Ins, with a major focus on productivity-increasing add-ins. Furthermore, it will briefly explain the necessary steps to be taken once a developer can’t find a needed functionality. And last but not least, it’ll also include something SharePoint 2010 related. So stay tuned!

 

On the 6th of June, we’ll also be at the OpenNight, to be available for community and developer questions.

 

See you there, at the .NET DevCon!

 

You can find an abstract about my session here.

 

Best regards,

Martin

Read Full Post »

Hi all,

After a fresh installation (or upgrade from a MOSS 2007), there are a couple of configuration steps that need to be performed. One is the configuration of the usage and health data collection. This can be done either using the Central Administration or PowerShell. This post focuses on how to do the configuration using powershell.

 

As the very first step we would need to bring up the SharePoint 2010 Management Shell.

Then, by issuing the cmdlet:

 

Set-SPUsageService

 

we can specify multiple parameters in order to set the data collection up:

 

  • -LoggingEnabled (1 or 0)
  • -UsageLogLocation (file path)
  • -UsageLogMaxSpaceGB [1-20]

More parameters exist, however: these are the most interesting ones. So, for example, issuing the following command:

 

Set-SPUsageService –LoggingEnabled 1 –UsageLogLocation C:\Logs -UsageLogMaxSpaceGB 3

 

would enable the usage data collection and write the corresponding logs to C:\Logs, up to amount of 3 GB. Please bear in mind that the logs max space must be within the interval [1-20].

 

image

 

There is also a way of specifying the usage data collection for a single event type, using the following cmdlet:

Set-SPUsageDefinition

 

The parameters of interest are here:

  • -Identity <GUID>
  • -Enable
  • -DayRetained [1-30]

An example command would be like follows:

 

Set-SPUsageDefinition -Identity 0a79e3a1-c60d-473b-82b7-
f43c2b4da -Enable -DaysRetained 15

 

This would set the event type with the GUID to be kept in the logs for 15 days.

 

Until here, we could have done the same operations using the Central Administration. However, there is a configuration that can only be performed using PowerShell:

 

Usage Logging in a Different Database.

 

As we might have guessed, another cmdlet is needed for this operation:

 

Set-SPUsageApplication

It uses the following parameters of interest:

  • -DatabaseServer <Server>
  • -DatabaseName <DBName>
  • -DatabaseUsername <User>
  • -DatabasePassword <PWD>

The latter two parameters, –DatabaseUsername and –DatabasePassword, are only required if our DB user differs from the user we are currently logged on as.

 

What else there is to mention? Well, do test the above commands thoroughly before applying them in any productive environment. They affect the logging and hence may have a negative and severe impact if applied the wrong way (or just as they are –please DO NOT copy paste and execute them – the parameters need to be adapted to your needs).

 

For all three methods, there exists also an additional –Verbose parameter, that tells you about success or failure of the application.

 

Best regards & happy SP-configuring!

Martin

Read Full Post »

Hi all,

I just put onto the Visual Studio Gallery the new version 1.2 of WADA. Mostly, I tried to fix some stability issues when querying the processes after W3WPs crash or an IISRESET occurs.

 

  • WADA 1.1: IISRESET –> “Get Procs” –> No results –> Restart VS 2010
  • WADA 1.2: IISRESET –> Refresh Webapp –> “Get Procs” –> Results

This means, if you execute an IISRESET, the worker processes end, and in order to make them run again you should refresh the web application you are testing (this will issue a new W3WP process). Then, just click on “Get Procs” in order to visualize the processes again. This should fix the problem of the annoying VS restart when wanting to see the processes again in WADA.

 

image

Fig.1 Multiple selection of processes

 

Attaching improvements

Now, there is also the possibility to attach to multiple processes, by simply clicking on each of the desired and then pressing “Attach”.

If you want to simply attach one process, just double click on that process, and the attach will be performed.

 

Planned future improvements

– Remote debugging

– <your improvement suggestion here>

 

Thank you all for your suggestions and valuable feedback, and keep sending more of it! This project isn’t finished, yet, and feedback/suggestions are always welcome.

 

Best regards,

Martin

Read Full Post »

Older Posts »