|
BugNET Forums
 |  | |
| | |
| | |
| | |
 | | |
|
|
|
| SQL 2005 instead of SQL 2000 |
|
|
I have a new box with Windows 2003 installed. There is an instance of SQL 2005 (I think), but I don't know how to get to it, so I installed SQL 2000.
Created the db, and all that. When I try to install, I get a LOT of errors, and they are all looking at 2005. How do I make it look at 2000 instead?
Installing BugNET
Version: 0.7.820.0
Installation Status Report
Installing Version: 0.7.820.0
Installing Membership Provider... - 00:00:00
Error!
Error in file:C:\BugNET\Install\dbscripts\InstallCommon.sql
Message:An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Error!
Error in file:C:\BugNET\Install\dbscripts\InstallMembership.sql
Message:An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Error!
Error in file:C:\BugNET\Install\dbscripts\InstallProfile.sql
Message:An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Error!
Error in file:C:\BugNET\Install\dbscripts\InstallRoles.sql
Message:An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Installing BugNET Database... - 00:00:00.0312500
Error!
Error in file:C:\BugNET\Install\dbscripts\BugNET.Schema.SqlDataProvider.sql
Message:An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Installing BugNET Default Data... - 00:00:00.0312500
Error!
Error in file:C:\BugNET\Install\dbscripts\BugNET.Data.SqlDataProvider.sql
Message:An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Creating Administrator Account... - 00:00:00.0468750
Server Error in '/BugNet' Application.
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. |
Stack Trace:
[SqlException (0x80131904): An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)]
System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +437
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +82
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105
System.Data.SqlClient.SqlConnection.Open() +111
System.Web.DataAccess.SqlConnectionHolder.Open(HttpContext context, Boolean revertImpersonate) +84
System.Web.DataAccess.SqlConnectionHelper.GetConnection(String connectionString, Boolean revertImpersonation) +197
System.Web.Security.SqlMembershipProvider.CreateUser(String username, String password, String email, String passwordQuestion, String passwordAnswer, Boolean isApproved, Object providerUserKey, MembershipCreateStatus& status) +3612
System.Web.Security.Membership.CreateUser(String username, String password, String email, String passwordQuestion, String passwordAnswer, Boolean isApproved, Object providerUserKey, MembershipCreateStatus& status) +224
System.Web.Security.Membership.CreateUser(String username, String password, String email) +30
BugNET.Install.Install.InstallBugNET() +368
BugNET.Install.Install.InstallApplication() +1449
BugNET.Install.Install.Page_Load(Object sender, EventArgs e) +260
System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +15
System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +34
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +47
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1061
|
Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42 |
|
|
|
| |
|
|
| Re: SQL 2005 instead of SQL 2000 |
|
|
You need to set the connection string in the web config to point to the proper database.
Davin Dubeau
BugNET - Core Developer
|
|
|
|
| |
|
|
| Re: SQL 2005 instead of SQL 2000 |
|
|
Davin wrote
You need to set the connection string in the web config to point to the proper database. |
therein lies my problem, I'm not sure how to point to the 2000 SQL install.
from web.config
<connectionStrings>
<clear />
<add name="LocalSqlServer" connectionString="server=local;database=BugNET;uid=bugnet;pwd=bugnet" providerName="System.Data.SqlClient"/>
</connectionStrings>
the 2000 install is called local. Do I need to create something else? |
|
|
|
| |
|
|
| Re: SQL 2005 instead of SQL 2000 |
|
|
It might have installed as an instance local\instancename.
Why not just use the sql 2005?
Davin Dubeau
BugNET - Core Developer
|
|
|
|
| |
|
|
| Re: SQL 2005 instead of SQL 2000 |
|
|
Davin wrote
It might have installed as an instance local\instancename.
Why not just use the sql 2005? |
I don't have any way to administer SQL 2005. Does it automatically install when you have Windows 2003? |
|
|
|
| |
| | |
| | |
| | |
|
Forum Policy
These Discussion Forums are dedicated to the discussion of the BugNET issue tracker.
For the benefit of the community and to protect the integrity of the project, please observe the following posting guidelines:
1. No Advertising.
2. No Flaming or Trolling.
3. No Profanity, Racism, or Prejudice.
4. Site Moderators have the final word on approving/removing a thread or post or comment.
5. English language posting only, please.
|
|