WordPress – Azure – Remote Desktop, almost.

As I mentioned in my last post, I got WordPress up and running in Azure using the Windows Azure Companion. I used one of the prebuilt packages, it was drop dead simple. I then proceeded to play around with Azure Remote Desktop access following Maarten Balliauw instructions which was simple enough. It was kinda fun to see Azure from the inside 😉

Naturally, the next step was to remote desktop into my WordPress instance. I added the required certificate to my instance, but the “connect” button on the dashboard never lit up. I reach out to Maarten via Twitter and he got right back to me. Turns out that the packages were created against an older version (1.2) of the SDK and Remote Desktop requires 1.3. So, after building the Companion from source (I had to fix some broken references to the WindowsAzure.StorageClient assembly), I tried to deploy. I thought I was in business as the solution began to deploy to a brand new deployment, but then I got hit with the following error:


Error Creating New Deployment Error creating deployment for hosted service ‘MyProject’ Invalid number of endpoints for role WorkerRole; maximum number permitted is 5. Invalid number of endpoints for role WorkerRole; maximum number permitted is 5. Dr. Watson Diagnostic ID: 3cd580025a79480faa5eb07f8f53c9d4 Subscription ID: 6eed2056-87ae-481e-87dc-cc2856447040 Time started: 12/7/2010 9:33:06 PM UTC
Time completed: 12/7/2010 9:33:10 PM UTC Duration: 0:00:04.2258416


Meanwhile, my .csdef file looks like this

My .csdef file looks like this:

<Endpoints> <!– Make sure that this HttpIn is same as that of HttpIn InputEndpoint in ServiceConfiguration.cscfg –>
<InputEndpoint name=”HttpIn” protocol=”http” port=”80″ />
<InputEndpoint name=”WindowsAzureCompanionHttpIn” protocol=”http” port=”8080″ /> <InternalEndpoint name=”VMManagerServicePort” protocol=”http” /> <InternalEndpoint name=”MySQLBasedDBPort” protocol=”tcp” /> </Endpoints>


I posted my issue up here


Satish got back to me and now I am in the process of contacting Azure Dev Support – who will hopefully be reading this post shortly.

I’ll get back to everyone – updating this post – once I hear more.


Looking forward to next steps.


UPDATE: 45 minutes later, this is the response I received from Frontline Azure Support


Issue Definition: We understand that you are facing issues while creating endpoints when deploying a solution and would like us to investigate on the issue. Scope Agreement: To provide you with the cause of the issue and to help you resolve the issue that you have.

We sincerely apologize for the inconvenience caused to you and would like to inform you that, we have a limitation on the number of endpoints per worker role and the web role. We can create only two endpoints for the web role (HTTP or HTTPS) and Worker role can have only a maximum of 5 endpoints/role(HTTP, HTTPS, or TCP). Please see below for more information on limitation on endpoints of azure web role or a worker role:


Hope the above information is useful to you. Please accept our apologies for the inconvenience caused. Let us know if you need any further assistance and we shall be glad to assist you.

Looking forward to your response. Thanks  & Regards,


I now need to run an additional test – if I turn OFF RDP, then I believe the deployment will be successful and the explanation provided will be insufficient. More news as it develops.


Update # 2 – Allowing RDP seems to be using up my Endpoints!

By that  I mean that I created the package without enabling RDP and the deployment went fine and Windows Azure Companion works fine.

I them packaged the exact same built, this time enabling RDP and when I deployed I once again got the message about Maximum number of endpoints. So, what does this mean? Does enabling RDP use up your available endpoints??

More info when I get it.

Update #3 – I have been escalated

I got a quick reply from Frontline support informing me that my issue was being escalated – mostly because I couldn’t provide a Deployment ID because my package won’t deploy ;o Here was the response:

Thank you for the quick response. We would like to inform you that in your case, our cloud integration team will be able to work with you and resolve the issue at a quicker pace. We have escalated your issue to our cloud integration team and one of our engineers will contact you to work with you to resolve the issue.

Meanwhile, if you have any further questions or concerns, please feel free to contact us and we shall be glad to assist you.

I am looking forward to working with the cloud integration team! More news as I get it.

Leave a Reply

Your email address will not be published. Required fields are marked *