LightSwitch app - Production deployment stops when I publish Staging deployment

Question

I have published my LightSwitch app to a production deployment many times without problems and today I added a staging deployment.  The problem is that when I publish to staging, the production deployment stops.  I can restart it and they are then both working.  I can swap VIPs and that works too.  (The screenshot below is after I have restarted production.)

But I obviously don't want my production deployment to go down when I publish to staging.  I asume that I have something configured wrong.    I would appreciate any ideas.

Thanks,

Mark

Answer 1

What do you mean that your production deployment "stops?" Does it actually go to the stopped state in the portal? Or does it stay "ready" but no longer work properly? How are you doing the deployment? Manually through the portal or with some tool?

Answer 2

Hi,

Does this situation occurs only once or all the times? Does Staging and Production role access some sharing resources?

If you can not make sure this issue is caused by your Azure subscription, try to contact our support to make sure your subscription is running good:

https://support.microsoft.com/oas/default.aspx?prid=14234&st=1&wfxredirect=1&sd=gn

Hope this helps.

---

Please mark the replies as answers if they help or unmark if not. If you have any feedback about my replies, please contact [e-mail] Microsoft One Code Framework

Answer 3

Hello Arvind, I too have the same problem. When I publish to staging bothe production and staging are shown in the portal as "stopping..."  staging starts automatically but and i have to manually restart production application.

I am publishing using lightswitch in Visual Studio 2010

Answer 4

Kiran:

I have opened a case with Azure support, but so far they apparently have no idea why it is happening.

Mark

Answer 5

Arwind:

Both my staging and production deployments share the same database.  Could this be an issue?

Mark

Answer 6

Steve:

I am using the LightSwitch publishing wizard in Visual Studio 2010.

When I publish to staging, my production deployment changes to "stopping...".  I can restart it, but obviously I don't want my production deployment to stop.

I have done this about 20 times and it is always the same.

Thanks,

Mark

Answer 7

Arwind:

Both my staging and production deployments share the same database.  Could this be an issue?

Mark

I don't think it's a good idea to do so. The testing LS app should use its own testing database to avoid affecting production database. Though I'm not sure why this would break the production slot it worth having a try to use a seperated testing DB for staging slot as this seems is the only entity shared by your staging/production LS apps at runtime.

It also worth a try to use another storage service for the staging slot. BTW, have you got any related diagnostic logs or LightSwitch traces?

---

Allen Chen [MSFT]
MSDN Community Support | Feedback to us
Get or Request Code Sample from Microsoft
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Answer 8

Hi Mark,

Any progress on this issue?

---

Allen Chen [MSFT]
MSDN Community Support | Feedback to us
Get or Request Code Sample from Microsoft
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Answer 9

Allen:

I submitted a case to the Azure team and they told me that it's a bug in LightSwitch 2011.  I have tried it in the new LightSwitch Beta (Visual Studio 11 Beta) and that seems to work.

For now, I just have to put up with restarting production every time... very annoying.

Thanks,

Mark