We have noticed that there is issue on the Citrix environment in regards to WebView2. We are trying to run office add-in inside the Outlook desktop (365) and as soon as Outlook tries to run the add-in we can see in the task manager that CPU and Memory usage spikes from 8 percent to 99 percent. Multiple instance of WebView2 processes running can be seen which consumes most of the processing power. The office add-in is not able to load at all. We have tried 2-3 office add-ins and we see the same behavior. There is no Microsoft edge installed on the Citrix .
Version
Runtime: 90.0.818.56
OS: win 10
Screenshots
Task Manager usage
Please let me know your thoughts on this.
This might be caused by hooks in Citrix which preventing the WebView2 component from starting. It can be fixed by adding the WebView2 process as an exception from all Citrix hooks. You can refer to this article to edit the registry to achieve this.
Reference link:
Webview2 application running in a Citrix environment
Is WebView2 supported in the Citrix Server
Related
We have a client that wants to run our Excel Add-in (web-based Office Add-in written with office-js), however, they don't have Edge or IE installed.
They are running Version 2008 (Build 13127.21766) of Excel, which according to the documentation from Microsoft uses the EdgeHTML WebView (Edge Legacy)
I know with the WebView2 runtimes you can install the runtime separately since Windows 8.1 and 10 didn't come with that runtime.
Can the same process be followed for the EdgeHTML WebView (Edge Legacy), as in can we install an EdgeHTML WebView runtime while not having Edge installed?
If so can someone point me in the right direction on where to get this runtime from?
The only way to get the EdgeHTML webview installed is to install Edge.
Are you sure the client is on a Windows version? According to my knowledge, Excel 2008 which belongs to Office 2008 is only for Mac. You can refer to this doc and this page.
According to the doc you mentioned, they can use Safari for Office Add-ins on Mac.
Microsoft Edge (Chromium) is in Beta on MacOS. Will there be a Microsoft Edge (Chromium) 'webview' control for MacOS? I suppose this is dependent on having support for .NET Core. Currently the support is limited to C++.
Is this same link, it says "In the future, we plan to support WebView2 on .NET.", I would assume this means .NET Core? Does anyone know what the plan is?
According to the comments in this Issue there is a plan to support Linux and MacOS, but probably only post 2021.
It is stated, that support for these platforms is on their Roadmap, though.
At present, we are not available with any information on whether there will a webview control for the MS Edge Chromium browser for MAC OS or not. We also don't have any information about it's future plan.
I suggest you wait for the official announcement from Microsoft about webview control for MAC OS.
I am trying to connect to a server in PowerPivot. I am running across a few problems. Here is the connection string:
Provider=Microsoft.Jet.OLEDB.4.0;Data Source=\accounting001\Accounting\TimeSlips2014\Databases\Philadelphia\;Extended Properties=Paradox 5.x.
It uses NT authentication as the password. I have read all about the problems with MS Jet 4.0. I am running 64x on 64x office apps. I receive the not registered on local computer error. Can anyone help me connect. I already installed the Access 2010 DB engine however I wasn't able to get it to connect. Thanks!
The Microsoft OLE DB Provider for Jet and the Jet ODBC driver are available in 32-bit versions only. You can't run them in 64 bit mode.
The Solution
If you run a program in a 64 bit environment and need to utilize jet to open an Access, Excel or text file there are several options to make this work.
Run the program in WoW64 mode (emulates 32-bit on 64 bit systems). This will make the 32 bit drivers work.
If the application is an web app hosted on IIS 7 you can choose to configure the web sites application pool to run in 32-bit mode.
With Office 2010, there are new drivers, the 2010 Office System Driver, which will be provided in both 32-bit and 64-bit versions. You can use these drivers to let your application connect to Access, Excel and text files in a 64 bit environment utilizing the new 64-bit drivers. The provider name is "Microsoft.ACE.OLEDB.12.0". You don't need to buy or install the Office suite, the components are available as a separate download. http://www.microsoft.com/downloads/details.aspx?FamilyID=C06B8369-60DD-4B64-A44B-84B371EDE16D&displaylang=en
Summary
It is possible to open Excel, Access and text files on 64 bit systems. You can either configure your app to go 32-bit or you can change your application to use the new 64 bit drivers.
See the original link for this information here.
A client runs our Delphi 2007 app on Windows 2008 R2 via Citrix XenApp.
He's been facing an issue where the file open dialog crashes sometimes. He's applied latest updates for windows and Citrix.
I've seen many articles on the net where similar issue occurs for various apps other than Delphi like MS Office apps, VS 2008, Adobe PDF etc.
The client doesn't face this on any other application and thus is blaming our application.
If the our app's "Compatibility Mode" is "Windows XP SP3" then all is fine. Hence, client has raised a question stating if our Delphi app is Windows 2008 R2 certified.
What changes are required if we have to make our Delphi 2007 app certified for Windows 7/2003/2008/2008 R2 ?
We have fixed lots of strange Delphi (2009) app crashes on Windows 2008 R2 64 Bit Terminal Server environment with these additional lines in the DPR:
// make it Terminal Server Aware (app without installer writing to ini files / registry)
{$SetPEOptFlags IMAGE_DLLCHARACTERISTICS_TERMINAL_SERVER_AWARE}
Note: to compile, it requires the Windows unit
The crashes appeared in many unexpected places like open dialogs. With the excellent madExcept tool we found that apps crashed within operating system routines in some Windows DLLs, and disappeared when we added the "terminal server aware" flag.
I am not a Delphi developer but a Google Search for Delphi 2007 System requirement took me to this page http://edn.embarcadero.com/article/36573#requirements
The following Windows platforms are supported:
Microsoft® Windows 2000 Professional or Windows 2000 Server (SP4 or higher and security updates are recommended)
Microsoft Windows XP Professional (SP2)
Microsoft Windows Vista™
Microsoft Windows Server 2003 (SP1)
The latest service packs and security updates are recommended for all platforms
Microsoft Internet Explorer 6.0 SP1 or later
I don't see Windows 2008 here.
Its not uncommon for the following:
It would be up to you to determine and test how your app functions under 2008. Knowing that a number of things as always change with each release of windows let alone server/workstation.
You tell them under what senarios YOU will support your application being run.
If you require your app to be run as compatbility mode with xp sp3, and tell them that, and tell them YOU dont support it outside that configuration. If you wont support it under a virtual environment.. then you tell them that.
Obviously the better answer would be to test it on 2008 R2, and check all your functionality and say you will support it running in a natural state.
I developed a Windows service which is running without any problem in Windows XP service pack 3. When I deployed this service in Windows Server 2008 it is not working. The service started without any problem.
I enabled the option Windows XP service pack 2 from the compatibility property of the .exe which deployed there.
But no more action after the starting the service.
What could be the problem?
One thing I would check it to see if any of your referenced assemblies are 32bit specific. We ran into a similar problem when using Microsoft SQL Server Reporting Services. The .dll we used to get a list of the web service interfaces, was 32bit/64bit specific, so we had to swap it out depending on which envionment we were running on.
Since the error could hide anywhere I would suggest to first discern what exactly is not working under Windows Server 2008.
Implement some logging functionality into your service (if you didn't do so already, I strongly recommend it) and let the result be printed into a log file. See what's working and when it stops to work. Hopefully this will give you a better understanding of what's going on under the hood.
Also, this way we can help you way better than now.
[EDIT]
Maybe these two can help you?
COM Class Factory Error
Running 32 bit app using 32 bit com on a 64 bit Windows machine