PDA

View Full Version : مشکل با کانکت شدن به دیتابیس



lvlostafa7
شنبه 24 آبان 1393, 22:31 عصر
سلام دوستان

بنده دیتا بیس پروژه رو ساختم و به پروژه اضافه کردم و با استفاده از Membership کد نویسی صفحه ثبت نام رو نوشتم
و کدهای لازمه رو به فایل web.config اضافه کردم
اما متاسفاته با ارور زیر مواجه شدم
و اما یک سوال دیگه راهی هست Sql Server 2008 r2 managment studio رو روی ویندوز 8 نصب کنم؟



Server Error in '/Example' Application.

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

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.

SQLExpress database file auto-creation error:

The connection string specifies a local Sql Server Express instance using a database location within the application's App_Data directory. The provider attempted to automatically create the application services database because the provider determined that the database does not exist. The following configuration requirements are necessary to successfully check for existence of the application services database and automatically create the application services database:



If the application is running on either Windows 7 or Windows Server 2008R2, special configuration steps are necessary to enable automatic creation of the provider database. Additional information is available at: http://go.microsoft.com/fwlink/?LinkId=160102. If the application's App_Data directory does not already exist, the web server account must have read and write access to the application's directory. This is necessary because the web server account will automatically create the App_Data directory if it does not already exist.
If the application's App_Data directory already exists, the web server account only requires read and write access to the application's App_Data directory. This is necessary because the web server account will attempt to verify that the Sql Server Express database already exists within the application's App_Data directory. Revoking read access on the App_Data directory from the web server account will prevent the provider from correctly determining if the Sql Server Express database already exists. This will cause an error when the provider attempts to create a duplicate of an already existing database. Write access is required because the web server account's credentials are used when creating the new database.
Sql Server Express must be installed on the machine.
The process identity for the web server account must have a local user profile. See the readme document for details on how to create a local user profile for both machine and domain accounts.



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): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)]
System.Data.SqlClient.SqlInternalConnection.OnErro r(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) +5295167
System.Data.SqlClient.TdsParser.ThrowExceptionAndW arning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) +242
System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean withFailover) +5307115
System.Data.SqlClient.SqlInternalConnectionTds.Att emptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover) +145
System.Data.SqlClient.SqlInternalConnectionTds.Log inNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout) +920
System.Data.SqlClient.SqlInternalConnectionTds.Ope nLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance) +307
System.Data.SqlClient.SqlInternalConnectionTds..ct or(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions) +434
System.Data.SqlClient.SqlConnectionFactory.CreateC onnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions) +5309659
System.Data.ProviderBase.DbConnectionFactory.Creat eNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions) +38
System.Data.ProviderBase.DbConnectionFactory.TryGe tConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection) +5311874
System.Data.ProviderBase.DbConnectionClosed.TryOpe nConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions) +143
System.Data.SqlClient.SqlConnection.TryOpen(TaskCo mpletionSource`1 retry) +83
System.Data.SqlClient.SqlConnection.Open() +96
System.Web.Management.SqlServices.GetSqlConnection (String server, String user, String password, Boolean trusted, String connectionString) +76

[HttpException (0x80004005): Unable to connect to SQL Server database.]
System.Web.Management.SqlServices.GetSqlConnection (String server, String user, String password, Boolean trusted, String connectionString) +131
System.Web.Management.SqlServices.SetupApplication Services(String server, String user, String password, Boolean trusted, String connectionString, String database, String dbFileName, SqlFeatures features, Boolean install) +89
System.Web.Management.SqlServices.Install(String database, String dbFileName, String connectionString) +27
System.Web.DataAccess.SqlConnectionHelper.CreateMd fFile(String fullFileName, String dataDir, String connectionString) +386



Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.17929

scarce
شنبه 24 آبان 1393, 22:58 عصر
سلام
برای استفاده از دیتابیس که در فولدر app_data قرار میگیره شما باید مجوز دسترسی خواندن و نوشتن این فولدر رو به iis بدی

اما بهترین روش اینه که شما دیتابیس رو در Sql server ابتدا attach کنید . بعد کانشکن استرینگ رو هم تغییر بدید

یا لطفا کانکشن استرینگ که استفاده کردید رو ارسال کنید یا فایل web.config ضمیمه کنید

lvlostafa7
شنبه 24 آبان 1393, 23:08 عصر
connectionStrings>
<add name="BilBoardDBEntities" connectionString="metadata=res://*/Model1.csdl|res://*/Model1.ssdl|res://*/Model1.msl;provider=System.Data.SqlClient;provider connection string=&quot;data source=mosi;initial catalog=BilBoardDB;integrated security=True;MultipleActiveResultSets=True;App=En tityFramework&quot;" providerName="System.Data.EntityClient" />
<add name ="cnn" connectionString="data source=mosi;initial catalog=BilBoardDB;integrated security=True;MultipleActiveResultSets=True;" providerName="System.Data.SqlClient"/>
</connectionStrings

این کانکشن استرینگ که موجوده
در مورد سوال دوم اطلاعاتی ندارین؟

lvlostafa7
یک شنبه 25 آبان 1393, 13:36 عصر
کسی نبود کمک کنه؟؟؟؟

scarce
یک شنبه 25 آبان 1393, 16:36 عصر
connectionStrings>
<add name="BilBoardDBEntities" connectionString="metadata=res://*/Model1.csdl|res://*/Model1.ssdl|res://*/Model1.msl;provider=System.Data.SqlClient;provider connection string=&quot;data source=mosi;initial catalog=BilBoardDB;integrated security=True;MultipleActiveResultSets=True;App=En tityFramework&quot;" providerName="System.Data.EntityClient" />
<add name ="cnn" connectionString="data source=mosi;initial catalog=BilBoardDB;integrated security=True;MultipleActiveResultSets=True;" providerName="System.Data.SqlClient"/>
</connectionStrings

این کانکشن استرینگ که موجوده
در مورد سوال دوم اطلاعاتی ندارین؟

لطفا وارد سایت http://www.connectionstrings.com/ شوید و براساس نسخه Sql server خود کانکشن استرینگ مورد نظر خودتون رو بسازید

بطور مثال:
فرض کنید شما اول دیتابیس خودتون در Sql Server با نام dbHelp ، بارگزاری یا attach کردین و یوزر sa شما در دیتابیس دارای کلمه عبور 123654 میباشد و نام سرور شما هم MSSQLSERVERNEW باشد،شما میتونید با استفاده از کانکشن استرینگ زیر به دیتابیس متصل شوید.
البته شما میتوانید از یوزرنیم و کلمه عبور اختصاصی خودتون استفاده کنید



<add connectionString="Data Source=localhost\MSSQLSERVERNEW;Initial Catalog=dbHelp;User ID=sa;password=123654" name="dbHelpConn" />/


چند نکته بسیار مهم
حتما باید نسخه sql server شما روی کامپیوتر خودتون هم نسخه sql server روی سرور یا نسخه آن کمتر از نسخه سرور باشه

یعنی اگر روی کامپیوتر شما نسخه sql server 2012 11.0.2100 بود روی سرور هم باید همین باشه اگر بیشتر باشه خطای بالا نمایش داده میشه

لطفا این موارد رو بررسی نمایید