I have published the website to sitecloud.cytanium.com (ASP.net MVC3+MYSQL+EntityFramework). Please help me out with this.
The Error I am facing on login is :
Server Error in '/' Application.
Unable to find the requested .Net Framework Data Provider. It may not be installed.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.ArgumentException: Unable to find the requested .Net Framework Data Provider. It may not be installed.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[ArgumentException: Unable to find the requested .Net Framework Data Provider. It may not be installed.]
System.Data.Common.DbProviderFactories.GetFactory(String providerInvariantName) +1425695
System.Data.EntityClient.EntityConnection.GetFactory(String providerString) +27
[ArgumentException: The specified store provider cannot be found in the configuration, or is not valid.]
System.Data.EntityClient.EntityConnection.GetFactory(String providerString) +92
System.Data.EntityClient.EntityConnection.ChangeConnectionString(String newConnectionString) +246
...........................
Unable to find the requested .Net Framework Data Provider. It may not be installed.
You should install provider for MYSQL on the server. Connector/Net or some other.
Same question:
C# MySQL Connector works in IDE, not after publish?
Related
My bot is implemented using v3 bot builder, and its hosted in Azure web app(previously hosed on prem IIS Server). after migrating the bot to Azure web app, it stopped working and I could observe the below error form application insights. I have enabled proxy and also enabled TLS versions required in global.asax and enabled the corporate proxy as per the policy. but could not resolve the issues.
Error refreshing OpenId configuration: System.InvalidOperationException: IDX10803: Unable to obtain configuration from: 'https://login.botframework.com/v1/.well-known/openidconfiguration'. ---> System.IO.IOException: IDX10804: Unable to retrieve document from: 'https://login.botframework.com/v1/.well-known/openidconfiguration'. ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond...
I have referred multiple links but could not really resolve it.
Azure Bot Service will require all connections to be secured using Transport Layer Security (TLS) 1.2. It doesn't support TLS 1.0 anymore.
https://blog.botframework.com/2018/11/06/announcement-azure-bot-service-enforcing-transport-layer-security-tls-1-2/
You may add something like this in startup code -
System.Net.ServicePointManager.SecurityProtocol = System.Net.SecurityProtocolType.Tls12;
The destination used for executing calls is configured for authentication type as oAuth2SAMLBearerAssertion, The business user is already onboard in the system with userid, email and other basic details. On calling execute method from SDK I get below error:
Caused by: com.sap.cloud.sdk.cloudplatform.connectivity.exception.DestinationAccessException: Failed to get authentication headers. Destination service returned error: Provided authorization grant is invalid. Exception was No user found with alias 'name#domain.com' (format: unspecified). For more information, consult the kernel traces or the OAuth 2.0 troubleshooting SAP note 1688545.
The issue is resolved by adding following properties in configured destination:
nameIdFormat urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress
here nameIdFormat is the additional property name.
I developed my application in visual studio 2008 and i deployed it on many computers with windows paltform. Its working fine but there is one mac book who has virtual windows 7 over it. my clickonce appliaction is working fine for the first time on this machine when it is installed. but after closing it when user start it again it is giving the following error. I have googled it but could not find the proper answer. Can anyone help?
PLATFORM VERSION INFO
Windows : 6.1.7601.65536 (Win32NT)
Common Language Runtime : 4.0.30319.296
System.Deployment.dll : 4.0.30319.1 (RTMRel.030319-0100)
clr.dll : 4.0.30319.296 (RTMGDR.030319-2900)
dfdll.dll : 4.0.30319.1 (RTMRel.030319-0100)
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of \\.psf\Home\Desktop\MyApplication.appref-ms| resulted in exception. Following failure messages were detected:
+ Invalid URI: The hostname could not be parsed.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
No phase information is available.
ERROR DETAILS
Following errors were detected during this operation.
* [01/03/2013 10:58:47] System.UriFormatException
- Invalid URI: The hostname could not be parsed.
- Source: System
- Stack trace:
at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
at System.Uri..ctor(String uriString)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
The answer is explained in the error: "\.psf\Home\Desktop\MyApplication.appref-ms| resulted in exception". It can't parse that as a URL or a network share.
So how are you installing your application? Are you hosting it on a webserver or a fileshare, or taking it on a cd and copying it to the machine and installing it? What is your installation URL in the Publish window for the project properties?
When I try to run the wp7 app which is used with Linq to sql database and stored in Isolated Storage,it throws an error:
There was no endpoint listening at
http://192.168.0.110:2502/ApplicationSessionService/ApplicationSessionService.svc
that could accept the message.
This is often caused by an incorrect address or SOAP action.
See InnerException, if present, for more details.
I'm not running it on IIS.i tried to find the solution on Google but no solution is provided.
Please help me to solve this problem
Check if you have a Service Reference in your project.
This error is not connected with Isolated Storage ect.
We have an ASP.NET MVC 3 web site which isn't working after it's deployed to the Azure Cloud Services. During development, we've been testing it using the Azure Web Sites platform but in order to get the SSL support for our custom domain, we are now trying to deploy it to Web Role in Cloud Services. But the site's database connection to SQL Azure doesn't work, instead we get: "The instance of SQL Server you attempted to connect to does not support encryption." Retrying the connection doesn't work, that error message persists.
To summarize, here's the platforms where the site works and where it doesn't:
Azure Emulator: Works
Azure Web Sites: Works
Azure Cloud Services (Web Role): Doesn't work
The "How to: Connect to Windows Azure SQL Database Using ADO.NET" states that the error "The instance of SQL Server you attempted to connect to does not support encryption." "indicates a failure during the login process, and is not an encryption failure. Beginning in .NET 4.5, ADO.NET displays a better error message." The Azure Cloud Services are limited to .NET 4.0.
The site is using NHibernate to connect to the DB. Here's an error from the log file:
Creating nhibernate session factory failed.
FluentNHibernate.Cfg.FluentConfigurationException: An invalid or incomplete configuration was used while creating a SessionFactory. Check PotentialReasons collection, and InnerException for more detail.
Database was not configured through Database method. --->
System.Data.SqlClient.SqlException: The instance of SQL Server you
attempted to connect to does not support encryption. at
System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection
owningObject) at
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection
owningConnection) at
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory) at
System.Data.SqlClient.SqlConnection.Open() at
YoureOnTime.Data.RetryConnectionStringProvider.<>c_DisplayClass2.b_0()
at YoureOnTime.Common.Retry.RequestWithRetry(RetryPolicy retryPolicy,
Action action) at
YoureOnTime.Data.RetryConnectionStringProvider.GetConnection() at
NHibernate.Tool.hbm2ddl.SuppliedConnectionProviderConnectionHelper.Prepare()
at
NHibernate.Tool.hbm2ddl.SchemaMetadataUpdater.GetReservedWords(Dialect
dialect, IConnectionHelper connectionHelper) at
NHibernate.Tool.hbm2ddl.SchemaMetadataUpdater.Update(ISessionFactory
sessionFactory) at
NHibernate.Impl.SessionFactoryImpl..ctor(Configuration cfg, IMapping
mapping, Settings settings, EventListeners listeners) at
FluentNHibernate.Cfg.FluentConfiguration.BuildSessionFactory() ---
End of inner exception stack trace ---
And here's how the connection is defined in the hibernate.xml:
<property name="connection.connection_string">
data source=database.database.windows.net;Initial Catalog=db;User ID=user;Password=password;Encrypt=true;Trusted_Connection=false;MultipleActiveResultSets=True
</property>
Any ideas?
Bases on my previous experience on seeing this error, it is an intermittent occurrence. SQL Database always enforces encryption and if during an early phase of the login process (before authentication) there is a failure, the protocol libraries (client side) will fall back to this error message. As you mentioned it is a misleading message and not related to encryption.
This article described the exact same error and explains how you can solve your problem by adding retry logic. So if you modify your code to use retry logic, after a few failure you may pass this error and get the connection going.