Error: No support for keyword: 'Provider'

Asked

Viewed 900 times

-2

I have to maintain a system and it is with a problem that I can not solve for 1 month because of a connection failure.

There is no support for the keyword: 'Provider'. Description: An untreated exception occurred during the execution of the current web request. Examine stack tracking for more information about the error and where it originated in the code.

Exception Details: System.Argumentexception: No support for keyword: 'Ovider'.

Error of Origin:

Untreated exception was generated during the execution of the current web request. Information related to the origin and location of the exception can be identified using the exception stack tracking below.

Connection string

<connectionStrings>    
  <add name="ApplicationServices" 
       connectionString="Server=SRVSQLDEALER\VDLSQLDB;User ID=monitor;Password=monitor;Database=dbRentabilidade_teste;Persist Security Info=True;Provider=SQLOLEDB" 
       providerName="System.Data.OleDb" />
</connectionStrings>

What is wrong?

c# sql-server connectionstring

  • put the code snippet that is using the connection string...

  • 1

    Why did you reverse the edit? It gets hard to read the way you left it... In addition, the Asp.net tag is unnecessary given the context, the problem is only in connection to the bank, it has no relation to ASP.NET.

1 answer

2

Just take this one Provider connection string...

connectionString="Server=SRVSQLDEALER\VDLSQLDB;
User ID=monitor; Password=monitor; Database=dbRentabilidade_teste;Persist Security Info=True;"

  • It did not work and generated another error... Server Error in the Application '/'. Could not find stored Procedure 'dbo.aspnet_CheckSchemaVersion'. Description: An untreated exception occurred during the execution of the current web request. Examine stack tracking for more information about the error and where it originated in the code. Exception Details: System.Data.Sqlclient.Sqlexception: Could not find stored Procedure 'dbo.aspnet_CheckSchemaVersion'.

  • @Thiagolopez There is another problem... It has nothing to do with the question.

  • If applicable, finish this question (since it seems to have solved the initial problem) and open another.

  • It was not finished because I could not make the connection yet. only generated another error for not solving the problem.

  • @Thiagolopez The error you posted has been solved. The problem is clearly something else and has nothing related to the error posted.

  • If you don’t want to help, friend, I’ll wait for someone with good will.

  • 3

    It’s not about not wanting to help, young man. It’s just about how the site works. But you want to stay on it, good luck...

  • 2

    @Thiagolopez The problem in your comment is different from the problem proposed in the question. The problem with the connection string has been solved by removing the attribute Provider, the error now reported is that the BD engine cannot find an internal management element dbo.aspnet_CheckSchemaVersion probably because your comic book was not registered with aspnet_regsql.exe. The ideal is to open another question to this problem. But you can try the Visual Studio Developer Console and type aspnet_regsql.exe and follow the wizard. Persisting error open a new question.

  • Okay, thanks @Augustovasques

  • 1

    @Thiagolopez create a new question with the new specific problem and put a link to this question to show what you have done so far.

Show 5 more comments

Browser other questions tagged c# sql-server connectionstring

You are not signed in. Login or sign up in order to post.