Service Strategy
Strategy generation
Financial management
Service portfolio management
Demand management

Service Design
Capacity, Availability, Info Security Management
Service level & Supplier Management

Service Transition
Planning & Support
Release & Deployment
Asset & Config management
Change management
Knowledge Management

Service Operation
Problem & Incident management
Request fulfilment
Event & Access management

Continual Service Improvement
Service measurement & reporting
7-step improvement process

Where do we want to be? — Vision & Business Objectives

Where are we? — Assessment

How can we get to where we want to be — Process Improvement

How do we know we’ve arrived? — Metrics

Support for running Microsoft Dynamics CRM 4.0 together with Microsoft SQL Server 2008

http://support.microsoft.com/kb/957053

When installing MS Dynamics CRM 4 on a SQL 2008 server you may get the following error:

“The specified path is not a metabase path.” Platform Error: System.Exception: Action Microsoft.Crm.Setup.Server.RSConfigAction failed.

This issue occurs when the path of Reporting Services does not exist on the server.

To work around this issue, create a Web site that runs on the same port and the same URL that the Reporting Services server is using. In SQL Server 2008 Reporting Services, IIS is not used for accessing reports. However, if Microsoft Dynamics CRM 4.0 is installed on the same server, Microsoft Dynamics CRM 4.0 must find a Web site that has the same URL to bypass the error. To verify the URL of Reporting Services, follow these steps:

Click Start –> click All Programs –> click Microsoft SQL Server 2008 –> click Configuration Tools –> and then click Reporting Services Configuration Manager.

Click connect to connect to your report server instance.

Click the Web service URL, and see what the report server Web service URL is. For example, the URL may be http://SQLServername:8181/ReportServer.

In Windows Server 2008, follow these steps:

Click Start, click Run, and then type inetmgr.

Expand the server name, right-click Sites, and then click Add Website.

Enter a name for the site, and then select a physical path.

Enter the port number of the report server Web service. For example, enter 8181.

Click OK.

In Windows Server 2003, follow these steps:
Click Start, click Run, and then type inetmgr.

Expand the server name, right-click Web Sites, click New, and then click Web Site.

Enter a description for the site, and then click Next.

Enter the port number of the report server Web service. For example, enter 8181, and then click Next.

Enter a path for the Web site, and then click Next.

On the Permissions page, click Next.

Click Finish.

When you add a new entry to announcements, to events, or to links on a Microsoft SharePoint Team Services and Windows SharePoint Services Web site, the new entry always includes a tag that is made up of the exclamation point character (!) and the word “new” (!New). This article describes how to stop the !New tag from appearing when you create a new entry.

Windows SharePoint Services 3.0 Web site (inc. MOSS 2007)

To stop the !New tag from appearing next to new entries on a Windows SharePoint Services 3.0 Web site, use the Stsadm.exe tool to change the “Days to Show New Icon” property to zero.

To do this, follow these steps:
Click Start, point to All Programs, point to Accessories, and then click Command Prompt.

Type the following commands, and then press ENTER after each command:

cd /d %programfiles%\Common Files\Microsoft Shared\Web Server Extensions\12\BIN

stsadm.exe -o setproperty -pn days-to-show-new-icon -pv 0 -url [Your Virtual Server's URL]

More From pstilgoe

• How to Prevent users from changing views in Sharepoint
• How to easily move / copy list items from one sharepoint list to another
• Sharepoint 2010: How to hide the quick launch menu

Ask pstilgoe To Recommend Your Posts

If you are trying to deploy a Sharepoint 2010 site template based on a Access Web Database & you see the following error:

Preparing Site …

Wait a moment and refresh your browser

You probably havent set up your Access service application:

Create a Access Service Application
(Central Administration –-> Manage Service Applications –-> New –-> Access Services)

Started the Access Database Service
(Central Administration –-> Manage Services on Server)

Now open the SharePoint 2010 Management Shell and enter:

enable-spSessionStateService –DataBaseName <NameOfYourNewDatabase>

This creates a session state database and turns on the session state service.

Had a weird problem where I was updating a master content type, adding a calculated column to it which I wanted to propogate down to all content types inheriting from the master but no matter what the new calculated column never appeared.

It turned out that the logic & syntax in my calculated column didnt make sense although it did accept it upon creation. Once I rectified the forumla in the calculated column so it was correct the column propogated to all child content types as it should do.

Hopefully this will solve someone sometime if they experience similar!