Sharepoint - MCPblog

10.3.2010

SharePoint alerts not working after restore

Yesterday, I've completed yet another successful restoration of SharePoint backup. Today users reported that they haven't received alerts from multiple sites. Soooo phone started ringing.

After troubleshooting SharePoint logs (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS), I've figure it out that I'm able to create new alerts and confirmation mail comes to user mailbox, but any modification to list or library is not being sent. Log stored information that OWSTIMER.EXE is unable to find specific file (modified one)

So I manually configured the alerts using set of STSADM commands.

Go to "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN"
stsadm.exe -o getproperty -url http://yoursite-pn alerts-enabled
Stsadm.exe -o setproperty -url http:// yoursite -pn alerts-enabled -pv Yes
Stsadm.exe -o setproperty -url http:// yoursite -pn job-immediate-alerts -pv "Every 5 minutes between 0 and 59"
stsadm.exe -o setproperty -url http:// yoursite -pn alerts-enabled -pv "Everyday between 12:00:00 and 05:00:00"
net stop sptimerv3
net start sptimerv3
Stsadm -o execadmsvcjobs

After that my colleague called to tell me "Something wrong with our SharePoint, I'm flooded with notifications" :)

Posted at 11:01 by Bojan Buhač | Category: Sharepoint | Permalink | Email this Post | Comments (0)

6.2.2010

How to connect to the SharePoint Services Integrated Database with SQL Server Management Studio Express

Yesterday I've installed WSS 3.0 (for houndret and one time) and wanted to connect to WSS 3.0 integrated SQL engine (basic install) with SQL Server Management Studio Express (free) and I got error mesage. Actualy you can't connect to WSS database remotely because network connectivity is disabled by default.

But after some late night digging I've found magic connection string \\.\pipe\mssql$microsoft##ssee\sql\query (for Sharepoint 2007) or \\.\pipe\mssql$sharepoint\sql\query or <servername>\sharepoint (for Sharepoint 2010) that you can use to connect to the Microsoft##SSEE instance.

Posted at 22:43 by Bojan Buhač | Category: Sharepoint | Permalink | Email this Post | Comments (0)

7.12.2009

“Contains” is missing from SharePoint Advanced Search

Last night I was setting up SharePoint Advanced Search Box in Enterprise Search and I was puzzled for a couple of seconds. For all text fields that I had in metadata mappings, I had no option "Contains" and "Does not contain"!!!

But I had couple of technical documentation for "old" implementation, and had no single word about this needed to be set explicitly. "New" implementation of Search has also been slightly modified but I had no clue what happened. So I decided to investigate and luckily I've found problem/solution.

If you don't have Microsoft Office Servers Infrastructure Update in your SharePoint farm than you have this problem (Or if you have SP2).

Don't panic!!!

Simply add following piece <Option Name="AllowOpContains" Value="True"/> underneath root node.

Go to Advanced Search page and click Site Actions, and Edit Page.

On the Advanced Search Web Part, click Edit in upper right corner of web part, and then click Modify Shared Web Part.
In the Properties text box, click the small rectangle Builder.
In the Builder dialog box, under the root node create <Option Name="AllowOpContains" Value="True"/> and click OK.

Why has this been removed from SharePoint?

This option has been removed from the Advanced Search page, because setting this restriction can issue a very extensive SQL query, such as "CONTRACT". This causes a huge load on SQL server and such queries often timeout!!!

So take care with this option.

Posted at 22:29 by Bojan Buhač | Category: Sharepoint | Permalink | Email this Post | Comments (0)

24.11.2009

Activate Site Directory in Sharepoint Server 2010

If you are playing with enterprise features of Sharepoint 2010 you have probably noticed that Site Directory template is missing. Site directory has been intentionally hidden because of compatibility issues with upgrade process between 2007 and 2010.

If you want to "enable it" simply follow these steps.

