I've got an issue when creating new tenant with database on other azure subscription, but database on the same Azure account is OK. I've tried to configure the azure database by turn on "Allow access to Azure services" but I got error message "The timeout period elapsed prior to completion of the operation or the server is not responding." When I updated "Connection Timeout" to 60 instead of 30 I got error message "An exception has been raised that is likely due to a transient failure. If you are connecting to a SQL Azure database consider using SqlAzureExecutionStrategy"
3 Answer(s)
-
0
Hi,
Is this log is written by your Web applicaiton ? I'm not an expert on Azure but there must be more detailed error logs on your azure subscription, can you also check that ? If you are using a Virtual Machine, you can check Window's Event Viewer logs.
And can you try to do same thing by disabling transactions using this code in your Web Module ?
Configuration.UnitOfWork.IsTransactional = false; -
0
Hi,
Sorry for late response. I've tried to disable transactions but got this message
Castle.MicroKernel.ComponentActivator.ComponentActivatorException: ComponentActivator: could not instantiate MyCompany.EntityFramework.MyCompanyDbContext ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Data.DataException: An exception occurred while initializing the database. See the InnerException for details. ---> System.Data.Entity.Core.EntityException: An exception has been raised that is likely due to a transient failure. If you are connecting to a SQL Azure database consider using SqlAzureExecutionStrategy. ---> System.Data.SqlClient.SqlException: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) ---> System.ComponentModel.Win32Exception: The specified network name is no longer available --- End of inner exception stack trace --- at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, DbConnectionPool pool, String accessToken, Boolean applyTransientFaultHandling) at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions) at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions) at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConne... -
0
Hi,
I had a similar issue with azure before and it was related to my connection string. Can you share your connection string for this database ?
