Azure SFTP Connector, Unable to edit App Settings values once created - powershell

I created an SFTP Connector in Azure Portal , once configured 'Root Folder' and 'IP address' of the ftp server I was unable to edit its values in the App Settings. The Save Icon in top bar is disabled in the Applications Settings Blade.
However I can change it via PowerShell script but when I try to edit key value pairs of App Settings in the Applications Settings Blade, The Save button remains disabled even If I enter new Key/Value pair in the App Settings or delete any of them. I also try reloading the portal but in vain.
Any Ideas?

With the latest February preview version of release there is a new concept called "connection" entity, which should be configured before using the new connectors. Basically appsettings are exposed through connections and are being used by the connectors during runtime, hence I would suggest try checking all the connection properties are configured correctly.
Erik Oppedijk It will be great if you can provide some more info of the scenario you are trying out and where is it failing.

Related

Mirth NextGen Connect desktop upper bar menu Server Manger links to wrong install of the Admin UI?

Having problem where the Mirth Connect Server Manager UI points to an earlier, non-working install version of the Admin interface.
Installed Mirth once and had to reinstall because the original install had set the password requirements to something that the default admin account could not pass. When I did this, the installer said that it detected that Mirth was already installed and asked if I wanted to re-install and I said yes. However, the Admin UI that the Mirth Connect Server Manager windows that remains in the upper menu bar of my desktop still appears to be using the old install with the password issue.
The Mirth Connect Server Manager icon in the upper menu bar takes me to wrong setup. Can't log in from the Admin UI that this bring up (told can't authenticate or connect (which was the problem I had with the earlier install)).
Need to use the Program from here
and make sure that I chose the right one, then I am able to use the default admin account to log in and proceed as normal.
Anyone know how to fix this (eg. somewhere in the underlying files where I can change this)? Anything else I should check that may be messed up due to this problem that I may not be noticing? I am on Ubuntu 18.04.4LTS MATE.
In the installation folder\conf\mirth.properties file, change the HTTP and HTTPS ports to values different from the prior one. Get to your browser type localaddress:new_http port then click on the icon -launch Mirth Connect administrator. Clicking the saved shortcut will launch an admin launcher which will allow you to edit and save the functional instance.

Is there a way to automatically map existing web.config settings if I'm deploying an existing Web App to Azure?

I have an existing ASP.Net MVC app that's currently hosted locally in IIS and I'm trying to deploy it to an Azure App Service.
I've seen several posts about setting the Applications Settings and Connection Strings manually in the Application Settings blade.
The problem with that is that I have a ton of App settings in my web.config file, along with various other config sections.
Is there a way to automatically map those to Azure Application Settings when I deploy my app?
Your best bet is to write a simple transform tool that changes those web.config based settings into the equivalent ARM template that sets those settings and connection strings (probably < 20 lines of code).
Note that there is no Azure equivalent of sections other than App Settings and Connection Strings.

Visual Studio Navision 2018 error

I am trying to create table and page Navision through visual studio code. but I am finding an error in this process. Can anyone help me?
Error: Could not open the specified startup page. Please check that the server configuration key PublicWebBaseUrl has been properly set.
I'm using Navision 2018.
I had the same error. You need to set the PublicWebBaseUrl property. You can do this in two places:
Edit the config file of the nav service you are trying to connect to
In the server administrator app the same property is under Client
Services tab called "Web Client Base Url".
Here it is in the Server Administration
You have to do the following 3 Steps:
Set the PublicWebBaseUrl property. Edit the config file of your service or use the Administration-App (there you set the "Web Client Base Url" under Client Services). You set it to HTTP://<Servername>:<Port>/<Instancename> (depending on your configuration, but Port should be 8080).
Restart the Service (obviously)
Restart Visual Studio Code. Yes, that is a not very intuitive, but a really crucial step.
After that, you should be able to publish to the Server without problems.

How to deploy application in bluemix from eclipse

When I try to deploy application to bluemix, I get following error
Error: Host taken error. A different mapped application URL is required before pushing or starting the application.
Though If I download a default application created bluemix, download the same and import in eclipse and then redeploying application works fine. I am sure I must be missing some key steps, wondering if someone can point me to the link that has those details or missing step.
Use the screenshot below to ensure that your mapped URL is correct:
according to the posted error you just set a wrong URL for your app's mapping URL: just check on Eclipse Server view, you should have Bluemix Server item, double click on it to open, it should show your server configuration, go to Applications and Services tab, here you could find you app listed; now double click on it, it should open you app properties, check on Mapper URL property under General configuration tab.
Otherwise could you provide some details more about the configuration used on Bluemix Eclipse plugin?
As per my understanding..
application name is globle. what ever application name using that already used by someone.
try to change Name.
ex:- cocacola.mybluemix.net change to cocacola429.mybluemix.net.
it worked for me.

Changes in Windows Azure web role via remote desktop are not propagating

I have deployed a web role on Windows Azure. It runs on one instance only. I set up the remote desktop to access it.
At the moment I need to change only two lines in a JavaScript file in the website.
I connected to the instance then ...
navigated to the E:\approot\Scripts
opened the target file, edited it
Changes didn't propagate. (I download the old content)
Then I tried to
Stop the IIS in web role
Edit the file
Start the IIS again
Changes didn't propagate (When I open the file in the RD I see my new content, but when open via http I see the old content)
Then I tried
Opened RD
Navigated to the file and edited it
Rebooted the instance via Windows Azure control panel
Again connected to RD
I still see the old content in the remote server
My question is what I should do in order to change only one file without redeploying the whole package?
My guess is you're editing the wrong location. Look in e:\sitesroot\0 (or something like that). When in doubt, open the IIS config UI and find out exactly where the website content lives.
EDIT: But as Dennis pointed out, changes you make this way don't persist, so use this only for testing.
I have had this work before, but there problems with this type of change. If something happened to the hardware you are running on and your instance needed to be 'healed', it will only be created from the package you uploaded. Azure does not know about the file edits you have made via RD.
There is not a way to make a single file change in side of a cloud service right now, but with the new Azure web site functionality it is just a git push or tfs push away.
You should be able to do a web deploy by right clicking on your website project (not the azure role project). This will only deploy files which have changed to the active instance. I believe there is a setting in your azure deployment profile (next to the remote desktop one) to enable this.
As noted in other answers these changes are lost should azure need to recreate or provision additional instances. Still, it is a great way to make incremental changes for development.