I need the VShadow or its equivalent for Vista (Business).
All the VShadows I am trying are giving errors. I need to use it from Command Prompt.
The procedure entry point ClusterGetVolumeNameForVolumeMountPoint could not be located in the dynamic link library RESUTILS.dll."
or
VSHADOW.EXE 2.2 - Volume Shadow Copy sample client
Copyright (C) 2005 Microsoft Corporation. All rights reserved.
(Option: Create shadow copy set)
ERROR: COM call "CreateVssBackupComponents(&m_pVssObject)" failed.
- Returned HRESULT = 0x80070005
- Error text: Access is denied.
This particular error means that you need to be elevated - run as administrator.
However there are multiple versions of this app for various windows versions. I'm trying to find one for Windows 8.1 - which I understand uses a whole different engine. So far I have only found versions - which has a link to a 2010 zip of various versions.
Note - you are using a compiled version of the VSS Tools 7.2 - which says in the documentation only works with Windows Server 2003 (NT 5.2) and Vista is NT 6.0.
Related
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.
I need to install Microsoft XML Parser 4.0 from Inno Setup.
How can that be done?
I was given a task to embed MSXML in the installer of ours. It's a proprietary piece of software our company makes (for accounting, it uses XML to store and exchange data). Apart from modern systems It's also going to be installed on many old systems using Windows XP.
I'm using Inno Setup 6.1.2.
Also, is there a quiet mode of installation as an option? So the users won't have to click anything and just be notified that MSXML was installed?
Did you Google this?
https://silent-install.net/software/microsoft/msxml_parser/4.30.2107.0
Eg:
msxml.msi /qn /L* "%temp%\XML Parser 4.30.2107.0.log" /norestart ALLUSERS=2
If you look at the Msiexec (command-line options) it does say the qn switch will display no user interface.
Somewhat of an aside, the requirement of installing both on XP and on 'modern' systems may create a conflict that you or your installer will have to resolve.
From Installing and Redistributing MSXML 4.0:
System Requirements
MSXML 4.0 is supported in Windows Server 2008 R2, Windows 7, Windows
Server 2008, Windows Vista Windows Server 2003, Windows XP, and
Windows 2000
From Installing and Redistributing MSXML 6.0:
System Requirements
MSXML 6.0 is supported in Windows Vista; Windows 2000 Service Pack 4;
Windows Server 2003; Windows Server 2003 Service Pack 1; Windows XP
Service Pack 1; Windows XP Service Pack 2.
MSXML 6.0 is preinstalled with Windows Vista. For earlier versions of
Windows, you can install MSXML 6.0 as a separate download.
So you can only use MSXML4 below Vista. And with Vista and above you should be able to reply on MSXML6 already existing.
Your installer could perform an OS version check (alt ref) and then only install MSXML4 if needed. Or you might be able to detect specifically if MSXML6 is installed and then install MSXML4 only if not (assuming therefore its an older system).
But I would test your application (if you haven't already) and see if it will run against MSXML6; it may, without changes. If so then I would forget MSXML4 and include MSXML6 in the installer instead (*). That way your installer could just run it 100% of the time, and expect that on Vista and up it would just do nothing. Your installer would therefore be simpler plus you would be taking advantage of "MSXML 6.0 provides security and performance improvements over earlier MSXML versions." noted here.
(*) Unless you have to run on WinXP pre-SP1?
I received an error while trying to execute an MS SSIS package that contained Excel source:
"The Microsoft.ACE.OLEDB.12.0 provider is not registered on the local machine".
While trying to install MS Access Database driver 64-bit, and then MS Access Database driver 32-bit, I get two conflicting errors:
"You cannot install the 64 bit version of Microsoft Access Database Engine because you have 32 bit Office Products installed"
and
"You cannot install the 32 bit version of Microsoft Access Database Engine because you have 64 bit Office Products installed"
I guess that on my pc 32-bit and 64-bit versions of office are running.
The interesting thing though is that I see that only MS office 2010 and MS office Viewer 2003 are installed on my machine and the latter through a 2007 compatibility package.
So, my question is probably two fold:
Is running the driver the proper way to solve my initial problem?
How can I overcome the situation where neither a 32-bit nor a 64-bit can be installed because there exist both 32-bit and 64-bit office versions on my pc.
Please keep in mind that I am not sure what should I uninstall. Office 2010 and MS windows viewer 2003 are running on my pc.
I came across the same conflicting error messages when installing the Access Database Engine.
Since I new I had installed a 32bit office, I installed the 32bit version of Access Database Engine with this command:
.\AccessDatabaseEngine.exe /quiet
I found this trick here: https://blogs.msdn.microsoft.com/dataaccesstechnologies/2017/10/18/unexpected-error-from-external-database-driver-1-microsoft-jet-database-engine-after-applying-october-security-updates/
By the way, in my case one of the two error messages was also mentioning that I had installed the click to run extensibility component 64-bit registration.
only one version 32/64bit of Microsoft Access Database Engine 2010 Redistributable can be installed.
Download it from this link https://www.microsoft.com/en-us/download/details.aspx?id=13255
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 am facing problem while installing Sharepoint 2010 Server on Windows-7 Professional I have followed the steps given in this MSDN page. Still I am getting the following error while trying to run Setup.exe.
Can anyone help me on this?
Thanks
It seems that SharePoint Server 2010 is only compatible with
Windows Server 2008 x64. But it's not. check this.
Source: Installing Microsoft SharePoint Server 2010 on Windows 7 x64
It is much simple to do this. Just a little work and your SharePoint Installation ready to work on Windows 7 64 bit Client OS.
You can simply install SharePoint Server 2010 on your client OS just by modifying a config file.
Copy CD contents to a folder on your hard drive and Follow following steps:
Go to the Files folder
Go to the Setup folder
Open config.xml
Add the following line before the closing </configuration> tag
<Setting Id="AllowWindowsClientInstall" Value="True"/>
Save the file and Run the Setup.exe. now it will work fine.
Remember: These lines are Case Sensitive so Write them correct.
On Windows 7, install the following additional prerequisites required before running Setup.exe:
Microsoft FilterPack 2.0. At a command prompt, type the following:
installation directory folder\PrerequisiteInstallerFiles\FilterPack\FilterPack.msi
Microsoft Sync Framework
SQL Server Native Client
Windows Identity Foundation (Windows6.1-KB974405-x64.msu)
Chart Controls (this is not required if you are going to install SharePoint Foundation 2010).
SQL Server Analysis Services - ADOMD.Net (this is not required if you are going to install SharePoint Foundation 2010).
For more detailed installation tutorial go through MSDN - Setting Up the Development Environment for SharePoint 2010 on Windows Vista, Windows 7, and Windows Server 2008
It seems like your copy of Sharepoint 2010 Server is intended to be installed onto a machine running Win Server 2008 SP2 or later. Not win 7. Either upgrade your machine or see if there's a more compatible copy of share point server.