This has been driving me crazy for weeks and I can't seem to find any info on it... Here is the scenario:
I've developed an intranet using ASP.NET 2 and SQL Express. I have the site running on my local development computer and also the production server (Windows Server 2003 running SQL Express).
Fully functional connection string for database running on local development computer and running on production server:
Once I roll the site out, I want to be able to develop (to some degree) against the production database. But when changing my connection string to point to the production server from my development computer...
User does not have permission to perform this action.
I've found some documentation about not using the "User Instance=True;" command but without that I get:
Cannot open database "D:OfficenetApp_DataASPNETDB.MDF" requested by the login. The login failed.
Login failed for user 'WITTEGregL'.
In regular SQL Server, (not Express), I just change the connection string to work against the Local or Production database and it's really easy. I just can't figure out the trick to do the same kind of thing using SQL Express.
In my office computer network system (LAN), my Windows XP Pro PC has SQL Server Express and VB 2005 Express installed and I was granted to have the Administrator priviledge to access SQL Server Express. I tried to create a SQLCLR project in my terminal PC. 1) I tried to set up a remote connection to SQL Server Express in the following way: SQL Server EXpress => SQL Server Surface Area Configuration. In the Surface Area Configuration for Service and Connection - local, I clicked on Remote Connection of Database Engine, SQLEXPRESS and I had a "dot" on "Local and remote connections" and "Using TCP/IP only". Then I clicked on "Apply" and "OK" buttons. Then I went to restart my database engine in SQL Server Management. When I went to check SQL Server 2005 Surface Area Configuration, I saw the arrow is pointing to "Service", not to "Remote Connections"!!!??? Is it right/normal? Please comment on this matter and tell me how I can have "Remote Connecton" on after I selected it.
2) After I restarted the database engine (I guess!!), I executed the following project code (copied from a book) in my VB 2005 Express:
//////////////--Form9.vb---/////////////////
mports System.Data.SqlClient
Imports System.Data
Public Class Form9
Dim cnn1 As New SqlConnection
Private Sub Form5_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load
'Compute top-level project folder and use it as a prefix for
'the primary data file
Dim int1 As Integer = InStr(My.Application.Info.DirectoryPath, "bin")
Dim strPath As String = Microsoft.VisualBasic.Left(My.Application.Info.DirectoryPath, int1 - 1)
Dim pdbfph As String = strPath & "northwnd.mdf"
Dim cst As String = "Data Source=.sqlexpress;" & _
"Integrated Security=SSPI;" & _
"AttachDBFileName=" & pdbfph
cnn1.ConnectionString = cst
End Sub
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
Catch ex As Microsoft.VisualBasic.FileIO.MalformedLineException
MsgBox("Line " & ex.Message & _
"is not valid and will be skipped.")
End Try
Loop
'Invoke the WriteToServer method fo the sqc1 SqlBulkCopy
'object to populate FromExcel table in the database with
'the FromExcel DataTable in the project
Try
cnn1.Open()
Using sqc1 As SqlBulkCopy = New SqlBulkCopy(cnn1)
sqc1.DestinationTableName = "dbo.FromExcel"
sqc1.WriteToServer(FromExcel)
End Using
Catch ex As Exception
MessageBox.Show(ex.Message)
Finally
cnn1.Close()
End Try
'Read the FromExcel table and display results in
'a message box
Dim strQuery As String = "SELECT * " & _
"FROM dbo.FromExcel "
Dim str1 As String = ""
Dim cmd1 As New SqlCommand(strQuery, cnn1)
cnn1.Open()
Dim rdr1 As SqlDataReader
rdr1 = cmd1.ExecuteReader()
Try
While rdr1.Read()
str1 += rdr1.GetString(0) & ", " & _
rdr1.GetString(1) & ", " & _
rdr1.GetSqlInt32(2).ToString & ControlChars.CrLf
End While
Finally
rdr1.Close()
cnn1.Close()
End Try
MessageBox.Show(str1, "FromExcel")
End Sub
End Class ////////////////////////////////////////////////////////////////////////////// I got the following error messages: SecurityException was unhandled Request for the permission of type 'System. Security. Permissions.FileIOPermission,mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'failed that is pointing to the code statement "Dim int1 As Integer = InStr (My.Application.Info.DirectoryPath, "bin")." Troubleshooting tips: Store application data in isolated storage. When deploying an Office solution, check to make sure you have fulfilled all necessary requirments. Use a certificate to obtain the required permission(s). If an assembly implementing the custom security references other assemblies, add the referenced assemblies to the full trust assembly list. Get general help for the exception.
I am a new Microsoft VS.NET Express user to do the SQL Server 2005 Express and VB 2005 Express programming by using the example of a tutorial book. Please help and tell me what is wrong in my SQLCLR sep-up and project coding and how to correct the problems.
We've had two instances now where when there is a network connection timeout to the mirror from the primary, the primary db server goes to 100% utilization and refuses all connections.
The first time we had to reboot the primary, the 2nd time mirroring picked up again 10 minutes later.
There are two dbs being mirrored, one is 15gig, the other 4gig. Both boxes are running SQL2005 64 bit and Win 2003 64bit.
This happened at 6am and typically there shouldn't be a lot of traffic at that time but here are the error messages in the SQL log below.
We are going to try and move db communications to a separate network and network card - but this looks like either a bug in mirroring or a configuration problem on our end - though it works just fine other times.
Any thoughts/suggestions would be greatly appreciated.
Thanks!
Mark
SQL Error Log:
11/01/2006 06:12:12,Logon,Unknown,The server was unable to load the SSL provider library needed to log in; the connection has been closed. SSL is used to encrypt either the login sequence or all communications<c/> depending on how the administrator has configured the server. See Books Online for information on this error message: 0x2746. [CLIENT: 10.16.7.7] 11/01/2006 06:12:12,Logon,Unknown,Error: 17194<c/> Severity: 16<c/> State: 1. 11/01/2006 06:12:12,Logon,Unknown,The server was unable to load the SSL provider library needed to log in; the connection has been closed. SSL is used to encrypt either the login sequence or all communications<c/> depending on how the administrator has configured the server. See Books Online for information on this error message: 0x2746. [CLIENT: 10.16.7.7] 11/01/2006 06:12:12,Logon,Unknown,Error: 17194<c/> Severity: 16<c/> State: 1. 11/01/2006 06:12:12,Logon,Unknown,The server was unable to load the SSL provider library needed to log in; the connection has been closed. SSL is used to encrypt either the login sequence or all communications<c/> depending on how the administrator has configured the server. See Books Online for information on this error message: 0x2746. [CLIENT: 10.16.7.2] 11/01/2006 06:12:12,Logon,Unknown,Error: 17194<c/> Severity: 16<c/> State: 1. 11/01/2006 06:12:11,spid22s,Unknown,Database mirroring connection error 4 '10054(An existing connection was forcibly closed by the remote host.)' for 'TCP://PYTHAGORAS.test.com:7024'. 11/01/2006 06:12:11,spid22s,Unknown,Error: 1474<c/> Severity: 16<c/> State: 1. 11/01/2006 06:04:53,spid26s,Unknown,Database mirroring is inactive for database 'NewScribe'. This is an informational message only. No user action is required. 11/01/2006 06:04:53,spid26s,Unknown,The mirroring connection to "TCP://PYTHAGORAS.test.com:7024" has timed out for database "NewScribe" after 10 seconds without a response. Check the service and network connections. 11/01/2006 06:04:53,spid26s,Unknown,Error: 1479<c/> Severity: 16<c/> State: 1. 11/01/2006 06:04:53,spid24s,Unknown,Database mirroring is inactive for database 'HL7Transfer'. This is an informational message only. No user action is required. 11/01/2006 06:04:53,spid24s,Unknown,The mirroring connection to "TCP://PYTHAGORAS.test.com:7024" has timed out for database "HL7Transfer" after 10 seconds without a response. Check the service and network connections. 11/01/2006 06:04:53,spid24s,Unknown,Error: 1479<c/> Severity: 16<c/> State: 1.
I've implemented an SQL-CLR stored procedure which makes an HTTP connection using the WebClient class to a server where the processing on the web server takes 10 seconds.
If I fire off a bunch of requests to the stored procedure, e.g. 80 in 1 second I noticed that SQL Server 2005 (Express Edition) only allows 2 concurrent network connections at a time.
I can confirm this by looking at the timing of the results when they come back, basically I get 2 results every 10 seconds and by doing a 'netstat -a' on the web server I notice that there are never more than 2 HTTP connections from the SQL Server at a time.
Is this some sort of sheduling policy in terms of the number of concurrent external network accesses allowed by CLR objects running in SQL Server? Or some side effect of the way the WebClient class blocks in terms of waiting for a network response?
I was expecting all 80 of the requests to block waiting on a network response almost immediately and then for all 80 of them to pretty much complete and return 10-11 seconds later.
[Microsoft.SqlServer.Server.SqlProcedure]
public static int CreditAuthorisation(string Name, decimal Amount)
{
WebClient client = new WebClient();
string result = client.DownloadString("http://someserver/Test.aspx");
I have SQL Server Express and VB 2005 Express installed in a Microsoft Windows XP Pro PC that is a terminal PC in our office Network. My Network Administrator has granted my terminal PC for Administrator Use. I tried to do the ADO.NET 2.0-VB 2005 programming in my terminal PC and I could not get a remote connection in the Window Form Application via Window Authorization. I do not know how to make this kind of remote connection in my Network. Please help and advise.
I have VC++ express and MSSQL SMS express and have an application working nicely locally. The Data explorer and data connections part works really easily.
Now, I want to make the application available to my home network.
I mapped the drive where the database is and called it Z: so I could put my "release" on my other network PC and assumed it would find Z: if I mapped the shared network drive on that machine and called it Z:
But: I can't even add the mapped connection on the local machine, I get:
The file "Z:databasescalorie.mdf" is on a network path not supported for database files. An attempt to attach.....etc"
It works fine on the original F drive.......
Am I approaching this the wrong way. How should I distribute to network PCs?
I have an Excel add-in that connects to a SQL Server Express 2005database. I've decided to create a configuration piece for this add-inin Visual Studio 2005 Express. I added a data connection using the dataconnection wizard and all appeared to go well. Anyways when I attemptto open SQL Server Express to administer the database, it was corruptedand I had to restore it.I eventually got it to work correctly (I'm pretty sure I followedpretty much the same steps as before), but I was just wondering ifanyone had experienced problems like this? I find it a bit scary thatit may be that easy to corrupt the database by just creating a dataconnection.
I have a laptop and a desktop that I both installed VWD and SQL Express. from my laptop, i see my laptop's name in the Server Name under data connections, but on the desktop, I only see an older Win2K Server with SQL 2000 in the list. Anyone know why my desktop doesn't show it's NAME?I can create new tables, users and all that stuff from the Management area. Thanks
I have notebook, client server application and sql express sp2 on this notebook. Also, I know domain user login/password, but I don't know any local user name/password and I don't know any sql server user name/password. Domain user is not a local administrator on this notebook.
When notebook connected to the office LAN I am working good with my app-> my sql express as a domain/user.
I'd like to work at home too. I can logon to the system (XP SP2) using domain account when notebook has no network connection. (probably OS caches something)
Is it possible to work with sql express using domain login when no network connection?
PS. old version of this software used MSDE 2000 and it was possible(!).
im redeveloping my application from using access 2000/DAO to VS2005 professional/SQL server express using ADO.NET (i use VB), and just want to make sure i'm on the right lines about using sql server express 2005 on a network. i've spent hours reading every concievable article on the web after failing to create a database on a network drive, and ive just come across a good artricle here but want to be sure i understand what i need to do properly.
am i correct in the following please:
i only need 1 instance of SQL Server installed on the server, local PC's that will be using my SQL database do not need SQL server/management express installing? obviously the database resides on the same server as SQL server 2005 on the network. i dont need any additional software/drivers etc installing on the local pc's (as a miniumum all local pc's will be running w2000 or XP) In my local pc's, i set the connection string to point to the instance of SQL server on the server PC i need to enable the tcp/ip connection stuff on the server. all local PC's need .NET framework 2.0 installing, as well as the server.
as an additional question, what if an end user has another SQL version installed already, say the enterprise version? is it recommended i link my app. to that, or still use SQL express for my own purposes, and are there any issues with having both database engines existing on the same server?
is there a limit on the number of concurrent users. i have read in some places that there is a limit of 4 or 5, and elsewhere that there is not.
is there anything else i should consider?, and any other help or advice is welcome.
The network admin is saying that if I run my SQL Express in the office , it will intefere with his SQL Server 2000 connection and its services.
He asked me to disconnect myself from the network and do the work locally, what the!??
I had my SQL express remote connection set to Local and remote connections (using TCP/IP connection )
However , I really dont believe a SQL express running on my laptop would in anyway steal incoming connection to the SQL server 2000 running on the company server.
I now have my SQL express set to Local connections only, I would like to ask you guys does SQL express actually conflict with ANY services running on the same network ??
If I deploy a database to the web using sql express 05 is there a limit to the number of connections that can be made on it? I have read posts stating that but cant find any documentation from MSFT that supports that idea. I just know that it has a limit of a db size to 4 gigs. Thanks!
I am running a standalone WinXP SP2 system with VS 8 and SS 5 Express on it. I have been working very nicely with VB and SSCE, but I want to learn to use Sql Server 5 Express, which I also have on my system from a prior install of VS 5. I am strictly doing this as a learning experience on my own.
I have been trying to install the NW sample database into SS 5 Ex, but it is obviously not configured properly, because I am getting errors stating that the scripts cannot install because they cannot establish a remote connection to SS. So I looked up the FAQ item here on setting up for remote connections (which I am not even sure applies for a standalone system like mine). Anyway, I followed the instructions in the FAQ, using the SAC util to configure for remote connections, but it does not work. Every time I try to start the DB engine, it fails with the following message:
When trying to start Database Engine when configuiriung for remote connections in SAC:
"TITLE: Surface Area Configuration ------------------------------ The service did not respond to the start or control request in a timely fashion, you need administrator privileges to be able to start/stop this service. (SQLSAC)
Now, I am the admin user on the PC but OK, so I selected the SAC option to set myself as SSadmin, even though this option is supposedly only for Vista users according to the dialog. Anyway, it does not allow me to set myself as SSAdmin, it returns the following error:
When trying to add myself to SQLSAC, even though it is for Vista:
"TITLE: .Net SqlClient Data Provider ------------------------------ 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) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtI D=2&LinkId=20476"
(which help link is no help BTW, because it is not valid). And the setting does not get set, because the next time I open that dialog, I am back to being a non-admin user.
So what is the solution here? Am I going to be able to use SS 5 Ex on my PC? No matter which connection option I select, either local only, or for any of the remote options, I cannot get it to work. Am I supposed to reboot my PC after changing a setting? Or is it just not possible to run SS 5 Ex on a standalone PC like mine?
Or worse, are there a bunch of other configuration settings I must change as well? I note that, when I look in the SS Config Manager at the properties for SS Express, I see that it shows the logon option that uses the built-in account "Network Service"rather than Local System or Local Service; is that correct? BTW the browser is always running in all this.
As you may gather, I know zip nada about SS, but I am an experienced VB/VBA/VC+/FP programmer of many years, did desktop Access databases w/VB6 frontends for a lot of customers, so I am familiar with DB design etc. I just know next to nothing about backend stuff like this, other than a little with BTrieve years ago.
In the latest issue of MSDN Journal , article "IIS 7.0: Enhance Your Apps Wioth Integrated ASP.NET Pipeline", Mike Volodarsky says:
"...Be sure to close the tool after you are finished as SQL Server Express Edition allows only one user identity to access the database at a time." Can someone elaborate on this?
Does anyone know of the procedure, steps that need to be followed to allow installing SQL 2005 Express from a network? Since SQL 2005 express requires .NET 2 and the MSI engine 3.1 and MDAC 2.8 it is a real problem pushing it from a network such as active directory using an AIP (Administrator Installation Point).
Is there a limitation in sql server 2005 express that it does not accept connections via the network? I am trying to develop a web application running the web server as a VM but I can't connect to the sql server on the host machine. Similarly, I can't create an ODBC connection on the VM, but I can on the host. I could install sql express on the VM, that is probably the next thing I'll try.
Hi all !Does someone know how many concurrent connections 2005 Express canaccommodate ? The limit on MSDE was 5 before performance drops considerably.Thanks for your help.Sebastian
I have an application that will deployed on LANS running 1- 10 systems on average.
The front end is C#.net 2.0 and the backend will be sql express.
I need to enable remote connections by default because 99.5% of our customers have 2 or more computers.
I have two questions:
1) How do I enabled remote access during installation? Can I run the sqlExpress install silently and turn this on so that my users (who are very non-technical) do not have to go into surface configuration and turn on network access?
2) If I already have sql express installed (like on my development machine now) how do I enable remote access via a command line utility without having to run the surface configuration tool? I want to be able to execute a command to turn on network access so my users don't have to go to a GUI tool(Surface area configuration) and turn it on themselves. Can I use sqlcmd to turn on network access or some other command line utility that I can execute easily. Perhaps there is some type of .NET assembly that I can reference from within my C#.net application that will allow me to enable remote access? Basically How do i take care of this without making my users have to do it?
I get the following error and have been trying to figure out why I keep getting it. Initially, I had placed my project under wwwroot folder and ran it under IIS and it gave this error. Then I moved it to my local C drive and same thing. I am sharing this project with two other co-workers and all our config files and code files are same...they don't get this error but I do. I checked that SQL Server Client Network Utility has TCP/IP and the 'Named Pipes' enabled. I thought maybe I have setting in the Visual Studio 2005 that I'm not aware of that's causing this problem...it can't be the server since my co-workers aren't having this error and can't be anything in the code since all of us are sharing this project through vss. I dont' think using different version of .net framework can create this error. I changed the version from 2.0 to use 1.1x and it gave same error... Any help would be greatly appreciated. Thanks in advance.
Server Error in '/RBOdev' 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: 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. 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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)] System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +739123 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188 System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject) +685966 System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject) +109 System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart) +383 System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +181 System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +170 System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +130 System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +28 System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +424 System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66 System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +496 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.UI.WebControls.WebParts.SqlPersonalizationProvider.GetConnectionHolder() +16 System.Web.UI.WebControls.WebParts.SqlPersonalizationProvider.LoadPersonalizationBlobs(WebPartManager webPartManager, String path, String userName, Byte[]& sharedDataBlob, Byte[]& userDataBlob) +195 System.Web.UI.WebControls.WebParts.PersonalizationProvider.LoadPersonalizationState(WebPartManager webPartManager, Boolean ignoreCurrentUser) +95 System.Web.UI.WebControls.WebParts.WebPartPersonalization.Load() +105 System.Web.UI.WebControls.WebParts.WebPartManager.OnInit(EventArgs e) +497 System.Web.UI.Control.InitRecursive(Control namingContainer) +321 System.Web.UI.Control.InitRecursive(Control namingContainer) +198 System.Web.UI.Control.InitRecursive(Control namingContainer) +198 System.Web.UI.Control.InitRecursive(Control namingContainer) +198 System.Web.UI.Control.InitRecursive(Control namingContainer) +198 System.Web.UI.Control.InitRecursive(Control namingContainer) +198 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +692
Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET Version:2.0.50727.832
I am trying to attach a network database to my sql server express
After some reading I "Enabled" tcp/ip, named pipes, and shared memory in sql server confiuration manager.
But when I go to "Attach Database" in Sql Express managemnent studio. It does not show the network drives much less allow me to attach anything on a network drive.
What am I missing here?
If I install sql server on the network machine will my local Sql express recognize it?
Hi all, I would like to connect & manage SQL Express 2k5 server from another SQL 2k5 Server / Dev. edition / Express edition management studio, running on the same network. I've followed the procedure at http://support.microsoft.com/kb/914277 and I can now manage SQL 2k5 Server / dev. edition from a remote management studio. Is it possible to manage the 2k5 Express edition from a remote 2k5 management studio as well? Thanks, Assaf
I have installed SQL Server Express and I can connect with it locally using "localcomputernameSQLEXPRESS". It is configured for remote connection and for some reason, when I browse for this instance on the Network Server, it does not appear in the list. I have unistalled/installed it several times and still I cannot see this instance on the SQL Network server list. Can anyone help troble shoot this frustrating issue...
After the install is done I start the service form the command prompt using
start mssqlserver
I see that the SQL Server service has started under NETWORK SERVICE account!!! when the documentation i Read on MSDN says it starts in Local System account
Hi, My Web Aplication read and write into a sql server express database. The database is in one server and the applicacion is running from my laptop. Everything works well. But if i publish the web in the same server that the sql server and getting the next error: 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) When am running the application from my laptop i am using the external IP and when I publish it in the same server i am changing the IP for the server name. The most interesting part is that the web can read but when it tries to insert is when am getting this error. Any clue??' I can select, delete, insert using Microsoft SQl Server management Studio from my laptop, then the sql server accept remote connections. I do not understand why the ASP.Net application works perfectly when runs from my computer but get this error when is publish in the server. Any help will be more than appreciate. Thanks in advance
i Have this stored procedure below that creates a backujp copy of tblpersons from database db1 into another database db2 with a table1 pressing f5 to create it it goes fine up to around 5 seconds and after that the error below appears and looking at the stored procedure it is not created either. I already activated the default settings SQL Server to allow remote connections but still the error appears.
CREATE PROCEDURE makebackup BEGIN SELECT * INTO table1 FROM sql1.database1.dbo.tblpersons END GO
OLE DB provider "SQLNCLI" for linked server "amps" returned message "Login timeout expired". OLE DB provider "SQLNCLI" for linked server "amps" returned 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.".
Msg 126, Level 16, State 1, Line 0 VIA Provider impossible to find the module
I was going over this article , and was intrigued by this statement "If SQL Server 2005 Express is running on Windows XP Home, it is limited to five simultaneous connections. If it is running on Windows 2000 or Windows XP Professional, it is limited to 10 simultaneous connections. However, these are limitations of the operating system and not of SQL Server 2005 Express."
What are simultaneous connections? Is this related to Max worker threads defined as 255 on other editions? How does underlying OS impose how many connections can be done to SQL server. And finally how many simultaneous connections can be done in Windows Server 2003?
Just upgraded to SQL Express 2005 from MSDE for Firehouse. Upgrade went great and the db is accessable and running fine. Except when not used for a while. Then I need to restart the db to allow connections of any kind. If I don't I get an error that the db is not accessable and I can't connect. Everything runs fine after until it goes to "sleep" on me again. We upgraded to make use of the 4GB limit as we were at 1.9GB and MSDE was getting a little unhappy.
Any suggestions? Is this a "feature" and if so, is there a script I can run to kick it into working mode again?
I have developed a Windows App in VS.NET 2005 which connects to a SQL 2005 Express database.
Now I want to install the app and database on the network and I am getting an error "File 'file_name' is on a network device not supported for database files"
