Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

IIS Manager Non-Responsive & SharePoint

  Asked By: Reynaldo    Date: Jan 09    Category: Sharepoint    Views: 1644

I have SharePoint running on a single web front end server with a DB
back end. I am on Windows Server 2003. My IIS manager consistantly
becomes non-responsive. If I attempt to restart the IIS service, it
only locks up and a reboot is the only thing that has been successful
in restore functionality of IIS manager. The sites are still being
server and functional. Has anyone experienced this and/or have any
thoughts on what may be causing this problem? The server should be
more then beefy enough to handle our web app.

In my application event log I am getting Windows Application Server
Administration job failed...

Reason: Logon failure: unknown user name or bad password

Techinal Support Details:
System.ComponentModel.Win32Exception: Logon failure: unknown user
name or bad password......

and Windows SharePoint Services 3 error....
The Execute method of job definition
ServiceJob (87f3) threw an exception. More information is included

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



8 Answers Found

Answer #1    Answered By: Shashwat Takle     Answered On: Jan 09

There may be two separate issues here. One, your iis  may be failing due to a
duplicate port number(s) - check the port numbers against all the Web sites
hosted on the server's IIS, i.e. are there any Web sites with a status of
'stopped' or are failing to start on server  reboot or iisreset?.
Two, I've seen the 'write protected memory issue' problem where I'd previously
added an additional Web front-end server to my farm and enabled/disabled Office
search on that new Web front-end server. The errors showed up in the main
(original) Web front-end server (the one running  Central Admin). Have you
recently extended the farm and/or enabled any additional services? Have you also
tried rebooting the SQL server (assuming the SQL server is on a separate

Answer #2    Answered By: Aastha Acharya     Answered On: Jan 09

I've resolved the same problem with this hot fix

Answer #3    Answered By: Glenda Roth     Answered On: Jan 09

I am glad someone else is seeing this as well. We have 3
wfes,1 app server, and an active/passive sql cluster. And yes, we
see the exact same thing. For the most part the servers seem to
still respond fine but you can not do anything with IIS manager  or
directly with the services. The only answer we have found is reboot.
BTW, when this non-responsive condition occurs, it does on multiple

For the write protected memory issue. We have a theory on it that we
discovered trying to implement the symantech sharepoint  backup
solution. We found that the VSS writers were hanging causing the
backups to fail. MS very recently released a OS patch the fix the
vss writer error(dont know the actual number) and it has appreared to
fix the bad memory error message.

Answer #4    Answered By: Jada Clemons     Answered On: Jan 09

This looks mysteriously like the notorious SPTimer Memory leak problem

Answer #5    Answered By: Brooke Lewis     Answered On: Jan 09

That could be likely. We do have a memory leak issue as well and I have not
reserached it yet, so I will start here. The link refers to restarting the
timer service....does this have to be done frequently? I am assuming this
is not a one time fix?

Answer #6    Answered By: Talia Johns     Answered On: Jan 09

You can get a free tool to reset SPTimer on all WFEs using an STSADM
command from the Mindsharp Premium Content page.

Answer #7    Answered By: Tera Callahan     Answered On: Jan 09

This does not seem to have resolved the issue, any other thoughts?

Answer #8    Answered By: Mark Davis     Answered On: Jan 09

Have you installed .NET 2.0 SP1?

There is an issue with programs such as Anti-virus locking IIS that is
included in SP1. If you cannot load SP1, then I would at least try the
patch support.microsoft.com/default.aspx

There is an outside chance the above is your issue. It is always
possible you have a corrupt metabase. In that scenario, you will have to
1. Restore from a metabase-only backup (don't restore the system state
as it will overwrite the registry, etc.). If you aren't doing standalone
metabase backups (best practice with SharePoint server  2007, btw... see
here mindsharpblogs.com/.../3486.aspx )

Then you could 1. Stop the Windows SharePoint Services Web Application
service in Central Administration for the WFE server in question. 2.
Uninstall IIS on that WFE Server 3. Reboot and re-install IIS on the WFE
Server 4. Start the Windows SharePoint Services Web Application in
Central Administration for the same WFE Server in question. But, be sure
to backup/document everything in the inetpub directories, multiple host
headers, assigned IP addresses, and SSL Certificates. These are not
copied back to the WFE Server from the configDB.

Didn't find what you were looking for? Find more on IIS Manager Non-Responsive & SharePoint Or get search suggestion and latest updates.