Format of the initialization string does not conform to specification starting at index 0

Question

I have an ASP NET application which runs fine on my local development machine  When I run this application online  it shows the following error   Format of the initialization string does not conform to specification starting at index 0  Why is this appearing  and how can I fix it

User · Answer

Make sure that your connection string is in this format:

server=FOOSERVER;database=BLAH_DB;pooling=false;Connect Timeout=60;Integrated Security=SSPI;

If your string is missing the server tag then the method would return back with this error.

User · Answer

This might help someone    My password contained a semicolon so was facing this issue So added the password in quotes  It was really a silly mistake   I changed the following     lt add name  db  connectionString  server local database dbanme user id dbuser password pass word  providerName  System Data SqlClient    gt    to   lt add name  db  connectionString  server local database dbanme user id dbuser password  pass word   providerName  System Data SqlClient    gt

User · Answer

I had the same error  In my case  this was because I was missing an closing quote for the password in the connection string    Changed from this   lt add name  db  connectionString  server local database dbanme user id dbuser password  password  providerName  System Data SqlClient    gt    To   lt add name  db  connectionString  server local database dbanme user id dbuser password  password   providerName  System Data SqlClient    gt

User · Answer

In my case  I got a similar error   An unhandled exception was thrown by the application  System ArgumentException  Format of the initialization string does not conform to specification starting at index 91   I change my connection string from   Server   Database dbname User Id myuserid Password mypassword   to   Server   Database dbname User Id myuserid Password  mypassword    and it works  I added single quotes to the password

User · Answer

I had this error and it turned out that the cause was that I had surrounded a  new  tableadapter with a Using End Using   Just changing the tableadapter to stay live for longer  duration of class in my instance  fixed this for me   Maybe this will help someone

User · Answer

Check your connection string like I forget to add             services AddDbContext lt dbsContext gt  options   gt  options UseSqlServer  Default      It causes the error and here when I add Configuration GetConnectionString  then it solves the issue   like now the connection is   services AddDbContext lt dbsContext gt  options   gt  options UseSqlServer Configuration GetConnectionString  Default        works fine  This problem is solved for  net core

User · Answer

For the one other unfortunate soul that is managing a legacy webforms application that uses an inline sqldatasource  along with connection strings stored in web config  then you may get this error if you access your connection string like  lt  APSDataConnectionString   instead of   lt    ConnectionStrings MyConnectionString      This happened to us when upgrading  NET from 3 5 to 4 x    lt asp DropDownList ID  ddl  runat  server  DataSourceID  SqlDataSource1    DataTextField  value  DataValueField  id  gt  lt  asp DropDownList gt                   lt asp SqlDataSource ID  SqlDataSource1  runat  server     ConnectionString   lt    ConnectionStrings MyConnectionString   gt     SelectCommand  select id  value from a table  gt   lt  asp SqlDataSource gt

User · Answer

I had the same problem  Locally the site ran fine  but on azure it would fail with the message above   turns out the problem was setting the connectionstring in the ctor  like this       public DatabaseContext                  Database Connection ConnectionString   ConfigurationManager ConnectionStrings  db   ConnectionString          Does NOT work  this will        public DatabaseContext     base  db                 Beats me

User · Answer

I had this error too and was able to solve it as follows  I previously wrote the connectionstring to the appsettings json into a section that I created  ConnectionsStrings  notice the extra  s   and tried to connect to my database which caused the error  It was an ASP NET CORE application and so I wanted to connect to it with the  GetConnectionString Method  details on that here   It seems that this method implicitly searches for a connectionstring in the  ConnectionStrings -section  which didn t exist  When I changed corrected it to  ConnectionStrings  it worked as expected

User · Answer

I had typo in my connection strings  Database  PESitecore1 master    lt add name  master  connectionString  user id sa password xxxxx Data Source APR9038KBD SQL2014 Database  PESitecore1 master   gt

User · Answer

I removed  amp quot at the end of the connection string and it worked  Instead of   App EntityFramework amp quot    Used   App EntityFramework    Set DefaultConnection as below   lt add name  DefaultConnection  connectionString  data source  local  initial catalog NamSdb persist security info True user id sa password sa MultipleActiveResultSets True App EntityFramework   providerName  System Data SqlClient    gt       Note   In connectionString Do not include              x  Metadata info    metadata res                  x  Encoded Quotes     quot

User · Answer

In my case the problem was that on the server  a different appsettings json file was used by the application

User · Answer

I copied and pasted my connection string configuration into my test project and started running into this error  The connection string worked fine in my WebAPI project  Here is my fix   var connection   ConfigurationManager ConnectionStrings  MyConnectionString    var unitOfWork   new UnitOfWork new SqlConnection connection ConnectionString

User · Answer

Set the project containing your DbContext class as the startup project   I was getting this error while calling enable-migrations  Even if in the Package Manager Console I selected the right Default project  it was still looking at the web config file of that startup project  where the connection string wasn t present

User · Answer

