John,

Thanks for this article. I am having a problem with an OWSTimer error and am starting to think it has to do with mixing 32-bit and 64-bit servers in my farm.

I have a fresh install of MOSS 2007 with 3 Windows 2003 R2 servers:

One 64-bit database server (SQL Server 2005 SP2), one 32-bit WFE

server, and one 32-bit Index/Query server. My web applications seem to

be working fine. However, in the Event Viewer on the Index/Query

server, I keep getting a whole bunch of errors - see screenshot 1

(www.intermedia4web.com/.../eventall.gif ) and screenshot 2

(www.intermedia4web.com/.../EventID5586.gif). I looked in the

trace logs and it seems like it's a problem with owstimer.exe . Here is

a sampling from the log:

================================

07/06/2007 20:59:51.97  OWSTIMER.EXE (0x0560)

0x0580  Office Server                   Setup and Upgrade

8u3j    High            Registry key value {SearchThrottled} was not found

under

registry hive {Software\Microsoft\Office Server\12.0}. Assuming search

sku is not throttled.

07/06/2007 20:59:52.06  OWSTIMER.EXE (0x0560)

0x0580  Search Server Common            MS Search Administration

90gf    Medium          SQL: dbo.proc_MSS_PropagationGetQueryServers

07/06/2007 20:59:52.14  OWSTIMER.EXE (0x0560)

0x0580  Search Server Common            MS Search Administration

8wni    High            Resuming default catalog with reason

'GPR_PROPAGATION'

for application 'SharedServices1'...

07/06/2007 20:59:52.36  OWSTIMER.EXE (0x0560)

0x0580  Search Server Common            MS Search Administration

7hmh    High            exception in SearchUpgradeProvisioner Keyword Config

System.InvalidOperationException: jobServerSearchServiceInstance is

null     at

Microsoft.Office.Server.Search.Administration.SearchUpgradeProvisioner..ctor(SearchServiceInstance

searchServiceInstance)     at

Microsoft.Office.Server.Search.Administration.OSSPrimaryGathererProject.ProvisionContentSources()

07/06/2007 21:00:01.67  w3wp.exe (0x08BC)

0x0900  Office Server                   Office Server Shared Services

6pls    Medium          Cache blocked for shared object

'1dd1db1d-8a07-4e27-9249-

b7d328818fa2' of type

'Microsoft.Office.Server.Search.Administration.SearchSharedApplication'.

================================

This error really worries me because I fear the instability this might

create. I have looked non-stop, for days, for an answer to this. Any

ideas as to why this is happening and what I can do to fix it?

Thanks!

Carol

John,

Thanks for the quick response. I will definitely check those things you mentioned.

Carol

Pingback from  Links (7/19/2007) « Steve Pietrek’s SharePoint Stuff

Pingback from  Sharepoint 2007 link love 07-20-2007 at  Virtual Generations

Thanks for the Article,

i was having the same error :

Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

and i 've just restarted the OWSTimer service and then every thing goes fine.

We've got a 64 bit setup and I am finding I can't get 3rd party web parts to work. For example, we're looking for an enhanced calendar like KwizCom or Bamboo Solutions calendar webpart. Neither of them seem to work, so I am really stumped on this and feel like I need to go back to the drawing board.

Hi Carol,

Did you resolve the OWSTimer issue? We're having the same problem. Any steer very gratefully recieved.

Thanks in advance,

Chris

Chris,

Unfortunately, we did not. This was in our development environment (we have not gone into production yet), so we decided to reload all servers with 32-bit Windows and 32-bit MOSS instead of 64-bit.

Carol

Has anyone has the proper solution for the "Attempted to read or write protected memory. This is often an indication that other memory is corrupt." error.

This error comes with the following events in Application logs:

events 6398, 8076,6482

Apparently there is a fix i found from some othe blogs (support.microsoft.com/.../923028)

but this error pops up after few days again after rebooting the machine. this becoming a pain now.

thanks

jaxy

I found that the 'Windows SharePoint Services Search' startup type had been set to disable. changing this to automatic and starting the service sorted my problem.

Found this blog on the issue...

geeks.ms/.../event-7076-6398-6482-regularly-displayed-in-the-event-log-on-a-sharepoint-server.aspx

I have migrated the sps2003 site to MOSS 2007 on a 32 bit development environment. Now i want to move the migrated site to production enivronment which is having two separate servers(32 bit for MOSS  and 64 bit for SQL Server).Is this necessary to have both MOSS and SQL server to have 32 bit machines? Any one please guide me to proceed successfully.

You can mix and match operating systems in your farm.  

to those having the "Attempted to read or write protected memory. This is often an indication that other memory is corrupt" error, this is a known issue with the Timer service, it has a memory leak.  We solved it by re-starting the timer service daily on all servers (Index first) with a batch job.  SP1 may fix it.  

I am having SharePoint server 2007 installed on windows 2003 32 bit envrionment , i am having the issue like the LOGS folder under %systemroot%/program files/common files/microsoft shared/web server extension/12 is reaching upto 6GB for 3 days.Please advice me what i can do to reduce the size of the diagnostic logging

Have you tried running the upgrade from SPS 2003 in 32bit mode on a Windows Server 2003 x64 edition to MOSS 2007?   It doesnt quite work does it. what a pain!  I had to go back to 32bit Windows to solve the headache, now do I go back to x64?

Thanks for this post, after much hair pulling it is at least encouraging to find that others are experiencing issues developing on x64.

I am able to develop MOSS 2007 Web Parts (can develop web parts that  install and work on the x64 server and x64 version of MOSS 2007) but I am unable to debug locally first.

I still get the dreaded "Could not load file or assembly ‘Microsoft.SharePoint.Search, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c’ or one of its dependencies" error at runtime when debugging on my localhost (VS 2008 using ASP.NET Development "cassini" web server) .

This is after advice from an MS SharePoint MVP:

Go create an explicit reference to the Microsoft.SharePoint.Search DLL – the 64 bit version in the GAC.  Then in your project tell it not to copy the Microsoft.SharePoint.Search.DLL (Right click on the reference and select properties.)  Make sure that you are NOT deploying a 32 bit version of the search DLL.

VS is a 32 bit application…. It sometimes gets confused.

I've encountered the "6398-6482-7076 error chain" at a customer recently. Resetting IIS and the OWSTimer Services is a workaround, but not a permanent fix. The customer in question gets a call every 2-3 months, with increasing frequency.

The bug, though it appears to be SharePoint-related (the Timer service is the "smoking gun" that appears in the error logs), it is really an IIS issue, and is not specific to 64-bit environments (my customer was on a 32-bit farm). This hotfix is available for the issue: support.microsoft.com/.../946517.

Yes, it's time to move to 64-bit MOSS if you haven't already. Here are a few points that I have been

TO everyone getting the IIS manager problem, along with sharepoint timer errors in moss:

Download hotfix 946517 from MS: support.microsoft.com/.../946517. This fixes BOTH issues.

...i too have had the protetced memory error and discovered that by going inot the bios and diasbling extnded memory protection this cured the error...

Thanks Mike Catignani for this update.  I am about to install MOSS on Windows 2008 x64.  I will post my outcome.  Good or bad.  :-)