No matching appSetting, applicationSetting, nor connectionString names were found in:

ajaybre · 14 June 2020 12:56

Hi Octopus Help,

we are using “Deploy a Package” step template for our code deployments. The same step template we have been using for around 2000 steps in multiple octopus deploy jobs. The only enabled feature for this step template is “custom installation Directory”, no configuration variables or configuration transforms. But we are seeing errors “No matching appSetting, applicationSetting, nor connectionString names were found in:” for some deployments, at the same time other deploy steps in the same project were successful without any issue. I have come across this error couple of times so far, if I create new deploy package step and use for same deployment it is working.

Can you please help us with why this issue is happening even though we are note enabled configuration features and that too only now and then. we using Octopus server version v2019.12.4 LTS. In Feb 2020, we upgraded version from V 2019.9.12 to V 2019.12.4. Before upgrade we never saw this issue before, not sure if it version related or something else.

Error logs:
08:13:43 Verbose | 08:13:44 Info | 08:13:44 Info | 08:13:44 Info | 08:13:44 Info | 08:13:44 Info | 08:13:44 Info | 08:13:44 Info | 08:13:44 Info | 08:13:44 Info | 08:13:44 Info | 08:13:45 Info | 08:13:45 Error | 08:13:45 Error | 08:13:45 Error | 08:13:45 Error | 08:13:45 Error | 08:13:45 Error | 08:13:45 Error | 08:13:45 Error | 08:13:45 Error | 08:13:45 Error | 08:13:45 Error | 08:13:45 Error | 08:13:45 Error | 08:13:45 Error | 08:13:45 Error | 08:13:45 Verbose | 08:13:45 Verbose |
08:13:45 Verbose |
08:13:45 Verbose |
08:13:46 Error | 08:13:46 Error | 08:13:46 Error | 08:13:46 Error | 08:13:46 Error | 08:13:46 Error | 08:13:46 Error | 08:13:46 Error | 08:13:46 Error | 08:13:46 Error | 08:13:46 Error | 08:13:46 Error | 08:13:46 Error | 08:13:46 Error | 08:13:46 Error | 08:13:46 Error | 08:13:46 Verbose | 08:13:46 Verbose | 08:13:46 Fatal | 08:13:46 Fatal | Looking for appSettings, applicationSettings, and connectionStrings in any .config files
No matching appSetting, applicationSetting, nor connectionString names were found in: C:\Octopus\Applications\Tenant1\Prod\DataStructure\25.5.456\deploy.config
No matching appSetting, applicationSetting, nor connectionString names were found in: C:\Octopus\Applications\Tenant1\Prod\DataStructure\25.5.456\Content\ConfigFiles\Debug.App.config
No matching appSetting, applicationSetting, nor connectionString names were found in: C:\Octopus\Applications\Tenant1\Prod\DataStructure\25.5.456\Content\ConfigFiles\Dev.App.config
No matching appSetting, applicationSetting, nor connectionString names were found in: C:\Octopus\Applications\Tenant1\Prod\DataStructure\25.5.456\Content\ConfigFiles\MultiClientTesting.App.config
No matching appSetting, applicationSetting, nor connectionString names were found in: C:\Octopus\Applications\Tenant1\Prod\DataStructure\25.5.456\Content\ConfigFiles\Testing.App.config
No matching appSetting, applicationSetting, nor connectionString names were found in: C:\Octopus\Applications\Tenant1\Prod\DataStructure\25.5.456\Content\ConfigFiles\AD-SC-WY\Release.App.config
No matching appSetting, applicationSetting, nor connectionString names were found in: C:\Octopus\Applications\Tenant1\Prod\DataStructure\25.5.456\Content\ConfigFiles\AR-NE-LA\Release.App.config
No matching appSetting, applicationSetting, nor connectionString names were found in: C:\Octopus\Applications\Tenant1\Prod\DataStructure\25.5.456\Content\ConfigFiles\Archive\CompletedInvalidated\Release.App.config
No matching appSetting, applicationSetting, nor connectionString names were found in: C:\Octopus\Applications\Tenant1\Prod\DataStructure\25.5.456\Content\ConfigFiles\Archive\CompletedInvalidated\Testing.App.config
No matching appSetting, applicationSetting, nor connectionString names were found in: C:\Octopus\Applications\Tenant1\Prod\DataStructure\25.5.456\Content\ConfigFiles\Archive\ELPAManual\Release.App.config
No matching appSetting, applicationSetting, nor connectionString names were found in: C:\Octopus\Applications\Tenant1\Prod\DataStructure\25.5.456\Content\ConfigFiles\Archive\ELPAManual\Testing.App.config
Exception while replacing configuration-variables in: C:\Octopus\Applications\Tenant1\Prod\DataStructure\25.5.456\Content\ConfigFiles\Archive\General\OldProduction.App.config
System.Xml.XmlException: ‘System.Data.SqlClient’ is an unexpected token. Expecting white space. Line 50, position 18.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ParseAttributes()
at System.Xml.XmlTextReaderImpl.ParseElement()
at System.Xml.XmlTextReaderImpl.ParseElementContent()
at System.Xml.Linq.XContainer.ReadContentFrom(XmlReader r)
at System.Xml.Linq.XContainer.ReadContentFrom(XmlReader r, LoadOptions o)
at System.Xml.Linq.XDocument.Load(XmlReader reader, LoadOptions options)
at Calamari.Integration.ConfigurationVariables.ConfigurationVariablesReplacer.ReadXmlDocument(String configurationFilePath)
at Calamari.Integration.ConfigurationVariables.ConfigurationVariablesReplacer.ModifyConfigurationFile(String configurationFilePath, VariableDictionary variables)
at Calamari.Deployment.Conventions.ConfigurationVariablesConvention.Install(RunningDeployment deployment)
at Calamari.Deployment.ConventionProcessor.RunInstallConventions()
at Calamari.Deployment.ConventionProcessor.RunConventions()
Running rollback conventions…
Adding journal entry:
‘System.Data.SqlClient’ is an unexpected token. Expecting white space. Line 50, position 18.
System.Xml.XmlException
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ParseAttributes()
at System.Xml.XmlTextReaderImpl.ParseElement()
at System.Xml.XmlTextReaderImpl.ParseElementContent()
at System.Xml.Linq.XContainer.ReadContentFrom(XmlReader r)
at System.Xml.Linq.XContainer.ReadContentFrom(XmlReader r, LoadOptions o)
at System.Xml.Linq.XDocument.Load(XmlReader reader, LoadOptions options)
at Calamari.Integration.ConfigurationVariables.ConfigurationVariablesReplacer.ReadXmlDocument(String configurationFilePath)
at Calamari.Integration.ConfigurationVariables.ConfigurationVariablesReplacer.ModifyConfigurationFile(String configurationFilePath, VariableDictionary variables)
at Calamari.Deployment.Conventions.ConfigurationVariablesConvention.Install(RunningDeployment deployment)
at Calamari.Deployment.ConventionProcessor.RunInstallConventions()
at Calamari.Deployment.ConventionProcessor.RunConventions()
at Calamari.Commands.DeployPackageCommand.Execute(String[] commandLineArguments)
at Calamari.Program.Execute(String[] args)
Updating manifest with output variables
Updating manifest with action evaluated variables
The remote script failed with exit code 100
The action AD_SC_WY Deployment on XXX.XXX.XXX.XX failed

dane.falvo · 19 June 2020 03:13

Hi Ajaybre,

Thanks for reaching out and I’m really sorry that you’ve hit this issue.

I have had a look through our issues and fixes since 2019.12.4 however it doesn’t look like there is anything discussing the issue that your seeing at the moment.

You mention: “if I create new deploy package step and use for same deployment it is working”

Do you see this issue after creating a new release for a project where the step template is returning that error? (as opposed to creating a new deploy package step)

Would you be able to provide me with the log files with the variables evaluated please?
You will need to follow the steps listed here:

Thank you for your time and I look forward to hearing back from you.

Regards,

Dane

system · 20 July 2020 06:45

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.