Browse to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\1033\XML
Open webtempsps.xml
Find section for Site Directory and change Hidden value
<Template Name="SPSSITES" ID="34">
<Configuration ID="0" Title="Site Directory" Type="0" Hidden="FALSE" ImageUrl="/_layouts/1033/images/template_site_dir.png" Description="A site for listing and categorizing important sites in your organization. It includes different views for categorized sites, top sites, and a site map." DisplayCategory="Enterprise" VisibilityFeatureDependency="5F3B0127-2F1D-4cfd-8DD2-85AD1FB00BFC">
After that open command prompt and browse to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
Run following command:
stsadm.exe -o activatefeature -id 5F3B0127-2F1D-4cfd-8DD2-85AD1FB00BFC –url http://yoursite

After that go to your site URL and create new site and you'll see "Site Directory"

Posted at 12:08 by Bojan Buhač | Category: Sharepoint | Permalink | Email this Post | Comments (0)

17.11.2009

“allowInsecureTransport” error during installation Sharepoint 2010 Beta

If you run into problem during running of Sharepoint 2010 Configuration wizard that reports error:

Failed to create sample data.
An exception of type Microsoft.Office.Server.UserProfiles.UserProfileException was thrown. Additional exception information: Unrecognized attribute 'allowInsecureTransport'. Note that attribute names are case-sensitive. (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebClients\Profile\client.config line 56)

Simply do the following:

Uninstall Sharepoint 2010 and anything you installed regarding Sharepoint after (Sharepoint will remove SQL 2008 Express, not full SQL).
- In case you used full SQL check for any additional databases
Run the install again, but STOP at the Configuration Wizard step!!!
On Windows Server 2008 right click Notepad and run it as Administrator,
Navigate notepad to "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebClients\Profile\",
Choose All files as file type,
Open file "client.config",
Delete two instances of "allowInsecureTransport" tag (mind the spaces and containing tag).
Proceed with Configuration Wizard.

I'm not sure what thing does but Wizard manages to complete successfully :)

20.11.2009 - FIXED by Microsoft:

http://blogs.msdn.com/sharepoint/archive/2009/11/19/installation-notice-for-the-sharepoint-server-public-beta-on-microsoft-windows-server-2008-r2-and-microsoft-windows-7.aspx?utm_source=feedburner&utm_medium=email&utm_campaign=Feed%3A+sharepointteamblog+%28Microsoft+SharePoint+Products+and+Technologies+Team+Blog%29

Posted at 13:13 by Bojan Buhač | Category: Sharepoint | Permalink | Email this Post | Comments (0)

23.10.2009

PageTest your Internet facing SharePoint site

Page testing utilities are more and more popular. There even companies specialized in Site optimization. If you want to know how Microsoft managed to speed up their http://sharepoint.microsoft.com visit http://blogs.msdn.com/sharepoint/archive/2009/09/28/how-we-did-it-speeding-up-sharepoint-microsoft-com.aspx

Couples of web sites where you can test yours site performance:

Test results for www.mcpblog.net :)

Posted at 9:35 by Bojan Buhač | Category: Sharepoint | Permalink | Email this Post | Comments (0)

29.5.2009

BDC step by step

You've probably heard about BDC feature in MOSS 2007 Enterprise Edition, but you have never tried it in practice. There is good walkthrough that describes everything you need to setup the BDC example.

http://dotnetdreamer.com/2008/09/26/business-data-catalog-in-moss-2007/

I have only couple of things to add:

If you don't manage to connect to BDC data in site collection, but you are able to connect to data via BDC template page, go to Permissions in BDC application and click "Copy Permissions to descendants"
If you have configured Sharepoint via NTLM instead Kerberos, you need to modify Application Definition File in section

<Property Name="AuthenticationMode" Type="Microsoft.Office.Server.ApplicationRegistry.SystemSpecific.Db.DbAuthenticationMode">
PassThrough
</Property>

Instead of "PassThrough" you should use "RevertToSelf"

Posted at 22:18 by Bojan Buhač | Category: Sharepoint | Permalink | Email this Post | Comments (0)

25.5.2009

Do you have MOSS SP2? Then type your PID key again

If you have deployed SP2 to your SharePoint Farm then you should definitely read this. There is known bug that converts your farm into Trial Environment for 180 days.

Luckily, there is easy solution, in a sense that you need to retype Product ID in Central Administration:

