| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
I'd like to know if there is a known problem with, or if
someone else has run across the same problem one of my
customers has recently experienced with the 'COPY' function.
The user is using the 'U' (Update) option from form WP to
essentially re-file a SFCP (that's right it's SFCP and I'll
cross-post this in the SFCP conference) to a private folder
by changing the Folder name from a shared file cabinet folder
to a private folder. This procedure usually works,
(oh-no it sometimes works!) but sometimes it results in the
following error message being displayed:
RMS-E-PRV, insufficient privilege or file protection violation
The trace reveals that the error occurs when the copy function
is executed:
3449 ! [SCP/TRACE] GET OA$FUNCTION='COPY OA$CURDOC_FILENAME "SFCP_DOCTRAN
3449 ! %OA-I-LOGFUN, Function: GET OA$FUNCTION='COPY OA$CURDO
3449 ! %OA-I-LOGFUN, Function: COPY OA$CURDOC_FILENAME "SFCP_D
3449 ! GET Symbol: #SFC_FOLDER_PRESENT
3449 ! Value: 1
3450 ! GET Symbol: OA$CURDOC_FILENAME
3450 ! Value: DISK$USER110:[SFC_SS3164.DOC4]ZTQWDBNO8.WPL;
3450 ! GET Symbol: "SFCP_DOCTRANSFER.WPL"
3450 ! Value: SFCP_DOCTRANSFER.WPL
3450 ! OA$FLO_OPEN_FORM: Opening form - SFCP_PDAF
3450 ! in A1_SYS:[ALLIN1.SITE.LIB_ENGLISH]SITEOAFORM.FLB;
3450 ! DSAB Name: SFCP_PDAF Requests : OPEN
3454 ! DSAB Name: SFCP_PDAF Requests : LOCATE
3454 ! DSAB Name: SFCP_PDAF Requests : LOCATE
3454 ! DSAB Name: SFCP_PDAF Requests : LOCATE
3455 ! GET Symbol: OA$CURDOC_FILENAME
3455 ! Value: DISK$USER110:[SFC_SS3164.DOC4]ZTQWDBNO8.WPL;
3455 ! DSAB Name: SFCP_PDAF Requests : LOCATE
3456 ! DSAB Name: SFCP_PDAF Requests : LOCATE
3456 ! GET Symbol: OA$CURDOC_FILENAME
3456 ! Value: DISK$USER110:[SFC_SS3164.DOC4]ZTQWDBNO8.WPL;
3456 ! GET Symbol: OA$CURDOC_FILENAME
3456 ! Value: DISK$USER110:[SFC_SS3164.DOC4]ZTQWDBNO8.WPL;
3457 ! GET Symbol: "SFCP_DOCTRANSFER.WPL"
3457 ! Value: SFCP_DOCTRANSFER.WPL
*** here is the error message ***
3460 ! %OA-I-LOGERROR, %OA-E-IOOPEN, Error opening file "DISK$USER110:[SF
3461 ! %OA-I-LOGERROR, -RMS-E-PRV, insufficient privilege or file protect
3461 ! GET Symbol: OA$FUNCTION='COPY OA$CURDOC_FILENAME "SFCP_DOCTRANSFER
3461 ! Value: COPY OA$CURDOC_FILENAME "SFCP_DOCTRANSFER.WPL"
3461 ! [SCP/TRACE] .IF OA$STATUS EQS "0" THEN .EXIT << SFCP_TRANSFER 0016
3462 ! GET Symbol: OA$STATUS
3462 ! Value: 0
3462 ! GET Symbol: "0"
3462 ! Value: 0
3462 ! [SCP/TRACE] .EXIT << SFCP_TRANSFER 0016
I've looked at all the obvious protections such as UIC and ACL's
and they all look good. Any ideas??? The user experiencing this
error had privilege to READ, MODIFY, and MODIFY INDEX of the
selected document. As I stated before, It sometimes works, which
is now the case so I can't debug any more until it happens again.
I'm hoping that someone else has had the same thing happen so I
can prevent it from happening again.
Thanks,
Mike
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 917.1 | Don't know, but here's some info | SHALOT::TROTTA | Still crazy after all these EARS | Tue Jun 23 1992 23:08 | 20 |
Mike, (since I didn't see this cross posted in OAWEGO::A1SFCP)
The only time I remembering seeing something like this was when there
was a local customization to blame (no, I don't remember exactly what
it was)
In the situation you describe, the SFCP COPY function will raise
privileges when: #SFC_FOLDER_PRESENT is set to "1" (which I can see is
true from your trace), and the input filename is located in the private
DAF.DAT of the Shared File Cabinet and the user has Read privilege to
the cabinet.
Of course turning on SYSPRV ain't gonna help if the file, or the
directory it's in, or any of the directories above it has a protection
mask of (,,,,). You must make sure the document file is accessible
even to a process with SYSPRV.
I hope this info will help you find the problem,
-- Paul
| |||||