Dialog opens without a problem, but the messageParent is not working
Working in
Outlook 2016 & Win 10
Outlook 2013 & Win 10
Outlook on web in Chrome.
The place I couldn't get to work and no value received at parent is
IE11 & Win 7
Outlook 2013 & Win 7.
Unfortunately we do not support windows 7 anymore. Support for Windows 7 ended on January 14, 2020. If someone is still using Windows 7, the PC may become more vulnerable to security risks.
https://www.microsoft.com/en-in/microsoft-365/windows/end-of-windows-7-support
Related
When we're trying to open CRM portal v2011 with chrome or edge but aren't seeing anything, we are seeing just an empty page. But we try to open with IE, portal is working, main page is opening.
Also an extra information we installed update roll 6 last.
What can we do for open to browser other than IE?
Apply a more recent rollup to get CRM 2011 working with later browsers, this depends on the combination of the operating system as well.
Microsoft Dynamics CRM 2011 Update Rollup 12 introduced additional
browser compatibility for the Firefox, Chrome, and Safari web
browsers.
Important Microsoft Dynamics CRM 2011 Update Rollup 17 introduced
compatibility with Internet Explorer 11 when it runs in Windows 7,> Windows 8.1 or Windows 10.
Browser compatibility with Microsoft Dynamics CRM 2011
On an Intranet web page, I have a link to an Excel document that resides on a network drive, like so:
ms-excel:ofv|u|file:///N:/folder/file.xlsx
This is an office protocol handler described here.
On computers with Office 2019 installed, the Excel document opens with the registered application (Excel) without problems; on computers with Office 2016 I get the following error:
The action couldn't be performed because Office doesn't recognize the command it was given.
I compared the registry keys at \HKEY_CLASSES_ROOT\ms-excel\ and they are basically the same (of course the path to protocolhandler.exe is different).
When I execute protocolhandler.exe on the command line on the computers with Office 2016, I always get the above error regardless of how I try to launch an Excel or Word document (e.g. ms-excel:ofv|u|file:///... or ms-word:ofv|u|http://...)
Versions of Office:
Office Professional Plus 2019 Version 1808 (Build 10382.20010 click-and-run) 64-bit
Office Professional Plus 2016 Version 16.0.5266.1000 MSO 64-bit
Is there any way to make the protocol handler work with Office 2016?
As you can imagine, that exe handles all the different protocols integrated into MS products. Because of this, every variation of office (or windows) need to have their very own version of this file, in order to operate correctly. Which is also why this file comes deeply embedded within the Office product folder.
We build an Outloook Addin and are testing it across different platforms.
It works on all the browsers (IE 11, Edge, Chrome and Safari), but not in the Outlook 2016 on Windows 10.
We root cause it, looks like the problem is Office JS API UI.displayDialogAsync() .
It does not open a dialog in Outlook 16 and the addin just hangs in there with the following progress message spinning forever,
[Your Addin] is working onr your [Request]
The closest thing we found on the Internet is this Stackflow post in which the answer says
the oldest Outlook build that supports this API is 16.0.6741.0000.
We are using 16.0.9226.2114, so we meet the requirement.
Here are versions of OS/Outlook and Office JS we use in the test:
OS: Window 10 Home, Version 10.0.16299, x64
Outlook: 16.0.9226.2114, 32bit (Version 1804)
Office JS: 1.1.5-release-next.1 (We download the exact package from GitHub and host it on our server)
Wonder is there any known issue of this API on Outlook 2016? Need some help here, thanks!
We have also been trying to debug Outlook 2016 using F12 developer tools .
But our addin cannot show up in the chooser page, no matter we launch the chooser before or after
we click on our addin. We have tried this on several windows 10 machines, but none of them work. Any suggestions that what we could possible miss here?
Seems to me that you had a similar issue to mine. For me adding the remote domain in the manifest resolved the case. Find and update the following section:
<AppDomains>
<AppDomain>https://your.domain.com/</AppDomain>
<AppDomain>https://auth.com/</AppDomain>
</AppDomains>
Proxy HTML works cause it's loading from your domain and still is viable solution.
I have an Excel add-in on a VM that uses the "Microsoft TreeView Control, version 6.0" as a part of Microsoft Windows Common Controls 6.0 (SP6), located at C:\Windows\system32\MSCOMCTL.ocx. The properties window on forms that use the TreeView control show the control as [TreeView control name] TreeView3. Everything works great, and I don't receive any errors.
I also have copies of the working VM with the same Excel add-in, but I receive a Microsoft Forms error that reads "Could not load an object because it is not available on this machine." when I open Excel and the add-in loads.
I am able to re-create the forms, using the same "Microsoft TreeView Control, version 6.0" (same file location and reference), but this TreeView control appears as [TreeView control name] TreeView2 and the error no longer appears.
Instead of re-creating all the forms that use the TreeView2 control, how can I prevent the issue from happening in the first place? The machines are obviously not exact copies. With the exception of .NET v4 installed on the working machine, I don't know what has changed that corrected the issue. It is my understanding that the Windows Common Controls should not be impacted by simply installing .NET v4 on the machines that have the error.
EDIT:
Installed the following and it did not work:
https://www.microsoft.com/en-us/download/details.aspx?id=10019
Also took a shot and installed .NET v4, and still no luck.
Specifications on working machine:
Windows 7 Professional SP1
Excel 2010, Version: 14.0.7162.5000 (32-bit)
Computer\HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP and it has v2.0.50727, v3.0, v3.5, and v4
Specifications on machines with the issue:
Windows 7 Professional SP1
Excel 2010, Version: 14.0.7162.5000 (32-bit)
Computer\HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP and it has v2.0.50727, v3.0, v3.5
EDIT #2: failed to mention that the machine with the issue is a 64-bit OS
Information from Registry for versions of TreeView controls on Working machine and Non-Working machine
Working Machine
Computer\HKEY_CLASSES_ROOT\MSComctlLib.TreeCtrl\CurVer - MSComctlLib.TreeCtrl.2
Computer\HKEY_CLASSES_ROOT\CLSID{C74190B6-8589-11D1-B16A-00C0F0283628}\Version - 2.1
Windows 7 Professional SP1 32-bit
Non-Working Machine
Computer\HKEY_CLASSES_ROOT\MSComctlLib.TreeCtrl\CurVer - MSComctlLib.TreeCtrl.2
Computer\HKEY_CLASSES_ROOT\Wow6432Node\CLSID{C74190B6-8589-11D1-B16A-00C0F0283628}\Version - 2.0
Windows 7 Professional SP1 64-bit
I just Use AJAX Library from WebDAV library to start WebDAV in browsers other than IE with your information from
http://www.webdavsystem.com/ajax/programming/opening_ms_office_docs/
And This is result:
Microsoft Office 2013
IE:Protocol ext ==> ok
Chrome:Protocol ext ==>ok
FF:Protocol ext ==> ok
Microsoft Office 2010
IE:ActiveX ==> ok
Chrome:Plugin2 ==>fault
FF:Add-on ==>ok
Microsoft Office 2007 and earlier
IE:ActiveX ==>ok
Chrome:Java applet2 ==> fault
FF:Java applet ==>ok
I can not run editing document when run in chrome (version 45) from Microsoft Office 2010, Microsoft Office 2007 and earlier.
please support us to run on Chrome.
I have attached my demo, please help me solve this problem:
http://www.mediafire.com/download/6kv2d8zcq47w9fj/TestWebDavHtml.rar
Thank you very much!
First of all make sure you are using the IT Hit WebDAV Ajax Library v5 or later.
Regarding MS Office 2010:
Make sure you have Microsoft Office 2010 SP2 or later installed. Also verify that you have all Windows updates installed. WebDAV components are updated rapidly and may fix some issues.
Regrding MS Office 2007:
In general MS Office 2007 and earlier are not supported any more by Microsoft. However you still can open documents using it:
Make sure you have all MS Office and Windows updates installed.
Make sure you have a latest WebDAV Ajax Library v5 or later, client protocol application installed and web browser extension enabled.