After yesterday's announcement of BizTalk Service GA on Windows Azure, I'm trying to create a new Development instance so I can start migrating my on premises BizTalk projects to there.
After I fill the wizard and start waiting for the instance creation, I get the following error:
Could not connect to the Tracking Database. Confirm that the SQL Database details are correct and that Windows Azure Services is enabled on the SQL Database. (RDFE - Operation ID = fcc014e60cea345c9e03dcd2dca787d3 )
What is happening?
Make sure DB allows Azure services to access it
Possibly the internal DNS problems are affecting it.
The Register Microsoft pulls its crowd-control tech from out of the shadows
a variety of Microsoft services including Windows Azure and Xbox became unavailable due to an as-yet-unspecified problem with Microsoft's global DNS configuration
or
Xbox One site BELLY-UP in GLOBAL Microsoft cloud catastrophe
Initial reports seem to indicate the problem stems from an internal DNS issue, as both the page and various Azure services are throwing DNS errors. Azure may be working, but reaching it is difficult.
Related
Using Dynamics 365 for Operation Could VM (deployed in scope of the LCS subscription), there is a requirement to access the SQL DB directly using ODBC connection from excel. Customer is not happy with implementation via Odata or custom service.
Current problem: can't connect to AX DB using ODBC
Please, could You correct me, if I'm wrong: in case there is cloud D365 VM, deployed in scope of the LCS subscription, the VM deployed against client Azure subscription, but VM is hosted on the Microsoft Azure site, thus there is no way to maintain VM from Azure (only RPD connection for non-production systems) and even we manage to open the required port on the VM site, the connection is not able to reach the DB because of Azure environment. Production system is even less manageable as required MS service requests. Following my logic, the appropriate way is to use one of the supported by AX frameworks \ protocols as it's always accessible regardless of system type and etc
You do not have direct SQL connection possibilities for D365fFO production environment located in Azure. Consider to use OData feeds, Logic Apps (MS Flow) or PowerApps (CDS Projects) instead.
If you planning to use direct connection for reporting purposes (read only), you able to configure copying the production DB to Sandbox and to another DB instance sequentually.
Also you able to restore DB on to production environment from Sandbox before Go-Live.
In the older management portal I was able to do SQL Server database management tasks but in the new portal (green and blue) that functionality seems to be removed. In fact the older Azure portal does not seem to have that functionality more as the always dumps me to the add Silverlight screen (I have added 3 times).
I have a simple datafix but I can not get to the server from my current location.
This functionality has be deprecated and removed.
(http://yourservername.database.windows.net)
Azure SQL Database Management portal:
Cannot manage V12 servers.
ref: https://azure.microsoft.com/en-us/documentation/articles/sql-database-v12-plan-prepare-upgrade/
If your client is not on Windows see suggestion #01 below.
If you are on Windows probably a good route to managing your Azure database is to download the free SQL Server Management Studio (SSMS) from [ https://msdn.microsoft.com/library/mt238290.aspx ] . You wind up wired into your cloud based SQL Server same as you would with an on-premise.
CAVEAT - due to the hardening of Azure SQL Database on firewall rules, you may find yourself going to the Azure Portal a great deal to open the firewall between your local client and your Azure SQL Database.
SUGGESTION #01 - Create a 'dev vm' in Azure and install the SSMS into it. Azure <-> Azure connections do not get firewall dinged every time the client IP changes. Shut down the 'dev vm' when you aren't using the tools and save some $s. Great option for folks who don't use a Windows desktop as well.
SUGGESTION #02 - still want to run SSMS local and hate the firewall restriction. Open it from 0.0.0.0 to 255.255.255.255 . I've done this on occasion but only temporarily, and removed the rule very quickly after I was done.
Hope this helps. Healy in Tampa
I created a Biztalk service (xyz.biztalk.windows.net) as a part of testing hybrid connection for my azure website.
I deleted the biztalk service (xyz) and tried to create a new service with the same name (xyz.biztalk.windows.net).
Azure would not allow me to use the same name (xyz). It gives me this error "the specified name is already in use or is not allowed"
Is there any specific time I need to wait until I can use the service name I deleted?
Any help or information related to this would greatly be appreciated.
According to my experiences with the Azure BizTalk Services Free and Developer tiers, I can only confirm this situation. This is not documented on MSDN as far as I was able to find out.
If this is a URL you where planning to use for a production environment, I suggest you contact Microsoft support.
I'm an MSDN subscriber beginning a personal project that will involve WPF, Web Services, and SQL Server. I'm planning on using my MSDN benefits to host the Web Services on Azure and the database on SQL Azure.
I was going to run TFS on my own dev machine, but then heard about Microsoft's Team Foundation Service cloud offering. Also, it appears that I could run my own instance of TFS on Azure. At this point I'm thinking that Team Foundation Service is the best option because:
I'd prefer to have TFS in the cloud over my main dev machine so that I can access it anywhere and not have to worry about having to back it up.
I'd rather not have to worry about setting up and administrating TFS on Azure if I'm not getting anything extra out of it.
I'm not exactly sure if setting up and using TFS on Azure will be free (or continue to be free) with my MSDN Subscription.
Has anyone experienced any major drawbacks to using Team Foundation Service, like a major loss of flexibility or functionality?
I've been using TFS Services since it has been in preview for my personal work - and I haven't had any limitations in terms of source control/build services. The service is fairly comparable to the full TFS server; but doesn't include the more advanced features such as test automation.
The pricing page also states that service will continue to remain free for MSDN subscribers: https://tfs.visualstudio.com/en-us/pricing/information/
Before TFSPreview existed, I asked some people in the know at MS about running TFS in Azure and I was told that there are some non-trivial problems with running TFS on a virtual machine on Azure. I believe this is why MS are offering TFS as a service rather than as a template for a virtual machine. As such, if you want to use TFS and you want it to be in the cloud, I'd definitely use the TFS Preview.
I have created my first app for azure. It's has an MVC3 web role which writes some data to table storage.
It also has a worker role that does some work behind the scenes to the same data.
It all works fine in the emulator.
I've uploaded it all to Azure as a staging deployment, the hosted service it is reports all roles as "ready". The health for all roles is "healthy", though the worker role appears to crash and goes to "degraded" and then resets itself (I assume this is what is happening).
So what now? I have found a "DNS Name" on my Web Role in the form "http://{guid}.cloudapp.net/"
Clicking on that link just gives me a network access error, http://www.downforeveryoneorjustme.com/ can't find it either.
What am I missing? Where can I see diagnostics similar to the emulator? I've set "Enable Diagnostics" to use my Azure storage account in each role. How do I get into the storage to see if it has traced anything? Can this be done through the Management Portal?
I've tried searching through MSDN, but I can't find a page that says "and then you click the DNS name link and your website will launch. I'm sure there is a lovely page like that but I can't find it.
thanks in advance!
In August 2011, the Windows Azure role templates were updated to work with the ASP.NET Universal Providers. As such, when you create a new project, the session state provider is backed by SQL Express by default. If you don't change this to SQL Azure or Cache (or disable session state), you'll run into issues.
I'm not sure this is exactly the issue you're running into, but it's a common one. See Nate Totten's blog post for more information about this (Nate calls out this issue a few pages down, under IMPORTANT NOTE).
You can access diagnostics data directly from Visual Studio Server Explorer.
Here you have all necessary information: Browsing Storage Resources with Server Explorer http://msdn.microsoft.com/en-us/library/windowsazure/ff683677.aspx
Personally I use Azure Diagnostics Manager from Cerebrata http://www.cerebrata.com/products/AzureDiagnosticsManager/ that is easy and has a good dashboard