Connecting to Datazen server on Azure VM

Hi,
I have a problem with connecting to Azure VM. Microsoft Server 2012 is installed on the VM as well as Datazen Enterprise Server.
If I try to connect to VM through web browser, Datazen control panel will load and everything works fine.
But when I try to connect to Datazen server using Datazen Publisher app, I get message that Server isnt available. I cant debug the connection because it doesnt show any records in fiddler.
Do you have any ideas what should I do?
Ondra Planicka

Hi Ondra;
Since you are not able to TELNET i suggest you to check the Firewall settings first. Also if you could provide a snippet that would be helpful.
Regards;
Shreya

Similar Messages

ODBC Slow resonse time when connecting to SQL SERVER on Azure VM

Hello,
I have extra small AZURE VM with SQL Server Express 2008.
I managed to connect to the SQL Server by ODBC connection (from access).
The problem is that the response time is very slow and it is not usable.
How can I improve the response time?
If I will use bigger VM or use AZURE SQL SERVER (instead of installing SQL SERVER on VM)
will the response time be better?
Thank you for your help

Hello,
In addition to resoure of the windows Azure VM, the network and the query may also result to the slow response. When create a Windows Azure SQL Database, it also share resources with other services.
You can refer to the following blog about manage connections in Windows Azure SQL Database:
http://social.technet.microsoft.com/wiki/contents/articles/1541.windows-azure-sql-database-connection-management.aspx#GeneralBestPractices
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

Azure Webjobs with EF DB - A network-related or instance-specific error occurred while establishing a connection to SQL Server

