All these attempts gave errors that the connection string was invalid.to Server= (with and without port) this did not work either. Our initial attempt was to replace with the IP-address to the new SQL Server (with and without port).In the application we needed to get back online: The initial connection string, that worked fine with the old SQL server before it crashed, was: DSN= UID= PWD= Database= We created a user and gave access to all the databases by giving ownership and db_datareader and db_datawriter to the user for all the relevant databases, and by granting rights under User Mapping. We set up a new SQL Server using SQL Server Express 2014 and attached the.
Here is a summarization of our efforts to make this work: Nor did Integrated Security=yes or Trusted_connection=yes.
This gives me the impression that there is some encryption problem(?), and that the SQL Server tries to decrypt the password with the wrong key or something, and by chance uses the correct key in certain circumstances.Īdding Integrated Security=SSPI, to the connection strings, did not help. We've tried changing the passwords: in which case neither connection worked. We've made sure the user has access to both databases under *User Mapping* and by right clicking the databases themselves, going to Properties > Permissions, and granting everything. We've tried changing the order of the connections, so that database B goes first, but it still fails at B so it is NOT a matter of a limit to the number or frequency of connections. Source = Microsoft OLE DB Provider for SQL Server What puzzles me is that it claims wrong password when the same password worked fine less than a second before, when it connected to the other database.ĭoes this have anything to do with the limitations of SQL Server Express? Application log file Microsoft OLE DB Provider for SQL Serverĭescription = Login failed for user 'goa'.
Both databases are on the same SQL Server instance. The user does have access to both databases, and we are able to log in with that user in SQL Server Management Studio and do anything with either of the databases. The only difference between the connection string that succeeds and the one that fails is the database. Reason: Password did not match that for the login provided. The SQL Server log files shows the following: The application successfully connects and reads data from one of the databases, but fails with error: "Login failed for user 'goa'." on another database. Provider=sqloledb Data Source= Network Library=DBMSSOCN Initial Catalog= User ID= Password= We changed the connection string in the application to use the new SQL Server and the new user. We created a user and gave access to all the databases. We've set up a new SQL Server using SQL Server Express 2014 and attached the. We need to get a very important application working again this is on a different server. Our SQL Server crashed and burned, the hard drives destroyed.