Home - MCPblog

10.4.2010

TSWA 2008 error - Attempted to read or write protected memory

If you experience following error accesing TFS web access, don't worry there is a solution.

"Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below."

Go to TFS cache folder "C:\Program Files\Microsoft Visual Studio 2008 Team System Web Access\Cache" and add NETWORK Account Change Permission.

Note!!!

If this doesn't work, go to web.config of TFSWA and modify location of cache to new location.

And reconfigure NTFS permissions for NETWORK account.

Posted at 15:32 by Bojan Buhač | Permalink | Email this Post | Comments (0)

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)

18.12.2009

TFS 2008 convert Workgroup license to Standard

If you have installed Team Foundation Server 2008 Workgroup edition than you may or may not know that you are eligible to only 5 licensed users. To unlock full potential of TFS for > 6 users you need to convert your product to Standard Edition.

Of course you need to have Standar Edition license, or if you have MSDN subscription, you can get it from there. Technet user, don't bother to look on technet since TFS is not available via technet. Microsoft Partners (Regular or Gold) will have to browse their DVD's or MSDN.

If you have key keep reading.

Go to add/remove programs, find TFS and select Change/Remove button:

Maintenance mode Options page will appear and you'll find that PID field is been prepopulated with some key. Don't be happy, because this is workgroup edition key!!! Silly, isn't it.

Problem is that setup.sdb file is been prepopulated with this key, and you need to delete PID section from this file. File can be found at:

C:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Microsoft Visual Studio 2008 Team Foundation Server - ENU\Setup.stb

Open it with Notepad, find and delete section Product key (both rows), and save changes.

Restart maintenance mode via "change/remove" and the fields are enabled. Type new product key, and press Next.

To verify version of TFS open registry (regedit.exe) and browse to:
HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > VisualStudio > 9.0 > TeamFoundation > Registration

You'll find a value named, "Edition_CT", Here's the table of available values to determine which edition you have:

"Full" = Team Foundation Server ("Standard Edition")
"Trial" = Team Foundation Server 180-day Trial Edition
"Workgroup" = Team Foundation Server Workgroup Edition

Posted at 13:02 by Bojan Buhač | Category: ASP.net | 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)

30.11.2009

Installing Team Foundation Server 2008 on Windows 2008 and SQL 2008

Today I have decided to deploy Team Foundation Server 2008 into my production environment, and imagine what? Yeeeees I run into a lot of problems. But you can presume, as I'm writing this post, I've managed to solve them.

So, if you want to do straightforward installations of TFS follow these steps:

Environment

Account <domain>\tfsadmin in as regular user
Platform: Windows Server 2008 with SP2 x86
- .NET 3.5 installed
- IIS installed
- Add <domain>\tfsadmin into local admins
SQL 2008 Standard (WITHOUT SP1 !!!!)
- Services are running under <domain>\tfsadmin
Log in as different user with local admin privileges

TFS SP1 slipstreaming

Create three folders on your C:\ drive
- TFSSP1
- TFSSP1extract
- TFS
- TFSwithSP1
Download TFS SP1 from http://www.microsoft.com/downloads/details.aspx?FamilyID=9e40a5b6-da41-43a2-a06d-3cee196bfe3d&displaylang=en
Copy it to C:\TFSSP1
From TFS install media copy contents from AT folder to TFS
To extract SP1 open command prompt ant type
C:\TFSSP1\TFS90SP1-KB949786-ENU /extract:C:\TFSSP1Extract
To merge installation with SP1 type:
msiexec /a C:\TFS\vs_setup.msi /p C:\TFSSP1Extract\TFS90sp1-KB949786.msp TARGETDIR=C:\TFSwithSP1

Than simply run setup from TFSwithSP1. From there you'll find that installation is pretty much simple. Keep in mind that you have to use TFSADMIN account during installation.

After you finish you can create new projects from some other workstation that has VS2008. Of course you need Team Explorer 2008 (http://www.microsoft.com/downloads/details.aspx?familyid=0ed12659-3d41-4420-bbb0-a46e51bfca86) and FINALLY you'll have to reinstall SP1 for VS after you install Team Explorer if you want to avoid this error (http://www.thejoyofcode.com/TF03177_Team_Project_Creation_Failed.aspx).

Another guideline I can give you when setting permissions developers is:

Set permissions on http://<tfsserver>/reports (from workstation as admin)
- Click Orange Properties on Home location
- New Role Assignment > Content Manager (One that will create project)
Site Settings in upper right corner
- Click Security in left side
- New Role Assignment > System Administrator (One that will create project)
If you are using Workgroup edition add users to Licensed Users group on TFS

Happy Teaming :)

Posted at 20:01 by Bojan Buhač | Category: ASP.net | 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)

28.10.2009

Active Directory Lightweight Services (ADAM) and ADSIEDIT ports

As you may know or may not know Exchange's EDGE role requires operating server that is not member of active directory. So how EDGE server knows info about recipient, configuration, and schema? One of the requirements before installing EDGE role is to install ADAM (on Windows Server 2003) or Active Directory LightWeight Directory Service Role (on Windows Server 2008). Btw, ADAM is short for Active Directory Application Mode and its kind a special mode of Active Directory service designed to store information for directory-based applications. Yes, the one that can read and speak LDAP.

After you're done with installation you have ADSIEDIT utility to examine data stored in partitions of this special AD. With regular AD you have data in "NTDS.DIT", here data is stored in "<EXCHANGE LOCATION>\TransportRoles\data\Adam\ADAMNTDS.DIT".