Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Security tab unavailable

  Asked By: Ezequiel    Date: Sep 15    Category: Sharepoint    Views: 756

We recently rebuilt the server on which our SharePoint Portal server
installation is house because of problems we were having with the site: no
access to the Document Library, and no categories available.

After the rebuild, it is again possible to search and find documents, browse
the library, and use the categories for finding documents. So far so good.

We also now, however, are experiencing a number of smaller problems probably
related to server configuration. The most serious problem is that even
though the security configuration was restored, now it is no longer possible
to open the security tab on the SharePoint properties dialog. You can get to
the other tabs - General, Index, Logging, Subscription/Discussions - but
when you click on the Security tab you get an error message:

"The file or folder properties cannot be read, because of the error
(0x80040e14): No description was found for this error."

When you click OK on this Property Read Error box, the security tab opens
but it is grayed out. You cannot read anything in the list that should have
all of the users and groups and their respective rights.

Has anyone seen this error? Is it possible that we need to configure the
proxy settings (I don't think we have done that yet since the server
rebuild) to have a fake proxy server configured and that by doing this we'd
get the security tab back?



15 Answers Found

Answer #1    Answered By: Narasimha Kamane     Answered On: Sep 15

I shoudl assume you restore the configuration  from a backup/restore, right ?

Make sure that the logged in user is a Coordinator of the workspace ! Also check
security for the folders you are trying to access.

Describe what you are seeing in the security  Tab (list of users  and so)

Answer #2    Answered By: Fidel Crane     Answered On: Sep 15

Exactly, we did a backup-restore operation (msdmback if I recall correctly).
And the workspace was restored  almost completely, with a few minor
configuration issues that have been corrected by hand.

It is true that I am a coordinator of the workspace, or at least I WAS
before the backup restore operation. I am also an administrator on the
server, but that shouldn't matter. Perhaps I have lost all of the security
during the back-up restore and now I can't see the security  tab. Then the
question becomes, how can anyone administer security if there's none
assigned to the space?

When I look at the security tab  after dismissing the error  message, the tab
is grayed  and there's nothing showing in the window (no list  of users  or
groups with their assigned security levels - coordinator, author, reader).
When I select the Documents folder  from Windows Explorer and dismiss the
error message, the entire security dialog  is blank. When I select a folder
underneath the Documents folder, everything is blank except the first check
box: Use parent folder's security settings. This check box  has a grayed out
check in it.

Answer #3    Answered By: Akshara Sanghavi     Answered On: Sep 15

I also faced the same problem  when I imported my backup from another
machine, I checked it with couple of people relating to this issue , it
removes all the security  setting of the workspace , you have to do it again
on the new machine where you had imported the backup

Answer #4    Answered By: Aishwarya Dixit     Answered On: Sep 15

What does it show in the sps mmc snap in for the server? You Should be able
to see all the workspaces and in the properties  you should see the security
tab. You may be able to re-set them all from there.

Answer #5    Answered By: Indrajeet Patil     Answered On: Sep 15

Yeah, that's a good  tip. From the mmc snap in I don't see the workspace I'm
interested in. No workspace shows at all. My network guy tells me he
experimented last week by creating a new workspace, and then reapplying
service pack 1. After applying SPS sp1 to the server, the workspace
disappeared from the MMC snap in. I don't think we'll resolve this issue
until we figure out what's happening during the application of the service

Answer #6    Answered By: Xavier Hopkins     Answered On: Sep 15

You have to make sure you restore the db on a system with the same Service Pack
that was installed when you backed up the system.

If you don't see the workspace in the MMC snap-in, I am not sure how you will be
able to administer the workspace.

If you back  the workspaces and SP1 was installed. You need to install SP1 first
before restoring.

Answer #7    Answered By: Viviana Rollins     Answered On: Sep 15

I'll ask the network engineers to see in what order the restored  and rebuild
process happened. It might be that applying the service pack after the
restore is causing the problems. You are of course correct: without the
workspace showing in the mmc, you can't administer the workspace.

Answer #8    Answered By: Erika Price     Answered On: Sep 15

Yes, the service pack was on the restored server  before the workspace was
restored. By now, however, one of the network engineers has reinstalled the
service pack on top of what was already there. I don't know if that is
causing any problems, but it hasn't fixed the main problem  either.

Answer #9    Answered By: Otis Blackwell     Answered On: Sep 15

Was SP1 on the server  before the backup ?, i.e. did you backup with or without
SP1 ?

Answer #10    Answered By: Virendar Chaudhari     Answered On: Sep 15

Yes, SP1 was on the server  before the backup was done. So the restored
workspace should have been restored  to an identical (as far as SharePoint
Portal Server is concerned) but newly rebuilt server. I'm very puzzled about
why this aspect of the server is no longer  available.

Answer #11    Answered By: Mitchel Villarreal     Answered On: Sep 15

If you can try restoring it to a different test server  to see if this is
specific server. We have done many backup/restore with no problems.

Are you sure that specific security  groups are identical ?

Is the server in a domain environment same as it was before the restore.

Make sure to compare setup before and after restore to see if something changed

Answer #12    Answered By: Ranu Badhan     Answered On: Sep 15

When you say 'do it again,' I have to assume you mean to the restore a
second time, is that right? If you mean, you have to set up the security
again on the server, then that's a different matter, and one that we can't
do because our security  administration tab  is not accessible to us, either
from within the mmc snap-in (that admin console for SPS) or from Windows
explorer. I would love to be able to just do that again, if the facility
were available.

I would very much appreciate hearing some more detail about what you had to
do to restore your back  up.

By the way, about a year ago we also moved from one server  to a new one, and
we did not experience this problem  before. The first time around we were
moving to a new, more robust server. This time we rebuilt the current server
to solve some other problems: the document  library and categories  were not
available anymore (mysteriously - one day they just went away). We rebuilt
the server, installed sharepoint  and then the service pack (SP 1), and then
did the restore on top of the rebuilt server.

Should we just do another back-up restore? Should we try to restore from an
earlier back-up? I'm really at a loss here.

Answer #13    Answered By: Irene Moss     Answered On: Sep 15

Any chance you are using local security  accounts instead of domain

Answer #14    Answered By: John Scott     Answered On: Sep 15

We use both on the machine - the local machine administrator's account and
domain accounts on the machine. I don't think that is the issue.

Answer #15    Answered By: Donald Torres     Answered On: Sep 15

Just an update to close out this thread:

Thanks for all of the suggestions and support. It's very helpful to have the
different angles and suggestions of the group so that we can narrow down our
focus during troubleshooting like this.

I have suspected for about a week that our network engineers had not set up
the fake proxy settings  on the rebuilt server. I recall doing it myself a
good while ago, when I first installed the server, but we did not have this
on our radar screen during the rebuild  restore process. So apparently the
proxy config settings do not get restored  during the backup-restore process
(or they are eliminated). I tested the network access to our site  by having
a staff member attempt to login to the site who didn't have permission to
use it: she was rebuffed appropriately. So even though the security  settings
were invisible and the security tab  inaccessible, the security settings
themselves remained.

With the fake proxy  settings configured, now the security tab is available,
and all of the settings visible.

The main lesson here is to document  carefully the server  configuration and
setup process to make the backup/restore process efficient and problem-free.

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