S
Stephen J. Shephard
Hi there,
I'm running SharePoint Team Services on a Windows 2000 Server box. My
clients are Windows 2000 running on an NT domain system, using Office XP Pro
w/FP.
My problem has to do with creating new documents within a document library.
Here're the facts:
* A given sharepoint team site will be created using unique permissions and
a given user will be added as a browser, administrator, or anything in
between using his/her domain user account.
* Users have full access to site as expected.
* However, when users with browser or site administrator rights click on
'New Document' in a document library, Word 2002 opens up but users are
prompted for authentication.
* After hitting the Cancel button on the authentication prompt (correct
credentials entered here result in a second or third prompt), the template
opens in Word and everything seems normal.
* When the user clicks on the Save button in Word, the authentication prompt
reappears
Thus, users cannot create new documents for STS via office XP, though they
are able to use the upload feature and delete existing documents just fine.
I had figured this all pointed to an issue with Office XP integration with
STS, but then the following two facts made me focus once again on finding an
issue on the server:
* When the user is a member of the local administrators group on the server,
they are able to use the 'New Document' feature perfectly and as expected
* When the user is a member of the Power Users group on the server, they
once again are UNABLE to use the 'New Document' feature.
* When the user is explictly given full control rights on the file level
(entire folder structure and/or individual template file), they are UNABLE
to use the 'New Document' feature.
To me this might point to the attempt by the user to use some privilage only
currently allowed to admins via a local group policy. Tomorrow I'll likely
enable security auditing for all failure events to try and track down which
object or privilage a sample user is trying to access.
I've examined the KB article 304133, "Errors Appear if You Use an Office XP
Program to Save Content", and have implemented two of their three
suggestions with no success in remediating the issue. Tonight I will attempt
to disable WebDAV completely (per the article's recommendation) to see if
that fixes anything.
Can anyone help? Adding all users to the local admin group is not an option
for me at this stage.
Any suggestions or advice would be of great help! Let me know if I can
illuminate my situation or environment any more.
Thanks,
Stephen
I'm running SharePoint Team Services on a Windows 2000 Server box. My
clients are Windows 2000 running on an NT domain system, using Office XP Pro
w/FP.
My problem has to do with creating new documents within a document library.
Here're the facts:
* A given sharepoint team site will be created using unique permissions and
a given user will be added as a browser, administrator, or anything in
between using his/her domain user account.
* Users have full access to site as expected.
* However, when users with browser or site administrator rights click on
'New Document' in a document library, Word 2002 opens up but users are
prompted for authentication.
* After hitting the Cancel button on the authentication prompt (correct
credentials entered here result in a second or third prompt), the template
opens in Word and everything seems normal.
* When the user clicks on the Save button in Word, the authentication prompt
reappears
Thus, users cannot create new documents for STS via office XP, though they
are able to use the upload feature and delete existing documents just fine.
I had figured this all pointed to an issue with Office XP integration with
STS, but then the following two facts made me focus once again on finding an
issue on the server:
* When the user is a member of the local administrators group on the server,
they are able to use the 'New Document' feature perfectly and as expected
* When the user is a member of the Power Users group on the server, they
once again are UNABLE to use the 'New Document' feature.
* When the user is explictly given full control rights on the file level
(entire folder structure and/or individual template file), they are UNABLE
to use the 'New Document' feature.
To me this might point to the attempt by the user to use some privilage only
currently allowed to admins via a local group policy. Tomorrow I'll likely
enable security auditing for all failure events to try and track down which
object or privilage a sample user is trying to access.
I've examined the KB article 304133, "Errors Appear if You Use an Office XP
Program to Save Content", and have implemented two of their three
suggestions with no success in remediating the issue. Tonight I will attempt
to disable WebDAV completely (per the article's recommendation) to see if
that fixes anything.
Can anyone help? Adding all users to the local admin group is not an option
for me at this stage.
Any suggestions or advice would be of great help! Let me know if I can
illuminate my situation or environment any more.
Thanks,
Stephen