What happened?

http://blogs.msdn.com/sharepoint/archive/2009/05/21/attention-important-information-on-service-pack-2.aspx

How to solve it?

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

Posted at 18:21 by Bojan Buhač | Category: Sharepoint | Permalink | Email this Post | Comments (0)

16.5.2009

Install & upgrade localized SharePoint farm to SP2 - part 2

This article is sequel to Install & upgrade localized SharePoint farm to SP2 - part 1 article in which we prepared installation resources to most recent SP.

Application role

After you have prepared slipstreamed contents, we can proceed with installation. On application server start MOSS-2007-x64-with-SP2 installation and when it comes to configuration wizard choose:

New farm,
Connect it to SQL server with proper account or simply use domain admin account (not recommended),
Wait for configuration to end,
Start installation from folder WSS-30-x64-LP-with-SP2 and run configuration wizard after installation finishes,
Start installation from folder MOSS-2007-x64-with-SP2 and run configuration wizard after installation finishes.

This concludes installation steps necessary for application role server and brings us to configuration. You need to start services and configure SharedService provider on this server before adding any new server to farm. So from central administration start following:

Document Conversions Load Balancer Service,
Document Conversions Launcher Service,
Windows SharePoint Services Search,
Office SharePoint Server Search,
Excel Calculation Services.

And after that in Shared Services Administration create new SSP. General recommendation is to create two web applications inside SSP one for SSP site and other for Mysite.

Web Front-End role

On front end server start MOSS-2007-x64-with-SP2 installation and when it comes to configuration wizard choose

Yes, I want to connect to an existing server farm,
Specify SQL server name and click Retrieve Database Names,
Provide same account you used while configuring Application role,
Wait for configuration to end,
Start installation from folder WSS-30-x64-LP-with-SP2 and run configuration wizard after installation finishes,
Start installation from folder MOSS-2007-x64-with-SP2 and run configuration wizard after installation finishes.

That's all. Go to Central administration and verify Servers in farm with their version.

Posted at 9:21 by Bojan Buhač | Category: Sharepoint | Permalink | Email this Post | Comments (0)

10.5.2009

Install & upgrade localized SharePoint farm to SP2 - part 1

Yesterday, I went in a SharePoint rampage in a Lab environment with localized SP2 environment. After couple of hours I've managed to install the all required SP2's on two servers.

Scenario

One DC and two member servers, all of them Windows 2008 x64
One member server has SQL 2008 x64, and he is now MOSS 2007 Application role server

IIS 7.0 and .NET 3.5 framework

Other member server will be MOSS 2007 Web Front-End role server

IIS 7.0 and .NET 3.5 framework

Preparation

Download MOSS 2007 x64 with SP1 (currently there is no Slipstreamed SP2)
Download SP2 for MOSS 2007 x64
Download SP2 for WSS 3.0 x64 EN
Download localized WSS 3.0 x64 language pack
Download SP2 for localized WSS 3.0 x64
Download localized Office Server 2007 language pack
Download SP2 for localized Office Server 2007

Nice isn't it

Slipstreaming

Create three folders
- 1. Folder - MOSS-2007-x64-with-SP2
- 2. Folder - WSS-30-x64-LP-with-SP2
- 3. Folder - MOSS-2007-x64-with-SP2

Copy installation files from MOSS 2007 x64 with SP1 to first folder, and delete all SP1 files in Update folder
Extract SP2 for MOSS 2007 x64 EN files to the same Update folder using extract command (SP2_filename /extract:<path>)
Extract SP2 for WSS 3.0 x64 EN files to the same Update folder using extract command,

Extract localized WSS 3.0 x64 language pack to second folder,
Extract SP2 for localized WSS 3.0 x64 to Update folder in the same folder,

Extract localized Office Server 2007 language pack to third folder,
Extract SP2 for localized Office Server 2007 to Update folder in the same folder.

Next article will address MOSS installation and upgrade procedure for two servers.

Posted at 22:45 by Bojan Buhač | Category: Sharepoint | Permalink | Email this Post | Comments (0)

1 - 10