Archive for February, 2011

Oracle VM VirtualBox

February 22, 2011

The latest release is version 4.0.4.

On this page you can download:

Backing Up Sharepoint Sites

February 21, 2011

There are three ways of backing up Sharepoint sites, which one you use depends on which site/subsite you are backing up and what you intend to do with the backup.

  1. stsadm backup
  2. Sharepoint Designer backup
  3. stsadm export

1.  stsadm -o backup and stsadm -o restore

This can only be performed from the server itself and only allows you to backup from the top level site downwards, however, it allows you to essentially clone the site collection along with preserving all metadata, user rights.  Ideal for disaster recovery purposes.

To backup:
  1. On the server locate the file stsadm.exe (should be in \Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN), 

Tip:  Add the path to the stsadm.exe file into the environment variable path for the server, saves a whole lot of typing!

  2. From a command prompt, type [path to stsadm.exe\]stsadm -o backup -url http://%5Burl-of-the-web-site%5D -filename [path\filename.dat]

To restore: 
  1. Create a web application (but don’t create a site collection) 
  2. From a command prompt, type [path to stsadm.exe\]stsadm -o restore -filename [path\filename.dat] -url http://%5Burl-of-the-web-site%5D

2.  Sharepoint Designer Backup

This backup method is ideal for moving inidividual sites and subsites around within a site collection as well as migrating them from one server to another.  You only need administrative rights to the site/subsite rather than access to the actual server.  The main issue with a Designer backup is the loss of created/modified metadata along with Sharepoint Designer created custom data-view web-parts. Another major problem with Sharepoint Designer backups is the 25MB limit which makes Designer backups not a whole lot of use once the site is in use.

To backup:
  1. Open the site with SharePoint Designer
  2. Select Menu Site > Administration > Backup web site
  3. On the next screen, you can check the box to include subsites in the backup
  4. Unless your current website is low on disk space, leave the temporary location where it is and choose where to save the final .cmp file.

To restore:
  1. Open the site above where the restored site will be using Sharepoint Designer
  2. From the File menu go New > Website
  3. From the website templates, choose the Empty Web Site template
  4. In the ‘Specify the location of the new website’ box type the path to the new site.
  5. From the Site menu select Administration > Restore Website
  6. Select the .cmp file and click Open.

3. stsadm -o export and stsadm -o import

This type of backup has similar uses to the Sharepoint Designer backups (loss of some metadata and web-part data-views), however this method avoids the 25MB site limit.  The other smallish issue is you need access to the server.

To export a site:
1. On the server locate the file stsadm.exe (should be in \Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN), 
2. At a command prompt type [path to stsadm.exe\]stsadm -o export -url http://%5Burl-of-the-web-site/subsite%5D -filename [path\filename.dat]

If you include the -includesecurity switch, then the security settings and site owner information is retained, otherwise the site owner becomes whoever performs the import.

To import a site:
1. Create a web application and a site collection using sharepoint central administration if they don’t already exist. Or you can create a subsite in an existing site collection, either way use the “Blank site” template.

Caution: Watch out here for subsites you included in the export, you will need to create blank versions of those as well otherwise the import will fail.  Check the spelling of the url rather than the site name, they do need to be exactly the same.

2. At a Command prompt type stsadm -o import -url http://%5Burl-of-the-web-site/subsite%5D -filename [path\filename.dat]

Microsoft Dynamics CRM 2011 Implementation Guide

February 20, 2011

 

The Microsoft Dynamics CRM 2011 Implementation Guide consists of the following documents:

  • Planning Guide: This Microsoft Office Word document gives you the information and tools that help you get your organization ready for Microsoft Dynamics CRM 2011. It includes two main aspects of planning for a customer relationship management (CRM) system:
    • Technical: These topics focus on areas such as the supported topologies, system requirements, and technical considerations to address before you install.
    • Implementation methodology: These topics cover the business management, CRM requirements, and project management aspects that are needed when you deploy a CRM system.
  • Installing Guide: This Word document provides the information that you need to install Microsoft Dynamics CRM 2011, such as step-by-step instructions for running Setup, and command-line instructions for silent installations.
  • Operating and Maintaining Guide: This Word document gives you information about how to back up, restore, and provide data recovery for Microsoft Dynamics CRM 2011. Additionally, this guide provides troubleshooting steps for known issues.
  • The Microsoft Dynamics CRM 2011 Implementation Guide Compiled HTML Help (CHM) file includes the contents of all three of the guides and provides a comprehensive index and full-text search.

The Planning Tools are 43 template, project, and worksheet Office documents that can be used to help plan your implementation.

Download:
Microsoft_Dynamics_CRM_2011_IG.zip
PlanningTools.zip

Microsoft Dynamics CRM 2011 Software Development Kit (SDK)

