| Server
rejected the connection; Access to selected database has been denied; Login
failed. When starting any MaxRecall program and you receive MaxRecall's
database not started error along with the standard connection failure error
plus error 4060: Please read the entire solution before
running any SQL commands or stored procedures. Basically there's something wrong with the tpo login for the
MaxRecall database. Server rejected the connection; Access to selected database has been denied; Login failed. When starting any MaxRecall program and you receive MaxRecall's database not started error along with the standard connection failure error plus error 4060. >>>>> Please read the entire solution before running any SQL commands or stored procedures. <<<<< >>>>> Basically there's something wrong with the tpo login for the MaxRecall database. <<<<< Error occurs when trying to start any MaxRecall program after system restore / server crash. Especially if things had to be re-installed and there weren't proper SQL backups available so the maxrecall mdf file had to be attached instead of restored. You may have trouble creating or updating the tpo login in SQL. It might look like it's there but SQL might act like it's trying to create a new login as if the tpo login didn't already exist. ========================================================================== You may be able to resolve the problem without having to run any SQL statements or stored procedures by just going through the Security interfaces in SQL but some problems may prevent that from working correctly. ========================================================================== Make sure the tpo login is configured correctly and has the necessary access levels to the MaxRecall database - you may need to refer to our initial install instructions to find out what they are. Make sure to give access to the tpo login in the MaxRecall database. ========================================================================== Make sure that the password entered in SQL for the tpo login is the same password that is in mrhide/ortcloud. Or that you at least know what the password is in SQL then update mrhide/ortcloud with the new value (you'll need dbset.bat and dbset.exe, plus any DLLs used by the EXE). ========================================================================== Don't forget to make sure that TCP/IP is enabled in the SQL Network configuration options. If Named Pipes is also enabled then make sure to update the DB Source in mrhide/ortcloud to force the use of TCP/IP. ========================================================================== Make sure that the default database for the tpo login is NOT the maxrecall database. If it is and there's a problem with the maxrecall database then you won't be able to connect to SQL with the tpo login. ========================================================================== If you're having trouble correcting the tpo login through the GUI but are able to run SQL statements then you might try the sp_change_users_login or ALTER USER command. The sp may not work in new versions of SQL. The following commands help with orphaned users - To map the tpo user in the maxrecall database to the tpo login try |
EXEC sp_change_users_login 'Auto_Fix', 'tpo', NULL, '8track' or ALTER USER tpo WITH LOGIN = tpo If that doesn't work then look at some of the other options for the sp_change_users_login and ALTER USER procedures. ========================================================================== If you're not able to log in to the SQL GUI at all, especially because there's an issue with the user's default database then try the following - SQL Server 2005 and later versions you can use the sqlcmd utility to change the default database in SQL Server 2005. To do this, follow these steps: 1 - Click Start, click Run, type cmd, and then press ENTER. 2 - Use one of the following methods, depending on the kind of authentication that the SQL Server login uses: - If the SQL Server login uses Microsoft Windows authentication to connect to the instance, type the following at the command prompt, and then press ENTER: sqlcmd -E -S InstanceName -d master - If the SQL Server login uses SQL Server authentication to connect to the instance, type the following at the command prompt, and then press ENTER: sqlcmd -S InstanceName -d master -U SQLLogin -P Password Note: InstanceName is a placeholder for the name of the SQL Server 2005 instance to which you are connecting. SQLLogin is a placeholder for the SQL Server login whose default database has been dropped. Password is a placeholder for the SQL Server login password. 4 - At the sqlcmd prompt, type the following, and then press ENTER: ALTER LOGIN SQLLogin WITH DEFAULT_DATABASE = AvailDBName Note AvailDBName is a placeholder for the name of the existing database that can be accessed by the SQL Server login in the instance. 5 - At the sqlcmd prompt, type GO, and then press ENTER. ========================================================================== Also see solutions 17 and 184 for other database connection issues and solutions. |