9

I created Azure Worker Role project in Visual Studio 2015. When i start this project locally (via emulator) it works good. But when i try to publish this worker role to Azure Cloud i receive these messages in Microsoft Azure Activity Log:

2:33:13 - Warning: There are package validation warnings.

2:33:13 - Sequence contains no elements

Publish status in Microsoft Azure Activity Log is Failed.

How to fix the problem and publish to azure? Why this problem happens?

Community
  • 1
  • 1
Maxim Kitsenko
  • 2,042
  • 1
  • 20
  • 43
  • Similar to this question https://stackoverflow.com/questions/32480411/erro-on-ninject-sequence-contains-no-elements However you really need to add more details to your question as it is hard to work it out with the little information you have given – Dijkgraaf Oct 04 '16 at 02:59
  • @Dijkgraaf Thanks but looks like author speak about WebRole in your link, my question is about WorkerRole. - Solution provided in thie link doesn't work since there is no such option "Remove additional files at destination"at all. I think i provide enough info. What details you suggest to add? – Maxim Kitsenko Oct 04 '16 at 04:05
  • Look at all the files in your solution that you are publishing and see if you can see anything amiss in them. If you cannot see anything at least give us the structure of your solution (what files are included) – Dijkgraaf Oct 04 '16 at 09:52
  • 1
    Restating the Windows resolve that issue on my machine. – Vladimir Feb 09 '17 at 11:48
  • 4
    @Vladimir thanks for comment (+1). After some steps: cleaning VS solution, restarting VS, restarting PC (my be some other steps) the problem was gone. But i don't know exactly what was the root o the problem and how to solve the problem – Maxim Kitsenko Feb 09 '17 at 12:17
  • Probably has something to do with the similar issue https://github.com/Microsoft/PTVS/issues/896, more like a minor bug within the Azure SDK. – Vladimir Feb 09 '17 at 12:35
  • 3
    For me, running Visual Studio as administrator resolved this issue. – user551113 Jul 11 '17 at 08:49
  • After have the same problem - in order to remove that you should restart PC and run VS as Admin ) that would solve the problem for good – Vladimir Mar 15 '18 at 08:20

0 Answers0