Closed FischerRobert71 closed 4 years ago
I have the same issue. It worked fine until today, without me changing anything. Has this extension been updated recently?
same issue! and it was deployed OVER the previous release so now everything is royally screwed! please revert back ASAP! Please bear in mind that you are deploying these updates to live environments, not updating the version has now stopped our live processes and I can't wind back!
I am going to have to report this to have the extension removed from the marketplace, 8hrs with no response is unacceptable. this has impacted a massive project which can no longer go ahead.
Same issue, this has caused a major problem on our live deployment pipelines, please revert back to previous version.
Working on this now
V4.5.0 has been released. It restores the original V4, please validate and let me know if you still have issue.
That fixed the issue for me. Thanks!
Thank you for your patience! I will move the new feature set to V5 so it does not impact the current task configuration.
2020-07-02T05:04:47.8332633Z ##[section]Starting: Deploy Windows Service 2020-07-02T05:04:47.8336273Z ============================================================================== 2020-07-02T05:04:47.8336315Z Task : Windows Service Manager 2020-07-02T05:04:47.8336338Z Description : Deploys a Windows Service to an Agent or a Deployment Group Target using WinRM. 2020-07-02T05:04:47.8336359Z Version : 4.4.9 2020-07-02T05:04:47.8336403Z Author : MDSolutions 2020-07-02T05:04:47.8336424Z Help : More Information 2020-07-02T05:04:47.8336448Z ============================================================================== 2020-07-02T05:04:48.6088433Z ##[error]String can't be parsed. The StringContainingPath parameter should contain a valid Path ending with an '.exe' or '.dll'. Current string [C:\Program Files (x86)\DA-IT\Virkreg Services\3444\Da.Virkreg.Service.Virkreg.Service.exe] 2020-07-02T05:04:48.6296074Z ##[section]Finishing: Deploy Windows Service