Unable to connect to the database - Revision history

Sunjammer: Restored TOC

2015-08-23T12:33:39Z

Restored TOC

Kelamor: Add language bar

2011-11-26T05:26:02Z

Add language bar

Sunjammer: /* Other Miscellaneous Solutions */ Removing dead link

2011-08-10T21:29:24Z

‎Other Miscellaneous Solutions: Removing dead link

Kelamor: Undo revision 15643 by Kelamor (Talk)

2011-02-03T01:55:45Z

Undo revision 15643 by Kelamor (Talk)

Show changes

Kelamor: Create russian page

2011-02-03T01:52:02Z

Create russian page

Show changes

FollowTheGourd: /* Permissions issues */

2011-01-12T03:31:10Z

‎Permissions issues

FollowTheGourd: Running the toolset on XP as a power user instead of using the admin account as per the forum thread

2011-01-12T03:28:27Z

Running the toolset on XP as a power user instead of using the admin account as per the forum thread

FollowTheGourd: another log file

2011-01-02T20:57:11Z

another log file

FollowTheGourd: /formatting /

2011-01-02T20:07:30Z

‎formatting

FollowTheGourd: Mentioning the ERRORLOG file's information.

2011-01-02T20:06:44Z

Mentioning the ERRORLOG file's information.

