Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Server Error

  Asked By: Fredrick    Date: Feb 18    Category: Sharepoint    Views: 678

I was playing with my new wss3, which is located on our LAN
server. First I made a little edit to the core.css file, because it did
not allow enough padding for the Title image. Then I installed
Sharepoint Designer on my desktop computer and went to poke around with
it, but now my portal won't run any more. I get the "Server Error in
'/' Application" error. It says the problem is in web.config at the
root directory, and says to make sure it says "<customErrors
mode="off"/>" but it already says "off." The problem is just in this
particular portal site, for I can still log in to Central Admin just
fine. What do I do now?



12 Answers Found

Answer #1    Answered By: Audra Mccormick     Answered On: Feb 18

ALWAYS make a copy of any file you modify, before you modify it!

Answer #2    Answered By: Christina Lewis     Answered On: Feb 18

Does it say "off" or "Off"? Case matters in XML.

Answer #3    Answered By: Meaghan Webster     Answered On: Feb 18

Sorry, it DOES say "Off." But changing that file doesn't seem to make any
difference. I also noticed that there are several folders in my site's root
called vti_pvt and they usually contain duplicates of the folder that contains
the vti_pvt folder. That may be normal, but everything worked before I browsed
the local files with sharepoint designer, but I don't recall saving anything
with SPD (and when I made the edit to core.css, I used notepad). I would just
delete the site and recreate it since it did not have much in it yet, but this
problem seems to have come so easily that I may need to troubleshoot it again
anyway. Would it make any difference if I edited the files via UNC paths with

Answer #4    Answered By: Sunny Delacruz     Answered On: Feb 18

Never edit anything other than files stored in the content database using
SharePoint Designer. It will corrupt the files. That is evidently what
happened to you. Most of the files stored in the 12 hive contain references
to virtual paths. If you open them in SPD it will change them to local
paths (since that's where you opened it from) and when you save it the file
won't be able to load what it needs to run. The first rule when using SPD
is never ever edit anything stored directly in the file system.

Answer #5    Answered By: .net Guru     Answered On: Feb 18

Okay, that sounds like good advice, and it makes sense to me. Then, I guess the
only way to fix things is to delete the site collection from my site and create
a new one? Also, I don't seem to have any problems with Sharepoint Admin -
doesn't the 12 hive affect that too?

Answer #6    Answered By: Renata Burt     Answered On: Feb 18

The Central Administration has its own set of files. It's basically another web

If you want the Title image to have more padding try using jQuery..

Answer #7    Answered By: Lazaro Rutledge     Answered On: Feb 18

this jQuery would do it:

$("#ctl00_onetidHeadbnnr0").css('padding', '10px');

Answer #8    Answered By: Karin Kerr     Answered On: Feb 18

You will probably need to do a complete re-install if

Answer #9    Answered By: Vinod Kumar     Answered On: Feb 18

You will probably need to do a complete re-install if you edited the files
stored in the 12 hive. Depending on which file you changed it might or
might not effect Central Administration. But deleting the site and
re-creating it won't help if you corrupted a file in the file system.

Answer #10    Answered By: Jeffery Hayes     Answered On: Feb 18

To get the ASP.net stack trace you need to also change this line-

<SafeMode MaxControls=“200“ CallStack=“false“…


<SafeMode MaxControls=“200“ CallStack=“true“…

Found this tidbit at:


Also direct editing of the web.config can land you trouble if you do not
copy it to all servers in the farm. I just finished troubleshooting a
problem on my dev farm where this was occurring. This was on a 3 server
farm. A site was rendering fine on two of the three servers. Fixed the
issue by copying the web.config from a working server to the broken one.
Now they all render.

Answer #11    Answered By: Mohini Tiwari     Answered On: Feb 18

I must have messed it up pretty bad because I had already tried
those things to no avail. I deleted the site completely and rebuilt it and now
it works. I'll just be more careful with SPD.

Answer #12    Answered By: Natasha Bennett     Answered On: Feb 18

Open your web application's web.config. Search for an attribute
"CallStack". By default, its value will be false. Make it true. Save your
file. This will show the actual error. Hope it helps.

Didn't find what you were looking for? Find more on Server Error Or get search suggestion and latest updates.

Related Topics:



Related Post