The 'DefaultConnection-Web.config Connection String' argument cannot be null or empty

Question

When I deploy my project with "Publish as Azure WebJob" using Visual Studio, I get the error in the title.

Hakan Fıstık · Accepted Answer · 2017-12-16 14:20:08Z

72

Fixed by removing the following markup from the .pubxml file. You must exit/restart VS after removing the markup (or VS will add it back in).

<ItemGroup>
  <MSDeployParameterValue Include="$(DeployParameterPrefix)DefaultConnection-Web.config Connection String" />
</ItemGroup>

edited Dec 16, 2017 at 14:20

Hakan Fıstık

19.9k16 gold badges124 silver badges152 bronze badges

answered Mar 11, 2015 at 20:25

RickAndMSFT

23.4k9 gold badges65 silver badges79 bronze badges

Sign up to request clarification or add additional context in comments.

6 Comments

James Reategui Over a year ago

does this change depending on the name of your connection string in App.Config?

Noah Stahl Over a year ago

These were readded for me after restarting. This worked in my case: stackoverflow.com/questions/28391460/…

hvaughan3 Over a year ago

Thanks for the answer. Made me realize I should just delete the publishing profile and create a new one.

CindyH Over a year ago

Using VS2015, update 2. It was the "restart Visual Studio" part that I was missing. THANK YOU. Now on to the next issue...

Mostafa Over a year ago

This doesn't work in Update 3 in VS 2015, please see my answer above by changing an attribute in pubxml file.

|

Hakan Fıstık · Accepted Answer · 2021-10-24 11:38:37Z

34

Reason of the problem is one of the followings:

Change the name of the connection string in the web.config.
Add a new connection string in the web.config

Solution

Select the website project, right-click on it, and click publish.

Press the settings link and from the pop-up window select the 'Settings' Tab
Uncheck the use this connection string at runtime from all your connection strings.

Click the Save button to close the window. (No need to restart Visual Studio)
Try to publish the website again, and it should publish without a problem.
You can reconfigure the settings as it was previously, the unchecking just triggers VS to regenerate the .pubxml file, So you are not forced to change your settings at all.

NOTE
I am using VS 2017 (and according to the comments this also work in Visual Studio 2013)

Just for Note
After I did the previous steps, I noticed that the .pubxml file changed automatically. here is the difference which has been made (automatically without any interference from me)

So I think this is a better way because it is easier for the developer and also it let the visual studio to solve its problems himself, without forcing it into a specific thing.

edited Oct 24, 2021 at 11:38

answered Dec 16, 2017 at 14:35

Hakan Fıstık

19.9k16 gold badges124 silver badges152 bronze badges

6 Comments

JohnWrensby Over a year ago

This works for me. VS2013. Just uncheck the Use Connection String at Runtime box in the Publish dialog.

stuzor Over a year ago

When I untick that option and press 'save', visual studio ignores it. When I open the settings again - the option is still checked. I can't get it to respect my preference. I can't have it run migrations without it injecting the connection string. Therefore I have to have one publish profile with the connection string to run migrations (injects into web.config), then a second with no connection string (no migrations) which then clears the web.config of any connection strings. Seems like a bug in VS2017:15.6.7?? or maybe AzureAppSericeTools build 15.0.40215.0 - very annoying!

Jay Over a year ago

Followed the steps and then restarted Visual Studio. After restart error was gone

Josh Noe Over a year ago

This no longer works in VS 2019. The checkboxes are there but they're ignored and MS has closed bug tickets reporting this.

Hakan Fıstık Over a year ago

@JoshNoe nice note, but this answer would still be helpful for people using VS 2017 and before. It would be helpful if you provide link to the bug, I will update my answer with according to your note.

|

Norbert Kardos · Accepted Answer · 2015-03-17 09:58:09Z

11

Create a Parameters.xml file in the Project root with the following content:

<?xml version="1.0" encoding="utf-8" ?>
<parameters>
  <parameter name="DefaultConnection-Web.config Connection String"
      description="DefaultConnection"
      defaultValue="Server=tcp:x.database.windows.net,1433;Database=x_db;User ID=x@y;Password=z;Trusted_Connection=False;etc." tags="" />
</parameters>

All the other missing config elements can be added here as well.

edited Mar 17, 2015 at 9:58

answered Mar 17, 2015 at 9:44

Norbert Kardos

1116 bronze badges

5 Comments

James Reategui Over a year ago

this worked for me, although it didn't actually set the connection string as i had hoped.

Norbert Kardos Over a year ago

I guess it will come from the App.config, it is just a must have to workaround the issue.

phillipwei Over a year ago

Black magic! So Deploy as WebJob just reads from any XML file in the Project root?

Norbert Kardos Over a year ago

No, not from any XML file. From the Parameters.xml file.

connectedsoftware Over a year ago

This works, but I don't like it. My first deploy worked perfectly only my second deploy complained about missing connection strings.

Mostafa · Accepted Answer · 2016-11-24 02:35:08Z

I have Visual Studio 2015 Update 3 and i was facing the same issue. The solution i found that is working for me is the following:

1) Open *.pubxml file under properties -> publish profiles.

2) Look for the Path attribute under PublishDatabaseSettings section:

<PublishDatabaseSettings>
      <Objects xmlns="">
        <ObjectGroup Name="eRecall.ETL.Models.erecallContext" Order="1" Enabled="False">
          <Destination Path="" />
          <Object Type="DbCodeFirst">
            <Source Path="DBContext" DbContext="eRecall.ETL.Models.erecallContext, eRecall.ETL" />
          </Object>
        </ObjectGroup>
      </Objects>
    </PublishDatabaseSettings>

3) Set Path attribute value to the following:

<PublishDatabaseSettings>
      <Objects xmlns="">
        <ObjectGroup Name="eRecall.ETL.Models.erecallContext" Order="1" Enabled="False">
          <Destination Path="{deployment connection string}" />
          <Object Type="DbCodeFirst">
            <Source Path="DBContext" DbContext="eRecall.ETL.Models.erecallContext, eRecall.ETL" />
          </Object>
        </ObjectGroup>
      </Objects>
    </PublishDatabaseSettings>

4) Delete the existing webjob deployment in Azure Job Collection Scheduler.

5) Re-Deploy the webjob, Re-run the webjob from the scheduler and it starts working with no issues!

Hope this helps.

Nomad77 · Accepted Answer · 2025-06-13 09:18:46Z

0

Delete the publishing profile and recreate it.

answered Jun 13 at 9:18

Nomad77

1253 bronze badges

Collectives™ on Stack Overflow

The 'DefaultConnection-Web.config Connection String' argument cannot be null or empty

5 Answers 5

6 Comments

6 Comments

5 Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

5 Answers 5

6 Comments

6 Comments

5 Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related