Office Uri Schema to open Visio documents stored on Sharepoint in desktop app is not working. As per official documentation I tried following but didn't worked. Browser is not detecting ms-visio command.
ms-visio:ofv|u|https://xyz.sharepoint.com/sites/XYZ/ABC/test.vsdx
ms-visio:ofe|u|https://xyz.sharepoint.com/sites/XYZ/ABC/test.vsdx
Visio must be installed on your system. If it is already there then try to repair it or at last reinstall Visio. That worked for me.
Related
I have a client who is asking me to fix an issue they are having with Microsoft Project.
The issue is that they are attempting to open a task list on SharePoint Online via the 'Open with Project' button in the ribbon, but after the alert asking them if they would like to open it in Project 2016 pops up nothing happens.
I have set up a fresh SharePoint environment and tried it at my end, but I get the same problem. There is no error message (as an alert or in the console) and I have wracked my brain and come up dry.
What I have tried:
New SharePoint instance.
Fresh Microsoft Project install.
Looked at the site/site collection features
Multiple browsers (specifically Chrome, IE and Firefox)
The issue is the same no matter what I do.
Has anyone else come across this problem before and, if so, how did you solve it?
Are you using 2016 Click-to-run (C2R) or MSI version? Can you share the build number from winproj.exe?
If you are on C2R version, can you try making the following registry edits (save the following as a .reg file and run it) and see if it helps?
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\SOFTWARE\Wow6432Node\Microsoft\Office\16.0\Common\ExperimentEcs\Overrides]
"ofhdegpklv1irq0"=dword:00000000
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Common\ExperimentEcs\Overrides]
"ofhdegpklv1irq0"=dword:00000000
Since the Windows update from October 10, the ODBC Excel drivers have stopped working. We get the following error when trying to read a file:
"Unexpected error from external database driver (1)"
We open Excel files in Delphi using an ADO connection with the following connection string:
Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\MyExcel.xls;Extended Properties="Excel 8.0;HDR=Yes;IMEX=1";
I can get it to work by switching to Microsoft.ACE.OLEDB.12.0, but for that to work, all our customers would have to install the Microsoft Access Database Engine Redistributable on all the computers they use our software on.
Does anybody have another solution or workaround? Thanks in advance.
On a customers machine I have deinstalled KB4041681 (Windows 7) which came with last Microsoft Patch.
On my machine I have deinstalled KB4041676 (Windows 10).
After that Microsoft.Jet.OLEDB.4.0 is now working.
I hope that Microsoft will fix this bug soon.
There is one solution. Replace "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\MyExcel.xls;Extended Properties="Excel 8.0;HDR=Yes;IMEX=1"
with Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\MyExcel.xls; Extended Properties=\"Excel 12.0;HDR = YES;
After this change you will have to install 2007 Office System Driver: Data Connectivity Components from link on customer machine.
I had the same problem with 2 applications developed by me since 3 years (c# and java).
Since 10-oct-2017 I couldn't export to excel 2003 but 2007 worked, and couldn't import from excel 2003 but 2007 worked too for import.
In ArcGIS Desktop 10.5.1 By ESRI (a most popular software for Geographic processing) Couldn't open excels 2003 and .mdb files.
Temporally Solution: uninstall KB4041693, KB4041687 in windows 8.1 (maybe for w10).
In microsoft changelog of both path say something about "updates [...] and security updates for microsoft jet".
After uninstall and restart all softwares becomes to be normal again.
this problem was introduced in 10-oct-2017.
In microsoft forums this problemas was reported (kb4041693 should "fix" it but still doesn't work).
Maybe in few weeks they will path (properly) this issue.
For me, it worked following these steps:
ps.: We have a Windows Server 2008R2
1 – Download and install this: https://www.microsoft.com/en-us/download/details.aspx?id=23734
2 – Open the .dtsx file and change your Excel connection. On the properties dialog, Click on the three dots in the ConnectionString property and change it to Microsoft Excel 2007. This will automatically change your connection string to:
Provider=Microsoft.ACE.OLEDB.12.0;Data Source={YOURPATH};Extended Properties=”Excel 12.0 XML;HDR=YES”;
3 – Some of our .dtsx files point to a config file (usually has a .dtsConfig extension). I also changed these guys to point to the right provider (pretty much copied and pasted the connection string I got from visual studio)
After this, I ran the SQL Job again and it worked fine.
If you are working with SSIS package then please change your Excel Sheet version 2003 to 2007 in Excel Source or Excel destination.Generally this issue due to excel version.
I had the same problem. Changed Excel 2007 in Excel destinations. It worked. This is same as changing the provider=Microsoft.ACE.OLEDB.12.0.
HERE is the solution... i found it in another forum and work perfectly for me...
it will works 100%
As mentioned in the following:
https://forums.embarcadero.com/thread.jspa?messageID=902557&tstart=0
https://forum.kanors-emr.org/showthread.php?tid=571&pid=2652#pid2652
The KB4041681 installs version 4.0.9801.1 of msexcl40.dll.
Find prior version (4.0.9801.0) of msexcl40.dll
Place in another directory. They suggest the application directory, but since in the next step you will modify registry to point to this older version, it can probably go anywhere.
Update registry key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Jet\4.0\Engines\Excel\win32 to point to the location from step 2.
Uninstall these updates(according to your OS) and your code will start running normally
KB4041681 - Windows 7 SP1 and Windows Server 2008 R2 SP1
KB4041690 -Windows Server 2012
KB4041693 - Windows 8.1 and Windows Server 2012 R2
KB4041678 - For me this was the issue
https://support.microsoft.com/en-in/help/4041678/windows-7-update-kb4041678
This problem was introduced by a recent update of Microsoft Office. there are not alternative solutions at the moment.
EDIT : Looks like a Microsoft issue, see forum indicated by correct answer.
EDIT 2: I am going to stop monitoring this page, looks like the Microsoft forum is dead and I also don't work for the same company anymore.
We have a Excel Add-in (C# / .NET 4.0) which supports Excel 2007/2010/2013 and is deployed through Excel Add-In. Today, a new client ran into problems on a single machine (other machines installed the add-in correctly). The error was:
The value of the property 'type' cannot be parsed. The error is: Could
not load file or assembly 'Microsoft.Office.BusinessApplications.Fba,
Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or
one of its dependancies. The system cannot find the file specified.
(C:\Program Files (x86)\Common Files\Microsoft
Shared\VSTO\10.0\VSTOInstaller.exe.Config line 10)
My buddy Google gave me a number of suggestions: We had the client try a repair of MS VSTO Tools for Office and a repair of Office, and had the IE cache cleared, but continued to get the same error. Finally, we tried re-naming the VSTOInstaller.exe.Config to 'hide' it from the installation and it appears to be working.
I don't believe that our Add-In or installation produces this file, and there is no dependancies on this file that I'm aware of (it appears to be related to a SharePoint assembly)
While I don't explicitly download the add-in myself (I run it through VS2013), I have a VSTOInstaller.config file (Note, not *.exe.config, as seen from client) which contains the following XML:
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<system.net>
<webRequestModules>
<remove prefix="http:"/>
<remove prefix="https:"/>
<add prefix="http:"
type="Microsoft.Office.BusinessApplications.Runtime.DeploymentAction.HttpFbaRequestCreator,Microsoft.Office.BusinessApplications.Runtime,Version=14.0.0.0,Culture=neutral,PublicKeyToken=71e9bce111e9429c" />
<add prefix="https:"
type="Microsoft.Office.BusinessApplications.Runtime.DeploymentAction.HttpFbaRequestCreator,Microsoft.Office.BusinessApplications.Runtime,Version=14.0.0.0,Culture=neutral,PublicKeyToken=71e9bce111e9429c" />
</webRequestModules>
</system.net>
</configuration>
In order to get a better idea of why this client is getting the specified error, I'm looking into
Where this file could have come from.
How does it affect the installation.
Any other comments or general tips related to the exception, or better yet, how to avoid it altogether.
Just try to rename the VSTOInstaller.exe.Config to VSTOInstaller.exe.Config.old and then run the setup
It seems to be a known issue which affects many users. Someone from Microsoft has jumped on the train. See Microsoft support forum where the current progress can be found.
Resolution by Microsoft seems not to be happening. There are several scripts around to fix it. We have added a "Fix It" button to our non-VSTO products. See post.
Had same error when trying to install word-addin on a single machine. I suspect it has something to do with mixed versions of office applications. I have nerver had this problem before on any other machine, but on this specific one, Office 2013 was installed first, followed by Project 2010 and Visio 2010.
Renaming the VSTOInstaller.exe.Config file solved the problem
Since I do not have enough points to add a Comment, I am posting an answer instead.
We were facing the same problems with our MS Word plugin when we tried to install as a regular non-admin user on a fresh machine. VSTOR was already installed through an earlier administrator task. So, I was not sure what was going on. These steps worked for me finally.
Login into the desktop with Administrator privileges.
Downloaded the setup.exe that was created by Visual Studio through
the Publish action of Visual Stuio.
In our we are using the Web based deployment.
Unblocked the Setup.exe by clicking on Properties dialog.
I used "Run as administrator" and let the Setup.exe do its work.
Log back in as regular non-administrative user Download.
Setup.exe and install. It worked fine.
We have same error when trying to install a Visio 2013-addin on a single machines where older versions of Visio have been installed. We have never had this problem before on any other machine, but now on numerous instances this is occurring as we update our Visio add-in to work in the newest version of Visio 2013. Office 2007 or 2010 and Visio 2007 or 2010 was installed first, followed by an upgrade to Visio 2013. Re-naming the VSTOInstaller.exe.Config to 'hide' it from the installation clears the error and our Visio 2013 add-in installs correctly.
Have you tried to run the setup.exe as an Administrator?
I think it'll fix your problem.
Good luck!
I was getting the same error above, but Running the setup published by Visual Studio as Administrator worked for me.
I need to have all the documents in Sharepoint opens in client applications. I set the appropriate setting in the admin page, but it doesn't work for all users. Also I tried to set this in library settings, result was similar.
I think the reason may be on a client side, but I haven't found it. All users with this trouble have IE7 and MS Office 2003.
Does anybody know, how i could handle this?
I would think that the server is checking if the user has Office installed locally. This is achieved by trying to activate an object from the ActiveX control installed by Office locally. You can find this DLL under c:\program files\microsoft office\office12[14]\OWSSUPP.dll. If this dll fails to load, for instance, missing or not registered probably, SharePoint assumes that no local client software is installed. You can register the DLL or run repair on the Office installation, that should fix the problem
How to fix this error in SharePoint:
"The list cannot be displayed in
Datasheet view. A datasheet component
compatible with Windows SharePoint
Services is not installed, your
browser does not support ActiveX
controls, or support for ActiveX
controls
It started to days ago, for apparently no reason. ActiveX is enabled on this site and I had everything working fine so far. Not sure what went wrong.
Thanks,
... from IE check out your Internet Options, and look under 'Programs'->'Manage Add-Ons'
When I had this problem it was because an add-on was missing or disabled... * thinks * "Microsoft Office List 12.0" or something.
I was getting the below in SharePoint 2010.
The Standard View of your list is being displayed because your browser
does not support running ActiveX controls.
Turns out the site (master page) was being rendered in IE9 mode and the datasheet supports only up to IE8.
The datasheet mode can be used temporarily by switching the Document mode and the User agent string both to IE 8, or permanently by using the meta tag X-UA-Compatible IE=8.
This is known issue and you have to install the hotfix provided by Microsoft.
The issue is addressed in the below specified link along with the URL for the hotfix.
http://www.himmeltech.com/blog/fix-for-datasheet-view-issue-error-in-sharepoint-2010/
Let me know whether the suggested solution fixes your issue
Please install below data connectivity component to resolve this issue.
http://www.microsoft.com/en-us/download/details.aspx?id=23734
This link helped me and it worked fine. Our environment was Windows 7 64bit and MS office 64bit as well, after installing this connectivity tools, user had a option edit the data sheet view in sharepoint.
I ran into the same issue after updating to Office 365 but remaining with IE 11 and Sharepoint 2010.
Issue:
using a 64-bit version of Office with a 32-bit version of IE
Reference: Technet
Resolution: Installed 2007 Office System Driver: Data
Connectivity Components
Seems like a client/browser problem.. do you have Microsoft Office installed? Did you change security settings in Internet Explorer?
My environment is SP2010 enterprise and after trying several solutions, I realized that the user that could not see the views in Datasheet style was because did not have installed "Microsoft Access" that is required when you are using views in datasheet style. So the solution for me was to upgrade that specific user from Office Standard to Office Professional
For me, I performed the following and it worked for me:
Open Control Panel and open Programs and Features
Find your instance of Microsoft Office and select it
Click change at the top
On the dialog that comes up, click Add or Remove Features and then continue
Make sure Microsoft Access Web Datasheet Component is installed under Office Tools/Microsoft SharePoint Foundation Support
Even if it is showing as installed, click Continue.
Let everything install, close any office programs out, then try again
These steps worked for me.