SQL Server Expired???

Editorial architecture visual showing SQL Server queues, database transaction boundaries, and integration message flow

So I am working on a vm that was built from Azure gallery BizTalk 2013 R2 developer for 2 weeks, suddenly got this message today

image

Microsoft, are you kidding me?? now I have to download the software from MSDN, re-configure the BizTalk and redeploy my interfaces.. time well spent!

Why do you do this Microsoft!!

Next step

Need this reviewed in a real system?

Use the article as a starting point, then bring the actual decision, constraints, and failure paths into an architecture review.

Join the discussion

Sign in to comment. Signed-in comments appear immediately.

5 responses to “SQL Server Expired???”

  1. Stephen Cairns

    Did you ever here if Microsoft admitted this as being a problem ans fixed it?

    1. No I don’t know that, another issue is server name need to change in database

  2. I have the same issue… not funny.
    Especially since I understand that creating a new VM will not fix this?

    1. Trick is you can download the media, update it to a enterprise version without going through the pain for reinstall SQL

      1. I must say I’m not sure what you mean… could you elaborate a bit? Tnx!

Join the discussion