Nerfed Tech

So we were getting an error where the import command was telling us the parent site didnt exist, and the import fails.

Looking into the Export log, we found:

Error: Access is denied. (Exception from HRESULT: 0×80070005 (E_ACCESSDENIED))
at Microsoft.SharePoint.SPGlobal.HandleUnauthorizedAccessException(UnauthorizedAccessException ex)
at Microsoft.SharePoint.Library.SPRequest.GetFileAsByteArray(String bstrUrl, String bstrWebRelativeUrl, Boolean bHonorLevel, Byte iLevel, Boolean bUnprotected)
at Microsoft.SharePoint.Deployment.FileSerializer.SaveFile(SerializationInfo info, ExportObjectManager objectManager, ExportDataFileManager fileManager, SPExportSettings settings, SPWeb parentWeb, Boolean isGhosted, String setupPath, String setupPathUser, Byte setupPathVersion, String webRelativeFileUrl, Int32 size, Byte level)

The import error was:

Error: The file  cannot be imported because its parent web /sites/grizzly/SAISB/grizzly does not exist.

Progress: Importing File Lists/General Discussion/Threaded.aspx.

  [8/27/2007 3:20:18 PM]: Error: Current item failed in the export with the error message: Access is denied. (Exception from HRESULT: 0×80070005

The fix was to grant the person doing the export site collection administrator status, then do the export.

So… some users were getting the

The document could not be opened for editing. A Windows SharePoint Services compatible application could not be found to edit the document.

dialog box error message when trying to open a word document in document library using the “Edit in Microsoft Word” drop down command.

After some investigation it turned out that they had created a HUGE URL trail in side the document library by creating folders with really long special character laden names. The URL was around 300 characters long or some such nonsense. IE’s limit is around 2084 so its not IE, probably SharePoint or Word related limitation on URL length, or some special character interference.

I shortened all the directory names and took out some of the special characters and it seemed to clear up the problem.

How annoying is that???

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

Alerts from lists and sites were being sent sporadically or not at all. When i looked into the Timer Job Status page in central admin, i noticed that the set of jobs on 1 of our Load Balanced Web Front Ends were in bad states. Specifically, 2 of them were stuck in Initializing, and 2 of them were stuck in Failed.

We restarted the Windows SharePoint Services Timer ( SPTimerV3 ) in Services Console, and this resolved the problem.

Usage Log Reporting Problem

Symptoms:

Little to no usage log data when looking at usage reports. Empty Usage Log files in the logging directories.

Problem:

During an upgrade from SPS 2003 to MOSS 2007, we think the usage logging directory was set to “C:\Windows\System32\LogFiles\STS”. This is the old SPS logging area? The ACL for this area did not contain the WSS_ADMIN_WPG or WSS_WPG groups. These groups are needed to give SharePoint access to write to the log file directory.

Solution:

Corrected the Log file directory in Usage Analysis Administration to use the “C:\program files\Common Files\Microsoft Shared\web server extensions\12\Logs” directory. This directory gets the two security groups added to it by the SharePoint installation.

Active Directory Profile Imports Failure

Symptoms:

Stale AD Profile Data being reported in sharepoint.
New users not having their profile imported.
Old users not being deleted.

Event log Entries like :

Event Type: Error
Event Source: Office Server Search
Event Category: Gatherer
Event ID: 2424
Date: 8/24/2007
Time: 6:00:26 AM
User: N/A
Computer: AI-MOSEMP1
Description:
The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.

Context: Application ‘MOSS1′, Catalog ‘SharedServices ProfileImport’

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Problem: The credentials in the Share services Administration for Profile Imports were incorrect.

Solution: Corrected the Credentials

Ever had a problem with sysfader.exe popping up errors?

Try this : http://beyondteck.blogspot.com/2006/05/how-to-stop-sysfaderexe-error.html

What is sysfader.exe? Is it Spyware? How much memory does it take up? Why does it give error?
Well, no first of all, it is not spyware. In fact it is a part of Windows XP that provides all the so called “cool animation effects”. These include fading menus in and out. Animating windows and so on. Nothing to worry about, unless it is giving you errors. But as a person who uses computers (and yes, I mean computers running Windows) a lot, I recommend that you disable all these extra effects. This in turn is going to make your computer faster and rid of the sysfader.exe problem.

Today I read a couple of e-mail from people telling me that they had an error regarding sysfader.exe. I’m guessing that this might be a common problem for a lot of people, besides the tips mentioned in this post are good for any computer running Windows. Be it Windows XP or Windows Vista (although the instructions for disabling unnecessary effects are different for Vista).

To get rid of this problem all you need to do is this:

1. Press Windows Flag (Windows Key) + Pause break key. If you don’t have the Windows key (most keyboards should have this - right beside the Alt key) just right click on My Computer and click Properties.
2. Go to the ‘Advanced‘ tab
3. Under ‘Performance‘ click on ‘Settings‘
4. Under the ‘Visual Effects‘ tab uncheck the first four check boxes
5. These 4 boxes are “Animate windows when minimizing and maximizing“, “Fade or slide menus into view“, “Fade of slide ToolTips into view” and “Fade out menu items after clicking“. Please note that if you are running other localizations of Windows XP (for example Windows XP Portugese) you have to find the options that somewhat describe the options mentioned above, since they might not be the first 4 options.
6. To make your computer even more faster, uncheck other checkboxes for the effects that you feel you can live without, for example “Slide taskbar buttons” etc…
7. Click on ‘OK‘

After doing this the problem with sysfader should instantly go away. And your computer is going to become much more faster without those annoying (at least I find it annoying) effects slowing it down.

I backed up and restored 2 content databases to a different farm. The content databases were serving applications originally on ports 33333 and 44444. Executing -o addcontentdb on the new farm to the 44444 port, for either database, works fine. When i brought these backups back to the original farm, i cant restore the 44444 content database to anything other than the 44444 port, even though the 33333 was restorable to 44444 on the other farm.

The content database gets added by the -o addcontentdb command, but it reports 0 sites…

Perplexing.

Found this answer here: http://sharepoint.microsoft.com/blogs/fromthefield/Lists/Posts/Post.aspx?ID=14

Timer Job Shocker Problem A customer was having a problems with Central Administration.  The backups would fail.  Creating a new web application would fail.  IIS manager couldn’t be opened.  An IISRESET sorted the problem temporarily but it soon came back. Symptoms I noticed the event log was generating 6 types of events at regular intervals since the 26/6/8.  They were: 7076 Attempted to read or write to protected memory 7076 Exception from HRESULT 0×80005006 6482 Attempted to read or write to protected memory 6482 Exception from HRESULT 0×80005006 6398 Attempted to read or write to protected memory 6398 Exception from HRESULT 0×80005006 They are all problems with the Application server administration Job. Answer I stopped the errors and the behaviour by doing two things: Installed hot fix 923028 for .NET 2.0 Re-entered the username and password for the SharePoint timer job service I’ve been told that for event 6398 you should check that he SSP service account is a member of the local WSS_ADMIN_WPG group on all query and index servers.

After restoring a site to a new URL, its search center wasnt functioning. Its links were all pointing to the old url. I just deleted and recreated it to fix the problem.

Annoying.