In the past I encountered this problem myself and a colleague of mine had the same problem this week. Uploading large files to SharePoint 2007 that is installed on a Windows Server 2008. By accident I have found the following post through the “Windows Server 2008 Resource Center for SharePoint Products and Technologies” which can [...]

Continue reading about Large file uploads on Windows Server 2008 SharePoint 2007 WFE

The application log of one of the sharepoint farm servers filled with the event id’s 6482, 7076 and 6398. On the Technet forum I found a link to KB article 946517. The hotfix descripted in this article solved the errors on the SharePoint farm.
The hotfix is for Windows 2003 and 2008.
The contents of the errors [...]

Continue reading about Event IDs 6482, 7076 and 6398 on SharePoint 2007 server solved

MarC on February 10th, 2010

If you have been installing SharePoint you have probably also seen and fixed the DCOM 10016 error. This error occurs in the event log when the SharePoint service accounts doesn’t have the necessary permissions (Local Activation to the IIS WAMREG admin service).
On a Windows Server 2003 or Windows Server 2008 machine you would just fire [...]

Continue reading about DCOM 10016 error on Windows Server 2008 R2

In the past this error could be solved by giving the mentioned accounts the “Local Launch” and “Local Activation” permissions to the IIS WAMREG admin service through Component Services.
On Windows Server 2008 R2 this is quite different. The property dialog is all disabled due to permission restrictions. It doesn’t matter if you are logged in [...]

Continue reading about Fix for SharePoint DCOM 10016 error on Windows Server 2008 R2

MarC on October 30th, 2009

Today I wanted to logon to the SharedServicesProvider (SSP) of one of our SharePoint servers (Windows Server 2008 R2 with SharePoint 2007 CU June 2009) but was unable to do so. In the eventlog there was an event ID 4625 “An account failed to logon”. The text of the event ID is below.
An account failed [...]

Continue reading about Event ID 4625 an account failed to logon (solution)

MarC on October 27th, 2009

At the moment I’m trying to deploy the ConnectedLookup 2.0 solution from CodePlex (download it here) at a customer SharePoint farm. Recently I deployed this solution succesfully at several other farms but now I’m running into some problems. Maybe you can help.
I first tried to deploy with the setup.exe file and secondly with the addsolution and [...]

Continue reading about Trust node error during solution deployment

After the installation of this solution, described in my previous post, I got an error in the eventlog:
Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Web Controls
Event ID: 7043
User:  N/A
Description:
Load control template file /_controltemplates/ConnectedLookupFieldEditor.ascx failed: Could not load the assembly ‘ConnectedLookupField, Version=2.0.0.0, Culture=neutral, PublicKeyToken=a646907c4a695009′. Make sure that it is compiled before accessing the page.
Resolve this by doing:

Open a windows [...]

Continue reading about SharePoint Connected Lookup with multiple childs (part 2)

MarC on June 23rd, 2009

Recently I was troubleshooting a SharePoint farm of a customer. The crawl of the content sources did not work and always ended with a “access denied” error in the crawl log. In the eventlog event ID 2436 appeared: “Access is denied. Check that the Default Content Access Account has access to this content, or add [...]

Continue reading about DisableLoopbackCheck on Windows Server 2008

MarC on June 15th, 2009

At a customer SharePoint farm there was a “strange” situation. When clicking the My Site link on the top right of the portal home page there appeared a 404 error page. It seemed that the root site of the My Site collection had disappeared. The only thing I heard was that a administrator had tried [...]

Continue reading about Recreate My Site Root

MarC on May 25th, 2009

Found on the Microsoft SharePoint Team Blog:
During the installation of SP2, a product expiration date is improperly activated. This means SharePoint will expire as though it was a trial installation 180 days after SP2 is deployed. The activation of the expiration date will not affect the normal function of SharePoint up until the expiration date [...]

Continue reading about SharePoint Service Pack 2 bug