I am attempting to set up an Azure VM to run an ElevateDB server.  If anyone has been successful in this painful endeavour I would appreciate knowing how you managed it.  I have the server running just fine on the VM and accessible via EDBManager.  I have set up incoming and outgoing endpoints in the NSG and have opened the edbsrvr application and 12010 port in the VM firewalls.  ShieldsUP running from the VM confirms that I have the 12010 port open (in "Stealth" mode.

I'm still unable to connect remotely using EDBManager - receiving the #1100 error.  I know the external IP is good as I can RDP into the VM.

Hints?

... Norm

On 3/30/2016 1:16 PM, Norman Clark wrote:
> I'm still unable to connect remotely using EDBManager - receiving the #1100 error.  I know the external IP is good as I can RDP into the VM.
> Hints?

What about the windows firewall itself (for EBD port) on vm ?

I don't use Azure myself but for Amazon EC2 i do need to configure both
the VM ACL rules and local firewall separately.

Raul

Norman Clark wrote:

> Hints?

Never used this myself, but if the Azure link is open and the VM
firewall open, then perhaps check the client end? I find that telnet is
a good test, even though it won't work.

telnet server-ip 12010

This will try to make a connection, and let you know the Windows view
of it. (If it is not installed, go to the Windows components control
panel to add it.) Sometimes you can type something and it will be
disconnected as it isn't what the server was expecting, but that's fine.

--

Matthew Jones

Norman Clark wrote:

I am attempting to set up an Azure VM to run an ElevateDB server.  If anyone has been successful in this painful endeavour I would appreciate knowing how you managed it.
=======================================================================
Finally!  OK - had to delete my original VM and recreate a "Classic" VM 2012R2 Server which provided for specifying the "Endpoints".  I had opened the port in the VM's Windows Firewall and permitted edbsvr as well.

I repeatedly tested access remotely and couldn't telnet into the port.  After several frustrating hours I finally deleted and re-created the Endpoint and "poof" - finally I was able to use the EDB Manager to access the engine.

Persistence finally pays the reward.

... Now on to test the VM for performance etc.

BTW, as a Microsoft Action Pack subscriber you receive a $100/month credit toward an Azure benefit.  That credit should cover the majority of the costs of the VM that can host the EDB Server.

Thanks for the ear(s) and the advice.  If any are considering this approach PM me and I'll do my best to tell you what I did.

... Norm

Norman Clark wrote:

>  After several frustrating hours

That is how Azure works for me too. I spent hours yesterday trying to
get the PowerShell Stop-AzureVM to work. You have to pass in a service,
and I couldn't identify one. Lots of info, nothing happening. And then
I mentioned it to a friend, and he did some digging, and accidentally
spotted the issue. Stop-AzureRmVM is what I needed to be using, because
obviously the RM version (not linked or referenced in anything on the
Stop-AzureVM web articles) is what I needed because it is the new way
they are doing things, not the classic way.

Also, if you are wanting to experiment, don't buy the cheapest 0.25
cores VM, as it is as slow as slow can be.

There, I feel better now. Excuse the tears. 8-)

--

Matthew Jones

"Matthew Jones" wrote:
Also, if you are wanting to experiment, don't buy the cheapest 0.25
cores VM, as it is as slow as slow can be.

Matthew,
I am looking at Microsoft Azure website. Page on Pricing - Virtual Machines Pricing.

https://azure.microsoft.com/en-us/pricing/details/virtual-machines/

(Ensure the Windows button is clicked)

All the cores are 1 or above. Where do Microsoft offer less than 1 core for Microsoft Azure?

Regards,
 Peter Evans

Peter Evans wrote:

> I am looking at Microsoft Azure website. Page on Pricing - Virtual
> Machines Pricing.
>
> https://azure.microsoft.com/en-us/pricing/details/virtual-machines/
>
> (Ensure the Windows button is clicked)
>
> All the cores are 1 or above. Where do Microsoft offer less than 1
> core for Microsoft Azure?

The A0 basic is 0.25 cores. It isn't on that page, but it is a lot
cheaper. WHen you select it in the control panel, it shows the true
core count. (Of course there must be a whole core, but I presume it is
throttled for sharing somehow).

--

Matthew Jones

"Matthew Jones" wrote:

>>The A0 basic is 0.25 cores. It isn't on that page, but it is a lot

Thanks for that.

Peter