Hi,
I have been trying to get a very simple WebJob developed and deployed onto Azure with little to no luck. I have a MVC Website which has a common project which handles my Data Access Layer with Entity Framework. I have created a WebJob project
using Visual Studio and added the following lines of code to the Manual Trigger Function
[NoAutomaticTrigger]
public static void ManualTrigger(TextWriter log, int value, [Queue("queue")] out string message)
RitualDBEntities db = new RitualDBEntities();
log.WriteLine("Function is invoked with value={0}", value);
List<Location> locations = db.Locations.ToList();
string msg = string.Empty;
foreach (Location location in locations)
msg += location.Name;
message = msg;
log.WriteLine("Following message will be written on the Queue={0}", message);
In my app.config of my WebJob i have the following connection strings:
<add name="RitualDBEntities" connectionString="metadata=res://*/RitualDBEntities.csdl|res://*/RitualDBEntities.ssdl|res://*/RitualDBEntities.msl;provider=System.Data.SqlClient;provider connection string="data source=ritual-pc\sqlexpress;initial catalog=RitualDB;integrated security=True;persist security info=False;MultipleActiveResultSets=True;App=EntityFramework"" providerName="System.Data.EntityClient" />
<add name="RitualContext" connectionString="Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=RitualDB;Data Source=ritual-pc\sqlexpress" providerName="System.Data.SqlClient" />
<add name="AzureWebJobsDashboard" connectionString="DefaultEndpointsProtocol=https;AccountName=ritual***;AccountKey=tQAP0gyMYKtWPJeIbsqk2iT2k69gyd1FwcyRf3+5Mc9b9EdYzpj0Dq8X2VHUmF*****"/>
<add name="AzureWebJobsStorage" connectionString="DefaultEndpointsProtocol=https;AccountName=ritual***;AccountKey=tQAP0gyMYKtWPJeIbsqk2iT2k69gyd1FwcyRf3+5Mc9b9EdYzpj0Dq8X2VHUmF*****" />
When i test locally (F5 Debugging) the webjob runs successfully and does the loop of the objects returned from the database. When i deploy this Azure the WebJob fails with the following error:
[03/29/2015 22:07:39 > 6ca05b: SYS INFO] Status changed to Initializing
[03/29/2015 22:07:41 > 6ca05b: SYS INFO] Run script 'Ritual.WebJobs.Members.exe' with script host - 'WindowsScriptHost'
[03/29/2015 22:07:41 > 6ca05b: SYS INFO] Status changed to Running
[03/29/2015 22:07:44 > 6ca05b: INFO] Found the following functions:
[03/29/2015 22:07:44 > 6ca05b: INFO] Ritual.WebJobs.Members.Functions.ManualTrigger
[03/29/2015 22:07:44 > 6ca05b: INFO] Executing: 'Functions.ManualTrigger' because This was function was programmatically called via the host APIs.
[03/29/2015 22:08:01 > 6ca05b: INFO] Function had errors. See Azure WebJobs SDK dashboard for details. Instance id is e99d7205-3ca0-4674-9414-f0381d5c2316
[03/29/2015 22:08:01 > 6ca05b: ERR ]
[03/29/2015 22:08:01 > 6ca05b: ERR ] Unhandled Exception: System.Data.Entity.Core.EntityException: The underlying provider failed on Open. ---> System.Data.SqlClient.SqlException: 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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean withFailover)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.SqlClient.SqlConnection.Open()
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.Infrastructure.Interception.DbConnectionDispatcher.<Open>b__36(DbConnection t, DbConnectionInterceptionContext c)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.Infrastructure.Interception.InternalDispatcher`1.Dispatch[TTarget,TInterceptionContext](TTarget target, Action`2 operation, TInterceptionContext interceptionContext, Action`3 executing, Action`3 executed)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.Infrastructure.Interception.DbConnectionDispatcher.Open(DbConnection connection, DbInterceptionContext interceptionContext)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.Core.EntityClient.EntityConnection.<Open>b__2()
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.<>c__DisplayClass1.<Execute>b__0()
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute[TResult](Func`1 operation)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute(Action operation)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.Core.EntityClient.EntityConnection.Open()
[03/29/2015 22:08:01 > 6ca05b: ERR ] --- End of inner exception stack trace ---
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.Core.EntityClient.EntityConnection.Open()
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.Core.Objects.ObjectContext.EnsureConnection(Boolean shouldMonitorTransactions)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.Core.Objects.ObjectContext.ExecuteInTransaction[T](Func`1 func, IDbExecutionStrategy executionStrategy, Boolean startLocalTransaction, Boolean releaseConnectionOnSuccess)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.Core.Objects.ObjectQuery`1.<>c__DisplayClass7.<GetResults>b__5()
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute[TResult](Func`1 operation)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.Core.Objects.ObjectQuery`1.GetResults(Nullable`1 forMergeOption)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.Core.Objects.ObjectQuery`1.<System.Collections.Generic.IEnumerable<T>.GetEnumerator>b__0()
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Data.Entity.Internal.LazyEnumerator`1.MoveNext()
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at Ritual.WebJobs.Members.Functions.ManualTrigger(TextWriter log, Int32 value, String& message)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at lambda_method(Closure , Object[] )
[03/29/2015 22:08:01 > 6ca05b: ERR ] at Microsoft.Azure.WebJobs.Host.Executors.VoidInvoker.InvokeAsync(Object[] arguments)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor.<ExecuteWithWatchersAsync>d__23.MoveNext()
[03/29/2015 22:08:01 > 6ca05b: ERR ] --- End of stack trace from previous location where exception was thrown ---
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor.<ExecuteWithOutputLogsAsync>d__1c.MoveNext()
[03/29/2015 22:08:01 > 6ca05b: ERR ] --- End of stack trace from previous location where exception was thrown ---
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor.<ExecuteWithLogMessageAsync>d__c.MoveNext()
[03/29/2015 22:08:01 > 6ca05b: ERR ] --- End of stack trace from previous location where exception was thrown ---
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
[03/29/2015 22:08:01 > 6ca05b: ERR ] at Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor.<ExecuteWithLogMessageAsync>d__c.MoveNext()
[03/29/2015 22:08:01 > 6ca05b: ERR ] --- End of stack trace from previous location where exception was thrown ---
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor.<TryExecuteAsync>d__1.MoveNext()
[03/29/2015 22:08:01 > 6ca05b: ERR ] --- End of stack trace from previous location where exception was thrown ---
[03/29/2015 22:08:01 > 6ca05b: ERR ] at Microsoft.Azure.WebJobs.Host.Executors.ExceptionDispatchInfoDelayedException.Throw()
[03/29/2015 22:08:01 > 6ca05b: ERR ] at Microsoft.Azure.WebJobs.JobHost.<CallAsyncCore>d__7.MoveNext()
[03/29/2015 22:08:01 > 6ca05b: ERR ] --- End of stack trace from previous location where exception was thrown ---
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at Microsoft.Azure.WebJobs.JobHost.Call(MethodInfo method, Object arguments)
[03/29/2015 22:08:01 > 6ca05b: ERR ] at Ritual.WebJobs.Members.Program.Main()
[03/29/2015 22:08:01 > 6ca05b: SYS INFO] Status changed to Failed
[03/29/2015 22:08:01 > 6ca05b: SYS ERR ] Job failed due to exit code -532462766
If i remove any of my database code and use just the basic Stub code my webjob will run successfully so i know that my connection strings (outside of the DB ones) are correct. My MVC web application also runs perfectly using the same connection strings
in Azure so i also know that they have also been configured.
I am now lost and need some guidance, so if someone is able to assist me that would be much appreciated.
Thanks
Ritual.

