To continue with the last topic, in order to disable the famous "Unknown error" so you can know what's happening.
- Open the web.config file of the Web Application you're receiving the error, it's located in the toor path of the Web App.
- Set the callstack value to ="true".
- Set the customErrors value ="Off"
- Repeat the operation that was giving the error, you should see now a descriptive error and its stack pile.
viernes, 19 de diciembre de 2008
jueves, 18 de diciembre de 2008
Managing .NET custom errors in Sharepoint 2007
The first problem I faced when started to manage Sharepoint 2007 farms was the error handling. Every time I see the "Unknown error" page I raged against Microsoft swearing about their family.
Just to introduce my case, I manage several Sharepoint 2007 farm, the most important one hosts sites for many countries. Because of that every time I have problems with the database server hosting the content databases, the help desk department reports users complain about an error in other language. I'd like to share to how to know what's going on your Sharepoint Farm, showing errors only for administrators where the users will see a custom error page.
Firstly, you should create a virtual directory in the root of the web application called /errors or something like that, then create a custom html page (e.g. General_error.html). As the Sharepoint 2007 is a .NET application the next step should be editing the web.config file. So open it and change the "Callstack" value from "false" to true. Next find the label custom errors and comment the line, next add the following line just below the one you have just commented.
The RemoteOnly Value, means all users accessing the web application form outside the webserver will see the custom error page, so you, as an administrator, should log in the server an browse the URL returning error and so you can see the real error.
Now you can try forcing a .Net error going to your database server and detaching a Content database, when trying to browse a site collection from the web application you have changed the web.config form outside the web server you should see your custom .html page.
Just to introduce my case, I manage several Sharepoint 2007 farm, the most important one hosts sites for many countries. Because of that every time I have problems with the database server hosting the content databases, the help desk department reports users complain about an error in other language. I'd like to share to how to know what's going on your Sharepoint Farm, showing errors only for administrators where the users will see a custom error page.
Firstly, you should create a virtual directory in the root of the web application called /errors or something like that, then create a custom html page (e.g. General_error.html). As the Sharepoint 2007 is a .NET application the next step should be editing the web.config file. So open it and change the "Callstack" value from "false" to true. Next find the label custom errors and comment the line, next add the following line just below the one you have just commented.
The RemoteOnly Value, means all users accessing the web application form outside the webserver will see the custom error page, so you, as an administrator, should log in the server an browse the URL returning error and so you can see the real error.
Now you can try forcing a .Net error going to your database server and detaching a Content database, when trying to browse a site collection from the web application you have changed the web.config form outside the web server you should see your custom .html page.
martes, 2 de diciembre de 2008
Welcome to the Jungle
Hi all,
I am a newbie in this blog thing... I usually saw my workmates writting in their blogs every hour in every day, saying many things, too many more than few times. Well, if you think it carefully, you may face yourself writing something to no one, at least the first or twenty first posts you write, so, you'd better not think aobut it.
I first thought to write down my experience solving MOSS problems, I mena an incident compendium or something like that, but, I do not know which path would it take. We'll see.
I am a newbie in this blog thing... I usually saw my workmates writting in their blogs every hour in every day, saying many things, too many more than few times. Well, if you think it carefully, you may face yourself writing something to no one, at least the first or twenty first posts you write, so, you'd better not think aobut it.
I first thought to write down my experience solving MOSS problems, I mena an incident compendium or something like that, but, I do not know which path would it take. We'll see.
Suscribirse a:
Entradas (Atom)
