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 at http://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 at http://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 at http://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.
すべての返信
Yes, we have this too.
We also have issues with not being able to view sites in explorer view.
Regards,
- We're logging this issue as well, though we have no visible issues being reported.
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,
EXACTLY same problem here
in 2 different, physically seperated domains.
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?
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
- Well I had this problem 2, it stayed on my server for 3 days and then was gone all by itself !!!
I am also facing the same problem from last week. any solution?
Thanks,
Arun
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.
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.
I am experiencing exactly the same problem... applied the hotfix but would not solve the problem...can someone please assist?
Thank you
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
> 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.
- 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...
- I've seen the same error on and off for the last month on the two frontend servers (not the index/search server).
The thing you all need to be aware of is this: The error will disappear when you reboot your server. It'll most likely reappear within a couple of days (at least in my case).
So: Whenever you post a new "fix", more ram, new security settings etc. please note whether you rebooted the server and allow some time to verify that it actually worked [and how would you know? ;-) ]
One more note:
Sometimes the "Not enough storage" event is replaced by:
[...]
An exception occurred while executing the Application Server Administration job.
Message: Old format or invalid type library.
Techinal Support Details:
System.Runtime.InteropServices.COMException (0x80028019): Old format or invalid type library.
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)
...........
[...]
with exactly the same frequency.
I'm also logging this error with MS. Hi..
I have the same problem here..
Not enough storage is available to process this command...
Is there any fix for this??
One thing I've noticed is that in the taskmgr of my server, there is a process called WssAdmin.exe that is occupies more thant 600 Mb out of my 2GB of RAM.. also another process called sqlservr.exe is taking another about 600 MB.... Appart from those, then i have 4 more proceses taking 100 MB each.. services.exe, w3wp.exe (twice), owstimer and mshta
I don't know if everything is related, but at least I think some of those are..
Please help!!
- Any news on this, we have the same problem.
- well, ever since that last post by me, a while back ago, my problem has never shown again. the RAM upgrade solved it.
Where you able to get this issue fully resolved yet? I'm experiencing the same problem, and I'm sure it's not memory related as I have 8GB of RAM on this server and it is hardly being used for anything at all at the moment. I'd be interested to know what MS said, if you logged this error with them.
Thanks!
Hi ,
I found over one of the blogs that says if you receive some kinda exception that says:
Microsoft.Office.Server.Administration.ApplicationServerAdministrationServiceJob threw an exception:
"Message: Not Enough Storage"
The resolution required not one but two hotfixes, both of which target the .NET 2.0 framework.
And they are available at :
http://support.microsoft.com/kb/923028
http://support.microsoft.com/kb/918642
hope this helps.
Hi,
I downloaded all the fixes for our SharePoint server's and it has been fine since - so I concur in that it seems that Microsoft must have spotted it and fixed it.
Regards,
Restarting the Sharepoint services appeared to work for me - WSSAdmin was using a fair amount of memory to which it then dropped down to the "normal" level (after the restart of services)I've been working with Microsoft Support on this same issue with the three recurring errors in the event logs. We've tried most of the recommendations that were posted to this thread, including the .NET 2.0 hotfix, re-entering the timer job service account and restarting the service, amongst others. I had tried most of these steps before initiatiating the support case, but the errors kept returning either after a few hours, or a few days. Microsoft support had me try an additional step which was due to the fact that at one point or another, I created a new SharedService Provider and tried to get rid of the old one.
I ran the following command: stsadm -o sync -deleteolddatabases 30
I did this about 4 days ago, and haven't seen the errors come back yet, but I've seen how the problem always appears to be resolved only to come back in another day or two, so I'm still cautiously optimistic that this is the actual resolution.
Thanks,
SharePointDave2007
The command in my previous post was not the resolution after all. I'm sure anyone who has worked on these recurring errors isn't shocked by hearing that.
However, I did receive the following from Microsoft Support:
Microsoft has now found the root cause of this problem to be the IIS ADSI provider. Essentially, if you have a process with more than one thread and two threads access IIS 6.0 at the same time, then this issue occurs. This problem is likely to occur for the SharePoint Timer service (OWSTimer.exe) in Microsoft Office SharePoint Server 2007. When this occurs, you may find that:
- In SharePoint Server 2007, tasks that are scheduled do not run.
- When you try to manage IIS 6.0 by using Server Manager, you receive a blank page, or you receive the following error message: "the path specified cannot be used at this time".
The Event ID's 7076, 6398 and 6432 and memory error messages described above will also be recorded in the Application Event Logs. Microsoft now has a KB article describing this problem http://support.microsoft.com/?id=946517 along with details of the fix and how to obtain it. This fix is not a SharePoint fix so you should be able to install the fix regardless of what Service Pack level you are running
I found this link. It also links to kb 949517.
http://www.epmfaq.com/ssanderlin/project-server-2007/event-id-6398-6482-and-7076-in-your-event-logs
