Azure devops web deploy weirdness
-
We have a web app. Asp.net running under .net 4.8. It runs on an internal dev and an internal production server. The dev server is windows 10 or a server version thereof, while prod is running 2008r2.
Deployment from VS works every time.
We have set up a CI build in azure devops, which on completion triggers a release, which deploys automatically to dev x and then manually should be triggered to deploy on prod.
The prod deploy is what fails. I installed powershell 5, ran the agent script, tagged the server, and it shows up right and is categorized right. The system knows where to deploy just fine.
When the deploy happens, msdeploy.exe on the prod machine fails, because it cannot initialize types within Microsoft.Data.Tools.Schema.Sql. This assembly does not seem to exist on my dev box or the dev server, and the project does not contain a database, so it must be trying to access azure devops databases or something.
I've tried installing sql server data tools, but I just get the infinitely useful error, Incorrect Function.
Does anyone have any ideas?
-
@Magus what happens when you manually create a production build and try to deploy it manually? Can you pull the package that was produced for the prod deployment and check what the configs say?
-
Why are Production and Dev on very different versions?
-
This answer may also be helpful: https://sitecore.stackexchange.com/a/15501
-
@loopback0 said in Azure devops web deploy weirdness:
Why are Production and Dev on very different versions?
Because it makes deployment more exciting.
-
@loopback0 because IT didn't want to give me a dev environment with old stuff on it. I'm hoping we can migrate prod eventually.
-
@Magus said in Azure devops web deploy weirdness:
I'm hoping we can migrate prod eventually.
Is your company paying for the extended security updates after January, or are you rolling the dice?
-
@Unperverted-Vixen the server is internal anyway, so not at that much of a risk, but I do hope someone panics and makes it be upgraded.
-
@Magus said in Azure devops web deploy weirdness:
the server is internal anyway, so not at that much of a risk
Famous last words.
-
@Magus said in Azure devops web deploy weirdness:
@Unperverted-Vixen the server is internal anyway, so not at that much of a risk, but I do hope someone panics and makes it be upgraded.
Reminds me of when I told a major Telco that their entire "secure net" had been put up on the web with a direct connection, with no firewall at all on the NIC and that the internal net was dead, and things only worked because all the internal data was being transmitted in the clear over the internet and that was why the connections weren't as stable as they should be. Fun times in 3rd line support.