Can you try to log the connection string you are using in both cases to make sure they are the same?
Also can you share your site name, either directly or indirectly?
This will help us investigate.
Thanks,
Amit

Unable to establishing a connection to SQL Server created via SqlManagementClient

Goal:
create an Azure SQL Server via .NET (Microsoft.WindowsAzure.Management.Sql.Modules.SqlManagementClient) and add a database to it.
Problem:
I am NOT able to access the newly created server from .Net code.
Description:
Using SqlManagementClient I SUCCESFULLY create a new Azure SQL Server (see code below).
After creating the server, I am able to access the new server from Azure Portal.
* firewall rule show valid client machine
* "Windows Azure Services" is set to "Yes"
An error occures when I try connecting to the database using the same user and pwd used to create it.
/* the following code results in a connection failure */
//string server = <name of newly created sql server>
//string db = <name of new database to create, inside of the server>
public void CreateDatabase(string server, string db)
using (ReliableSqlConnection conn = new ReliableSqlConnection(
                Configuration.GetConnectionString(server, "Master"),
                SqlRetryPolicy,
                SqlRetryPolicy))
                conn.Open(); //// throws System.Data.SqlClient.SqlException
    //// A network-related or instance-specific error occurred while establishing a connection to SQL Server.
                SqlCommand cmd = conn.CreateCommand();
