Conference chefs::ms-exchange

Yes, on NT you have to manually add your
TeamLinks directory. Right click on My Computer,
select the Environment tab, and update your
path.

Jerry

    I had a bit of a problem adding the C:\TEAMLINK path in a way that it
    would work.  It appears that this has to be ALL CAPS for it to work
    cleanly.
    
    Anyway, now it not only lets me convert docs, but promps to connect to
    ALL-IN-1 IOS as well.  I wasn't sure if EL was supposed to do this.
    
    Now, how about getting the folders in Exchange sorted in alphabetical
    order?
    
    (Thanks for the tool!)
    
    FJP

    I've installed Exchange V5.0 RC1 client and Outlook 97 client on my
    Windows NT V4.0 SP2 Intel machine.  I'm also running TeamLinks V2.7 ECO
    1.
    
    Since the upgrades I am getting a GPF in ExchangeLink.  I'm getting a
    GPF in ELNKMAPI.DLL at 0001:2EB5.
    
    Any suggestions?
    
    - Dave

Dave,


This is a problem I escalated to Microsoft about 4 weeks ago.  They've only 
just taken it seriously.  The MAPILogonEx call fails from a 16-bit 
application using the new MAPI.DLL.  The call actually returns a success 
code but gives a NULL pointer for the active session.  This is what causes 
the GPF.  I could fix the code so that it doesn't GPF but you wouldn't be 
able to log on as the MAPI.DLL is just plainly broken!
    

For the time being Exchange V4.0 SP3 is the newest supported release.  
Sorry!  As soon as Microsoft get back to me with a fix it'll be in the 
conference and on the ExchangeLink web site...



Ian.


P.S.  If anyone knows a better route into Microsoft than the U.K. Exchange 
Beta support team please mail me...!

I have just installed ExchangeLink and am getting the following error message:

"ExchangeLink was unable to load its MAPI support DLL. Please re-run SETUP to
ensure that ELNKMAPI.DLL is correctly installed."

I am running version 1.0.05 of ExchangeLink. In addition, I have installed
Outlook 97 but am also running Exchange 4.0. I checked the version of MAPI.DLL
in windows\system directory and it is 4.0.993.3. Could this be the problem?

thanks for any assistance,
Andrew
[Posted by WWW Notes gateway]

Andrew,


That MAPI.DLL is the one supplied with Exchange V4.0 SP3 (I think!) but 
should be fine.  It's build 1389 onwards of the DLL which seems to have a 
bug in it.

Could you check the following:

1.  ELNKMAPI.DLL exists in the directory where EXCHLINK.EXE was installed.
    Also that there are no other versions of this DLL anywhere else on your
    system.

2.  Check the [XTI Transports] section of WIN.INI and make sure that the
    entries for DECNET, WSDECNET and WINSOCK point contain the path where
    windows is installed on your system.


If neither of these fix the problem, please could you let me know what 
version of Windows this is running under.



Ian.

I have checked the location of ELNKMAPI.DLL and its OK. Also, the XTI section 
in WIN.INI was point to a C:\WINNT\ directory. I've fixed this, but still the
same problem.

I have previously had Teamlinks 2.7 installed on this system and removed it.
Could this be a problem?

I am using Windows 95 with Microsoft Plus installed. How do I get a more
precise version number for you?

thanks, Andrew
[Posted by WWW Notes gateway]

Andrew,


I suspect that the removed copy of TeamLinks is the problem.  I check for 
the existance of a TeamLinksPath value in the [TeamLinks] section of 
OFFICE.INI.  If that's there I assume that TeamLinks has already been 
installed.

Try deleting your OFFICE.INI, re-installing ExchangeLink and see if the 
problems go away.  (You may also need to re-do the [XTI Transports] fix 
mentioned in .-2 as it'll probably get overwritten!  I'll fix that one in 
the next release...!)



Ian.

Ian,

Thanks for your help but....

I still have the same problem. I have also installed a beta version of Office
97 which I subsequently removed. Could there be files lying around (eg a
MAPI232.DLL) that could be causing ELNKMAPI.DLL to fail to load?

Andrew
[Posted by WWW Notes gateway]

Andrew,


Yes, that's quite possible.  The MAPI.DLL you posted details of earlier is 
called a "thunking" DLL.  It's 16-bit and translates the calls to 32-bit 
calls which it passes to MAPI32.DLL.  If the 32-bit environment and all of 
its support files are not installed correctly then the thunk will fail and 
ELNKMAPI.DLL may well fail to initialise.

