| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2146.1 | | XANADU::CUMMINGS | Jerry Cummings, TeamLinks | Tue Apr 22 1997 16:31 | 6 |
| I don't recall ever hearing of a problem like this. If
he does not connect to remote filecabs is local filecab
available? Is the local filecab on a local hard disk or
on a network share?
Jerry
|
| 2146.2 | Are long-name directories supported? | TEAMLK::alfras1_port27.alf.dec.com::teamlk::maximous | | Tue Apr 22 1997 16:52 | 2 |
| Could it have anything to do with TeamLinks being installed
in a subdirectory under Program Files - a long-name directory?
|
| 2146.3 | | NNTPD::"[email protected]" | | Wed Apr 23 1997 09:17 | 18 |
| Thanks for your replies so far...
re .1
>>>Is the local filecab on a local hard disk or
>>> on a network share?
This is on a laptop, the local filecab is on the harddisk.
re .2
>>>Could it have anything to do with TeamLinks being installed
>>> in a subdirectory under Program Files - a long-name directory?
I had the same thought, but my laptop is set up the same way. BTW, this
is a Sales Workbench laptop/setup.
[Posted by WWW Notes gateway]
|
| 2146.4 | Bad external object ID associated with the script ? | XANADU::x400it.zko.dec.com::manana::rought | | Wed Apr 23 1997 17:49 | 12 |
| Where is the script for the send unsent messages button command stored ?
Have them remove the button from the button bar and then add it back
again.
My guess is that an external object id associated with the process of
sending the unsent messages has become invalid. Two things that come
to mind is the location of the script and the location of the drawer that
holds the unsent messages. If it is the location of the script, then
removing the button and adding it back may fix the problem.
Dave
|
| 2146.5 | | XANADU::cascobay.zko.dec.com::TAMARA::STJEAN | Bob St.Jean | Wed Apr 23 1997 18:17 | 5 |
| TL 2.7 has been out since September 1996. Shouldn't the Sales
Workbench PCs have been updated by now?! :-)
Bob
|
| 2146.6 | | NNTPD::"[email protected]" | | Thu Apr 24 1997 08:38 | 36 |
| re .4
> Where is the script for the send unsent messages button command stored ?
>
> Have them remove the button from the button bar and then add it back
> again.
>
> My guess is that an external object id associated with the process of
> sending the unsent messages has become invalid. Two things that come
> to mind is the location of the script and the location of the drawer that
> holds the unsent messages. If it is the location of the script, then
> removing the button and adding it back may fix the problem.
I briefly tried looking for the script with the script editor, but couldn't
find it. Will spend more time. You could be onto something here as the
button
for the send unsent messages is blank. Will also try removing and re-adding.
re .5
> TL 2.7 has been out since September 1996. Shouldn't the Sales
> Workbench PCs have been updated by now?! :-)
Good point, I'm usually ahead one version on TL (running 3.0 now), so will
have him upgrade.
re .4 & .5
If he did re-install 2.5, wouldn't that have fixed the script/button???
thanks again for your thoughts.
r
[Posted by WWW Notes gateway]
|
| 2146.7 | I saw that error too - briefly.. | CHEFS::annep.uvo.dec.com::taylora | | Fri Apr 25 1997 07:51 | 18 |
| Rod,
I don't think this is probably going to help much, but you might be interested to know I
had exactly the same error yesterday. I was investigating something else, so I didn't
take much notice and had to reinstall anyway and the problem went away. However two
things I thought might have contributed were:
1. Some of the TeamLinks files in the Windows directory were probably 2.7 files NOT 2.5
files, so it was running with a mixed set.
2. It was using an NTFS drive.
As I said, reinstalling cured my problem, but I don't know if either of the above could
be a factor in your user's case?
Regards,
Anne
|