SharePoint User Group UK

Hi everyone,

I've been a bit of a lurker here since Spencer Harbar (hello Spence!) first introduced the SUGUK site a few months ago but I've just recently came across a series of problems with our MOSS 2007 Farm implementation.

We had an issue where we had a web part on a team site that could not be deleted (would display the infamous 'Unexpected error encountered') and trying to edit the web part would result in nothing actually happening other than the browser windows focus jumping to the top of the webpage.

So I dived into the event logs of our web servers to see if there was perhaps a deeper explanation to the problem hidden within only to be confronted by a full event log full of 6482, 6398 and 7076 errors (and nothing to do with the problem I was looking for typically).

Specifically (I've omitted the Stack trace, can be provided if required):

----------------------------------------------------------------------------------------------------
Source: Office SharePoint Server
Category: Office Server Shared Services
Event ID: 6482
Description:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchAdminSharedWebServiceInstance (609392df-a32f-48ff-a23d-b307e378fda2).

Reason: Not enough storage is available to process this command.

Techinal Support Details:

System.Runtime.InteropServices.COMException (0x80070008): Not enough storage is available to process this command.
-------------------------------------------------------------------------------------------------------------------------
Source: Windows SharePoint Services
Category: Timer
Event ID: 6398
Description:
The Execute method of job definition Microsoft.Office.Server.Administration.ApplicationServerAdministrationServiceJob (ID 41cfde90-1c83-4465-aac5-48989cfb3d7f) threw an exception. More information is included below.

Not enough storage is available to process this command.
-------------------------------------------------------------------------------------------------------------------------
Source: Office SharePoint Server
Category: Office Server Shared Services
Event ID: 7076
Description:
An exception occurred while executing the Application Server Administration job.

Message: Not enough storage is available to process this command.

Techinal Support Details:

System.Runtime.InteropServices.COMException (0x80070008): Not enough storage is available to process this command.
-------------------------------------------------------------------------------------------------------------------------

These 3 errors happen after each other and has been repeating every few seconds for who knows how long.

Our Server farm consists of 6 machines:

2 Web servers runnning Windows Server 2003 sp2 with the .net 3.0 framework installed. (hosting server search, web application, incoming email, help search)
2 Application servers running Windows Server 2003 sp2 with .net 3.0 framework installed(one hosting central admin, doc conversions, doc conversion load balancer, excel calc, incoming email, the other just hosting server search)
2 database servers Running SQL 2005.

Now, both of my web servers are encountering these errors that I am describing above. Also, one of my app servers is also experiencing these errors except perhaps every 30 seconds to a minute the errors are describing a different reason:

Event ID: 6482, 6398, 7076
Reason: Old Format or invalid type library

Then the errors go back to describing the space issue as above.

I did a quick google search on the errors but any responses seems to revolve around instances of MOSS that was an upgrade from SharePoint Portal Server 2003 to MOSS 2007 and issues with version 2.0 of the .net framework. Some of these responses had a link to a possible hotfix for the .net framework which I am reluctant to touch at this time without further understanding of the errors I am specifically experiencing.

However, the server hosting the central admin application doesn't have any of these errors. Instead we have a few instances of the following error:

Source: Office SharePoint Server
Category: None
EventID: 5000
Description:
EventType ulsexception12, P1 owstimer.exe, P2 12.0.4518.1016, P3 45529fd9, P4 microsoft.office.server.search, P5 12.0.4518.0, P6 45439dcc, P7 2833, P8 183, P9 webexception, P10 837q.

A quick google of this resulted in suggestions that there where scheduled jobs that where overlapping each other. But a search of the Timer Job Status on Central admin came up with no errors reported.

Plus, and I am assuming this is releated, I am sometimes getting faced with the following error when I try to access the 'Manage Search Servce' section within Central Admin:

"A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host failed to respond"

But when I do finally get access it reports that the 3 servers that is reporting the above errors all have sufficient space (12/47/48 gig respectively).

Can anyone out there shed some light on what is causing these issues?

I finish work today at 4 but if anyone needs anymore information to help me then I can provide that first thing tomorrow morning (assuming anyone can help me).

Thanks in advance

Uber

Is there anyone who can help me with these issues?

If there is any other information I can provide to help someone help me sort this issue then please ask.

My first thought here is that your memory has run out on the servers. What is task manager and your performance counters telling you ? How much Memory is installed on the web servers ?

Steve Smith

Hi,

I am getting the same errors on the Index Server, I ahve not found any fixes yet, but have a read of the following article:

http://soerennielsen.wordpress.com/2007/06/29/%E2%80%9Dnot-enough-storage%E2%80%9D-event-log-error/

Let me know, if you find a fix

Thanks

Steve Smith wrote:

My first thought here is that your memory has run out on the servers. What is task manager and your performance counters telling you ? How much Memory is installed on the web servers ?

Steve Smith

All servers are running with 2gig of Ram,

as for task manager:

Web01:
owstimer.exe is using about 135 meg of available memory (134,768k to be exact)
wssadmin.exe is using about 618 meg of available memory (618.816k) is this normal?
w3wp.exe (process attached to our sharepoint site) is using about 198 meg of available memory (197,780k)
there is also another instance of the w3wp.exe using about 65meg as well (I think its the default app pool in IIS).
mssdmn.exe (attached to our SharePoint Search account) is using about 69meg of available memory (68,984k)
There is also two other instances of mssearch.exe attached to the same search account described above, using 20 meg (20,032k) and 58 meg (57,652k) respectively.

A total of 1.29 gig of ram is being used.
-----------------------------------------------------------------------------------------------------

Web02:
owstimer.exe is using about 202 meg of available memory (201,752k)
wssadmin.exe is using about 614 of available memory (613,976k)
w3wp.exe (process attached to sharepont site) is using about 184 meg of available memory (184,136k)
a second w3wp.exe taking up 184 meg (184,168k) attached to our mysites site collection (on Web01, this process if only taking up 6 meg)
2 instances of mssearch.exe taking up 71 meg between them.

A total of 1.42 gig or ram is being used.
-----------------------------------------------------------------------------------------------------

App01:
owstimer.exe is using about 182 meg of available memory (182,392k)
wssadmin.exe is using about 642 of available memory (642,812)
2 instances of w3wp.exe each using 73 meg (73,304k) and 93 meg (93,044k) respectively

A total of 1.11 gig or ram is being used.
-----------------------------------------------------------------------------------------------------

App02:
(first off there seems to be unexpected errors being encountred when I log on:
Application - Office SharePointe Server. 4 instances of this error, over 4 days at the exact same time. The error signature tells me:

EventType : ulsexception12     P1 : owstimer.exe     P2 : 12.0.4518.1016    
P3 : 45529fd9     P4 : microsoft.office.server.search     P5 : 12.0.4518.0    
P6 : 45439dcc     P7 : 2833     P8 : 183     P9 : webexception     P10 : 837q

So the timerservice is playing funny bugger again)

owstimer.exe is using about 364 meg of available memory (364,272k)
wssadmin.exe is using about 349 of available memory (348,572k)
w3wp.exe  is using about 58 meg of available memory (57,364k)
Microsoft.office.server.Conversions.Launcher.exe is using about 30meg of available memory (29,788k)
Microsoft.Office.Server.Conversions.LoadBalancer.exe is using about 23meg of available memory (23,204k)

A total of 1.45 gig or ram is being used.
-----------------------------------------------------------------------------------------------------

Does this provide any further insight?

Foxxi wrote:

Hi,

I am getting the same errors on the Index Server, I ahve not found any fixes yet, but have a read of the following article:

http://soerennielsen.wordpress.com/2007/06/29/%E2%80%9Dnot-enough-storage%E2%80%9D-event-log-error/

Let me know, if you find a fix

Thanks

I've seen similar response on the web after googling my problem but all my servers have version 3.0 of the .NET framework installed. I'm jus tnot sure if this update would be appropriate for my installation since the update is for version 2.0 of the framework.

Hi,

I started getting the error on our second web server as well,

What I did was as follows:

There were 2 Sharepoint service accounts missing from the local administrator account on the 2nd web server (compared the 1st web server), added these accounts in to the local administrator group on the server and restarted the Windows SharePoint Services Timer service.

Did the same thing on the index server (only one account was missing)

Have had no errors so far.

Thanks

Could you please elaborate on what accounts were missing, what you named them, and what permissions you gave them?

These are service accounts created for sharepoint, look at what account is used for the sharepoint timer service, this account needs to be part of the local admin group

Thanks

Hey Uber!

I think I know who you are but don't worry your secret is safe :)

I wouldn't touch this hotfix - what I wouold recommend however is installing the latest MOSS hotfix roll up. install the binary on each box running sharepoint and then run the config wizard - the gory details are on the kb article.  939654

I've seen this behaviour before in least privilege installs of MOSS (such as yours) also watch out for

http://www.harbar.net/archive/2007/06/29/SharePoint-Farm-Least-Privilege-and-hotfix-packages.aspx

after the patch installation.

cheers

s.

 

---

Cheers
Spence
www.harbar.net

harbars wrote:

Hey Uber!

I think I know who you are but don't worry your secret is safe :)

I wouldn't touch this hotfix - what I wouold recommend however is installing the latest MOSS hotfix roll up. install the binary on each box running sharepoint and then run the config wizard - the gory details are on the kb article.  939654

I've seen this behaviour before in least privilege installs of MOSS (such as yours) also watch out for

http://www.harbar.net/archive/2007/06/29/SharePoint-Farm-Least-Privilege-and-hotfix-packages.aspx

after the patch installation.

cheers

s.

 

Hey Spence,

Thanks for replying and providing a link to this hotfix. It hasn't been appled yet as I'm in the middle of writing up a plan to provide to the infrastructure team about applying the fix.

Can you tell me what is the actual cause of these events and what potential damage they can cause if left unchecked for so long? It's just so I have a better understanding of this issue.

Also, is there any particular order to the servers that the patch should be applied to? Considering that both web apps are running on NBL. Should it be web apps first and then App servers or vice versa, or does it not matter which order they are done?

Glad to hear you are doing well too, talk soon hopefully.

Cheers,

Uber

often times

http://sharepoint.microsoft.com/blogs/fromthefield/Lists/Posts/Post.aspx?ID=28

 

is the cause of 6398s

s.

---

Cheers
Spence
www.harbar.net

a fix has now been released for this

 

http://support.microsoft.com/Default.aspx?id=946517

---

Cheers
Spence
www.harbar.net

Thanks Spence!

Will look into getting this installed and will let you all know how i got on.

Not sure if you found the solution to this but we had a similar problem on removing web parts when we had a user that had copied text from another site into a web part, what was happenign was that an HTML tab was inadvertantly also getting copied.

For example you have a welcome note at teh top with 2 paragraphs of text in a rick text window, you copied this text from another Mock site. now you go to add other web parts or remove some web parts that you have on your default template but want to remove and you get an error.

The fix is to use designer to remove the Rich Text Web Part and then readd it and manually type the welcome message.

Just a knopwledge share, not sure if relevant, please let me know if it is. 

Durbs