[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
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 |
3055.0. "Teamlinks and connect to ALL-IN-1 failure" by KERNEL::OTHENJ () Fri Jul 23 1993 12:26
Can someone help me with the following problem?
ALL-IN-1 v3.0 Starter
Teamlinks v1.1
The customer can successfully connect to another ALL-IN-1 system (v3.0
Classic) from Teamlinks, but if she tries to connect to the File Cabinet of
the above machine she gets the error
Access to drawer or document not granted
on any ALL-IN-1 accounts she has tried. The FCS is started on the ALL-IN-1
system, and the user can access ALL-IN-1 drawers if she logs onto the VMS
machine, so I am not sure where to look next (I am a bit new to Teamlinks I
am afraid). Can anyone help me out and tell me where else I should be
looking?
================================================================================
Note 2293.1 Access to ALL-IN-1 drawer not granted 1 of 4
IOSG::WALKER 8 lines 16-JUL-1993 12:03
-< Protections? OAFC$DEFAULT account? >-
--------------------------------------------------------------------------------
I am afraid I can't think of an immediate answer to this, but it looks
like a protection problem. Try looking at protections on your account
FILECAB.DAT and ACCESS.DAT. Also look at OA$DATA:OAFC*.DAT, and
PARTITION*.DATs. Check that the FC Server account OAFC$DEFAULT is not
disusered, and you could also check to see if you have the VMS system
parameter NCP MAX links set high enough.
================================================================================
Note 2293.2 Access to ALL-IN-1 drawer not granted 2 of 4
KERNEL::OTHENJ 20 lines 20-JUL-1993 10:56
--------------------------------------------------------------------------------
File protections are as follows;
filecab.dat (RWED,RWED,,)
ACCESS.DAT;1 (RWED,RWED,,)
OAFC$SERVER_CONFIG.DAT;1
(RWED,RWED,,)
OAFC_SERVER_MASTER.DAT;1
(RWED,RWED,RE,RE)
PARTITION.DAT;5 (RWED,RWED,,)
oafc$default account is not disusered. The protections look the same as
our default ALL-IN-1 system, so I do not knwo why the customer is
getting the errors. Any other ideas?
================================================================================
Note 2293.4 Access to ALL-IN-1 drawer not granted 4 of 4
KERNEL::OTHENJ 15 lines 23-JUL-1993 06:21
--------------------------------------------------------------------------------
I have set CFCLOGOPTIONS in office.ini, and have received this
additional error
oafcopencabinetw error 55805066
oafcstatus 2 : 0
resource open cancelled
when trying to open the ALL-IN-1 file cabinet. Can anyone translate
what this error means, please?
T.R | Title | User | Personal Name | Date | Lines |
---|
3055.1 | /ACCESS hours? | IOSG::MAURICE | Differently hirsute | Fri Jul 23 1993 14:17 | 9 |
| Hi,
I looked in the code and I think the error is "Not authorized to use
this VMS account at this time.", which I'll guess relates to the
AUTHORIZE /ACCESS parameter.
Cheers
Stuart
|
3055.3 | | KERNEL::OTHENJ | | Wed Jul 28 1993 13:07 | 17 |
| Stuart,
Another quick question for you (or anyone else that knows the answer!).
The translation that you gave me for the problem that the customer has
was correct, but if I look in \teamlink\trblshot.wri then the error I
had translates to
A connection was attempted to an undefined node
which is clearly wrong. Where did you locate the error, and can you
give me a location of the correct list of error codes, as the list in
the .wri file seems to be wrong.
Thanks,
Julie
|
3055.4 | oafcext.h | CHRLIE::HUSTON | | Wed Jul 28 1993 15:08 | 10 |
|
If you look on the VMS system, look in file sys$library:oafcext.h, or
oafcext.sdl. THese have all the FCS error messages, mapped to symbols.
I believe you can also use f$message to get the text.
Stuart probably has access to the original FCS error message file,
that's how I found it.
--Bob
|