I have installed Service Fabric, and although the cluster explorer has installed, I have noticed that the standard SFDevCluster folder has not been created
The error message in the local cluster manager is useless - error occurred resetting cluster.
I then delved into the PowerShell side and got the message below.
I am out of ideas and getting pretty frustrated! This has installed loads of other times on other machines without any issues at all.
I have uninstalled and reinstalled multiple times.
I have added Service Fabric to Visual Studio.
PS C:\program files\microsoft sdks\service fabric\clustersetup> .\DevClusterSetup.ps1
A parameter cannot be found that matches parameter name 'Refresh'.
Get-Module : A parameter cannot be found that matches parameter name 'Refresh'.
At C:\program files\microsoft sdks\service fabric\clustersetup\DevClusterSetup.ps1:54 char:35
+ Get-Module -ListAvailable -Refresh <<<< --quiet *>$null
+ CategoryInfo : InvalidArgument: (:) [Get-Module], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Commands.GetModuleCommand
PS C:\program files\microsoft sdks\service fabric\clustersetup>
I have even tried to copy my Service Fabric files over to the machine and that doesn't work either.
Has anyone ever had anything like this? Please note that these issues are occurring outside Visual Studio (2017).
Paul
I generally have these kind of problems when I upgrade my local cluster runtime and SDK.
This specific error I've not faced yet, but the rule of thumb I always follow when the update fails (that is pretty often) is:
Remove Local Cluster via SF Cluster Manager App
Uninstall the old SDK and Runtime version
Restart the computer
Install the new versions
Restart the computer
Setup the cluster via SF Cluster Manager if not already set as part of the setup
I could notice that most issues I had with SF installations was related to the old resources not being totally wiped out from the machine, when installing new ones, something left behind was affecting the new installation, after following these steps, I've never had issues again.
Regarding your error message, issue might be because you are running these scripts directly, and they are intended to be run from SF Cluster Manager App. Also, I would not be surprised if any modules are still loaded when these PS scripts run.
Related
I'm setting up Azure Data Studio ( ADS ) 1.29 running the Machine Learning extension , to manage SQL 2019 Machine Learning Services in Win2016. The reason for running ADS is so I can install Python and R packages into SQL MLS via ADS. Ultimately we will use this against an Azure SQL Managed Instance ( MI ).
I have configured the default Python and R directories installed by SQL 2019 MLS on the server, as my Python and R machine learning paths in Settings\Extensions\Machine Learning.
When I go to the ADS Machine learning extension and click on "Manage Packages" I get these errors which I cant resolve :
"the following R packages are required to be installed vctrs, odbc , sqlmlutils"
These R packages are confirmed installed in SQL server.
Not sure how you check if they are installed in ADS?
"the following python packages are required to be installed sqlmlutils==1.0.3"
These Python packages are confirmed installed in both ADS and SQL server.
"Failed to complete task 'Verifying package management dependencies' : Error invalid selection.
This error directly above seems to be a result of the first 2 errors.
I have tried reinstalling ADS in new directory etc but this has not worked.
Any assistance appreciated....
A solution :
It appears when you configure ADS it needs this very specific configuration, right down to the .exe name
Machine Learning: Python Path :
C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\PYTHON_SERVICES\python.exe
Machine Learning: R Path :
C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\R_SERVICES\bin\R.exe
Install this SSL workaround for Python, if needed from
https://sourceforge.net/projects/openssl-for-windows/
file is : Win64OpenSSL_Light-1_1_1k.msi
Also you need to install the odbc and sqlmlutils as per these instructions :
https://github.com/microsoft/sqlmlutils/blob/master/R/README.md
Windows
Download the latest release from https://github.com/microsoft/sqlmlutils/releases:
From command prompt in directory where R.exe resides , run
R.exe -e "install.packages('odbc')"
R.exe CMD INSTALL sqlmlutils_1.0.0.zip
Once all this installs and runs, you should then be presented with an option to manage both Python and R packages within the Machine Learning extension.
We also found R packages could not be installed in SQL MAnaged Instance or On Prem until you go to ADS version 1.31.0 or higher.
While deploying the Service Fabric Cluster, I got the below issue.
Connect-ServiceFabricCluster : An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)
At XXYYZZ(path of script):62 char:2
+ Connect-ServiceFabricCluster #ConnectionParams
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Connect-ServiceFabricCluster], BadImageFormatException
+ FullyQualifiedErrorId : CreateClusterConnectionErrorId,Microsoft.ServiceFabric.Powershell.ConnectCluster
Actuall it was running perfectly when we installed required modules
https://www.microsoft.com/en-in/download/details.aspx?id=30679
http://www.microsoft.com/web/handlers/webpi.ashx?command=getinstallerredirect&appid=MicrosoftAzure-ServiceFabric-CoreSDK
But we wanted to install the service fabric cluster from the system, where system do not have the required Service Fabric Components(which are above ones). Now we are loading these components/modules/dll through the Import-Module command by placing the dll's in a particular folder and used the command called Import Module. May I know, how can I resolve this issue.
I'm doing the exact same thing and didn't want to install the Service Fabric SDK on our build system. After some trial and error I finally got it right:
I've placed the necessary Service Fabric Tools and SDK files into source control, check those tools out during the build, and then import the PowerShell modules from both before calling Connect-ServiceFabricCluster. I realize that placing binaries and related files into VCS isn't a great solution: in the future I'd love to use something like Artifactory instead.
Here's the solution in detail.
First, put the necessary tools into VCS:
Create a folder in your VCS working copy with two sub-folders: Tools
and SDK.
Copy the contents of
%WINDIR%\System32\WindowsPowerShell\v1.0\Modules\ServiceFabric into
the Tools sub-folder
Copy all of the DLLs from C:\Program
Files\Microsoft Service Fabric\bin\Fabric\Fabric.Code into the Tools
folder
Copy all of the files from C:\Program Files\Microsoft
SDKs\Service Fabric\Tools\PSModule\ServiceFabricSDK into the SDK
folder.
Add all of these files to your VCS working copy
Commit the changes to VCS (and push if applicable)
Second: Add the tools to your build
Third: in your PowerShell script import the tools and SDK modules (I'm assuming the Service Fabric tools and SDK are in a ServiceFabric sub-folder relative to the current working directory):
Import-Module ServiceFabric\Tools\Microsoft.ServiceFabric.Powershell.dll
Import-Module ServiceFabric\SDK\ServiceFabricSDK.psm1
Here are some final thoughts:
I use a 64-bit flavor of Windows 7 and all of our build machines are 64-bit. I honestly don't know if a 32-bit version of the Service Fabric SDK and tools exists. At any rate you need to be sure you are using a 64-bit version of PowerShell. We use TeamCity and I explicitly set the Powershell run mode Bitness to x64.
The Deploy-FabricApplication.ps1 script that is included with Service Fabric projects attempts to load the Service Fabric SDK module by reading a registry key for the SDK path and then calling Import-Module. Since the build machines do not have the SDK installed I added a modified copy of this script to VCS as well, commented out the lines that read the registry and load the module, and then make use of the -UseExisingClusterConnection parameter.
We have a VSTO Application that is installed on many machines. If the Add-In is already installed, there is no issue. If you try to uninstall or install, you get the following error message:
The following Microsoft Office solution cannot be installed due to a general installer error: App_Name.vsto
0x80070002
This application has been working without hiccups for almost a year now. Our Sys Admin and I believe we've narrowed it down to a mandatory Windows 10 update as our base Windows 10 image has it working fine and it works on Windows 7 no issue. However, the update is already pushed out and nothing is showing up in the logs.
I know the VSTOInstaller.exe.Config file has been the cause for several of these installer issues, however I cannot find that file on any of our machines even though I KNOW I modified one machine and changed the name to VSTOInstaller.exe.Config.Old for the Business.fba error some have gotten. I assume an update somehow packaged the config file into the .exe.
The Windows 7 machines also don't have the Config file as well...
What we've tried:
Searching for an older .Config file to place in the folder
Rolling back to a previous version
Recompiling
Changing the publish destination folder and setting version back to version 1.0.0.0
Update: Placing a VSTOInstaller.Exe.Config then a VSTOInstaller.Config in the C:\Program Files\Common Files\microsoft shared\VSTO\10.0 folder
Update: Running repair then doing an uninstall/reinstall on Visual Studio Tools for Office Runtime (x64) program from Control Panel.
Update: Cleared Application Event Log
Update: Stopped Windows Update service, Renamed C:\Windows\SoftwareDistribution folder to C:\Windows\SoftwareDistributionOld, then restarted the Windows Update service.
I'm at a loss. Any help is GREATLY appreciated.
If anyone has the VSTOInstaller.exe.Config file, I'd love to try and place that in the folder to see if it works.
Version:
Word Version - 16.0.6769.2040
VS Version - 14.0.25420.1
OS Version - 1511 (OS Build 10586.494)
Turns out the error was part of a Microsoft Office update. Unsure if somehow the update listed in the question updated Office 2016 in the background somewhere.
The steps to resolution were as follows:
Uninstall O365 from the Control Panel
Download the a full removal tool and run it from https://support.office.com/en-us/article/Uninstall-Office-2016-Office-2013-or-Office-365-from-a-PC-9dd49b83-264a-477a-8fcc-2fdf5dbf61d8
At this point after those have ran, uninstall the add-in if it was installed.
Reinstall O365
Reinstall/Install the VSTO Add-In
Easier resolution than I thought and really appreciate all the assistance.
Windows 10 Update error 0x80070002 or 0x80070003
Step 1: Windows Service Checklist:
Open Windows services.msc, check the following services status (If it is different set it to the recommended settings)
[enter image description here][1]
Disable any third party antivirus applications, as it may block the Windows 10 upgrade process.
Step 2: Reset Windows updates:
Resetting windows updates, in this step we will clean up old failed updates that have been saved in the computer, let start by first disabling the windows update service.
Service Status(Start/Stop/Blank) Automatic/manual/Disabled
Background Intelligent file Transfer Started Automatic
Crytographic Service Started Automatic
DCOM service Started Automatic
RPC Started Automatic
Windows Modules Installer Started Automatic
Windows Update Started Automatic
Windows defender Blank Disabled
Windows firewall Blank Disabled
Disable Windows update service and stop the service
Now open Run command and type %windir%
Check for Software distribution folder delete the folder. (If it fails restart the computer, then try deleting it)
In Run command window type “cleanmgr” to launch disc cleanup to clean old junk files.
Restart the windows update service set it Automatic. Once completed, the windows upgrade error code 80070002 should be resolved. Try the upgrade now. Still unlucky, get in touch with us or proceed to next step
Step 3: Dism/Readiness Tool
This step is to fix core Operating system files that are corrupted and is affecting the Windows 10 upgrade and causing the error. Most of the cases running the tool or the command will fix the corrupted files, there are cases where some stubborn files remain. We can assist you in repairing them manually, post the log to us so we can check and revert back to you.
Depending on the OS, you have to choose proper tools,
For Windows 8 and higher use the following command in elevated command prompt.
Dism /Online /Cleanup-Image /ScanHealth
For windows 7: Download and run windows update readiness tool
microsoft.com/en-in/download/details.aspx?id=20858 –X64
microsoft.com/en-in/download/details.aspx?id=3132 – X86
Check the logs for the above tools in the following location
%windir%/logs/cbs
Post the log for further steps.
Please refer to this link for more info :
http://www.msofficelivesupport.com/windows-update/windows-10-update-error-0x80070002-or-0x80070003/
I have very recently started working toward the 70-410 exam, and almost straight away I'm having issues regarding installing the GUI on a core install of server 2012 using install-windowsfeature command in powershell.
I am using virtualbox, Server 2012 installs and runs fine both installed as Core and Standard versions. With Standard install I can use the remove-windowsfeature command to remove the GUI and at a later date I can reinstall the GUI on that Standard install, though I believe that is due to the files still being present on that machine after uninstall.
To reinstall on the Standard installation I only need to use Install-WindowsFeature Server-Gui-Mgmt-Infra, Server-Gui-Shell -Restart
It restarts and all is fine, Gui is now installed.
Now for the Core installation the above command fails as it has no idea where to look for the files. Which is what I would expect.
Using both a mounted Iso file or a physical DVD with the following commands have the same results.
Initially I used the command DISM /Get-Wiminfo /Wimfile:d:\Sources\install.wim
Which Lists the 4 versions that I have on the DVD or ISO.
Server 2012 Core, Server 2012 Standard, Datacenter 2012 Core, Datacenter 2012 Standard
Now I have tried using Index 1 and 2, though I expected only index 2 'Server 2012 Standard' to work as Server 2012 Core shouldnt have the GUi files required.
The command I am using is:
Install-WindowsFeature Server-Gui-Mgmt-Infra, Server-Gui-Shell -Source wim:d:\sources\install.wim:2
This completes on the Standard version (after gui has been removed), and boots with Gui on restart.
On the core machine it gives an error saying:
install-windowsfeature: The request to add or remove features on the specified server failed.
Installation of one or more roles, role services, or features failed.
The component store has been corrupted. Error: 0x80073712 at line:1 char:1
+ install-windowsfeature server-gui-mgmt-infra, server-gui-shell - source wim:d:\so ...
+ CategoryInfo : InvalidOperation: <#:PSObject> [install-windowsfeature], exception
FullyQualifiedErrorId : DISMAPI_Failed_To_Enable_Updates.Microsoft.ServerManager.Commands.AddWindowsFeatureCommand
I suspect it will have something to do with the source but I am not sure, any help is most welcome.
I tested this on one sample test server I have and it is working without any errors. However, in your case as error suggests. Just try to copy the source files again from some good source as those files seems corrupt.
I am trying to install the latest Azure PowerShell (released Nov. 9th 2015). If I try to install it using Web Platform Installer, I get the following error:
Azure Modules from the PowerShell Gallery are installed on this machine. Please remove these modules before installing this MSI.
If I run Get-InstalledModule in PowerShell, I see that the Module Azure (version 0.9.11) is installed. So I tried uninstalling it using the PowerShell command Uninstall-Module Azure. Here I get the following error:
PackageManagement\Uninstall-Package : The property 'ModuleBase' cannot be found on this object. Verify that the
property exists.
At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\PSGet.psm1:1351 char:21
+ ... $null = PackageManagement\Uninstall-Package #PSBoundParameters
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (Microsoft.Power...ninstallPackage:UninstallPackage) [Uninstall-Package],
Exception
+ FullyQualifiedErrorId : PropertyNotFoundStrict,Microsoft.PowerShell.PackageManagement.Cmdlets.UninstallPackage
Ok, I solved my problem. Stupid mistake: I was not running Uninstall-Module Azure as an admin. Once I started PowerShell with admin priviledges, uninstalling old Azure PowerShell was no problem.
Hm, would love to see a more descriptive error message in that case ;-)
I hit the same issue, but did not have anything Azure related appear when I executed Get-InstalledModule.
If you execute $env:PSModulePath in a powershell prompt it will list out all of your Module path locations, navigate to each of those and delete anything azure related and you should be able to install the new azure powershell cmdlets.