Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1558
  • Last Modified:

Can't open central admin

When I browse to the central admin site on my dev box I just get a blank page.
I looked in the event viewer on the server I see this
Could not load all ISAPI filters for site 'SHAREPOINT CENTRAL ADMINISTRATION V4'.  Therefore site startup aborted

So I go to the central admin site in IIS and try to open the isapi config and I get the error shown in the image.
I've googled this and seen results for uninstalling 1.1 framework and running aspnet_regiis but as this is a SP box I'm not too keen to go to far under the hood. isapi error
0
QPR
Asked:
QPR
  • 11
  • 4
1 Solution
 
Ramkisan JagtapLead DeveloperCommented:
0
 
QPRAuthor Commented:
No change
0
 
Justin SmithSr. System EngineerCommented:
Is this a new install?
What else is running on the server?
What patch level are you on (SharePoint)?
0
Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

 
QPRAuthor Commented:
Not a new install.
Nothing but a stand alone instance of 2010 Enterprise (fresh not an upgrade).
SQL Express.
Just installed SP1.
How can I check the patch level? Normally I'd go to Central Admin and servers in farm but.... :)
0
 
QPRAuthor Commented:
Ouch just looked in the logs folder and this (hardly used, lonely dev box) is producing 110MB log files every 30 minutes. No idea if this is related (or just another symptom of me installing SP1) but the logs are full of "stuff" like...
CSTS3Accessor::InitURLType: Return error to caller, hr=80041206  

STS3::COWSServer::InitializeClaimsCookie: Probing url 'http://xxxx:37615' failed. Return error to caller, hr=80041206  [sts3util.cxx:1332]  d:\office\source\search\native\gather\protocols\sts3\sts3util.cxx

37615 is the port number where central admim lives. My *guess* is that this is a symptom of the central admin site being down rather than the other way around based on the IIS problem
0
 
Justin SmithSr. System EngineerCommented:
Have you tried running the config wizard?
0
 
QPRAuthor Commented:
I did via central admin yes. Just to be sure I just ran psconfig from the SP powershell command line. Said it went fine and all upgrades were complete.
Still the same problem
0
 
QPRAuthor Commented:
Hmmm got this in event viewer now
Could not allocate space for object 'dbo.MSSCrawlURLLog'.'PK_MSSCrawlURLLog' in database 'WSS_Search_xxxx because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
Because this is a dev environment I only used a local sql express. I don't care about search on this server so am happy to turn it off (or not crawl) and free up the DB space. When I try to shrink voa SQL management studio it tells me there is < 10mb free.

Without access to central admin, how can I clear all crawl data and empty the contents of the search DB?

0
 
QPRAuthor Commented:
ok solved this with a dbcc shrinkfile.
No doubt highly unsupported in a SP environment but I had to get past it and it is only a dev box.

Still no central admin so that was a red herring
0
 
QPRAuthor Commented:
Got past one bit... opened the file mentioned in the original error applicationhost.config and went to line 5087
I commented out this bit:
<isapiFilters>
                <filter name="ASP.NET_4.0.30319.0" path="c:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_filter.dll" enabled="true" enableCache="true" />
            </isapiFilters>

I can now view the isapi info for the central admin site... in other words that error does not appear.
However central admin page is still blank and event viewer still claims it can't load isapi filters for central admin. I have done an iisreset
0
 
QPRAuthor Commented:
ok with this commented out I am able to view the isapi filters for central admin in iis. I removed and readded each one in turn and can now browse the central admin site IF I do so on the local machine. If I try to view it from my workstation I am prompted for the network username and password.
I give this (even tho I shouldn't have to) and it just keeps asking - 3 times until I get the blank page.
0
 
Justin SmithSr. System EngineerCommented:
Have you disabled loopback on your server?

I'm wondering how all this would happen out of the blue :)
0
 
QPRAuthor Commented:
What is that and how do I do it?
I put it down to the installation of SP1.... has made me very very wary of installing it into production.
Now I see that is is causing job defeinitions to fail... jobs that weren't enabled prior to SP1
0
 
Justin SmithSr. System EngineerCommented:
2.Click Start, click Run, type regedit, and then click OK.
3.In Registry Editor, locate and then click the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

4.Right-click Lsa, point to New, and then click DWORD Value.
5.Type DisableLoopbackCheck, and then press ENTER.
6.Right-click DisableLoopbackCheck, and then click Modify.
7.In the Value data box, type 1, and then click OK.
8.Quit Registry Editor, and then restart your computer.
0
 
QPRAuthor Commented:
Done. What did I just do? What is loopback?
I fixed the "unable to open central admin from other machine" problem. In an attempt to fix some of the health analyser warnings I had changed the central admin app pool to a different account. Changing it back to network fixed that.
This question has morphed a bit hasn't it!
0
 
QPRAuthor Commented:
Solved my problem by changing the account for the app pool
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 11
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now