Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Help with a disaster

  Asked By: Tanya    Date: Jul 01    Category: Sharepoint    Views: 836

I have a little problem with wss v3 - I added a link to the top nav
bar - I put the link in as ../sitename.

Now, it wont let me access the site !

If I try and open default.aspx in sharepoint designer i get the error
the details of which are

"soap:ServerServer was unable to process request. ---> A Web Part or
Web Form Control on this Web Part Page cannot be displayed or
imported because it is not registered as safe on this site. You may
not be able to open this page in an HTML editor that is compatible
with Microsoft Windows SharePoint Services, such as Microsoft Office
SharePoint Designer. To fix this page, contact the site administrator
to have the Web Part or Web Form Control configured as safe. You can
also remove the Web Part or Web Form Control from the page by using
the Web Parts Maintenance Page. If you have the necessary
permissions, you can use this page to disable Web Parts temporarily
or remove personal settings. For more information, contact your site
administrator.
"

I can only guess this is the top nav bar on the default.aspx page

If I just iverwrite the default.aspx page by uploading teh page for
another site I can get into it in designer - if i delete the top nav
i can get back into my site (but no top nav - boooooo).

I guess if i can go into topnav.aspx I can remove the site link and
everything will be ok.

The only problem is, I cant get into there !

I can get into any sub site fine and, bizarrely, see the top nav bar
with a link to this site - I can even click on teh tab on teh top nav
bar and it lets me into the site !

What O cant do is get into the home page of the top level site, nor
sit settings, nor the top nav bar ;

If anyones got any ideas of how I can get round this without haveing
to restore and lose a days work I'd be grateful.

Share: 

 

6 Answers Found

 
Answer #1    Answered By: Donta Kirkland     Answered On: Jul 01

Oh yeah, the message I get when I try and access  default.aspx and the
others is the ever helpful

An unexpected error has occurred.
Troubleshoot issues with Windows SharePoint Services.
<javascript:HelpWindowKey('troubleshooting')> !

 
Answer #2    Answered By: Cade Velazquez     Answered On: Jul 01

One of the first things you're going to want to do is get a hold of
web.config. In this file, there is a parameter you can set that
will show you the real error. The file is on the server and on our
system it reside in the c:\inetpub directory. The parameter
is "customErrors mode". After switching it from On to Off, launch a
cmd.exe session and do an iisreset on the server. Then, instead of
getting "an error has occurred", you'll get an error message you can
probably diagnose and fix.

 
Answer #3    Answered By: Ariana Christensen     Answered On: Jul 01

tried that and it just gives the same error.

 
Answer #4    Answered By: Gopal Jamakhandi     Answered On: Jul 01

If a webpart is causing this issue,

you can go to the url which throws the error and append "?contents=1 "
to view the list of webparts, remove the error causing webpart.
e.g http://servername/default.aspx?contents=1
<http://servername/default.aspx?contents=1>

 
Answer #5    Answered By: Kyla Eckert     Answered On: Jul 01

same error unfortunately as it cant open the page in the left hand
side to show the web part on the right hand side

I'm thinking i'm just gonna have to phone ms pss.

 
Answer #6    Answered By: Joshuah Huber     Answered On: Jul 01

You want to set CustomErrors="RemoteOnly" rather than to "Off". It won't
change what you see but if the web.config ever got moved to a production
box, only people browsing the site  from the console would see the actual
error details, something hackers can easily exploit.

Also, you might consider setting callstack="true". When the error
message isn't very good, this can sometimes help  you isolate the problem
by letting you discover the approximate vicinity of the problem. What
method had called what method that caused what method to fail.

 
Didn't find what you were looking for? Find more on Help with a disaster Or get search suggestion and latest updates.




Tagged: