Am following Microsoft's "Getting Started" tutorial to deploy a Node.js Express app as a Cloud Service.
After carefully installing all the tools on two machines, one Win 7 and one Win 8, I get down to the point of generating "Hello World" and the tutorial suggests running the intuitively named: New-AzureServiceProject helloworld in Windows PowerShell.
Here is what happens:
PS C:\node> New-AzureServiceProject helloworld
New-AzureServiceProject : Could not find a part of the path 'C:\Program Files (x86)\Microsoft
SDKs\Azure\PowerShell\ResourceManager\AzureResourceManager\AzureRM.Profile\Resources\Scaffolding\General\scaffold.xml'.
At line:1 char:1
+ New-AzureServiceProject expressapp
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : CloseError: (:) [New-AzureServiceProject], DirectoryNotFoundException
+ FullyQualifiedErrorId : Microsoft.WindowsAzure.Commands.CloudService.Development.Scaffolding.NewAzureServiceProjectCommand
Taking a look at my system after installing Powershell and the Azure SDK as instructed, I DO have a directory:
C:\Program Files (x86)\Microsoft SDKs\Azure\PowerShell\ResourceManager\AzureResourceManager\AzureRM.Profile
However, that directory does NOT have a subdirectory "Resources" and hence it never finds the scaffold.xml file....
I tried creating the subdirectory Resources\Scaffolding\General inside of AzureRM.profile. That changed the error to simply "could not find scaffold.xml"
I tried setting the write positions on "General" to be wide open. No change.
The above error is on the Win 8 machine. On my Win 7 machine after digging more carefully into the install and going multiple layers deep into prereqs not mentioned in the tutorial, AzureRM.Profile ends up installed in C:\Program Files\C:\Program Files\WindowsPowerShell\Modules rather than in C:\Program Files (x86)\Microsoft
SDKs\Azure\PowerShell\ResourceManager\AzureResourceManager but the behavior is identical.
I have looked all over the web and have not been able to find any information on the missing scaffold.xml that might point to a solution. Is this a template that New-AzureServiceProject needs to create the app? Or is this something that is supposed to be generated by New-AzureServiceProject?
Any suggestions would be appreciated...
Thanks!
I solved this problem by copying folder
C:\Program Files (x86)\Microsoft SDKs\Azure\PowerShell\ServiceManagement\Azure\Services\Resources
to
C:\Program Files (x86)\Microsoft SDKs\Azure\PowerShell\ResourceManager\AzureResourceManager\AzureRM.Profile
Need to copy the Resources folder from:
C:\Program Files\WindowsPowerShell\Modules\Azure\3.1.0\Compute
to
C:\Program Files\WindowsPowerShell\Modules\AzureRM.profile\2.3.0\Resources\Scaffolding\General
According your error message from PowerShell, it seems that you miss installed powershell AzureRM.* modules.
Please try to run the following commands from the Windows PowerShell console running as Administrator:
PS C:\> Install-Module AzureRM
PS C:\> Install-AzureRM
Then run New-AzureServiceProject helloworld again.
Meanwhile, if you want to get started with the node.js application on Azure Web Apps, you can refer to Azure Website Cmdlets.
Apologies for the terrible experience. This looks like a bug in one particular version of Azure PowerShell. To diagnose, we would need to know which version - if you used the msi installer, or WebPI, you will find thins in the 'Uninstall a Program' control panel, the entry is 'Microsoft Azure PowerShell'.
One piece of confusion in some of the comments - the hosted service cmdlets are part of the older RDFE (Service Management) commands in Azure. The cmdlets that support these are in the 'Azure' module, and not in any of the 'AzureRM' modules.
To install the latest version, I highly encourage you to use Web Platform Installer, or the msi installer that you can retrieve from our GitHub repo. PowerShell Gallery is a great solution as well, if you are very comfortable with PowerShell module management.
I will bring this tutorial to the attention of the documentation team. Meanwhile, if you can identify the azure powershell version and the sdk version you are using, I can see if there is a fix for the problem.
Copy content from
C:\Program Files\WindowsPowerShell\Modules\Azure\4.3.1\Services\Resources\Scaffolding\General
To
C:\Program Files\WindowsPowerShell\Modules\AzureRM.profile\3.3.1\Resources\Scaffolding\General
Related
I am trying to run service fabric local cluster manager but it is giving following error : Failed to setup local cluster.
I have Microsoft Azure service fabric SDK 3.2.187 installed locally.
Steps I followed is -
Install Visual studio 2017 - version - 4.7.03056. While installing I selected Azure development workload from VS installer.
After VS installation, I installed Service Fabric SDK from Web Platform Installer.
After this right click on Service fabric local cluster manager -> Setup local cluster -> 1 Node.
When I do this, I am getting There were errors while setting up the local cluster. Retrying..
Any help would be really appreciated.
I had similar issues many times when I tried to install SF on local machine.
Try the following steps:
First of all, check if you have IIS enabled on your PC from Windows Features. If it is disabled, enable IIS and related features.
If this not helped, do the following:
Uninstall:
Remove the installed Service Fabric SDK, Runtime and VS tools
Delete installation folder under C:\Program Files\Microsoft Service Fabric
Delete folder from registry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Service Fabric
Reboot PC
Install:
If you already installed Microsoft Web PI, run the program and install the Microsoft Azure Service Fabric SDK again the following way:
Check if IIS is selected from the configuration of installation
Check if the prerequisite C++ package is installed during the process (Microsoft Visual C++ 2012 SP1 Redistributable Package (x64) ).
Then
Install Service Fabric tools using the Visual Studio Installer
Run the command Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Force -Scope CurrentUser from a command line as admin
Hope this helps.
Delete Fabric*.dll under C:\Windows\System32 makes it work for me.
It seems new SF would not insert these binaries into System32 folder, while old version uninstall program would not delete them. So it cause version corruption in running new version.
After successfully upgrading my cloud service to the new "Azure SDK for .NET 2.5.1" I got the following error when trying packaging/publishing.
Could not load file or assembly 'Microsoft.WindowsAzure.Packaging,
Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or
one of its dependencies. The system cannot find the file
specified. C:\Program Files
(x86)\MSBuild\Microsoft\VisualStudio\v12.0\Windows Azure
Tools\2.5\Microsoft.WindowsAzure.targets
The related line in the "Microsoft.WindowsAzure.targets" config file is 2930 which obviously is related to CSPack.
<CSPack
ServiceDefinitionFile="#(TargetServiceDefinition)"
Output="#(PublishServicePackage)"
PackRoles="#(Roles)"
SiteMapping="#(SiteMapping)"
RoleProperties="#(RoleProperties)"
ImportedModules="#(ImportedModules)"
CopyOnly="false"
>
</CSPack>
So I went on to create a fresh new Azure Cloud service in a fresh new project to see if something went wrong with the upgrade. Unfortunately the problem persists.
Is there a workaround or will I have to rollback to v2.4 (that will cause me significant amount of pain)
I am running on VS 2013 update 4.
Sorry for the trouble, everyone. We are investigating what's causing this. It looks like there is an odd behavior with our installers where in some environments those two binaries are not installed correctly.
We did discover if the 2.5.1 Azure Authoring Tools is removed and reinstalled, the missing binaries will be installed correctly. So if you run into this issue, please remove Authoring Tools v2.5.1 from Programs and Features, and reinstall via either the Web Platform Installer or the direct download links:
http://download.microsoft.com/download/1/E/7/1E76DD6F-66F1-47E0-A76A-3BBAAC617316/MicrosoftAzureAuthoringTools-x64.msi
http://download.microsoft.com/download/1/E/7/1E76DD6F-66F1-47E0-A76A-3BBAAC617316/MicrosoftAzureAuthoringTools-x86.msi
Apologies for the inconvenience. We will continue the investigation.
I searched locally for the required dll and found it in almost all previous versions of the Azure .Net SDK had it (from v2.0 onwards I believe).
So in order to fix this you need to copy the following dlls from the previous version v2.4 of the SDK to the similar location for v2.5.
SDK installation paths.
Src location: "C:\Program Files\Microsoft SDKs\Azure\.NET SDK\v2.4\bin"
Dst location: "C:\Program Files\Microsoft SDKs\Azure\.NET SDK\v2.5\bin"
Dlls to copy (missing):
Microsoft.WindowsAzure.Packaging.dll
Microsoft.WindowsAzure.ServiceModel.Common.dll
Since there may be a better answer to this I will not mark this as an answer yet.
I am trying to publish ASP.NET MVC 6 App to Azure with Visual Studio 2015 CTP. And getting the following error
Publishing with publish method [MSDeploy]
Calling msdeploy with the command: ["C:\Program Files (x86)\IIS\Microsoft Web Deploy\msdeploy.exe" -source:IisApp='C:\Users\*****\AppData\Local\Temp\AspNetPublish\NgCalendar-28\wwwroot' -dest:IisApp='ngcalendar',ComputerName='https://ngcalendar.scm.azurewebsites.net/msdeploy.axd',UserName='$ngcalendar',Password='{PASSWORD-REMOVED-FROM-LOG}',IncludeAcls='False',AuthType='Basic' -verb:sync -enableLink:contentLibExtension -enableRule:DoNotDeleteRule -retryAttempts:2 ]
INVOKEPOWERSHELL(0,0): Error : Unrecognized link extension 'contentLibExtension'.
INVOKEPOWERSHELL(0,0): Error count: 1.
Not sure where it's coming from and how to tweak it.
Try deselecting "Publish using PowerShell script" checkbox in publish Settings
It worked for me
I had the same error.
In my case the problem was an old version of "msdeploy.exe".
After some searching I found one "msdeploy.exe" in the folder "C:\Program Files (x86)\IIS\Microsoft Web Deploy\msdeploy.exe" which caused the problem and another one in the folder "C:\Program Files (x86)\IIS\Microsoft Web Deploy V3\msdeploy.exe".
As I don't know how to change the path in Visual Studio to the newer version, I just saved the old folder and copied the complete content of the new folder into the old.
After this everything worked for me and I was able to publish to Azure :)
Hope this helps.
I want to take some of MSDN help files offline on a windows machine which does not have visual studio installed on it. the problem is that I cannot find a way to get and install Help Library manager and Help viewer without installing the visual studio or sql server.
How can I install them without installing the visual studio or sql server?
I just wrote an answer on how to do this for an older question, which can be found here.
For convenience, here are the essential steps to get Help Viewer 2.2 to run without going to the trouble of installing a complete copy of Visual Studio 2015:
Most of the files required by HlpViewer.exe can be found on the Visual Studio DVD in two different MSI packages. By passing some additional command line arguments to msiexec, it's quite easy to install them manually:
msiexec.exe /i help3_vs_net.msi VS_SETUP=1
msiexec.exe /i vs_minshellcore.msi MSIFASTINSTALL="7" VSEXTUI="1"
While this installs most necessary files, it doesn't account for all of them ... to keep things simple, I copied the rest of them from a working installation on another computer:
C:\ProgramData\Microsoft\HelpLibrary2
Essentially only contains a CatalogType.xml and some empty directories.
C:\Program Files (x86)\Microsoft Help Viewer\v2.2\CatalogInfo\VS11_en-us.cab
Moreover, it's necessary to provide the application with a valid ContentStore path by importing the following .reg file:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Help\v2.2\Catalogs\VisualStudio14]
"LocationPath"="%ProgramData%\\Microsoft\\HelpLibrary2\\Catalogs\\VisualStudio14\\"
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Help\v2.2\Catalogs\VisualStudio14\en-US]
"SeedFilePath"="C:\\Program Files (x86)\\Microsoft Help Viewer\\v2.2\\CatalogInfo\\VS11_en-us.cab"
"catalogName"="Visual Studio Documentation"
Finally, I created a new Application Shortcut and changed its Target: to read as follows:
"C:\Program Files (x86)\Microsoft Help Viewer\v2.2\HlpViewer.exe" /catalogName VisualStudio14 /launchingApp Microsoft,VisualStudio,14
Et voilĂ !, with that HlpViewer.exe should finally execute without any problems!
In MSDN to USB v2.5, you don't have to have any Visual Studio IDE installed:
https://stackoverflow.com/a/66595500/3268088
I know its old question. I just run into a problem involving Help Viewer.
my recovery steps are :
get sqlexress installer (if you haven't got one)
after extracting the files, check its folder and find for "help" folder
I got mine "SQLEXPRWT_x64_ENU\redist\VisualStudioShell\Help\x64"
run install.exe with administration priveleges (Run as Administrator)
all done.
I've downloaded and installed the official Windows Azure SDK v1.6 but for some reason csrun.exe (needed for running a package locally) is not in the bin directory with all the other exe files like cspack.exe etc. I have tried reinstalling and still did not get the executible. Is there anywhere to manually download this file, google wasn't any help...
It is installed by the new v1.6 SDK into the directory
C:\Program Files\Windows Azure Emulator\emulator
Just an update to this, looks like this is installed to the following location now.
C:\Program Files\Microsoft SDKs\Azure\Emulator
This question was prompted by my attempts to follow the post here http://blogs.msdn.com/b/brmeena/archive/2010/08/06/how-to-deploy-azure-roles-in-net-4-0-on-development-fabric.aspx about how to deploy to the dev fabric.
Andrew Patterson is correct in his answer above and I've marked it so, but I also found that I could run the tool from the Windows Azure Command Prompt even when I couldn't find the .exe (I still can't get Windows 7 search to behave)
Sharing here for my own recollection as well as to assist anyone else who might run into this issue.