# Connection string error **URL:** \ **Category:** V5 Question\ **Created:** [September 27, 2026, 2:38am UTC](https://forum.sambapos.com/t/connection-string-error/32319 "2026-09-27T02:38:14Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![MathiasMaghanga](https://forum.sambapos.com/letter_avatar_proxy/v4/letter/m/74df32/32.png) [@MathiasMaghanga](https://forum.sambapos.com/u/MathiasMaghanga)\ **Post date:** [September 27, 2026, 2:38am UTC](https://forum.sambapos.com/t/connection-string-error/32319/1 "2026-09-27T02:38:14Z")
database crashed and did a repair of the mdf file and it was successful how ever when i put the connection string to link the pos to the database it throws an error and i confirmed both users exist and ,are public and db owner and the db has both windows and sql server authentication enabled.. the only thing that works is using this as the connection string Data Source=MATHIAS-PC\RMSPOS;Initial Catalog=RmsPos1;Integrated Security=True; it accepts windows authentication and not sql server authentication . Data Source=MATHIAS-PC\RMSPOS; User Id=sa; Password=icui4cu9669; Database=RmsPos1; ---
**Author:** ![Memo](https://forum.sambapos.com/user_avatar/forum.sambapos.com/memo/32/55443_2.png) [@Memo](https://forum.sambapos.com/u/Memo)\ **Post date:** [September 27, 2026, 4:54am UTC](https://forum.sambapos.com/t/connection-string-error/32319/2 "2026-09-27T04:54:59Z")
What error was logged? Post it here. ---
**Author:** ![MathiasMaghanga](https://forum.sambapos.com/letter_avatar_proxy/v4/letter/m/74df32/32.png) [@MathiasMaghanga](https://forum.sambapos.com/u/MathiasMaghanga)\ **Post date:** [September 27, 2026, 5:17am UTC](https://forum.sambapos.com/t/connection-string-error/32319/3 "2026-09-27T05:17:25Z")
Juts the norma connection string error. ---
**Author:** ![MathiasMaghanga](https://forum.sambapos.com/letter_avatar_proxy/v4/letter/m/74df32/32.png) [@MathiasMaghanga](https://forum.sambapos.com/u/MathiasMaghanga)\ **Post date:** [September 27, 2026, 5:22am UTC](https://forum.sambapos.com/t/connection-string-error/32319/4 "2026-09-27T05:22:45Z")
Top-level Exception Type: System.Data.ProviderIncompatibleException Message: An error occurred while getting provider information from the database. This can be caused by Entity Framework using an incorrect connection string. Check the inner exceptions for details and ensure that the connection string is correct. Source: EntityFramework Stack Trace: at System.Data.Entity.ModelConfiguration.Utilities.DbProviderServicesExtensions.GetProviderManifestTokenChecked(DbProviderServices providerServices, DbConnection connection) at System.Data.Entity.ModelConfiguration.Utilities.DbConnectionExtensions.GetProviderInfo(DbConnection connection, DbProviderManifest& providerManifest) at System.Data.Entity.DbModelBuilder.Build(DbConnection providerConnection) at System.Data.Entity.Internal.LazyInternalContext.CreateModel(LazyInternalContext internalContext) at System.Data.Entity.Internal.RetryLazy`2.GetValue(TInput input) at System.Data.Entity.Internal.LazyInternalContext.InitializeContext() at System.Data.Entity.Internal.InternalContext.GetEntitySetAndBaseTypeForType(Type entityType) at System.Data.Entity.Internal.Linq.InternalSet`1.Initialize() at System.Data.Entity.Internal.Linq.InternalSet`1.get_InternalContext() at System.Data.Entity.Infrastructure.DbQuery`1.System.Linq.IQueryable.get\_Provider() at System.Linq.Queryable.Count[TSource](IQueryable`1 source) at Rms.Infrastructure.Data.SQL.EFWorkspace.CountT at Rms.Presentation.Services.Common.DataGeneration.DataCreationService.ShouldCreateData() at Rms.Presentation.Services.Common.DataGeneration.DataCreationService.CreateData() at Rms.Presentation.Bootstrapper.InitializeShell() Inner Exception 1 Type: System.Data.ProviderIncompatibleException Message: The provider did not return a ProviderManifestToken string. Source: System.Data.Entity Stack Trace: at System.Data.Common.DbProviderServices.GetProviderManifestToken(DbConnection connection) at System.Data.Entity.ModelConfiguration.Utilities.DbProviderServicesExtensions.GetProviderManifestTokenChecked(DbProviderServices providerServices, DbConnection connection) Inner Exception 2 Type: System.Data.SqlClient.SqlException Message: Login failed for user ‘sa’. Source: .Net SqlClient Data Provider Stack Trace: at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, DbConnectionPool pool, String accessToken, Boolean applyTransientFaultHandling, SqlAuthenticationProviderManager sqlAuthProviderManager) at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions) at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions) at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection) at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection) at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection) at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection) at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection) at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions) at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions) at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry) at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry) at System.Data.SqlClient.SqlConnection.Open() at System.Data.SqlClient.SqlProviderServices.UsingConnection(SqlConnection sqlConnection, Action`1 act) at System.Data.SqlClient.SqlProviderServices.UsingMasterConnection(SqlConnection sqlConnection, Action`1 act) at System.Data.SqlClient.SqlProviderServices.GetDbProviderManifestToken(DbConnection connection) at System.Data.Common.DbProviderServices.GetProviderManifestToken(DbConnection connection) ---
**Author:** ![Memo](https://forum.sambapos.com/user_avatar/forum.sambapos.com/memo/32/55443_2.png) [@Memo](https://forum.sambapos.com/u/Memo)\ **Post date:** [September 27, 2026, 9:50am UTC](https://forum.sambapos.com/t/connection-string-error/32319/5 "2026-09-27T09:50:02Z")
Either mixed-mode is not enabled for SQL Server or you have the wrong password. From a command prompt on the computer running SQL Server, run the following command: `sqlcmd -U sa -P sa-password-here -N o` replace “sa-password-here” with the password of the sa account You should see `1>` if login is successful. If not then follow B here: > **[Change Server Authentication Mode - SQL Server](https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/change-server-authentication-mode?view=sql-server-ver17&tabs=ssms)** > > Learn how to change the server authentication mode in SQL Server. You can use either SQL Server Management Studio or Transact-SQL for this task. Ensure the proper password is set: `ALTER LOGIN sa WITH PASSWORD = 'sa-password-here';` ---
**Author:** ![MathiasMaghanga](https://forum.sambapos.com/letter_avatar_proxy/v4/letter/m/74df32/32.png) [@MathiasMaghanga](https://forum.sambapos.com/u/MathiasMaghanga)\ **Post date:** [September 27, 2026, 3:05pm UTC](https://forum.sambapos.com/t/connection-string-error/32319/6 "2026-09-27T15:05:44Z")
Funny thing sa password is correct since i can log in with it to the sql sever managment studio and do queries,confirmed its mixed mode. ---
**Author:** ![Memo](https://forum.sambapos.com/user_avatar/forum.sambapos.com/memo/32/55443_2.png) [@Memo](https://forum.sambapos.com/u/Memo)\ **Post date:** [September 28, 2026, 12:14am UTC](https://forum.sambapos.com/t/connection-string-error/32319/7 "2026-09-28T00:14:14Z")
Hmm. You may have multiple instances installed. Run this in a terminal (not command prompt) and see if more than `RMSPOS` is returned: `(Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Microsoft SQL Server').InstalledInstances` ---
**Author:** ![MathiasMaghanga](https://forum.sambapos.com/letter_avatar_proxy/v4/letter/m/74df32/32.png) [@MathiasMaghanga](https://forum.sambapos.com/u/MathiasMaghanga)\ **Post date:** [October 1, 2026, 11:57pm UTC](https://forum.sambapos.com/t/connection-string-error/32319/8 "2026-10-01T23:57:01Z")
> [@Memo](#): > > (Get-ItemProperty ‘HKLM:\SOFTWARE\Microsoft\Microsoft SQL Server’).InstalledInstances ![image](https://forum.sambapos.com/uploads/default/original/3X/1/3/138fea5c9cdfce8651d6715c5c61d7668d31f2aa.png) ---
**Author:** ![Memo](https://forum.sambapos.com/user_avatar/forum.sambapos.com/memo/32/55443_2.png) [@Memo](https://forum.sambapos.com/u/Memo)\ **Post date:** [October 2, 2026, 2:25am UTC](https://forum.sambapos.com/t/connection-string-error/32319/9 "2026-10-02T02:25:41Z")
You have three instances of SQL Server running. So whilst you are able to login using SSMS to _ **AN** _ instance of SQL Server using the `sa` account, the instance used for SambaPOS does not have mixed mode enabled. So you have a some options: - uninstall all intsances and all SQL dependencies (OLE, ODBC, etc.) and do a fresh install for once instance - remove the instances not related to SambaPOS (SQLEXPRESS, UTANGE) - using SSMS, connect to the RMPOS instance and enable mixed mode auth - have SambaPOS use one of the other instances instead that has mixed mode enabled Were I in your position and nothing else was using SQL Server, I would uninstall everything SQL, including SSMS, and then perform fresh instalsl everything being sure to remove the `C:\Program Files\Microsoft SQL Server` folder, too.