/* the following code creates a sql server and firewall rules */
ServerCreateResponse response;
SubscriptionCloudCredentials creds;
X509Certificate2 cert;
//// Gets the certificate
cert = CredentialUtil.GetCertificate(certificateStoreName, certificateStoreLocation, certificateThumbprint);
//// Using the certificate and the subscription build credential
creds = new CertificateCloudCredentials(azureSubscriptionId, cert);
//// using creditials create server and set firewall rules
using (SqlManagementClient client = new SqlManagementClient(creds))
        response = client.Servers.Create(new ServerCreateParameters()
                AdministratorPassword = sqlPwd,
                AdministratorUserName = sqlUser,
        Location = location
        if (response.StatusCode == HttpStatusCode.Created)
  //// 0.0.0.0 is added to enable "Windows Azure Services" on the "Configure" tab.
  //// <MyInternetIp> would be my actual IP address.
  //// - (which works for other servers that i have manualy registered
  validIPs = new List<string>() {"0.0.0.0", "<MyInternetIp>"};
  CreateFireWallRule(client, response.ServerName, validIPs);
//// Adds IP to Azure firewall.
private static void CreateFireWallRule(SqlManagementClient client, string azureServerName, IEnumerable<string> validIPs)
            foreach (string ip in validIPs)
                FirewallRuleCreateParameters rule = new FirewallRuleCreateParameters() { Name = string.Format("Allow {0} - {1}", Environment.MachineName, ip), StartIPAddress
= ip, EndIPAddress = ip };
                client.FirewallRules.Create(azureServerName, rule);
/// Error
System.Data.SqlClient.SqlException was unhandled
HResult=-2146232060
Message=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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Source=.Net SqlClient Data Provider
ErrorCode=-2146232060
Class=20
LineNumber=0
Number=53
Server=""
State=0

Using SqlManagementClient I SUCCESFULLY create a new Azure SQL Server.
ServerCreateResponse response;
SubscriptionCloudCredentials creds;
X509Certificate2 cert;
cert = CredentialUtil.GetCertificate(parameters.CertificateStoreName, parameters.CertificateStoreLocation, parameters.CertificateThumbprint);
creds = new CertificateCloudCredentials(parameters.AzureSubscriptionId, cert);
using (SqlManagementClient client = new SqlManagementClient(creds))
                response = client.Servers.Create(new ServerCreateParameters()
                    AdministratorPassword = parameters.SqlPwd,
                    AdministratorUserName = parameters.SqlUser,
                    Location = parameters.Location
                if (response.StatusCode == HttpStatusCode.Created)
                    CreateFireWallRule(client, response.ServerName, parameters.ValidIPs);

Can't Create a Data Source - Failed to test connection. [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied

Hi there,
I am having a serious issue with The Power BI Data Management Gateway which I am hoping that someone can help me with.
Basically I am setting a connection between a Power BI demo site and a SQL 2012 Database based on Azure. The Data Management Gateway and is up and running, and Power BI has managed to connect to it successfuly.
By following the tutorials at
here I was able to successful create my Data Connection Gateway with a self-signed certificate.
However, when trying to create the data source I come into problems. The Data Source Manager manages to successfully resolve the hostname, as per the screenshot below:
Bear in mind that I exposed the require ports in Azure as endpoints and I managed to modify my hosts file on my local machine so I could access the SQL server hosted in Azure using its internal name -- otherwise I would not be able to get this far.
However the creation of the data source also fails when trying to created it whilst logged in the SQL server in question:
The Data Source Manager returns the error when using the Microsoft OLE DB Provider for SQL Server:
Failed to test connection. [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied
I tried using the SQL Server Native Client 11.0 instead but I also get an error. This time the error is:
Failed to test connection. Login timeout expiredA network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.Named Pipes Provider: Could not open a connection to SQL Server [53].
Some considerations
If I provide an invalid username/password, the Data Source Manager does say that the username and password is incorrect.
Firewall is turned off in the SQL Server (either way, this error also happens if I try top use the Data Source Manager whilst logged in the SQL Server itself).
SQL Profiler does not show any attempt of connection.
The SQL server instance in question is the default one.
The error happens regardless if I select the option to encrypt connection or not.
In SQL Configuration manager I can see that all protocols are enabled (TCP/IP, Named Pipes and Shared Memory.
The Event Viewer does not provide any further errors than the one I have copied in this post.
I'm at a loss here. Could someone please advise what might I be doing wrong?
Regards,
P.

Here is what I had to do to solve this issue:
Basically I had to add the MSSQL TCP/IP port as an end-point in Azure. After I did that, then I was able to create the data-source. However, I was only able to authenticate with a SQL account, as any domain account would return me an error saying that the
domain isn't trusted.
What puzzles me here is how come the Data Source Manager would inform me that an account username/password was invalid, but it would fail/timeout if I provided valid credentials (!?!?!!?)

Visual Studio very slow to connect to SQL Server

Hi all,
I'm running a Windows 8.1 laptop, and have Visual Studio Ultimate 2013 as well as SQL Server Management Studio 2014 and SQL Server Express 2014. I also have a Windows Azure
SQL Server 2014 database server.
I set up all of this while living in North America - Quebec to be exact. While working from there, I had no trouble connecting to my database server, through Visual Studio or through SSMS.
I'm now living in France, and am having an extremely hard time accessing my databases. While connecting through Visual Studio, it takes 10-20 minutes of waiting before the connection is established with the server. This is true for both the Windows Azure database
server AND the SQL Server Express edition installed on the same laptop!
It makes absolutely no sense - how could it take so long to connect to a server installed on the *same* machine as the applications? What's even more strange, once the connection is established, all other actions happen instantly. There is no delay in communicating
with the server once the connection is set up - it seems like the problem is specifically with connecting to the server.
I've tried using the IP Address instead of localhost, I've also tried using the instance name of the SQL Server Express instead of localhost. Neither have solved the problem.
Can anyone help me with finding out why this is happening? Thanks!

Hi all,
I'm running a Windows 8.1 laptop, and have Visual Studio Ultimate 2013 as well as SQL Server Management Studio 2014 and SQL Server Express 2014. I also have a Windows Azure
SQL Server 2014 database server.
I set up all of this while living in North America - Quebec to be exact. While working from there, I had no trouble connecting to my database server, through Visual Studio or through SSMS.
I'm now living in France, and am having an extremely hard time accessing my databases. While connecting through Visual Studio, it takes 10-20 minutes of waiting before the connection is established with the server. This is true for both the Windows Azure database
server AND the SQL Server Express edition installed on the same laptop!
It makes absolutely no sense - how could it take so long to connect to a server installed on the *same* machine as the applications? What's even more strange, once the connection is established, all other actions happen instantly. There is no delay in communicating
with the server once the connection is set up - it seems like the problem is specifically with connecting to the server.
I've tried using the IP Address instead of localhost, I've also tried using the instance name of the SQL Server Express instead of localhost. Neither have solved the problem.
Can anyone help me with finding out why this is happening? Thanks!
Hello,
Since this issue is not related to Visual Studio debugger tools, I will help you move this thread to Visual Studio General forum to get help about using Visual Studio.
Regards,
Carl
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Securing SQL Server 2012 Azure VM with SSL - Help!!!

Hello all,
I am trying to encrypt with SSL my SQL server 2012 Azure VM; I have created the cert and I can see it in cert mgr but when I go to SQL config MGR -protocols for MSSQLSERVER to setup the encryption, the certificate tab contains no certificates :(
this is so annoying please can someone help me with this?
Thanks so much,
BN.

Also, I am getting the following error whilst connecting to the Azure VM client side via SQL management studio:
“The certificate chain was issued by an authority that is not trusted”
I can get around this by specifying "TrustServerCertificate=True" in the connection string; what is causing this and should I be alarmed? can this be resolved?
Hi ,
According to your error message, When the SQL Server instance has only a self-signed certificate, the encrypt property is set to true and the trustServerCertificate property is set to true. There is an similar issue about SqlException (0x80131904), you can
review the following post.
http://stackoverflow.com/questions/17615260/the-certificate-chain-was-issued-by-an-authority-that-is-not-trusted-when-conn
In addition, there is detail about writing secure connection strings for SQL Database in Windows Azure, you can review it.
http://social.technet.microsoft.com/wiki/contents/articles/2951.windows-azure-sql-database-connection-security.aspx
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Connection to SQL Express on Azure VM not working

Hello,
I'm sorry if this has already been answered somewhere else, I didn't find anything that helped.
Setup:
Two VMs running Windows Server 2012 R2 Datacenter, one running SQL Express.
When trying to connect to the SQL Express, the connection does not work.
Here's what I've done so far:
Set up the MSSQL instance, named SQLEXPRESS
Set up a database, named TESTDB
Set the instance to mixed authentification
Set up VM endpoint TCP 1433
Opened ports TCP 1433, 1434 in the firewall
Activated the SQL Browser
Activated the TCP/IP-Service in the SQL Server Network Configuration
Testing connection via UDL file with the following information:
Server name: <cloud storage>.cloudapp.net\<sql server>\SQLEXPRESS
Username: sa
Password: <password>
Database: TESTDB
Now it returns the following error:
"Test connection failed because of an error in initializing provider.
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied."
Now I keep reading that it may be a firewall problem. But I turned off the firewalls on both servers completely for testing purposes (they're test servers and will be deleted anyway) and it still doesn't work.
I know I must have forgotten something, but what? Or am I entering the wrong connection information?
Does anyone know?
Regards
~Irolan

Server name: <cloud storage>.cloudapp.net\<sql server>\SQLEXPRESS
Hello,
I wonder about the Server Name, it should be "MachineName\SQLEXPRESS" only.
Olaf Helper
[ Blog] [ Xing] [ MVP]
Damn... you're right. That works. Uhm... but what if I want to access it from another computer that is not an Azure VM?

Is it dangerous if I expose UDP 1434 port of SQL 2008R2 server in Azure VM to the Internet ?

I am setting up client/server Application running on SQL2008 server on Azure VM.
Is it dangerous if I expose UDP 1434 port of SQL 2008R2 server in Azure VM to the Internet ?

I do not get your answer exactly , but you mean "That is a much bigger issue from a security perspective." this is dangerous to expose SQL server connection port to the Internet ?
Application uses named SQL instance , so it needs UDP 1434 port to connect to SQL server.
Exposing any server to a network is dangerous.  Exposing a server to the public internet is more risky than connecting to a private network. You cannot eliminate risk but it can be mitigated.
An inherent risk with exposing the SQL Server port is that any client with network connectivity can then try to compromise security, commonly with a dictionary attack.  A malicious user can then gain access to the database limited only by
the compromised account security context.
There are several steps you can take to mitigate this risk. To name a few, allow only trusted IP addresses through the firewall. Run only those services actually needed. Expose only those ports needed. Rename the sa login.
Assign strong passwords to all accounts. Keep all software up-to-date with security patches. Use a service layer to access database services instead of directly from front-end clients.
In your case, you can hard-code the named instance port in connection strings instead of using the SQL Browser service.  Your connection strings do not need to specify the instance name with this technique and UDP 1434 is not needed for connectivity.
Dan Guzman, SQL Server MVP, http://www.dbdelta.com

We're having trouble connecting to the server

HI,
We install SharePoint 2013 on Azure and were using it from clients via vpn connection to our Azure virtual Net.
When trying to edit or add office document from the client we get this error: "we're having trouble connecting to the server..."
sometimes will get the "document is locked ..." which is typical for a document which is still locked by office , I guess its all related to some connection failure from the office client.
Thanks

Hi,
According to your post, my understanding is that you failed to edit or add office document from the client.
Usually a file is locked when a particular user has ‘checked out’ the file for editing purposes. A write lock is created so that no other user can edit this file simultaneously.
There can be numerous reasons for this such as:
         1.    System crashes while the file is still open.
         2.    File has been closed unexpectedly.
         3.    Check in was not successful.
         4.    Network connection is lost while file is still open.
In most of the cases, the write lock still exist for the file so its gives an editing error.
To resolve the issue, you follow the steps in the article as below:
SharePoint error: File is locked for editing by ‘domain\username' : SharePoint Tutorial #6
More information:
Remove SharePoint Client Side File Lock
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Adobe cloud has lost connection with the server

Adobe cloud has lost connection with the server, can't get adobe cloud to work so I can re-install photoshop to fix a corrupted DLL file.

*Adding new items/removing orphans*
Try iTunes Folder Watch or iTunes Library Updater. Folder Watch is much faster on the adding files front, can be set to run in the background and includes a useful exclusion feature, however it’s slow at removing orphans. iTLU is better for this although doing it manually after looking at a list of proposed removals generated by Folder Watch is probably faster still. iTLU can also be set to update iTunes when you've used 3rd party tools to change tag info.
You may need to amend the list of file types these programs look for. My list includes:
.mp3 .mp4 .m4a .m4b .m4p .m4v .mov .wav .aif .mid .ipa .ipg .ite .itlp .m4r .pdf
Note the last 6 types may not be recognised as already being in the library so should either be omitted from the search or you can add (at least for Folder Watch) individual exclusions for files you know are already in your library.
tt2

How do I connect to SQL Server with Muse?

I want to query items from database and load it back to front end. Is there a way Muse can connect to sql server database?

You cannot connect to databases via Muse at the moment. Please refer: http://forums.adobe.com/message/5090145#5090145
Cheers,
Vikas

Hi there, I am trying to connect to my server at work from home using a vpn connection. It connects fine and the time ticks along, but when i click go - connect to server, it comes up with connection failed. Please help!

Hi there, I am trying to connect to my server at work from home using a vpn connection. It connects fine and the time ticks along, but when i click go - connect to server, it comes up with connection failed. Please help!

... when i click go - connect to server, it comes up with connection failed.
If you're trying to connect to a Bonjour server on the remote network, that won't work over a layer 3 VPN. Use something like Hamachi or one of the SSH-tunnelling Bonjour proxy apps for that.

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. (p

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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)(Microsoft SQL Server, Error: 2)
The system cannot find the file specified
Cannot connect to COWBOYS.
Here are the technical details===================================
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:
Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476
Error Number: 2
Severity: 20
State: 0
Program Location:
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean withFailover)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer
timeout)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance,
SqlConnectionString userConnectionOptions, SessionData reconnectSessionData)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
===================================
The system cannot find the file specified
I have tried from so many forms. This is so frustrating. Thank for everyone/anyone who wants to help. So this is what happened: I had to uninstall my previous sqlserver 2012(which worked great) for some reason, and I uninstalled everything from that download.
Then I installed the trial edition of sql server 2012 (64 Bit) and It wouldn't connect to the database. (Error mentioned above.) My local DB is COWBOYS. (COWBOYS is also my computer name.) After this, I have tried downloading sqlexpress and sqlserver 64bit
many times and cannot connect to my local DB.
How do I connect to my Local DB?
Also, I think this might help: (When I run sqlserve.exe, which I was able to find in C:\Program Files\Microsoft SQL Server\110\LocalDB\Binn, I get an error: Your SQL server installation is either corrupt or has been tampered with(Error getting
instance ID from name). Please uninstall then re-run setup to correct this problem.
I would happily re install it, if it wasn't my 20th time.
I don't have any remote connections, I don't use username/password, only window authentication. I work mostly on visual studio, but without able to store /retrieve data, I don't know how to survive.
May be the solution is very simple, but I am too frustrated.
Some of the things I have tried:
From a command prompt, enter one of the following commands:
net start "SQL Server Agent (MSSQLSERVER)" OR
net start "SQL Server Agent(instancename)"(for instance)
on my sql configuration, I cannot start anything because there is nothing there to start. I can post more details, if that would help. Also, some more details about the error:
Details
Product:
SQL Server
ID:
2
Source:
MSSQLServer
Version:
10.0
Component:
SQLEngine
Message:
An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error:
40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)
Explanation
SQL Server did not respond to the client request because the server is probably not started.
User Action
Make sure that the server is started.
Version:
9.0
Component:
SQLEngine
Message:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error:
40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)
Explanation
SQL Server did not respond to the client request because the server is probably not started.
User Action
Make sure that the server is started.
Any one that can help me, I will be greatful. Thank you so much. p.s. please ask me anything if you have any questions.

It sounds like there are a couple things going on here. First check if you have a successful install of SQL Server, then we'll figure out the connection issues.
Can you launch SQL Server Configuration Manager and check for SQL Server (MSSQLSERVER) if default instance or SQL Server (other name) if you've configured your instance as a named instance. Once you find this, make sure the service is started.
If not started, try to start it and see if it throws an error. If you get an error, post the error message your hitting. If the service starts, you can then launch SSMS and try to connect. If you have a default instance, you can use the machine
name in the connection dialog. Ex: "COWBOYS" where Cowboys is the machine name. However, if you named the SQL Server instance during install, you'll need to connect using the machine\instance format. Ex: COWBOYS\Romo (where Romo
is the instance name you set during install).
You can also look at the summary.txt file in the SQL Server setup error logs to see what happened on the most recent install. Past install history is archived in the log folder if you need to dig those up to help troubleshoot, but the most
recent one may help get to the bottom of it if there is an issue with setup detecting a prior instance that needs to be repaired.
Thanks,
Sam Lester (MSFT)
http://blogs.msdn.com/b/samlester
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click
"Mark as Answer" and
"Vote as Helpful" on posts that help you. This can be beneficial to other community members reading the thread.

Client Upgraded from Tiger to Leopard Can No Longer Connect to Tiger Server

I just finished upgrading a G5 2GHz DP Powermac from Tiger to Leopard. This was an Archive and Install upgrade with importing the old settings. After verifying the account migration, including .Mac connectivity, and fixing all 3rd party software compatibilities/upgrades, I tried to connect to our Tiger 4.11 server by clicking on the server's Icon in the Shared section of the Finder Sidebar. The finder then switches to browse the the server for shares: "Connecting..." is displayed under the tool bar, with a "Share Screen..." and "Connect As..." buttons to the right.
At this point the "Connecting..." remains displayed with the spinning circle in the bottom right of the Finder window.... spinning. This situation continues for several minutes until is seems the system gives up.
If I click on the Path button on the Tool Bar, and go up to the Shared level, ALL the Shares on the Network are displayed, including all the Tiger Client machine shares. I can click on the triangle beside the Tiger Client's icon, and all the drives and home directories on the Mac are listed. All the client shares can be accessed without any issues. NOTE: There are no other Leopard clients on the LAN.
Prior to the Leopard upgrade, this client could connect to the Tiger server as well. All the other clients on the LAN can access the Tiger server also.
On the Leopard client I have tried clicking and the "Connect As..." button and using the menu "Connect to Server" and specifying the server's IP, and I get the same "Connecting..." message with a "non-connecting" result.
I can only assume that somehow the Account Name and password are not being passed correctly. But, using "Connect As..." should resolve that. However, "Connect As..." does not give me a user/password window!
If I check the AFP Access log on the Server, the only messages displayed are "Mounted Volume..." No messages in the error log, and no messages in the "Connections" section.
Can anyone help me figure out why the Leopard client can not connect to the Tiger Server?
My apologies if the description of my problem is a bit disjointed. I have been thrown into server admin and am learning "Trial by Fire".
Any help or suggestions on how to resolve this issue will be greatly appreciated.
Thanks
Gary
Message was edited by: Gary Sumlak

OK. A quick update.
After waiting for about 10 minutes for the rotating circle in the bottom right corner to stop, I was able to click on the "Connect As..." button. It took another 10 minutes, but the Connect As window eventual popped up. I entered the Userid and Password (saving to Keychain) and was able to see all the sharepoints on the the server. I browsed all the connected drives and folders without issue.
I then disconnected from the server. Reviewing the AFP logs on the server shows messages for the connection Login and Logout.
I then tried to reconnect to the server, and again another 10 minutes wait, although this time the Leopard client eventually connected automatically with the proper User, as per the AFP logs confirms.
Although, the client can now connect to the server, for it to take 10 minutes will be unacceptable to management, not to mention the end user. Tiger clients can connect in a couple seconds!
Is there a way to reduce the Leopard login time to, say, a couple seconds, like it does with the Tiger clients?
Again, any help or suggestions would be greatly appreciated.
Thanks
Gary

Connecting to Datazen server on Azure VM

Similar Messages

Maybe you are looking for