HCL Traveler for Microsoft Outlook 3.0.0.0 (Previously IMSMO) is now available on Flexnet!

HCL Traveler for Microsoft Outlook 3.0.0.0 (Previously IMSMO) is now available on Flexnet!!
In this release, we offer the following features:
(1) Microsoft Office 2019 Support
(2) HCL washed client
(3) AUT check is removed (as it is an IBM Connections feature)

Good news to see an update on this. Any improvements on the core code?

I have the following issues:

1) Client resyncs frequently - either manually (Missing e-mail, stuck e-mail in Outbox) or it does it automatically after an error.

2) Registry Error requiring users to have admin privileges to fix profile - Every user, at least 1X a month.

3) E-Mail Folders and Content will duplicate requiring a re-sync.

4) No Attachments in Calendar Items / Also content is limited to certain characters

Excited to see how the new app performs! Thanks!

Hello Kevin,

We have not observed the issue which has been pointed but would request to raise a Case with us if you still observing this issue with the latest client, we will be happy to resolve your issue.

For 4) No Attachments in Calendar Items / Also content is limited to certain characters

This is still a limitation with the product.

Thanks and Regards,

Manish Jha

Thank you for your response. We continue to have the issues noted above with no improvement using the new version. We have also seen the registry the error more than the IBM version. A new looping issue has occurred where the registry error will prompt each time the user starts Outlook. To resolve this, I have to remove the whole solution then setup again.

Please let me know if you have any insights to this issue.

Thanks!

Hello Kevin

If you are migrating from IBM Mail Support for Microsoft Outlook (IMSMO) to HCL Traveler for Microsoft Outlook (HTMO), you are required to create a new profile. Existing profiles created under IMSMO will not function in HTMO.

https://help.hcltechsw.com/traveler/11.0.0/htmo/3.0/use_HTMO_setting_up.html

Thanks and Regards,

Manish Jha

Here is the process I followed:

1) Removed Outlook Profile using IBM

2) Remove IBM Sync

3) Rebooted

4) Installed new HTMO client

5) Setup New Profile using the HTMO Client.

I have done this on multiple PCs. So actually right now my PC is doing this. I close Outlook, and reopen, I get the prompt for the registry repair. I even rebooted my PC this morning. I have been running the new software since released. I have had my Outlook resynced 3-4 times this month with a repair or automatically repair.

Let me know you have any ideas.

Hello Kevin,

Have not seen this issue occurring in my test. Would request you to raise a case with us (HCL Support) to further troubleshoot the issue

Please follow the below steps for log collection and share us the client data by reproducing the issue

Note: share the time when the issue was reproduced and user information

Reporting a problem with HCL Traveler for Microsoft Outlook

https://help.hcltechsw.com/traveler/11.0.0/htmo/3.0/use_HTMO_reporting_a_problem.html

Thanks and Regards,

Manish Jha

Thank you, if others have these issues. Please provide feedback in this thread so we can help to improve this product.

Hi All,

missing -EMails can be solved, if you organize a rule within the HCL Notes Database, which moves incoming new mail ("All Documents)" into a new folder...I don't know why, but there seems to be a synchr. Problem when HTMO tries to sync the "(inbox)" - folder..

I tested this workaround and it still works, if the new folder is added to MS Outlook Abonement...

Thanks, I can give this a try. Working outside the Inbox could work.

HCL - Fix this program!!!

We have the same issue with HTMO v3.0.0.0!

2) Registry Error requiring users to have admin privileges to fix profile - Every user, at least 1X a month.

I then reinstall HTMO and a few days it works without any issue...then out of a sudden the registry message pops up!

I think I might have a solution, waiting on the HCL Dev Team to provide the details.

So the repair itself calls : htmo:repair_registry?profile=<PROFILENAME>

The protocol is stored in the registry key like HTTP but when I check for HTMO handler its blank, I do have the old IMSO key but its blank.

Here is reference they provided https://help.hcl-software.com/domino/9.0.1/admin_imsmo/adm_imsmo_protocol.html

Once I confirm the correct key and command, I will update this thread.

Do you get any of my other issues on your end? If not what server version are you running?

I installed a bulk of users with the command

imsmo:add_account?server=mail.example.com&profile=IBM&email=samantha%40mail.example.com&display=Samantha

This worked for me to setup automatically users Outlook profile, but everytime they start Outlook they get the message to repair via registry!

It would be interessting why this is happening, as eg. my workstation does not have this issue. Probably because HTMO on my ws was installed manually with admin privileges?

1) Client resyncs frequently - either manually (Missing e-mail, stuck e-mail in Outbox) or it does it automatically after an error.

You mean the whole mailbox is synched again? Since we have 10 Users who use HTMO since a week, i have to wait for their response

3) E-Mail Folders and Content will duplicate requiring a re-sync.

Same here.

4) No Attachments in Calendar Items / Also content is limited to certain characters

Known Limitation?

Thx, Zafer

Can you run on your PC : htmo_tools.exe htmo:repair_registry?Profile=XXX

I get an error - invalid map <K, T> Key

So I got the repair to work using imsmo:repair_registry?profile=XXX which indicates it being successful, but the registry error continues to prompt.

I also tried running htmo_tools.exe which is the application handler for IMSMO so the command should be htmo_tools.exe repair_registry?profile=XXX but it errors out with a invalid map <K, T>

I'll continue to push support to work with Dev on this one.

Hi, it was the same thing here.

I did a imsmo:repair_registry?profile=XXX it said, successful, but the error still occurs! After that is took the HTMO_300.exe and installed it with elevated rights and since then the issue seems to be gone.

At least for today after several restarts!

I did the install originally as admin, and it takes a week or 2 for the registry error to hit, then it doesn't go away till you remove and reinstall the whole setup. I did it at least 3 times on my PC but that registry error keeps coming back. Its like the registry repair is not doing what is needed to clear the issue.

We should get successful feedback running : htmo_tools.exe repair_registry?profile=XXX ; There is also a disconnect with the Dev and Support, they still think the correct protocol handler is HTMO: repair_registry?profile=XXX but its IMSMO

Support did provide me with this : https://support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0039175&sys_kb_id=2fd824e01badf30083cb86e9cd4bcbed

But my registry key was as described in the article

Waiting on the feedback from the Support/Dev to see what is next.

I was able to speak to Dev, the registry repair does not work.

So the work around, is import the registry settings manually to fix it.

I use Office 365, so it might be different key if you use 2016/19 but you can search for SchedulingInformation

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\Software\Microsoft\Office\16.0\Outlook\SchedulingInformation\FreeBusySupport]
"EX"="{0006F014-0000-0000-C000-000000000046}"
"SMTP"="{FD8E8A04-39FE-4CA2-A04D-9D383F599BED}"

In my case SMTP was a different value. This value refers to a DLL in the classes root registry hive.

There is another release coming of HTMO with a few other fixes and features, so that is good news.

If you upgrade to 3.0.1, there is an issue with the application handler where it was updated to HTMO but the application is still using IMSMO.

Fix - update \HKEY_CLASSES_ROOT\HTMO to \HKEY_CLASSES_ROOT\imsmo

Command Line repair:

htmo_tools.exe url "htmo:repair_account?profile=<Profile_name>"