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

Question

I uploaded my site on godaddy shared host  I can access this database from my management studio  I can t access this database from my site  I get following error      Format of the initialization string does not conform to specification starting at index 0    My connection string is in web config and it looks like this    lt connectionStrings gt       lt add name  mcn  connectionString  Data Source mydatabase db 8706856 hostedresource com  Initial Catalog mydatabase  User ID username  Password xyz   providerName  System Data SqlClient    gt       lt  connectionStrings gt    What cause this error  I have also tried to write    Data Source  local

User · Answer

I was having the same issue when accessing a published ASP.NET Web Api. In my case, I realized that when I was about to publish the Web Api, I had not indicated a connection string inside the Databases section:

So I generated it using the three dot button, and after publishing, it worked.

What is weird, is that for a long time I am pretty sure that there was no connection string in that configuration but it still worked.

User · Answer

I originally was calling the connection string value as shown below  VB NET  and got the error being mentioned    Using connection As New SqlConnection  connectionStringName          more code would go here     End Using   adding a reference to System Configuration and updating my code as shown below was my solution  The connection string was not the problem since others controls used it without any issues  SqlDataSource   Using connection As New SqlConnection ConfigurationManager ConnectionStrings  connectionStringName   ConnectionString          more code would go here    End Using

User · Answer

For my case  the culprit was the semicolon and double quotes in the password for prod DB  Our IT team use some tool to generate passwords  so it generated one with the semicolon and double quotes Connectionstring looks like   lt add key  BusDatabaseConnectionString  value  Data Source myserver Initial Catalog testdb User Id Listener Password BlaBla     qrk  gt    Got the password changed and it worked

User · Answer

I had the same error message in my localhost development with my Visual Studio  Note that everything was working when released with Microsoft Release Management  MRM   I fixed my situation by changing the initial value that was a MRM reference   My App config initial value was the following      lt connectionStrings gt       lt add name  BDORA  connectionString    token3      gt     lt  connectionStrings gt    Locally  the application execution could not interpret the token3 reference to its real value in Tokens xml  To make it work on my localhost  I had to force the value from token3 in Tokens xml into the App config file

User · Answer

My fix was suprisingly simple and another one of those obvious when you realise what you ve done  I was manually building the configuration using  NET Core Standard in the following fashion   var configurationBuilder   new ConfigurationBuilder    var root   configurationBuilder Build       and had forgotten to include the appsettings json file that had my configuration settings in it  configurationBuilder AddJsonFile  appsettings json   false     Once added  all started working once more

User · Answer

If you re using EF and Publish Profiles  you could have a blank connection string entry in your publish profile   Annoying but entirely possible

User · Answer

I was getting this exception  fixed it by adding throwIfV1Schema  false to my DbContext constructor   public class AppDb   IdentityDbContext lt User gt        public AppDb             base  DefaultConnection   throwIfV1Schema  false

User · Answer

I had this in VS2015 and my fix was to change the first line in my WebConfig from   lt  xml version  1 0  encoding  utf-8   gt    to   lt  xml version  1 0   gt    Curious

User · Answer

An unwanted single quote was my problem  Checking the connection string from the location of the index mentioned in the error string helped me spot the issue

User · Answer

Another pitfall is that connectionString sometimes refers to the name of the connection string in the app web-config and sometimes to the actual connection string itself and vice versa   Very easy to fix but sometimes hard to spot

User · Answer

I was facing the same problem and found out that my connection string had an extra double-quote character in the middle of the connection string

User · Answer

For anyone who may stumble across this thread while trying to fix this same error that results by running Enable-Migrations  chances are none of the solutions above will help you  I tried them all    I encountered this same issue in Web API 2 after running this in PM console   Enable-Migrations -EnableAutomaticMigrations -ConnectionString IdentityConnection -ConnectionProviderName System Data SqlClient -Force   I fixed it by changing it to actually use the ApplicationDbContext created in IdentityModels   Enable-Migrations -ContextTypeName ApplicationDbContext -EnableAutomaticMigrations -Force   The interesting thing is not only does this reference the same exact connection string  but the constructor includes code that 4castle said was a potential fix  i e   the throwIfV1Schema  false suggestion   Note that the -Force parameter is only being used because the Configuration cs file already exists

User · Answer

None of the listed solutions in this thread worked for me   I started getting this error after I made some changes to the connection strings section of the web config file    My app connects to multiple databases    I carefully examined what changes I had made are realized I had removed the  tag at the top of my list   I restored the  tag at the top of my list of connection strings and the problem went away immediately   This site that was getting the error is a application that resides below the main site  https   www domain org MySite    This might not fix the problem for everyone  but it did resolve the problem for me

User · Answer

It might help to see what the actual connection string is  Add to Global asax   throw new Exception ConfigurationManager ConnectionStrings  mcn   ConnectionString     If the actual connection string is   ReplacableToken mcn-Web config Connection String 0   that would explain the problem

User · Answer

I have wasted 1 5 working days on this error and in the end a coworker solved the issue by replacing User Id by Uid and password by Pwd  The updated connection string for  Net was the error for me

User · Answer

In my Case  it is because of having more than one connection string in your Solution  one for your current project and the other one for a startup project in your Solution  for more information please refer to Telerik report not working here we have the same situation

User · Answer

I got below error when trying to launch application    Format of the initialization string does not conform to specification starting at index 57    And during my research I found this stack and I was able to fix this error by looking at the web config file and found there was a extra string in the passowrd  Once I removed the string I was able to access the website without any error

User · Answer

My issue was that my web config file kept a reference to a deleted entity model connection so check there are not any outdated connection strings

[asp.net] How to fix error ::Format of the initialization string does not conform to specification starting at index 0::

Examples related to asp.net

Examples related to connection-string