February 18, 2011
The Microsoft Dynamics CRM 2011 Software Development Kit (SDK) is for developers, system customizers, and report writers.This SDK documentation contains information for developers writing server side code, custom business logic, integration modules, workflow assemblies, and plug-ins. It provides an architectural overview of Microsoft Dynamics CRM, the entity model, security model, and Web services. Sample code and walkthroughs are provided to guide you through the new features. It also contains information for developers customizing the Web client or Microsoft Dynamics CRM for Microsoft Office Outlook, including scripting, integration of custom Web pages, and lots of sample code.

In addition to the documentation, this download package includes the assemblies and tools needed for development, helper code for authentication, and Microsoft Visual Studio projects for all sample code found in the documentation. The package includes a visual style guide you can use to make your customizations fit in smoothly. Look for regular updates to this SDK.

Download

MS Dynamics CRM 2011 Developer Training Kit

February 16, 2011

This training kit is for .NET developers to learn the development features of Dynamics CRM and help them build applications using Microsoft Dynamics CRM 2011 and CRM Online. Microsoft Dynamics CRM uses familiar components such as WCF & oData web service endpoints, JavaScript, Silverlight, .NET 4, Workflow Foundation 4, SQL reporting and more; making it a general purpose framework for line-of-business applications. This kit drills into the details of such development and explains how developers can connect, extend, and embed their applications with Microsoft Dynamics CRM.The training kit includes various resources to help you learn the development features of Dynamics CRM. It includes:

  • Presentations – Presentation decks in PowerPoint (.pptx) format that you can use to learn the concepts.
  • Videos – Video recordings of the presentation along with demos delivered by expert trainers.
  • Hands-on Labs – Hands-on labs with detailed instructions and source code that will walk you through various development features.

 For download , click here: Start download

How to do a Sharepoint site export and import

February 14, 2011

How to do a Sharepoint site export:

stsadm -o export -url http://sharepointsite -filename c:\backup\sharepointsite.bak -includeusersecurity -versions 4 -nofilecompression

Hot to do a Sharepoint site import:

stsadm –o import –url http://sharepointsite -filename c:\backup\sharepointsite.bak –includeusersecurity

More information to stsadm:

C:\>stsadm -help export

stsadm.exe -o export
           -url <URL to be exported>
           -filename <export file name>
               [-overwrite]
           [-includeusersecurity]
           [-haltonwarning]
           [-haltonfatalerror]
           [-nologfile]
           [-versions <1-4>
               1 – Last major version for files and list items (default)
               2 – The current version, either the last major or the last minor
               3 – Last major and last minor version for files and list items
               4 – All versions for files and list items]
           [-cabsize <integer from 1-1024 megabytes> (default: 25)]
           [-nofilecompression]
           [-quiet]

C:\>stsadm -help import

stsadm.exe -o import
           -url <URL to import to>
           -filename <import file name>
           [-includeusersecurity]
           [-haltonwarning]
           [-haltonfatalerror]
           [-nologfile]
           [-updateversions <1-3>
               1 – Add new versions to the current file (default)
               2 – Overwrite the file and all its versions (delete then insert)
               3 – Ignore the file if it exists on the destination]
           [-nofilecompression]
           [-quiet]

Fabulous 40 for Sharepoint Foundation 2010

February 11, 2011
After the Fabulous 40 templates for SharePoint 2010 that we created and released on our blog as a community service. We have been receiving requests of setting up the Microsoft Fabulous 40 templates on SharePoint Foundation server. Due to increasing requests, we attempted to set up some of the templates and were successful in doing that. We have been posting the individual templates for SP Foundation 2010 to individual requesting clients and after receiving a general positive response I am posting some of the templates for Fabulous 40 for the Sharepoint Foundation in this blog post and a readme file with setup instructions. Please review the templates and feel free to post your feedback.

Board Directors

BugDatabase

BusinessPerformance

CaseManagement

ClinicalTrial

HelpDesk

InventoryTracking

ITTeamWorkspace

ManufacturingProcess

Project Tracking Workspace

Room Equipment Reservations

TeamWorkSite

TimecardManagement

SportsLeague

 LendingLibrary

KnowledgeBase

ExpenseReimbursementApproval

DocumentLibraryReview

ComplianceProcessSupport
 
BudgetingTrackingWorkspace
 
AbsenceVacationSchedule
 
EmployeeTraining 

Fabulous 40 Templates for MOSS 2010

February 10, 2011

Fabulous 40 templates were free templates released by Microsoft for SharePoint 2007 and WSS 3.0 to address some of the common scenarios encountered by SharePoint administrators, developers and event business/Marketing managers to demonstrate and show case some of the capabilities of MOSS to end users.

Discussion about that how good these templates are and in which scenario these are more helpful versus things which needs to be improved in these templates is a separate topic but I have noticed many SharePoint people using these templates either for small clients , for demonstration purpose and even for training purposes etc. ..

