Submit My Question - Recent Questions - Recent Answer
Msdn Tech >> SharePoint Products and Technologies >> SharePoint - Setup, Upgrade, Administration and Operation

Persistent Sharepoint Server Error Events

Hi -

I'm running Sharepoint Services 3.0 and am seeing 3 different errors logged every single minute - IDs 6398, 7076, and 6482. Searches on these IDs have shown that other users are seeing them for different reasons. They all have to do with a "lack of storage" somewhere. Below are the pasted contents of 1 of each of these errors:

Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Timer
Event ID: 6398
Date: 1/22/2007
Time: 3:41:17 PM
User: N/A
Computer: SPNACDEV06
Description:
The Execute method of job definition Microsoft.Office.Server.Administration.ApplicationServerAdministrationServiceJob (ID 929b1b3b-ef23-4379-915f-33e61709a2d3) threw an exception. More information is included below.

Not enough storage is available to process this command.


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

Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server Shared Services
Event ID: 7076
Date: 1/22/2007
Time: 3:41:17 PM
User: N/A
Computer: SPNACDEV06
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.


Server stack trace:
at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
at System.DirectoryServices.DirectoryEntry.Bind()
at System.DirectoryServices.DirectoryEntry.get_IsContainer()
at System.DirectoryServices.DirectoryEntries.CheckIsContainer()
at System.DirectoryServices.DirectoryEntries.Find(String name, String schemaClassName)
at Microsoft.SharePoint.AdministrationOperation.Metabase.MetabaseObjectCollection`1.Find(String name)
at Microsoft.SharePoint.AdministrationOperation.Metabase.MetabaseObjectCollection`1.get_Item(String name)
at Microsoft.SharePoint.AdministrationOperation.SPProvisioningAssistant.ProvisionIisApplicationPool(String name, ApplicationPoolIdentityType identityType, String userName, SecureString password, TimeSpan idleTimeout, TimeSpan periodicRestartTime)
at Microsoft.SharePoint.AdministrationOperation.SPAdministrationOperation.DoProvisionIisApplicationPool(String name, Int32 identityType, String userName, String password, TimeSpan idleTimeout, TimeSpan periodicRestartTime)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.SharePoint.AdministrationOperation.SPAdministrationOperation.DoProvisionIisApplicationPool(String name, Int32 identityType, String userName, String password, TimeSpan idleTimeout, TimeSpan periodicRestartTime)
at Microsoft.SharePoint.Administration.SPMetabaseManager.ProvisionIisApplicationPool(String name, Int32 identityType, String userName, SecureString password, TimeSpan idleTimeout, TimeSpan periodicRestartTime)
at Microsoft.Office.Server.Administration.SharedWebServiceInstance.CreateSharedWebServiceApplicationPool(SharedResourceProvider srp)
at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

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

Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server Shared Services
Event ID: 6482
Date: 1/22/2007
Time: 3:41:17 PM
User: N/A
Computer: SPNACDEV06
Description:
Application Server Administration job failed for service instance Microsoft.Office.Project.Server.Administration.ProjectApplicationServiceInstance (57f6ad55-2755-46e5-96d5-7023d8dc0375).

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.


Server stack trace:
at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
at System.DirectoryServices.DirectoryEntry.Bind()
at System.DirectoryServices.DirectoryEntry.get_IsContainer()
at System.DirectoryServices.DirectoryEntries.CheckIsContainer()
at System.DirectoryServices.DirectoryEntries.Find(String name, String schemaClassName)
at Microsoft.SharePoint.AdministrationOperation.Metabase.MetabaseObjectCollection`1.Find(String name)
at Microsoft.SharePoint.AdministrationOperation.Metabase.MetabaseObjectCollection`1.get_Item(String name)
at Microsoft.SharePoint.AdministrationOperation.SPProvisioningAssistant.ProvisionIisApplicationPool(String name, ApplicationPoolIdentityType identityType, String userName, SecureString password, TimeSpan idleTimeout, TimeSpan periodicRestartTime)
at Microsoft.SharePoint.AdministrationOperation.SPAdministrationOperation.DoProvisionIisApplicationPool(String name, Int32 identityType, String userName, String password, TimeSpan idleTimeout, TimeSpan periodicRestartTime)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.SharePoint.AdministrationOperation.SPAdministrationOperation.DoProvisionIisApplicationPool(String name, Int32 identityType, String userName, String password, TimeSpan idleTimeout, TimeSpan periodicRestartTime)
at Microsoft.SharePoint.Administration.SPMetabaseManager.ProvisionIisApplicationPool(String name, Int32 identityType, String userName, SecureString password, TimeSpan idleTimeout, TimeSpan periodicRestartTime)
at Microsoft.Office.Server.Administration.SharedWebServiceInstance.Synchronize()
at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

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