I'm afraid the fix isn't an easy one.  If you were to just re-install 
Exchange Client V4.0 and all the service packs they would not replace any 
newer DLLs.  Therefore, you have to find and remove all the DLLs Exchange 
uses first!  This is a real needle in a haystack job (I don't know if 
you're English but that's probably a local phrase).

I'm afraid my recommendation would be a fresh build of the PC starting with 
the operating system :-(  The problem with beta and RC code is that it 
often doesn't come with very well tested un-install utilities.  Even the 
best ones very rarely roll shared file versions back to their original 
levels after removing a product...



Ian.

The European Mail, Messaging and Electronic Commerce group are about to 
release a service called Digital Mail Migration Startup for Microsoft 
Exchange (QS-MSXA9-5Z) which will contain the migration tool previously 
known as ExchangeLink.

Details of this new service offering will are avaialable at the previous 
web site http://flossy.reo.dec.com/ExchangeLink.  If your customer is 
interested in migrating via this service please contact David Newman 
(NewmanDa@mail.dec.com) on +44-1189-202349 (DTN: 830-2349).  Alternatively 
your local NSIS representative should have details.

As soon as the announcement has been made official I will post a copy here.



Ian.

    RE:.109  CleanSweep95 from Quarterdeck will monitor all installs and
    save a log of the files that are added.  This has helped me find DLLs
    that have caused me problems.

re. 109 etc

I have fixed the problem and have ExchangeLink working. It is great! Just what
I needed.

To fix the problem I uninstalled Exchange, Office and anything else I could
think of :-) Then I re-installed Windows 95 (over the top of the existing
install - I made it replace any files it thought were newer. Then I
re-installed everything. 

Surprise, surprise it all worked.

Thanks for your help on this!
regards, Andrew
[Posted by WWW Notes gateway]

Has anyone managed to get ExchangeLink to work with Exchange Client V5.0 or 
Outlook 97?  If so, please could you post your configuration details, 
including operating system, here?

I'm trying really hard to get Microsoft to admit that there is a bug in 
MAPI.DLL for the above versions.  I reported the problem over 2 months ago 
whilst Exchange V5.0 was in beta and they have still not taken it 
seriously.  This is just a sanity check to ensure that a GPF will happen in 
ELNKMAPI.DLL for these versions...

I'm very sorry that this is causing an issue to so many people but the ball 
is totally out of my court.  Microsoft PSS will not even talk to me as I'm 
not one of the named few!



Ian.

Exchangelink Version 1.0.05
"Digital Internal Use Only"

"This version of Exchangelink has expired. Please contact your
 software supplier for details of the latest release"

Any pointer to a new/unrestricted release ?

*donald

PS: it was expired on monday 3/24. somewhere it read "expires end of
march" ??

The latest version of ExchangeLink is available at:

	http://flossy.reo.dec.com/ExchangeLink

The Internal Use Only Version no longer expires but must not on any account 
be given to a customer as it contains Digtial and Adobe licensed code.

The long awaited Customer Trial version may be freely given to customers 
but expires at the end of each month.  To register this version (and remove 
the restrictions) please contact the Programme Manager, David Newman, on 
+44-1189-202349 or DTN 830-2349.

I'll be on holiday now until Tuesday 8th April so please direct any 
questions to Dave...



Ian.

    Well, I'm having a bit of problem installing the updated version of
    ExchangeLink.  All install attempts (regardless of installing account)
    return the error "An error occurred whilst setting the attributes of a
    copied file.  Please check you have full access to the files you are
    creating."
    
    Any ideas what this might be due to?
    
    Also, any response from Microsoft on fixing the MAPI.DLL bug they
    introduced in V5.0?
    
    Thanks,
    
    - Dave

    RE: Installation problem.
    
    The installation problem occurs with both Exchange V5.0 RC1 and
    Exchange V5.0 "Gold".  I'll try to find a V4.0 environmnrt I can test
    the installation on.
    
    Any info would be appreciated.
    
    - Dave

Dave,


Sorry for the huge delay in the reply - I've been on holiday.

What platform is the installation giving trouble on?  I presume you're 
using V1.0.06.  If not, try copying from 
http://flossy.reo.dec.com/ExchangeLink as I've put some fixes in place 
around this area.

I'm not allowed to talk to Microsoft directly about this as I'm not one of 
the (about 5) named few on the PSS contract!  Therefore, I'll only hear 
second-hand when it gets fixed.  I keep asking but haven't heard yet.  
Expect an announcement here the moment I do...

Regards,



Ian.

    The platform is Windows NT V4.0 SP2 (Intel), with the Exchange V5.0
    Gold client.
    
    - Dave

    ExchangeLink V1.0.6 installed successfully -
    Migration apparently works successfully.
    WPS+ docs are converted to RTF.
    
    Still I have a problem - trying to read in Exchange one of the
    attachments fails with the message 
    file C:\WINDOWS\TEMP\ATT00001.RTF or one of its components cannot be
    found.
    An attached Word document within a specific mail can also not be read
    ("application associated with the attachment cannot be started")
    
    Changing back to TeamLinks I can read all attachements.
    
    What must I do ?
    
    regards
    Artur
     
    

    
    Hi,
    
    I fetched V1.0.6 today and got the migration to work but for one
    serious problem: the dates of the messages are seriously corrupted.
    
    Example: source 1997-01-08 14:34; target 1698-01-10 14:35:
    
    Difference 298 years 363 days 23 hours 59 minutes :-) 
    
    Clients: Win95 Swedish, Teamlinks V2.7
    Servers: ALL-IN-1 V3.1 Swedish, MSX production IS whatever that is
    
    What should I be looking at?
    
    	cheers,
    
    		Stefan

