Hello I am facing one issue during snapshot replication between SQl servers reside in Windows Azure Virtual Machine.
I had 2 VM with below configuration
1) Windows server 2012 (Installed sql server 2012 with msdn licence)
2) SQL server 2008 R2 (Databases reside on this server, on this i had created publisher for replication)
Now when i creating subscriber over target sql server (1st server) then while selecting publisher connection it shows me error in connecting as shown below image.
Is there any need to create virtual network? in future target server would be on premises server instead of Azure VM.
Note : For both VM i had opened 1433 port and enabled Mixed Mode Authentication.
Create an alias in SQL Server Configuration Manager and give it the name the replication component expects. The alias contains the cloupapp url and port.
Now reconnect using the simple alias. Just did this for my cloudapp.net VM.
I got solution by adding alias entry in host file on VM (C:\Windows\System32\drivers\etc)
[IP Here instead of cloudapp.net URL] [SQL server instance name]
So for clarification, using the example above, the solution as I've experienced it, is to create a SQL Server alias for the server name shown in the error message. In this case, the alias name should be SQL-AZURE and the server should be the server name as shown at the top of the error message dialog:
catalysttg.cloudapp.net, port no 1433, protocol tcp/ip
Related
I have created a sql server instance on an Azure VM and uploaded my sql server backup and the various reports that were previously running on a local box. This has all gone well and I can connect to the database via management studio from my remote client.
I can also run all my reports locally on the Azure VM using RDP. They all work fine.
The problem comes when I try to connect to my report server using Internet Explorer from my remote client. All I get is Page is not found messages.
I have opened Port 80 on the Azure firewall and added an inbound rule in my Azure Portal to allow connection on Port 80.
I have tried using the Public DNS name I have created something like AFDSQL.NorthEurope.cloudapp.azure.com/Reports_MSSQLSERVER/Pages/Folder.aspx and also tried the IP address directly but neither work.
What am I missing?
Roy
Just got mine working!
Yes, you have to open port 80 on the windows firewall in your azure vm.
You also have to open the port in the network security section of your azure portal.
Finally the address to use is http://servername/reports/browse not reports/folder.aspx like you are used.
I've deployed my version in windows azure.
After that I've added sql database. When I trying to connect, it doesn't allow from local. So I've clicked on "Set up Windows Azure firewall rules for this IP address" and added ip address. Now working fine when I run from local.
But When I tried to access from the iis8, I got an isssue is,
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - No such host is known.)
.Net SqlClient Data Provider.
In local, the same functionality is working fine.
Your server running IIS8 needs to be added to the firewall just like you did with your local machine, you can do this either using the Management Portal or you can connect to your SQL Azure instance from your local machine and run:
exec sp_set_firewall_rule N'IIS8 Webserver','X.Y.Z.0','X.Y.Z.0';
Where the first arguments is name of this firewall rule and X.Y.Z.0 is the public ip of your IIS8 Webserver.
The reason its specified two times is that you can specify a range of IP's.
More info here
I'm working through an Azure tutorial on MSDN as suggested by #BrentDaCodeMonkey. Basically, I'm trying to learn how to set up a Windows domain, so I can use it for a some other SQL Server tutorials. See my previous question here.
I'm running into a problem where I cannot connect my servers to my Active Directory Name Controller. When I try to add my domain name to the server in System Properties, I get an error message instead of the Windows Security popup dialog.
An Active Directory Name Controller (AD DC) for the domain "corp.ejm.com" could not be contacted. Ensure that the domain name is typed correctly. [...] The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Name Controller (AD NC) for domain "corp.ejm.com"; The error was: "This operation returned because the timeout period expired."
Note that I am able to verify the DC's IP address, with nslookup in the command prompt.
Complicating this issue is that the tutorial instructions don't exactly match what I'm seeing in Azure. For example, I'm not allowed to use Windows Server 2008 R2 SP1 when setting up SQL Server virtual machines. I had to use Windows Server 2012 for those, but still used 2008 for the DC. I thought that the problem might be a conflicting operating systems, so I tried running the tutorial again using Windows Server 2012 for everything. Same error message.
Also note: the tutorial says that I should use the example domain, corp.contoso.com. I used my own example domain instead, corp.ejm.com. I'm wondering if this has something to do with it. My example domain is not registered on the Internet.
Connect to the DC VM and find out its IPAddress (10.*).
Go to the virtual network configuration and set the DNS server IP Address to that.
Also make sure you use this IP Address during step #8 in install SQL VMs section.
Now try joining the SQL VMs to the domain.
Hope this helps.
I installed TFS on windows azure VM, this VM has public ip:42.134.156.116 for example,i find it is with the port 63630 indeed when i remote this VM with using a downloaded .RDP file.
In visual studio on my local machine, i can not connect to this tfs via its public IP.
I think this maybe a port or firewall issue,but not exactly. because vm has the port 63630 and tfs defualt port is 8080, in addition：the inbound rule of port 8080 has the Profiles "private" and "public", ,
any help?
In Azure go to the VM and click on the endpoints and enable 8080 for your TFS.
Azure also has firewall rules as well as your local VM. The VM as you mentioned looks to have 8080 inbound open.
Regarding your local VM firewall, whether it is public or private depends on what type of network you assigned to your local VM network.
Then try to telnet from your local machine to your VM to confirm the port is open.
Then if that works you should be able to connect. If you can't after that point, it is a TFS or VS Configuration issue.
If you are having troubles, I normally find it good to disable ALL firewalls, get a good connection, then switch them on one by one until you find out which one is causing the issue.
I have created an ssrs report inside an Azure Virtual Machine (SQL Server 2012 SP1 on Windows Server 2012). When I try to view the report from the Virtual machine it opens up in the browser with a proper url like
http://mysamplevm/ReportServer/Pages/ReportViewer.aspx?%2fMySampleReport&rs:Command=Render
When I try to open the same url from my local machine, it says webpage is not available. I have completed the following settings too.
Created Inbound & Outbound rules in Virtual Machine Firewall for port numbers 80 and 443.
Created end points for the same port numbers in azure management portal.
You shall access the report server via the public DNS Name - this is sort of http://mysamplevm.cloudapp.net/ReportServer/Page, and not http://mysamplevm/. You can get this when you navigate to the dashboard of your VM in the management portal - right hand links are named Quick glance, the second is DNS Name.
Because your computer has no idea how to find mysamplevm.
While astaykov is correct regarding the URL, there are two more steps you need to go through to make your report server accessible from outside your VM:
Open HTTP/HTTPS endpoint for your VM in Azure management portal
Open a firewall port:
Open Windows PowerShell on your Virtual Machine
Run the following (for port 80):
New-NetFirewallRule -DisplayName “Report Server (TCP on port 443)” -Direction Inbound –Protocol TCP –LocalPort 80
Now you can access your report server from remote computers through:
http://yourservername.cloudapp.net/reportserver
You have to log into the VM and open windows firewall advanced settings. In Inbound settings, allow port 80 to accept connections.
In addition to what DivineOps has mentioned. In Azure portal (new version), you have to go into NSG to configure firewall rules.
For me, I had to configure inbound rules, both on VM (via RDP) and via Azure portal for it to be accessible.