Fixing issue where SharePoint 2010 logs is 0 kb

by Christian Fredh 17. mars 2011 03:40

This was an interesting issue I came across. All the SharePoint 2010 logs where 0 kb (commonly located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS). It was really hard searching for error messages for the issue I was trying to fix in the first place, so I had to fix this first.

Turned out to be the account that runs the service SharePoint 2010 Tracing (SPTraceV4) that didn't have the correct permissions. Someone had probably messed with the service accounts. Here is how to fix it on Windows Server 2008 R2:

  1. Go to Start menu -> Administrative Tools -> Services
  2. Right-click on the SharePoint 2010 Tracing service and then click Properties
  3. Note the service account that runs the serivce under the tab Log On and then close the Properties window
  4. Go to Start menu -> Right-click Computer -> Manage
  5. Navigate to Configuration -> Local Users and Groups -> Groups
  6. Locate the group Performance Log Users -> Right-click and then click Properties
  7. Click Add... and the write or select the service account that you got in 3. and add it to the group
  8. Close the Server Manager windows
  9. Go back to the Services window and click Restart
  10. When restarted the log files should start filling up again and you can start fixing other stuff ;)

 

Tags: , , ,

SharePoint | SharePoint 2010

Using the ListView Control in SharePoint 2010 Beta

by Christian Fredh 24. februari 2010 02:57

In SharePoint 2007 you had to modify the web.config file, manually or with a feature, to enable the ScriptManager, ListView and other features in ASP.NET 3.5.

SharePoint 2010 is built on ASP.NET 3.5 so it should just work. However, the namespace for the ListView control is not mapped in the web.config or in the SharePoint Project Item templates by default. If you do not register the the namespace you will see the "Unknown server tag 'asp:ListView'" error message if you for instance use it in a web part:

 

To fix it add this line to the <controls>-section under <system.web> and <pages>:

<add tagPrefix="asp" namespace="System.Web.UI.WebControls" assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />

Or register the namespace in the .ascx or .aspx file:

<%@ Register Assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Namespace="System.Web.UI.WebControls" TagPrefix="asp" %>

And it should work:

Hopefully they will add both before RTM.

Tags: , ,

SharePoint | SharePoint 2010

SharePoint 2010 Sandbox Solutions and Visual Studio 2010 Project Templates

by Christian Fredh 3. januari 2010 19:16

Sandbox Solutions for SharePoint 2010 are great news for SharePoint development. I think we will see a lot of great features without the need of doing farm deployments. But sandboxed solutions do have their limitations and not all project templates or SharePoint Project Items (SPI) are available for sandboxed solutions.

Below are lists of the templates installed with Visual Studio 2010 Beta 2 and the availability for sandboxed solutions.

Project Templates

 

Name Available for sandboxed solutions
Empty SharePoint Project Yes.
Visual Web Part No. Visual Web Part template uses a user control (.ascx file) and must be deployed as a farm solution.
Sequential Workflow No. Programmatic workflows are not available for sandboxed solutions.
State Machine Workflow No. Programmatic workflows are not available for sandboxed solutions.
Business Data Connectivity Model No. BDC models is deployed at farm level and are therefore not available.
Event Receiver Yes.
List Definition Yes.
Content Type Yes.
Module Yes.
Site Definition No. Site definitions is deployed at farm level and are not available.
Import Reusable Workflow No. Programmatic workflows are not available for sandboxed solutions.
Import SharePoint Solution Package Yes, if the items that is imported from the package are supported.

SharePoint Project Items

 

Name Available for sandboxed solutions
Visual Web Part No. Visual Web Part template uses a user control (.ascx file) and are not available for sandboxed solutions.
Web Part Yes.
Sequential Workflow No. Programmatic workflows are not available for sandboxed solutions.
State Machine Workflow No. Programmatic workflows are not available for sandboxed solutions.
Workflow Association Form No. Association forms includes .aspx files and are not available for sandboxed solutions.
Workflow Initiation Form No. Initiation forms includes .aspx files and are not available for sandboxed solutions.
Business Data Connectivity Model No. BDC models is deployed at farm level and are therefore not available.
Application Page No. Application pages includes .aspx files and are not available for sandboxed solutions. Nothing under the Layouts folder can be deployed in sandboxed solutions.
Event Receiver Yes.
Module Yes.
Content Type Yes.
List Definition From Content Type Yes.
List Definition Yes.
List Instance Yes.
Empty Element Yes.
User Control No. User controls includes .ascx files and are not available for sandboxed solutions. Nothing under the ControlTemplates folder can be deployed in sandboxed solutions.

