We were getting an error on one of our Load balanced web servers.

First of all we got “Attempted to read write to protected memory” error followed by the “The path specified cannot be used at this time” which is then logged every minute in the event viewer on our server.

This then ends up using all the resources on that server, which then makes the server become unavailable. Once the machine becomes unavailable it will move onto the next server and kill that one.

This was reported to Microsoft support and they identified it as a bug that will be fixed in SP1.

In the meantime the following will need to be done to work around this problem.

  1. Install the following hotfix 923028
  2. Retype the password for the search service from The central administrator page.
  3. Run “services.msc” and select the Windows SharePoint Services Timer
  4. Make sure the service is running with a MOSS service account, if it is running with MOSS services account then stop the service, retype the password and then start the service account again.
  5. Install / script a tool that automatically restarts the Windows SharePoint Services Timer when the following Event IDs are raised; 6398, 6482 and 7076. Microsoft Support maybe able to provide you with this tool if you raise a support request with them.

This is a particularly scary bug to be appearing in a “Production” ready product, especially as it is only happening in the farm environment and can take down you whole farm.

I believe there needs to be more information on the whole way SharePoint propagates between servers in a farm, there seems to be little understanding of it presently.

Comment and share

UPDATE

I have had an update from Microsoft on this issue, apparently the wording is wrong.

It will retain the number of major versions entered, but the number for minor versions is not to limit the number of minor versions, but to limit the number of major versions that have minor versions (Does that make sense?).

For example, if I set major versions to 10 and minor versions to 2, it will show me 10 major versions of which 10 and 9 will have minor versions still available.

The problem here is that I can still create 100 minor versions so this is not helping me limit the amount of versions my users keep and keep my storage costs down


In a document library under “Versioning Settings” you can choose to set the number of major and minor versions to retain.

Number of version to retain

This does not work! You are still able to create more than the number of versions specified in both major and minor

Version

I have spoken to Microsoft and they have confirmed this to be a “design limitation”. Has anyone ever got someone at Microsoft to say “bug”?

I’ll keep you updated if I get a fix for this.

Comment and share

There is currently a bug in MOSS 2007 search that automatically converts any URLs entered to lower-case.

We had a site hosted on a UNIX server that had a case sensitive URL, so when I entered http://server.net/Start/Welcome.html MOSS 2007 converted it to http://server.net/start/welcome.html and then tried to crawl this URL, but UNIX would return a “page could not be found” error.

Microsoft provided us with a hotfix for this, so if you have the same problem I suggest you raise a support request. :-)

Comment and share

SSO Configuration

in admin

If you are getting errors when trying to configure SSO in MOSS 2007, something we discovered that solved this that is worth trying

  1. In Central Administration go to Operations·
  2. Under Secuirty Configuration, click on Service Accounts·
  3. Select “Windows service” option and then “Single Sign-on service” in the corresponding dropdown·
  4. Enter in the service account username and password·
  5. Click OK

Even though we had set this up through the “Services” console, doing this through the central administration screen fixed the problem.

Some of the errors we were getting was “Login failed for user: domain\user” in the event logs

Comment and share

UPDATE

Don’t use the Sharepoint Solution Generator, so far we have not been able to upgrade the site definitions through a solution without it killing existing sites based on the site definition.


I have seen many different ways of doing this, but I found the following method seemed to work for me, using the “SharePoint Extensions for Visual Studio 2005” and the “SharePoint Solutions Generator

  • Use the “SharePoint Solution Generator” to create a site definition project.
  • Open the project and add your custom master page to the “Site Definition” folder

  • Open up “onet.xml”
  • Add the following node to the “ListTemplates” section
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
<ListTemplate 
Name=”mplib”
DisplayName=”$Resources:MasterPageGallery;”
Description=”$Resources:global_onet_mplib_desc;”
SetupPath=”global\lists\mplib”
Type=”116”
BaseType=”1”
Path=”GLOBAL”
Hidden=”TRUE”
HiddenList=”TRUE”
NoCrawl=”TRUE”
Unique=”TRUE”
Catalog=”TRUE”
OnQuickLaunch=”FALSE”
SecurityBits=”11”
AllowDeletion=”FALSE”
AllowEveryoneViewItems=”TRUE”
Image=”/_layouts/images/itdl.gif”
AlwaysIncludeContent=”TRUE”
DocumentTemplate=”100”
/>
  • Add the “MasterUrl” attribute to the “Configuration” node with a value of “_catalogs/masterpage/project.master”, where project.master is the name of your custom master page. This means all the pages using the “~masterurl/default.master” token will use the URL defined to point to your custom master page
1
2
3
4
5
<Configuration 
ID=”0”
Name=”Default”
MasterUrl=”_catalogs/masterpage/project.master“
>
  • Add a “Module” node to the Modules section of the configuration called “MasterPage” that will reference the module definition in the “Modules” section of the onet file
1
<Module Name=”MasterPage” />
  • Add a module definition to the “Modules” section of the onet file. This will copy the custom master page file into the master page library when the site is provisioned.
1
2
3
4
5
6
7
8
9
10
11
<Module 
Name=”MasterPage”
List=”116”
Url=”_catalogs/masterpage”
RootWebOnly=”FALSE“>
<File
Url=”project.master”
Type=”GhostableInLibrary”
IgnoreIfAlreadyExists=”TRUE”
/>
</Module>
  • Save the onet file and then deploy the project into your environment using the deploy option in “SharePoint Extensions for VS 2005”
  • When you create a new site from your site definition it should now use your new master page.

Below is a screen grab of the onet.xml file with all the changes highlighted

Comment and share

  • page 1 of 1
Author's picture

Toby Statham

Independent Office 365 / SharePoint Specialist and an associate consultant at aiimi.com, an Information Management company.

Independent Office 365 / SharePoint Specialist

Brighton, UK