@@ Line 4: / Line 4: @@
 This error is kind of like the "Service Engine" light on your vehicle.  When the service engine light starts flashing, it means something is wrong, but it is a very general warning that does not give you much information on what is wrong, just that something is wrong.  The cause of it could be anything from a loose gas cap to a failed spark plug to some bad sensor.
 When it comes to the cannot connect error, it can range from the long file path issue to interference from UAC, to permissions issues, to a conflict with an existing installation of SQL Server, to registry entries, to the location of the installation file on your computer. The list is long. Here is a troubleshooting guide to try and help you diagnose what particular problem is vexing you and how to repair it.  If the troubleshooting is getting you nowhere, the [[#Full Manual Install|full manual install]] is another method that may be more effective, as you take things into your own hands and have better visibility to errors.
@@ Line 19: / Line 19: @@
 You also may have to exit and open c:/ again to make sure that it took affect. This would allow the installer to access the games file to properly install MSSQL Server Express.
 {| cellspacing = "5" cellpadding = "2" class="toc"
-__NOTOC__
-{| cellspacing = "5" cellpadding = "2" align="center" class="toc"
 |- align="center"
 | style="border:solid 1px" |  [[#Did the database get restored?|Did the database get restored / created?]]
@@ Line 52: / Line 50: @@
+|
 |}
 ===Is the Database Service Running===
@@ Line 69: / Line 66: @@
 ===Did SQL Server Install?===
 Check your Start menu and see if it installed at all.  Go to Start>>Program Files>>Microsoft SQL Server 2005.  If nothing exists here then there are two basic explanations:
 # When you ran the installer, you may have unchecked the option to Install MSSQL Express 2005 SP3.  If this is the case.  Try running the toolset installer a second time, make sure that you leave that option checked so that the installer will attempt to install SQL Server 2005.
@@ Line 76: / Line 74: @@
 ===Did the database get restored?===
 Check the toolset installation directory for the restored database files.  Depending on where you installed the Game and Toolset, they will be in a location similar to
 {{dashedborder|C:\Program Files\Dragon Age\tools\toolssql\Data\ <--- version 1.00 installed under the Tools folder
@@ Line 95: / Line 94: @@
 ===Is the Toolset correctly pointing to database?===
 Run [[Configure Toolset]] to send the toolset in the right direction and test the database connection.
@@ Line 110: / Line 110: @@
 ==Full Manual Install==
 Manual database installation works almost every time.  If it does not, it should at least give you clues as to why it is failing, which you do not generally get when using the toolset installer.  If this "cannot connect to the database" error is frustrating you and you want to just make it work, and don't want to keep troubleshooting, this is probably your best bet:
@@ Line 116: / Line 117: @@
 # '''Manually install SQL Server and restore the database'''
 #:It is not as hard as it may sound, and is documented [[manual database installation|here]].  Basically, when you do this, you are taking control of the two steps that you told the installer not to do, and doing them on your own.  This is effective as this way you can babysit the installation process.  Running the SQL installer this way will throw more explicit errors at you when it is having problems, making it easier to diagnose the problems and find solutions.
 '''Why does this work?'''
@@ Line 129: / Line 129: @@
 === MSSQL Server cannot install to compressed or encrypted folders ===
 SQL Server Setup cannot install files.
@@ Line 159: / Line 160: @@
 ==Other Miscellaneous Solutions==
 * You can use SQL Server Express 2008 instead of 2005.  It is better suited to some of the permissions issues that occur in Vista and Windows 7.  Many users have installed SQL Server Express 2008 and are using it instead of 2005.  You could download it and follow the instructions [[Manual database installation|here]] substituting 2008 for 2005.
 * You can try setting up your database separately from the toolset installer. See [[Manual database installation]] for the steps needed to install MSSQL Express 2005 and configure it for use with the toolset manually.  Users have been successful by setting up the toolset this way.

@@ Line 181: / Line 181: @@
 [[#top|&uarr; Return to top]]
 [[Category:Toolset bugs]]
 [[Category:Database]]

← Older revision		Revision as of 21:29, 10 August 2011
Line 178:		Line 178:

	*Some users have been successful simply installing from a more direct path (eg place the installer in C:\DAInstall and then run the exe file from that location rather than from My Documents or a similar long path).		*Some users have been successful simply installing from a more direct path (eg place the installer in C:\DAInstall and then run the exe file from that location rather than from My Documents or a similar long path).
−
−	*[http://social.bioware.com/project/2804/ NErWOnek's pictorial guide] may help.

	[[#top\|↑ Return to top]]		[[#top\|↑ Return to top]]

@@ Line 154: / Line 154: @@
 *On Vista systems the toolset may need administrator privileges to read the database where it's installed but fail to prompt you for them. Try right-clicking the toolset's shortcut and selecting "Run as Administrator" from the dropdown menu.
-* On Windows XP systems, you may need to run the toolset as the Administrator by right-clicking on the toolset's shortcut, selecting the "Run as..." menu item, and then select "The following user" radio button where you can enter the password for the Administrator account. You can also run the toolset with a power user account, but you'll have to add a new database user to authenticate your user account with. An easy way is to run the Server Surface Area Configuration tool that should have been installed with the toolset and Microsoft SQL Server 2005 Express. Launch it as a privileged account and then click the "Add New Administrator" link. For "user to provision", enter your Windows account name and grant them the SysAdmin role from the window below. For possibly more information, see the forum thread [http://social.bioware.com/forum/1/topic/8/index/5517509/ Anyone able to run the toolset as NOT administrator in XP?].
+* On Windows XP systems, you may need to run the toolset as the Administrator by right-clicking on the toolset's shortcut, selecting the "Run as..." menu item, and then select "The following user" radio button where you can enter the password for the Administrator account. You can also run the toolset with a power user account, but you'll have to add a new database user to authenticate your user account with. An easy way is to run the Server Surface Area Configuration tool that should have been installed with the toolset and Microsoft SQL Server 2005 Express. Launch it with the Administrator account and then click the "Add New Administrator" link. For "user to provision", enter your Windows account name and grant them the SysAdmin role from the window below. For possibly more information, see the forum thread [http://social.bioware.com/forum/1/topic/8/index/5517509/ Anyone able to run the toolset as NOT administrator in XP?]. If you were previously using the toolset under another account, then don't forget to check back in any outstanding resources so you can work on them from the current Windows account.
 [[#top|&uarr; Return to top]]

@@ Line 154: / Line 154: @@
 *On Vista systems the toolset may need administrator privileges to read the database where it's installed but fail to prompt you for them. Try right-clicking the toolset's shortcut and selecting "Run as Administrator" from the dropdown menu.
-* On Windows XP systems, you may need to run the toolset as the Administrator by right-clicking on the toolset's shortcut, selecting the "Run as..." menu item, and then select "The following user" radio button where you can enter the password for the Administrator account.
+* On Windows XP systems, you may need to run the toolset as the Administrator by right-clicking on the toolset's shortcut, selecting the "Run as..." menu item, and then select "The following user" radio button where you can enter the password for the Administrator account. You can also run the toolset with a power user account, but you'll have to add a new database user to authenticate your user account with. An easy way is to run the Server Surface Area Configuration tool that should have been installed with the toolset and Microsoft SQL Server 2005 Express. Launch it as a privileged account and then click the "Add New Administrator" link. For "user to provision", enter your Windows account name and grant them the SysAdmin role from the window below. For possibly more information, see the forum thread [http://social.bioware.com/forum/1/topic/8/index/5517509/ Anyone able to run the toolset as NOT administrator in XP?].
 [[#top|&uarr; Return to top]]

@@ Line 8: / Line 8: @@
 When it comes to the cannot connect error, it can range from the long file path issue to interference from UAC, to permissions issues, to a conflict with an existing installation of SQL Server, to registry entries, to the location of the installation file on your computer. The list is long. Here is a troubleshooting guide to try and help you diagnose what particular problem is vexing you and how to repair it.  If the troubleshooting is getting you nowhere, the [[#Full Manual Install|full manual install]] is another method that may be more effective, as you take things into your own hands and have better visibility to errors.
-As a potential source of more information to diagnose the problem with, you could always look for connection errors in {{dashedborder|C:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ERRORLOG}}. You may have to use an administrator account to read this file. As an example ERRORLOG entry:
+As a potential source of more information to diagnose the problem with, you could always look for connection errors in both {{dashedborder|C:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ERRORLOG
 <pre>
 -01-02 11:32:15.08 Logon       Error: 18456, Severity: 14, State: 38.