More information about sandboxed solutions:

SharePoint 2010 Development Environment Options

by Christian Fredh 4. november 2009 08:25

Great news for developers targeting SharePoint 2010 at the SharePoint Conference 2009. Many exiting features and tools, one of them being that SharePoint 2010 is installable on Windows 7 (and Vista), which means that SharePoint development is now supported on the client. This is a huge deal, since SharePoint development becomes more mainstream and easier to get started with.

Having SharePoint installed on the client is also good for demos. It is not supported for production environments.

Since SharePoint 2010 only support 64-bit operating system, this also applies if installing on Windows 7, you have to have the 64-bit versions. Since Windows Virtual PC doesn’t support 64-bit operating systems and Microsoft Virtual PC 2007 cannot be installed on Windows 7, using VPC is no longer an option – which is a good thing.

Basically, you are down to three different options when developing on the client, all with pros and cons.

On the Metal

SharePoint installed on your regular Windows 7 environment.

Pros

  • You can use all the hardware on your computer with no additional work, including networking. This means better performance and fewer problems with VPN connections.
  • You can use your other applications like Outlook and browsers at the same time with convenience.
  • You can start up SharePoint when developing and shut it down again when not using it, with simple PowerShell scripts. I will provide this scripts as a separate blog post.

Cons

  • If you are like me, switching between different projects a lot, it might take some thought to set them up on the same environment. Writing PowerShell scripts to set up environment and data for different projects could probably help with this.
  • If the SharePoint install gets messed up, it might take some time to solve, although I think it will be a lot easier in this version.

Bootable VHD

In Windows 7 you set up a bootable virtual hard drive with the SharePoint environment. When the computer is booting up, you choose to boot from the VHD where SharePoint is installed.

Pros

  • You can use all the hardware on your computer with no additional work, including networking. This means better performance and fewer problems with VPN connections.
  • You cannot use different VHDs for different projects with ease.
  • If you need a fresh install, just throw the VHD away and replace it with a backup with the fresh install.

Cons

  • You cannot use your regular applications when developing, and a restart is needed if you would like to switch to your regular environment. Of course, you can install as many applications as you which on the VHD, but it would need some work to keep it synchronized if that is preferable.

Hyper-V

Using Windows Server 2008 R2 with Hyper-V on VHD, or if you use it as your base operating system, and then set up the SharePoint environment on one or more VHDs with Hyper-V.

Pros

  • Supports advanced scenarios with multiple servers and environments.
  • Your tests will be run in a realistic environment.

Cons

  • Takes time to set up, especially if your not used to Hyper-V.
  • As with the bootable VHD options you are not in your regular environment and don’t have your regular applications available. If you use Hyper-V to run your regular environment you would be able to switch faster, but that is probably not a common scenario.

Personally, I will try to use the On the Metal option, because I think it’s such a huge win to be able to work in your regular environment, and try to solve issues with different projects and SharePoint installment issues with PowerShell scripts, for setting up project environment and resetting the installation.

In later posts I will dig deeper on how to set up these environments.

Tags: , ,

SharePoint | SharePoint 2010

Powered by BlogEngine.NET 1.5.0.7
Theme by Mads Kristensen

About Christian Fredh

Christian Fredh

A twenty six year old solutions architect and developer living in Stockholm, Sweden. I work as a SharePoint consultant at Avega Group with .NET and SharePoint development.

Disclaimer

The opinions expressed herein are my own personal opinions and do not represent my employer's view. Use the information on this site at your own risk.

Copyright

Creative Commons License
This work is licensed under a Creative Commons Attribution 3.0 Unported License.

© Copyright 2009, Christian Fredh.