They don't seem to be "breaking" my sharepoint implementation in any noticable fashion, but 3 errors every minute are worth investigating. Thanks in advance for any help anyone may be able to provide.
[8074 byte] By [ChockFulloNuts] at [2007-12-30]
«« Regular Expression Help
»» Error Creating Control - CreateUserWizard1
# 1

Yes, we have this too.

We also have issues with not being able to view sites in explorer view.

Regards,

sb132 at 2007-9-5 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
# 2
We're logging this issue as well, though we have no visible issues being reported.
KevinFusselman at 2007-9-5 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
# 3

The error was solved by giving the applcation pools different domain accounts.

Still not perfect, but getting better: is seems that the security (both domain and SharePoint) is more more complex that before, which may contribute to the variety of errors experienced by both end-users and admin staff.

Regards,

sb132 at 2007-9-5 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
# 4

EXACTLY same problem here

in 2 different, physically seperated domains.

GeorgH at 2007-9-5 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
# 5
sb132 wrote:

The error was solved by giving the applcation pools different domain accounts.

could you maybe elaborate on that a bit? which app pools? which accounts? which rights?

GeorgH at 2007-9-5 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
# 6

Hi,

I created to domain accounts, Sharepoint, and SharepointAdmin. I made the application pool for the Admin web site (ends in V3) SharepointAdmin and set the rest to Sharepoint.

In local groups and users, I placed SharepointAdmin in the group for WSS_Admin and Sharepiont in the other two (not restricted) - but this is all in the implementation guide, so I would have a look through that.

BTW the error has just come back as one of our guys try to deploy a new site through the configuration wizard - haven't yet fixed this.

I would have thought that some one in the Sharepoint Team would know about this as it seems a very common problem.

cheers

sb132 at 2007-9-5 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
# 7
Well I had this problem 2, it stayed on my server for 3 days and then was gone all by itself !!!
GeorgesKhalil at 2007-9-5 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
# 8

I am also facing the same problem from last week. any solution?

Thanks,

Arun

starun24 at 2007-9-5 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
# 9

Well, about my post earlier, after the errors disappeared from the lof, i got three new recurring errors instead, they have the same Event IDs. but the errors are different, instead of "not enough memory", now its saying that: " the path specified cannot be used at this time". I've posted my errors in another thread...

M upgrading my RAM today. i'll keep you posted if it does any difference.

GeorgesKhalil at 2007-9-5 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
# 10

Had my RAM upgrade, im working with 4GB now. and it's working like a charm (looks like sharepoint is a sucker for RAM !!!!).

I got rid of the three errors.

Good Luck guys.

GeorgesKhalil at 2007-9-5 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
# 11

I am experiencing exactly the same problem... applied the hotfix but would not solve the problem...can someone please assist?

Thank you

ElenaWaldburger at 2007-9-5 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
# 12

I think this error might be really related to memory issues:

I have two gig ram and never had this errors before suddently they appeared and they disappeared same way I havent done anything.

I think here is a possible explanation: Sharepoint may have a range of memory to work within if a task overpasses this range the application would keep throwing this errors . Once the task has ended up erros disappear.

Problem is to know if Sharepoint has such a registry key to work with a certain memory and if you are really able to change this

ElenaWaldburger at 2007-9-5 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
# 13

> Had my RAM upgrade, im working with 4GB now. and it's working like a charm (looks like sharepoint is a sucker for RAM !!!!). I got rid of the three errors.

If you were getting the error - "Not enough storage ... to complete this command" (something to that effect) it may have been the reboot after the RAM upgrade that got rid of the message. I started getting the message with a 4GB server and I finally gave up and rebooted and the error went away. That's been weeks ago and the error message is yet to return. Although, I'm sure Sharepoint is happier with your extra RAM.

JasonFL at 2007-9-5 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
# 14
well actually that couldnt be it... because i actually restarted before thinking that it was from the RAM. it went away, and then it is recurring... 1 day in couple of days out...
GeorgesKhalil at 2007-9-5 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
SharePoint Products and Technologies
SharePoint - Setup, Upgrade, Administration and Operation

SharePoint Products and Technologies Hot Topic

SharePoint Products and Technologies New Topic

SharePoint Products and Technologies

Java / MSDN / Linux Tech / PHP Tech / MSDN DotNet / MSDN TECH / Health Library / Programmers Tech / visual basic Tech / Developer Tech / Ipod faqs / Msdn China Tech

Site Classified