SharePoint Blog - René Hézser

Anmelden RSS Feed RSS Feed
Startet die SucheErweiterte Suche

Archive

Kategorien

Links

Andere Blogs



Add to Technorati Favorites

Sep 282009

Disable Loopback Check?

A while ago Microsoft released an update, which prevents that you can log on locally to a website which has a FQDN.

To resolve issues with e.g. the crawling a KB article has been published.

You receive error 401.1 when you browse a Web site that uses Integrated Authentication and is hosted on IIS 5.1 or a later version

You can disable the loopback check completely, or just for the used FQDNs. This would be the better way.

Manually setting the required registry entries on every SharePoint server in the farm can be a nasty task.

A better way to do so is a custom stsadm extension. Gary Lapointe has written such an extension. Take a look at it: Setting Back Connection Host Names for SharePoint 2007 Using STSADM

Quote:

You can of course do this using Group Policy but for those not managing their servers using GPO I decided to implement a custom STSADM command that would make setting the BackConnectionHostNames registry key really simple.  I called this new command, oddly enough, gl-setbackconnectionhostnames.

The following is an example of how to update the BackConnectionHostNames registry key on the current server only:

stsadm -o gl-setbackconnectionhostnames

The following is an example of how to update the BackConnectionHostNames registry key on all servers in the farm:

stsadm -o gl-setbackconnectionhostnames -updatefarm -username domain\spadmin -password pa$$w0rd

Download of the custom stsadm extension: http://stsadm.blogspot.com/2009/02/downloads.html (WSS Only STSADM Extensions (x86, x64))


Published: 9/28/2009  11:41 AM | 2  Comments | 0  Links to this post
Tagged as: SharePoint, Solution

Jun 242009

.NET 3.5 and Silverlight

Using AJAX or Silverlight from within SharePoint in Webparts requires you to modify the web.config to support the technology. I don’t mention that you have to install the .NET Framework 3.5 SP1 and Silverlight to be able to use it…

Instead of changing the web.config manually (.NET Framework 3.5 AJAX und Silverlight in SharePoint registrieren von Fabian Moritz), you can use my features. They do all the necessary changes for you. The Silverlight feature requires the .Net 3.5 feature.

image

Installation

  1. Add the solution to your farm “stsadm -o addsolution -filename RH.Net35WebConfig.wsp”
  2. Deploy the solution “Central Administration > Operations > Solution Management”
  3. Activate the features on a web application “Central Administration > Application Management > Manage Web Application Features”

Uninstall the solution

After you’ve deactivated the feature(s), you might get an exception (if you have set your customErrors to Off, or visit the site from your SharePoint Server):

image

This exception is thrown, because the IIS does not like the empty XML Nodes:

<system.web.extensions>
  <scripting>
    <webServices>
    </webServices>
  </scripting>
</system.web.extensions>

You can safely delete the empty nodes from your web.config.

Update 22. Aug 2009

Add section configuration/system.web/pages if it does not exist.

Download

Download RH.Net35WebConfig.wsp

Download Source RH.Net3.5WebConfig-Source


Published: 6/24/2009  7:13 PM | 0  Comments | 0  Links to this post
Tagged as: Development, SharePoint, Solution

May 262009

Solution deployment fails

Deploying a SharePoint solution (.wsp file) to a SharePoint farm should be easy. Even if the farm contains 4 SharePoint Servers.

Just stsadm –o addsolution –filename solution.wsp. Some waiting so the deployment is done on every server, and we should be happy.

Well, the result was an Error in the solution status. Additionally the ULS log showed

Updating SPPersistedObject SolutionOperationStatus Name=SolutionOperationStatus Parent=SPSolutionLanguagePack Name=0. Version: -1 Ensure: 0, HashCode: 38896601, Id: 87c32e71-13f0-4d85-a215-29f1d180d239, Stack:    at Microsoft.SharePoint.Administration.SPPersistedObject.Update()     at Microsoft.SharePoint.Administration.SPSolutionLanguagePack.SetOperationResult(SPSolutionOperationResult opResult, String msg, SPWebApplication webApp, Int32 updatesPerServer)     at Microsoft.SharePoint.Administration.SPSolutionLanguagePack.DeployFilesInstallFeatures(SPWebApplication webApp, Boolean globalInstallWPPackDlls, Boolean installFeatures, Boolean force, Int32 tries)     at Microsoft.SharePoint.Administration.SPSolutionLanguagePack.DeployLocalCore(Boolean globalInstallWPPackDlls, Collection`1 webAppl...

...ications, Boolean useAdminService, Boolean force)     at Microsoft.SharePoint.Administration.SPSolutionDeploymentJobDefinition.Execute(Guid targetInstanceId)     at Microsoft.SharePoint.Administration.SPTimerJobInvoke.Invoke(TimerJobExecuteData& data, Int32& result)

To get rid of the error, I went to the Timer Job definitions, and deleted the one which tried to add deploy the solution. The status went back to not deployed.

The reason for the Error was that the “Windows SharePoint Services Administration” was not stated on all SharePoint servers. After the services has been started, the deployment worked just as I expected it.

So make sure your Administration service is started, and running as System Account!


Published: 5/26/2009  11:04 AM | 0  Comments | 0  Links to this post
Tagged as: SharePoint, Solution

Feb 152009

The file manifest.xml does not exist in the solution package

Creating a SharePoint solution file (which is a cab file renamed to wsp), can cause problems if the size of the file would exceed the space on an 1.44MB disk.

1.44MB? What the…? The default values for makecab, which is used for generating the cab file, will prevent the creation of a valid cab file :-(

Thanks to Eugene Rosenfeld for finding this one.


Published: 2/15/2009  7:05 PM | 0  Comments | 0  Links to this post
Tagged as: Solution, SharePoint

 Next >>