Viewmail For Outlook 2013
Hi all, I have in a customer a Cisco software, called Jabber for Windows (It's basically a softphone), installed on all end users' PCs and, besides other features, it has the ability to integrate with Outlook in order to search por users' personal contacts. The goal of this search is only to take the the contact's phone number (that is on the Outlook contact profile) and then Jabber can call the contact. The problem is that the integration is not working properly with Office 2013 Home and Business. After struggling around with this issue, I have found out that the integration works fine with Office 2013 Professional Plus. The screen shot bellow shows that Jabber is integrated with Outlook Address Book. From the Outlook perspective, does anybody have any new information or any idea that could drive me to the right direction? I have been trying with Cisco support since last november and by now, I don't have any new information.
I downloaded Viewmail 9.0 but failed installing, after I upgraded my outlook from 2010 to 2013, it shows 'no supported version of MIcrosoft Outlook was found'.
Thanks in advance! Just to eliminate some things as possible causes (have absolutely no experience with Jabber - questions provided only as potential starting points for investigation) 1) was the same bit level used in both cases for Office H&B and Pro? 2) What does '.The problem is that the integration is not working properly with Office 2013 Home and Business.' Mean exactly in terms of what happens (or doesn't) as compared to using '2013 Pro?
Does this involve the same machine or 2 different systems? 3) Are both versions using the same kind of installer (i.e. C2R - Click to run vs using the.msi install)? Karl Timmermans Outlook MVP 'Outlook Contact Import/Export/Data Mgmt' http://www.contactgenie.info.
Hi Karl, Thank you for your reply. Find bellow the answers to clarify: 1) was the same bit level used in both cases for Office H&B and Pro? A: Actually no. It's been quite dificult to have exactely the same release on both versions. However I have already updated H&B to a higher release than the Professional. Also tried different H&B builds, as well as different Professioal Plus releases in parallel implementations. 2) What does '.The problem is that the integration is not working properly with Office 2013 Home and Business.'
Mean exactly in terms of what happens (or doesn't) as compared to using '2013 Pro? Does this involve the same machine or 2 different systems? A: On the non-working scenario(H&B), Jabber can find the contact but only brings the Contact Name, E-mail and IM address. On Office Pro, Jabber are able to collect all information, including phone numbers.
3) Are both versions using the same kind of installer (i.e. C2R - Click to run vs using the.msi install)? A: Forgive my ignorance, but I'm not sure what kind of installer I have used.
Both are installed through the following setup.exe. H&B seems to need Internet connection. Thanks, Flavio.
A little confused about what you're using and to stress - have no experience with Jabber (nor have I installed or worked with Office H&B) but that not withstanding something is not making sense regardless since the version of Outlook should be the same regardless of which suite is involved To conduct a valid comparison test would mean running the different versions of Office (H&B) or Pro on the same machine using the same email account(s) where everything is identical (especially the Outlook profile in use) except for the version of Office installed. Even then, if everything is updated correctly, version of Outlook should be the same. A real quick way to determine if you are running a C2R installation of an Office suite is whether or not you have the option to make any changes to the individual components of the suite (C2R installs are an 'all or nothing' installation whereas an.msi install (i.e. Available via an MSDN subscription) allows you to select which components of the suite can be installed.
The C2R installer also allows you to have both the O'2013 version of Outlook installed along side any prior version which the.msi installer would not. Original question regarding bit level was in reference to 32 & 64 bit installs - not Office build versions but for the same of this - gong to presume that you are installing the same bit level version regardless of the suite selected. Without knowing anything else about this - things I'd be checking are - the email accounts (and type) in use in all cases ensuring that everything is identical - especially the email account 'type' (I.e. EAS, POP, Imap, Exchange etc) - whether or not there is another version of Outlook installed on a given system where '2013 is installed Hard pressed to believe that Jabber would return different results if the ONLY thing that's different is the Office suite in use - that makes no sense at all - Outlook doesn't differ between different suites. Karl Timmermans Outlook MVP 'Outlook Contact Import/Export/Data Mgmt' http://www.contactgenie.info. Try these reg hacks. HKEYLOCALMACHINE SOFTWARE Microsoft Windows NT CurrentVersion MAIL 'MAPI'='1' 'MAPIX'='1' HKEYLOCALMACHINE SOFTWARE Microsoft Windows Messaging Subsystem 'MAPI'='1' 'MAPIX'='1' HKEYLOCALMACHINE SOFTWARE Wow6432Node Microsoft Windows NT CurrentVersion MAIL 'MAPI'='1' 'MAPIX'='1' HKEYLOCALMACHINE SOFTWARE Wow6432Node Microsoft Windows Messaging Subsystem 'MAPI'='1' 'MAPIX'='1' We were having the same issue on Office 2013, but it only appears to happen with the click to run version.
After finding similar posts for different products and Office 2013 integration (QuickBooks Office integration). We added the registry settings above.
This resolved the MAPI calendar issues for us. Apparently Office 2013 uses MAPIX for this particular part of the integration/sync.
The click to run version of Office apparently does not install these registry settings so they must be added manually. Hope this works for you. Try these reg hacks. HKEYLOCALMACHINE SOFTWARE Microsoft Windows NT CurrentVersion MAIL 'MAPI'='1' 'MAPIX'='1' HKEYLOCALMACHINE SOFTWARE Microsoft Windows Messaging Subsystem 'MAPI'='1' 'MAPIX'='1' HKEYLOCALMACHINE SOFTWARE Wow6432Node Microsoft Windows NT CurrentVersion MAIL 'MAPI'='1' 'MAPIX'='1' HKEYLOCALMACHINE SOFTWARE Wow6432Node Microsoft Windows Messaging Subsystem 'MAPI'='1' 'MAPIX'='1' We were having the same issue on Office 2013, but it only appears to happen with the click to run version. After finding similar posts for different products and Office 2013 integration (QuickBooks Office integration).
We added the registry settings above. This resolved the MAPI calendar issues for us. Apparently Office 2013 uses MAPIX for this particular part of the integration/sync. The click to run version of Office apparently does not install these registry settings so they must be added manually. Hope this works for you. This fixed my problem. Jabber would not show any appts and would not show a presence of 'in a meeting' if your outlook calendar had an apt scheduled.
Now everything is working. Note: I did not need to do the WINDOWS NT settings on my Windows 8 computer Many thanks for posting this solution!!!! Like Chuck's note below, I did not have to do the Windows NT settings either, for CUCI Lync on Windows 7. These were sufficient.
HKEYLOCALMACHINE SOFTWARE Microsoft Windows Messaging Subsystem 'MAPI'='1' 'MAPIX'='1' HKEYLOCALMACHINE SOFTWARE Wow6432Node Microsoft Windows Messaging Subsystem 'MAPI'='1' 'MAPIX'='1' You also need to ensure your IM provider is set to Lync for CUCI Lync, under HKCU- Software - IM Providers Delete the Jabber key and ensure the Lync and Communicator are set to 00002. It's best to turn them off first. There are two other settings, under Options in Outlook and Lync/Skype, under the People/Person menus, where Sharing needs to be enabled as well.
Viewmail For Outlook 2010
Continuing from my previous post a few days ago, let’s talk more about application errors when Office add-ins are virtualized. It is pretty easy to resolve most add-in issues with the right methodology. One of the first steps in my methodology is to first determine if the issue is related to the add-in loading or a general application error occurring after the add-in has loaded. “First Launch Only” Issue or “Every Launch” Issue? If you have isolated the problem to a load issue, now determine if the problem occurs on first application launch only or on every launch.
If it is a first launch issue, the issue resides most likely with the package. If it is on every launch, the issue could be easily in the package or within the configuration and/or user state of the client machine.
As mentioned in my previous blog post on the subject, the first place you want to check is the LoadBehavior key in the registry. After that I follow a basic process where on first launch issues, I eliminate LoadBehavior as an issue first, then I determine if registry opacity might be a factor. Registry opacity is where the virtual registry key is configured to either “merge” with the local key or “override” the local key. If it is an issue that is occurring on all launches, I first eliminate user state as a potential culprit whether it is an incorrect configuration or corrupted configuration. I’ll repair the package first as well as eliminate any other elements related to user state management before I start actually digging into the package configuration. If the add-in is still failing to load or function properly after loading then you may have to look to ensuring that you have done the basics of planning prior to virtualization.
Time to back track a little: Have We Verified Bitness? Do we have matching bitness - (i.e. A 64-bit Office application requires a 64-bit COM add-in.) App-V does not change the fact that Office requires the add-ins to match the bitness of the office application. In other words, if you are using a 64-bit version of Office, you do not want to be loading 32-bit add-ins Are you sure we aren’t missing requirements somewhere? Razzle magazine 2010. Have you confirmed that any pre-requisites or middleware required for the add-in have been either included in the add-in package or are installed locally on the client machine? I have been burned by this before.
This is the most common reason why an add-in may actually “load” according to Office, but may actually still fail (by either crashing or giving a strange error.) Sometimes the application dependency may appear to be installed but may actually be partially installed. Let’s look at an example: The Case of the Crashing Add-in Now here is an interesting case: Let’s say the Office Add-in loads according to the Event Viewer, yet the Add-in still errors out. What is the best way to go about troubleshooting it? In the example below, a component called Cisco ViewMail for Outlook has failed to load in Outlook 2010. We initially get the following error: ‘VMOAddIn’ has fired an exception. Click the ‘Details’ button to see the detailed information about the error.
This error will contain details including a stack trace. This information may prove to be valuable later. This error is exactly what it says. It is not a load error – it is a handled exception or a crash.
In this example, it is then followed by a more user-friendly message: Cisco ViewMail encountered an error while starting and was not able to recover. ViewMail functionality is not available. So when you get this error, the first thing you will want to do is take a look at the details of the crash.