I had the same problem and finally I managed to resolve it in the following way   The problem was in the connection string definition in my web config    lt add name  DefaultConnection  connectionString  DefaultConnection ConnectionString  providerName  System Data SqlClient   gt      The above worked perfect locally because I used a local Database when I managed users and roles  When I transfered my application to IIS the local DB was not longer accessible  in addition I would like to use my DB in SQL Server  So I change the above connection string the following SQL Server DB equivalent    lt add name  DefaultConnection  connectionString  data source MY SQL SERVER  Initial Catalog MY DATABASE NAME  Persist Security Info true  User Id sa Password Mybl00dyPa    providerName  System Data SqlClient   gt    NOTE  The above  also  suppose that you are going to use the same SQL Server from your local box  in case that you incorporate it into your local web config - that is what exactly I did in my case

User · Answer

Check your connection string  If you need help with it check Connection Strings  which has a list of commonly used ones   Commonly used Connection Strings   SQL Server 2012  Standard Security  Server myServerAddress Database myDataBase User Id myUsername Password myPassword    Trusted Connection  Server myServerAddress Database myDataBase Trusted Connection True    Connection to a SQL Server instance  The server instance name syntax used in the server option is the same for all SQL Server connection strings   Server myServerName myInstanceName Database myDataBase User Id myUsername  Password myPassword    SQL Server 2005  Standard Security  Server myServerAddress Database myDataBase User Id myUsername Password myPassword    Trusted Connection  Server myServerAddress Database myDataBase Trusted Connection True    Connection to a SQL Server instance  The server instance name syntax used in the server option is the same for all SQL Server connection strings   Server myServerName myInstanceName Database myDataBase User Id myUsername Password myPassword    MySQL  Standard  Server myServerAddress Database myDataBase Uid myUsername Pwd myPassword    Specifying TCP port  Server myServerAddress Port 1234 Database myDataBase Uid myUsername Pwd myPassword    Oracle  Using TNS  Data Source TORCL User Id myUsername Password myPassword    Using integrated security  Data Source TORCL Integrated Security SSPI    Using ODP NET without tnsnames ora  Data Source  DESCRIPTION  ADDRESS LIST  ADDRESS  PROTOCOL TCP  HOST MyHost  PORT MyPort    CONNECT DATA  SERVER DEDICATED  SERVICE NAME MyOracleSID    User Id myUsername Password myPassword

User · Answer

My problem wasn t that the connection string I was providing was wrong  or that the connection string in the app config I thought I was using was wrong  but that I was using the wrong app config

User · Answer

I had the same issue  came to find out that the deployment to IIS did not set the connection strings correctly  they were    ReplacableToken devConnection-Web config Connection String 0   when viewing the connection strings of the site in IIS  instead of the actual connection string  I updated them there  and all worked as expected

User · Answer

I had the same problem spent an entire day  The error indicates Connection string issue for sure as index 0 is connection string  My issue was in the  Startup class  I used  var connection   Configuration  quot ConnectionStrings DefaultConnection quot    services AddControllersWithViews    services AddApplicationInsightsTelemetry    services AddDbContextPool lt Models PicTickContext gt  options   gt  options UseSqlServer  quot connection quot       which is wrong instead use this  services AddControllersWithViews    services AddApplicationInsightsTelemetry    services AddDbContextPool lt Models PicTickContext gt  options   gt  options UseSqlServer Configuration GetConnectionString  quot DefaultConnection quot       and my problem was solved

User · Answer

Sometimes the Sql Server service has not been started  This may generate the error  Go to Services and start Sql Server  This should make it work

User · Answer

As I Know  whenever you have more than 1 connection string in your solution your current project  startup project       you may confront with this error this link may help you click

User · Answer

My problem was I added database logging code to my constructor for a DB object  and this seemed to cause havoc on my azure deployment profile    FYI - I simplified this example  in the real code this was turned off in production  but still in the code   public class MyDB   DbContext       public MyDB                  this Database Log   x   gt    Debug WriteLine x

User · Answer

This also happens when you copy a web page from one solution to another  then you run your solution and find out that it has a different connection string name in the webconfig  Then you carelessly change the name of the connection string in the properties panel in the design view of the page    Better to just change it in the code portion instead of the design

User · Answer

I solved this by changing the connection string on the publish settings of my ASP NET Web Api   Check my answer on this post  How to fix error   Format of the initialization string does not conform to specification starting at index 0

User · Answer

In my case the problem was in the encoding of the connection string  In local it worked without problems  but when installing it in a production environment it showed this error  My application allows to set the connection string using a form and when the connection string was copied from local to production  invisible characters were introduced and although the connection string was visually identical at the byte level it was not  You can check if this is your problem by following these steps   Copy your connection string to Notepad    Change the codification to ANSI  In Menu Encoding gt Encode to ANSI  Check if additional characters are included   If these characters have been included  delete them and paste the connection string again

User · Answer

Referencing the full sp path resolved this issue for me   var command   new SqlCommand  DatabaseName dbo StoredProcedureName   conn

[c#] Format of the initialization string does not conform to specification starting at index 0

Examples related to c#

Examples related to asp.net

Examples related to sql-server-2008