| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2073.1 | Beats me... | TAMARA::redear.zko.dec.com::tamara::cummings | Jerry Cummings, TeamLinks | Wed Mar 19 1997 10:55 | 2 |
| Perhaps a log file with tracing enabled would
give us a clue?
|
| 2073.2 | remote drawer in your config? | TROOA::MSCHNEIDER | [email protected] | Wed Mar 19 1997 22:20 | 24 |
| Do you have a remote drawer in your configuration? I ask this because
I have had problems starting TeamLinks 2.7 yesterday (my VT connection
to A1 works fine). It starts and the hourglass appears when I would
expect the drawers to appear.
I traced the problem to the fact that the Reading England drawer I have
configured is not reachable. When I try to select that drawer in VT
mode I get no response ... no timeout, no indication of an error. Only
a Ctrl-Y gets me out of this.
It gets better ... because I had the MAPI interface installed with my
Exchange client, it too hung at startup because it could not reach the
remote drawer ... again no timeout (it let it sit for an hour) or error
message. Remove the ALL-IN-1 MAPI interface at least lets me now use
my Exchange client successfully against the Exchange server
I can't believe that there is no timeout on this incorporated into the
product. We've had numerous people with the Reading drawer configured
all of whom can't access ALL-IN-1 via TeamLinks. Also as an end-user I
have not discovered any way to to delete the drawer without the Reading
ALL-IN-1 server being active.
So I'm hosed until the Sys Admin folks can hack my drawer profile or
whatever.
|
| 2073.3 | Wasn't this problem supposed to be fixed? | XANADU::usr316.zko.dec.com::TAMARA::STJEAN | Bob St.Jean | Wed Mar 19 1997 23:23 | 5 |
| I was under the impression that this was fixed in either TL 2.7 or
the ALL-IN-1 FC Server. Perhaps someone from either TL or ALL-IN-1
who's knowledgible about this can comment.
Bob
|
| 2073.4 | | AIMTEC::ZANIEWSKI_D | Taking bids on Andrew's Alphatraz cell | Thu Mar 20 1997 16:05 | 4 |
| I think this is one of the features that requires ALL-IN-1 v3.2.
I no longer suffer from this problem.
Dave Zaniewski
|
| 2073.5 | | XANADU::cascobay.zko.dec.com::TAMARA::STJEAN | Bob St.Jean | Thu Mar 20 1997 17:44 | 4 |
| So I guess the question now is what version of ALL-IN-1, or what
verson of the FC Server, is running in Reading?
Bob
|
| 2073.6 | not Readings fault .... | TROOA::MSCHNEIDER | [email protected] | Thu Mar 20 1997 22:08 | 6 |
| How can the Reading Server be the problem with respect to versions if
it is down? I suspect it has more to do with the ALL-IN-1 server that
I connect to here locally. It definitely is NOT at 3.2 and never will
be given the migration to Exchange.
Anyway this is a major pain.....
|
| 2073.7 | How to delete? | STP01::VOINOV | | Fri Mar 21 1997 01:51 | 5 |
| Re. 2073.2 - Yes, I have DECPRODINFO remote drawer, I am not sure
where it is located, but it seems the problem is there.
How to delete it from my Teamlinks?
Vladimir.
|
| 2073.8 | Thanks, it works now | STP01::STPVNV::stp01::voinov | Vladimir Voinov, MCS Russia | Fri Mar 21 1997 04:03 | 3 |
| Thanks, I've fixed it, ALLIN1 manuals were on the shelf.
Vladimir
|
| 2073.9 | Just another thing to confound internal users of DEC messaging products. | XANADU::cascobay.zko.dec.com::TAMARA::STJEAN | Bob St.Jean | Tue Mar 25 1997 09:58 | 16 |
| RE: .6
Oops! I guess I didn't stop to think that the local server is the
important one to be at version 3.2 for this feature to work.
To bad this company won't even install upgrades to it's own software.
This is a problem that was fixed and you cannot get the benefit
of the fix. All you get instead is frustration in trying to get
your work done. I would push back hard on whoever is responsible
for that ALL-IN-1 server in order to get it updated.
RE: .8
Anyway, Vladimir, I'm glad you were able to work around it.
|
| 2073.10 | frozen in time..... | TROOA::MSCHNEIDER | [email protected] | Tue Mar 25 1997 19:29 | 17 |
| You're hopeful in assuming that we run current products and have any
motivation to do so.
It took many years for our OA cluster to get to V3.0 and then V3.1....
I think support for V2.x was being withdrawn which forced our MIS folks
into upgrading. Of course in the meantime we got rid of virtually all
the people who knew ALL-IN-1. I'm not even sure if we ever moved beyond
VMS 5.5-2 and now the writing is on the wall for our cluster so V3.2 is
never going to make it to our VAX 65xx cluster which I suspect is also
still running PATHWORKS for VMS V4.2-1.
Well at least the availability is high, something that can't yet be
said of its successor. I'm starting to get used to starting the
Exchange Client and going for coffee waiting for the startup to
complete.
;^)
|