Follow the instructions in readme file to install these, I strongly recommend that you install it in your test environment before testing it in real/production.

AbsenceVacationSchedule

BoardofDirectors

BudgetingTrackingMultipleProjects

BusinessPerformance

CallCenter

CaseManagement

ChangeRequestManagement

ClassroomManagement

ClinicalTrial

CompetitiveAnalysis

ComplianceProcessSupport

ContactsManagement

DiscussionDatabase

DisputedInvoice

DocumentLibraryReview

EmployeeActivities

EmployeeBenefits

EmployeeTraining

EquityResearch

EventPlanning

HelpDesk

JobRequisition

KnowledgeBase

ManufacturingProcess

MarketingCampaign

NewStoreOpening

PhysicalAssetTracking

ProductPlanning

RequestForProposal

SalesLeadPipeline

TeamWorkSite

TimecardManagement

Sharepoint Hotfix 936867 renders Sharepoint unuseable

February 9, 2011

After requesting an and applying Windows Sharepoint Services 3.0 hotfix 936867 our Sharepoint stopped working completely.

I’ve found the following error messages in the application log:

Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Topology
Event ID: 5617
Date: 31.12.2010
Time: 17:17:17
User: N/A
Computer: SERVERWEB
Description:
The schema version (3.0.149.0) of the database SharePoint_AdminContent_f80b1f17-ff1d-4df2-93d3-66bbbaf5790f on x64a is not consistent with the expected database schema version (3.0.150.0) on SERVERWEB.  Connections to this database from this server have been blocked to avoid data loss.  Upgrade the web front end or the content database to ensure that these versions match.

Solution: called “stsadm -o upgrade -inplace -url http://{central_admin_url}”

That seemed to have solved the problem.

Upgrade the web front end or the content database to ensure that these versions match

February 7, 2011

After requesting an and applying Windows Sharepoint Services 3.0 hotfix 936867 our Sharepoint stopped working completely.

I’ve found the following error messages in the application log:

Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Topology
Event ID: 5617
Date: 31.12.2010
Time: 17:17:17
User: N/A
Computer: SERVER
Description:
The schema version (3.0.149.0) of the database SharePoint_AdminContent_f80b1f17-ff1d-4df2-93d3-66bbbaf5790f on x64a is not consistent with the expected database schema version (3.0.150.0) on SERVER. Connections to this database from this server have been blocked to avoid data loss. Upgrade the web front end or the content database to ensure that these versions match

Option # 1

Start the Windows SharePoint Services Administration service using the Services applet (Start, Run, Services.msc) and run SharePoint Products and Technologies Configuration Wizard.

Option # 2

Start the SPAdmin service under the context of a local administrator on the server where the SPAdmin service failed to start when running the SharePoint Products and Technologies Configuration Wizard (psconfig.exe) and run SharePoint Products and Technologies Configuration Wizard.
net start spadmin

Option # 3

Download wssv3-kb934525-fullfile-x86-glb.exe from http://www.microsoft.com/downloads/details.aspx?familyid=76FC2225-2802-46E5-A294-A842E3841877&displaylang=en.
Extract wssv3-kb934525-fullfile-x86-glb.exe and run the installation by executing C:\temp\STS.msp (see below).

:\wssv3-kb934525-fullfile-x86-glb.exe /extract:c:\temp.

Option # 4

On the machine where psconfig failed to start the SPAdmin service run:
%commonprogramfiles%\Microsoft Shared\Web Server Extensions\12\BIN\psconfig -cmd upgrade -inplace b2b -wait -force
Modify the service timeout values in the Registry:

HKLM\SYSTEM\CurrentControlSet\Control add/modify DWORD value ServicesPipeTimeout to 60000 (60 seconds)

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control add/modify STRING value WaitToKillServiceTimeout to 120000 (120 seconds)
Restart the server machine.

A solution is available to administrators of SharePoint Products and Technologies deployments experiencing the following application event after introducing WSS October public update KB934525.

Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Topology
Event ID: 6800
Date: 31/12/2010
Time: 10:10:10 PM
User: NA
Computer: SERVER
Description: The database WSS_Content on HOME\Microsoft##SSEE is not accessible to missing Windows Internal Database signatures.

1. Run the following STSADM operations to stop and start the SPWebService:

stsadm -o provisionservice -action stop -servicetype spwebservice -servicename “”

stsadm -o provisionservice -action start -servicetype spwebservice -servicename “”
2. Instantiate the upgrade by executing psconfig.exe or psconfigui.exe.

The cause of this issue is the SPWebService instance failed to finish provisioning. The status of that service is marked as provisioning. However, it has done enough provisioning work so that the user sites are working and/or during upgrade, the upgrade code skipped any web service instances that are not online, upgrading the administration sites; however, skipping the user sites.

A good artice about STSADM:http://www.microsoft.com/technet/technetmag/issues/2007/01/CommandPrompt/