Monday, 25 February 2008

"0x80040E14" or "HTTP 500" error message when you connect to your Windows SharePoint Services Web site after you install a Windows SharePoint Services

If anyone has come across this error:

Exception from HRESULT: 0x80040E14. Troubleshoot issues with Windows SharePoint Services.
HTTP 500 - Internal server error


either in search error logs or event error logs, specially after installing a service pack or a hot fix, there's an easy fix.

The main cause of this error is when the content databases in Windows SharePoint Services are not updated correctly during the installation.

Simply go to a command prompt and type:
cd /d %commonprogramfiles%\Microsoft Shared\Web Server Extensions\60\Bin stsadm -o upgrade -forceupgrade
This is a fix for both WSS 2.0 and WSS 3.0. If you're still having the problem, please let me know.

20 comments:

Sumit said...

Some users in our company are getting error HRESULT: 0x80040E14 from last few hours when they are trying to access one sub-site in SPS2003. can you please suggest me what we do to cure this problem?

Fadi Noja said...

did you try the same command? It might fix your problem. Also do you have the lastest service pack installed?

DanielL said...

Fadi,
Thanks for all the posts, it greatly helped out on one or two occasions. Question...have you ever seen this for 500 Error?

I have a customization request from a client which doesn't want to co-operate with me, may be someone has seen this before. I need to create a custom 500 error page that is displayed every time IE generates a 500 error. I have created a custom 500 and 404 pages and they work, except for one instance when a url is http://www.site.com/~abcd (any letters after tilde / tilda)

I have created an .aspx page and have it pointed in IIS custom error pages as well as under customError tags in web.config.
The errors work for all the 404 pages (which was a customization in the SharePoint dll files) and for some 500 errors, but not for the ~ url's....and this one is an important thing for a client, because they moved sites from Unix (where sites were ..../~username) to SharePoint, they want to tell the people who will go to their old site structure that it has moved, instead of a general 500 error and get calls on their help desk saying that the server is down. It has been troubling because IE says its a 500 error, but it is not a standard 500 error, plus the ~ is a reserved character in IIS.
I also tried the global.asax code that a co-worker recommended (which did not work) for Application_Error with Context.RewritePath
Please need help on this one.

Thanks!

Fadi Noja said...

hmmm, a tricky one. You won't be able to do it from sharepoint, because you can't use ~ in the url. Maybe write a very stupid site that when people hit the url with ~, it will display a page saying it's moved to "http://newurl" and redirect them. Shouldn't be too hard to write, but you will need to do some configuration to IIS so that when people hit the site, it won't let sharepoint intercept it. Plus you will have to make sure that the users sites in SharePoint match the same username in the old unix. ie, if it http://url/~username it will have to be something like http://url/mysite/username or something like that, otherwise the redirect will send them to the wrong site.

DanielL said...

I already created a virtual directory called ~ with a default error page on it that says that the site moved. So if they go to www.site.com/~ they will see the message, but if they go to www.site.com/~whatever or www.site.com/~whatever/whatever/.... They will get 500 error page from IE. Nothing I have done so far will autoforward to the custom pages with information. With the creation of the virtual directory ~ I was hoping to create a catch all site that will get everything that would come after the tilde...but no luck.

DanielL said...

I was hoping to do something like this site: http://ualr.edu/~hamradio/
without the re-direct
If you type anything after the tilde ~ it will recognize it and display the error page.

Fadi Noja said...

ok, can you give me the weekend to think about it and i should be able to come up with a solution for you.

DanielL said...

Great! Thank you very much.
I been hitting the wall with my head for 4 days on this now.

Fadi Noja said...

Hi Daniel,

Quick question: Were you able to display just a simple "hello world" in the custom500.aspx page? If you can setup the web.config to use a custom500.aspx page when you get a 500 error, make it say hello world. If that works, let me know.

DanielL said...

Fadi,
The custom 500 error works on anything, but the /~abc. If I type in the tilde abc, no custom error at all, just a generic 500 internal server error.

Thanks,
Daniel

Fadi Noja said...

have you set up IIS to display a custom error 500 page also?

DanielL said...

Yes I did.

DanielL said...

with everything set-up as it should work...it still doesn't.

DanielL said...

Fadi,
Were you able to figure out the problem and/or possible solution. I have MS support working on it, but their IIS team couldn't figure it out so they moved it to SharePoint support and that is back logged for at least a week.

Thanks.

Fadi Noja said...

still trying to find a fix. Ill let you know as soon as i have.

nmagee said...

Hi there, we got the 0x80040E14 error on our MOSS 2007 (SP1) box, but running that stsadm.exe command line didn't fix the problem! We're looking at other things to try, but wondered if you had a suggestion? It's rendered the whole server "read-only" for now ...

Fadi Noja said...

nmagee, have you checked if the db has enough space? What is the message you when when you run stsadm -o upgrade -forceupgrade???

nmagee said...

Hi Fadi, you were right, and minutes later after I posted we were checking the event log and errors to that regard were there -- not enough space on the DB. It was running on SQL Express and we had maxed out the 4096MB (I think that was the size) capacity for the express license. So we just did a quick upgrade to Standard, ran the command again and all is well. Thanks again!

Fadi Noja said...

Glad you were able to solve the problem.

Anonymous said...

Worked for me as well after the site wouldn't come back after installing a hotfix (404 Error)