I have an azure website running as an App Service which I publish to Azure from Visual Studio. I have multiple webjobs which are all linked to the main web project.
When I add a new webjob it fails because the wrong RUN COMMAND is attached to it. For instance, the webjob QuarterHrsWebJob fails because it has somehow been set up with a Run command of "doctap.exe". doctap.exe is the exe belonging to a different webjob (called doctap) - but somehow it has been assigned to QuarterHrsWebJob as well.
See screenshot showing "Run command: doctap.exe" for the QueryHrsWebJob.
Many thanks for your help.
Do you have a project reference to the project containing doctab.exe from the QueryHrsWebJob? I was able to reproduce the problem you are seeing by creating a similar reference between two Web Jobs.
If you do not have a reference like this, could you please share the project file for both affected Web Jobs and your webjob-publish-settings.json files?
Related
We recently stood up a new Azure account and are in the process of developing a new application to be deployed to it as a web app. While we are able to deploy to our staging slot from Visual Studio 2015, when attempting to deploy an automated build from Visual Studio Team Services (hosted by Microsoft) we are getting the following error:
Get-AzureWebSite -Name $APPLICATION -ErrorAction SilentlyContinue -ErrorVariable azureWebSiteError -Slot staging
System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.WindowsAzure.Commands.Websites.GetAzureWebsiteCommand.Do(Action call) in d:\workspace\powershell-publish\src\ServiceManagement\Services\Commands\Websites\GetAzureWebSite.cs:line 138
at Microsoft.WindowsAzure.Commands.Utilities.Common.AzureSMCmdlet.ProcessRecord() in d:\workspace\powershell-publish\src\ServiceManagement\Common\Commands.ServiceManagement.Common\AzureSMCmdlet.cs:line 174
New-AzureWebSite -Name $APPLICATION -Location North Central US -Slot staging
Conflict: Website with given name $APPLICATION already exists.
Publish-AzureWebsiteProject -Name "$APPLICATION" -Package "C:\a\1\a\$APPLICATION.zip" -Slot "staging" -ErrorVariable publishAzureWebsiteError
The website $APPLICATION was not found. Please specify a valid website name.
Cannot get website, deployment status is not updated
This is a fairly significant issue since it is preventing us from using continuous deployment at this time. Are there any work around or configuration settings that we should look at to fix this?
There is a known issue that causes publishing from VSTS to fail if the Web App has VS 2015 Debugging enabled. Can you check whether it is the case for you, and try again after turning off debugging in the Azure portal?
That issue will be fixed soon, so treat this as a temporary workaround.
This was eventually traced back to two problems.
The first problem was that we needed to load up a different management certificate since the one we were using was defaulting to a different account. This goes back to the issue of having one account associated with more than one subscription. At the time of this writing, there doesn't appear to be a way of specifying which subscription to download.
The second problem appears to have been associated with the known bug mentioned by David Ebbo in their answer.
A couple things you can try:
Since you mentioned you have 2 subscriptions, make sure that script you have above is running against the correct subscription, if it's not, it would give the exact error you're seeing. Put a:
Get-AzureSubscription -Current
command at the top of your script and see if that's what you'd expect.
VSTS has a build task for deploying to a web app, can you deploy the package using that task?
I have deployed a node.js app in Bluemix using cf push. I have removed the start: entry from manifest.yml. In Bluemix I have set the environment variable BLUEMIX_APP_MGMT_ENABLEto devconsole+shell+inspector. This restages the app.
But when I open the App Manager by adding /bluemix-debug/manage/ I get a 404 error.
When I start Live Edit on the same project from DevOps Services I can open the App Manager. But I don't see what is different, it also seems to set the environment variable only.
What am I missing?
The Live Edit tool will automatically add 256MB to your application to facilitate execution of the additional features, which is likely why it is working with Live Edit.
Manually enabling the feature, however, will not automatically bump up the memory. Can you try adding some more memory to your application and restaging?
There are a couple of other limitations; refer to the Restrictions section on the App Management docs.
EDIT: Found issue in comments below. If command: node app.js is in manifest.yml, or if you are using -c with the CF CLI, it overrides the buildpack's ability to start the development utilities in App Mgmt. This happens even if you have the start command correctly specified in package.json or Procfile. To fix this, remove the manifest.yml entry, delete the application, and restage the application.
I need to create installer package for WCF(service) class library,which i created in VS2012 with .net framework 4.5.
2.I try to install the service manually using VS2012 command prompt with the following link, http://www.youtube.com/watch?v=vTPCWrZedKI
Actually it put entry in Window services, when i try to start the service manually i am getting an error like "The service on local computer started and then stopped,Some services stop automatically if they are not in use by other services or programs.
I tried to fix those errors by changing to local system account and clearing the evenlog,
but nothing works fine for me.
I tried it using Advance installer by providing the dll file in Services tab,but it fails to start the service getting an error like "Verify that you have sufficient privileges to start the stystem sevices".
Please tell me how can i proceed further?
I don't need to use third party softwares like wix for creating installer package.
*Is there any way to achieve this task. If so please guide me and give me a sample application to achieve this task.*
I am spending more than 10 days for this task..
Awaiting for your repliessss!!!
Regards,
Lokesh.J
I’m trying to create a set-up project for a windows service. I’ve followed this tutorial and many others like it but, after installing my service, I still can’t see the service. I’ve added the primary output of the service to the application directory and created a custom action to include this output on Install, Commit, Rollback and Uninstall.
It claims that it installs correctly.
Should this work? Is there anything else that I can try to get this to install?
Did you create an installer for your service? It is separate from a Setup Project.
See: http://msdn.microsoft.com/en-us/library/system.serviceprocess.serviceinstaller.aspx
You can create an Installer by right-clicking on your service's Design window and selecting Add Installer.
In my case, adding the installer was a first step as described by dhirschl's answer. I then needed to add custom actions to the setup project.
Right click the setup project/view/custom actions
then add the primary output to every folder there.
Source
I'm building an application which will be run on Azure. My Visual Studio solution contains multiple Azure role projects. When debugging locally, I use the Azure compute emulator.
To start debugging, I follow these steps:
I right-click on my Azure project and click Set as start up project.
I press F5 to start the debugger.
What happens now is that the emulator/vs2010 launches both my web roles and worker roles, even if I'm only interested in debugging a single worker role at the moment. Often when writing some background-processing code in my worker role, I'm interested to step through that code without starting the web role, launch Internet Explorer and so on as well.
Is there a convinient way to make the debugger only launch one of the role instances and not all of them?
I'm thinking of creating a separate project in my solution of type Console Application, where I load the same assemblies as in my worker role and execute the same code.
The emulator (similar to Azure itself) works just on the concept of a "Cloud Service". So when you launch w/ debug, its going to launch whatever is defined in your Cloud Service (.ccproj) project. This mimics Azure 100% which is why it occur, but I can definitely see where your scenario would be helpful.
Few options, based on your needs.
If you need to test azure-specifics (aka it has to run in the emulator)
Create a second solution file, create a new Cloud service in here, add your project. I like this option because the projects/roles themselves remain untouched.
What Stuart suggested before me, create a second Cloud Project, set as startup, run that.
Similar to above, create a second project, but don't worry about startup. You can right click on any project, go to Debug and select start w/ debugging and achieve what F5 does without binding F5 to this solution
If you dont need to test azure-specifics (ie you are just testing the role)
Right click on the role's project, Debug, Start with Debugging This way the whole solution remains intact and you are just testing the logic
I think you can do this by:
create a new Azure Cloud Project within your solution
add just the one worker role to that cloud project
set that cloud project as your startup project
This will single out just the worker you are interested in
An easier solution would be to open the ServiceConfiguration.cscfg file, and set the "Instances > Count" property to "0", for all the roles that you don't want running (this only works in the compute-emulator, and NOT on the azure cloud).
That way, you keep your solution intact and your configurations safe, while just omitting them from the compute-emulator during run-time.