Artur:

Please could you set Debug=1 in the [Settings] section of ExchLink.Ini.  
Then migrate just the single message which gives problems.  In the middle 
of the migration ExchangeLink will stop and tell you the location of 
HEADER.INI.  Please ZIP and send me the contents of the TEMP directory at 
that point.  Also, a copy of the message forwarded (via ALL-IN-1) to 
MCMICHAEL_I@A1CHEFS@RDGMTS@REO could be useful.


Stefan:

It's been a while since I made you life hell asking MR Memo questions - I 
suppose it's your turn now!!!

Could you also turn DEBUG on and send me just the HEADER.INI file for a 
single message?  It would be useful to know the original time and date 
stamps of the message you pick.  Also the destination (IE. Public folder, 
Mailbox or PST file).



Ian.

    Info for the date problem sent to Ian off-line

Well, it works great for me. One thing. Can you add a 'x of y' line so I 
can see how many docs it has done. The '30%' is fine but I'd like explicit 
info if possible.

regards

Alan

Exchange link (v 1.0.6) seems to be missing documents when I expand the 
list in an ALL-In-1 folder.

Is this a known problem ?

Alan

Hi Alan,


I'm not aware of this one - does your folder have lots (possibly thousands) 
of documents and messages in it?



Ian.

    Any answers on the installation problems I am encountering in an NT
    (Intel) V4.0-SP2, Exchange V5 (Gold) environment?  The environment and
    problem were discussed in detail a couple Notes back.
    
    Thanks,
    
    - Dave 

re .127

It can be a folder with 4 items - only 2 shown, or 210 items - the last 19 
missing.

Umm - I wonder. I applied a filter some time ago. Does that still apply 
after I shutdown and restart ?

Alan

Yup - thats it.....

Alan

Re: .128

Dave, I'm still waiting for a response from Microsoft on when the MAPI.DLL 
bugs will be fixed in Exchange V5 and Outlook '97.  I will post any updates 
here as soon as I get them.  Considering they've know about it for three 
months now I'm not terribly impressed!


Re: .129 and .130

Alan, glad you've solved the "problem"!  I'm pretty sure that the text of 
the filter button changes from "Add Filter" to "Modify Filter" or 
something like that when it's applied.  Perhaps I should add something else 
to make it more obvious...



Ian.

Change in Price for :		

"The Digital Mail Migration Startup for MS-Exchange" Consulting Service

The service is delivered with the migration tool (previously known as 
ExchangeLink).

The new price for the Migration Service will now be a 50% cross charge for the 
number of ExchangeLink licences provided to the customer.

Additional Information, including the pricing details can be found on the 
ExchangeLink web site :

http://flossy.reo.dec.com/ExchangeLink

Requests for the ExchangeLink Migration tool must be submitted to the Program 
Manager, Dave Newman @REO (mail to: newmanda@mail.dec.com)

Regards

Dave

Welcome to the conference Dave...  :-))