I am sure I am using the same connection string for all connection.open, and closing all connections as soon as possible… but
When I try to debug my web app with vs, it runs for some time then I get:
The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached exception
However, if I just access the application normally form the url (not using vs.net) it runs flawlessly.
Has some one had the same problem? i can't debug help!!
I encountered a very strange problem again. Why the time series displayed on the chart are so strange? The Key time column I chose for my time series algorithm is cal_month(e.g 199001...), but why the date displayed on the time series chart is like :05/06/2448? (it should be like 199001..?) What is that data? And where exactly did it come from? What is the exact cause of this?
Hope it is clear for your help.
I am really confused on this and thanks a lot for your kind advices and help and I am looking forward to hearing from you shortly.
To set up the problem, paste this into QA:if exists (select * from dbo.sysobjects where id =object_id(N'[dbo].[WorkOTRate]') and OBJECTPROPERTY(id, N'IsUserTable')= 1)drop table [dbo].[WorkOTRate]GOCREATE TABLE [dbo].[WorkOTRate] ([TimeFrom] [smalldatetime] NOT NULL ,[TimeTo] [smalldatetime] NOT NULL ,[RateMultiplier] [float] NOT NULL) ON [PRIMARY]GOINSERT INTO dbo.WorkOTRate (TimeFrom, TimeTo, RateMultiplier)VALUES ('18:00:00', '23:59:59', 1.2)SELECT TimeFrom, TimeTo, RateMultiplier FROM dbo.WorkOTRateThis gives the following result:1900-01-01 18:00:001900-01-02 00:00:001.2So, it's storing the time 23:59:59 as midnight. That's odd.(NOTE: If you rescript the table using datetime instead ofsmalldatetime types, the data are stored correctly.)It gets worse (or better, if you like perversity).If I go to Enterprise Manager, right-click on WorkOTRate and select"Open Table" -> "Return All Rows" I get:01/01/1900 18:00:0002/01/19001.2So, I bite the bullet and change the two column types to datetime,clear out the old data and run the INSERT again. The data looks betternow.Go back to the view in EM.If I put the cursor in a new row, and type into the TimeFrom column18:30:00 and the TimeTo column 19:30:00 and the RateMultiplier column1.3, and refresh the data by pressing the red shriek !, I get this:01/01/1900 18:00:0001/01/1900 23:59:591.218:30:0019:30:001.3If I re-run the SELECT from the QA, I get this:1900-01-01 18:00:00.0001900-01-01 23:59:59.0001.21899-12-30 18:30:00.0001899-12-30 19:30:00.0001.3Is it just me, or does this seem to be remarkably inconsistent?Edward
Again I encountered a very strange problem which displayed the predicted attribute values as percentage format? The data type of the attribute is actually double, why is that?
That's really frustrated.
Thanks a lot in advance for your kind advices and I am looking forward to hearing from you shortly.
We've been experiencing this strange error from our SQL server for about a month now and i've tried alot of things, visited alot of websites and manufactured a few possible solutions but nothing helps! Its very frustrating. This is the error i get when i try and expand the server tree:
A connection could not be established to [OurServerName]
Reason: SQL Server does not exist or access denied.
ConnectionOpen (Connect())..
Please verify SQL Server is running and check your SQL Server registration properties by clicking on [OurServerName] node) and try again.
What really gets to me is that everything works after i restart the server. Then things will go fine for about a day or two and then the same thing again. This i causing alot of downtime for us. Can anyone please just give me a suggestion? :confused:
Vendor app (written in VB '05) connects fine building screens that list data from only one record but blows up building 'list' screens that list multiple records. Really strange-it works fine when run locally on the server (Win2K3) and when run from one developer's machine (which has VS 2005 but not SQLExpress) but not from other developer's machines (which have both VS 2005 & SQLExpress) nor from a 'user' machine (which has neither). All have .Net Frameworks 2.0, the developer machines have SQL Management Studio & connect fine via that.
Vendor, of course, says it's a configuration issue so not their problem. I'm trying to figure out what they could be doing differently when building a list screen & therefore why it would fail. Fact that it works locally suggests that the failure is in the remote connection-but fact that it connects on 'single record' screens says that remote connections work. So what would be different about a request to return multiple records and why would it work locally but not remotely?
BTW, Surface Area Configuration Manager won't run-it reports 'localhost does not exist on the network or it cannot be configured remotely'. This is when running the Configuration tool directly on the server.
Hi I've got a database in SQL Server 2000 on Windows Server 2003 which appears to be okay from SQL Enterprise Manager and from SQL Query Analyser but which has a problem with one particular table when connected to from a VB DLL using ADO. The queries do either a select or an insert - the latter is via a stored procedure. Once the failure happens, any other queries generate a -2147217871[Microsoft][ODBC SQL Server Driver]Timeout expired. If I delete the table and recreate it all is well. If I run an integrity check nothing shows up. I've tried deleting the indexes and that made no difference either. SQL Server is patched up to SP4 and ADO is from the MDAC 2.8. VB is version 6 Enterprise with SP6. None of the other databases in the instance exhibit the problem and they're all structured in an identical way. The table is quite large but we've got much larger one's using the same procedures and they don't have a problem. Also, if I restore a backup of the problem database onto another machine the problem shows on the other machine too.
Hello,I developed a win32 .exe CGI that connects to a clustered SQLServer toreport some data.The software is written with Borland C++Builder.This is the oledb string:Name=Provider=SQLOLEDB;Password=xxx;Persist Security Info=True;UserID=xxxx;Data Source=xxxxx;Initial Catalog=xxxxx;NetworkLibrary=dbmssocnIt suddendly stopped working on my customer network, so I made sometest and I verivied that the problem is on the connection withSQLServer: my test program just opens a connection, closes it andexits, reporting in a log file if the open was successful or failed.If I run the program locally, just launching it, no problem, it works.I can run it mutilple time continuosly and is connects every time.If I run the program through my webserver, as a CGI that's how it issupposed to work (http:\localhostscriptsconnect.exe), it connectsthe first time, and then I have to wait 40 seconds to connect againsuccessfully, or it fails.If I try against MY sqlserver on my laptop or on my network no 40 secproblems, but on my customer network, with THEIR SQLServer , if I tryto connect from their webserver, or from my laptop webserver, I havethis 40sec problem.I analyzed the network traffic, and I discovered that when I run mytest program locally it originates only TCP/IP packets, and SQLServeranswers only with TCP/IP.But when I use it from the webserver as a CGI, it originates an UDPpacket, then SQL answers with another UDP packet, and then theycommunicate over TCP/IP.This when it works: the second time my program continues to send theUDP packet, but it receives no answer, and fails the communication.I can only say that:- we haven't touched the program for months, and it really stoppedworking suddendly, so I suspect that something in my customer netowrkhas changed- I tried many different OLEDB strings, disabling connection poolingand all the services, calling the SQLServer by name or IP...- the problem can't be related to my program, because now is reallyjust an oledb connection testAnyone have an idea?Thank you very much,Mattia
Well this has got most of us stracthing our head as not matter what we do we can't connect remotely
But it get's a bit more complex. We have an existing web application running with a local instance of express running fine. However as the server is getting hammered we need to put the new version of the site on a second server. Unfortunately the key contact who use to work on the old system and set it up is no longer avialable. We've been through all the basics and nothing works... our latest attempt was to install a new instance of 2005 as we were not sure what was going on.
So, here is the log for this new clean instance:
Code Snippet
2008-02-28 15:12:13.75 spid5s Server name is 'S15271584SQLEXPRESS'. This is an informational message only. No user action is required. 2008-02-28 15:12:13.75 spid5s Starting up database 'msdb'. 2008-02-28 15:12:14.00 spid8s Clearing tempdb database. 2008-02-28 15:12:14.26 Server A self-generated certificate was successfully loaded for encryption. 2008-02-28 15:12:14.29 Server Server is listening on [ 'any' <ipv4> 4286]. 2008-02-28 15:12:14.29 Server Server local connection provider is ready to accept connection on [ \.pipeSQLLocalSQLEXPRESS ]. 2008-02-28 15:12:14.29 Server Server named pipe provider is ready to accept connection on [ \.pipeMSSQL$SQLEXPRESSsqlquery ].
The Browser is up and running and we try to connect via SQL Management Studio with the following details:
SERVERNAMESQLExpress SQL Server Authentication
But get:
Code Snippet
TITLE: Connect to Server ------------------------------
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) (Microsoft SQL Server, Error: -1)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476
------------------------------ BUTTONS:
OK ------------------------------
How do I know this is not a connectivity/firewall issue? Simple:
1. We stop the SQLExpress instance 2. Setup netcat to listen on that port (nc -l -p 4286) 3. Connect via telnet (telnet SERVERNAME 4286) and type something which then appears printed out on the other end.
Anyway, the Windows Firewall is off and I can't see any other firewalls installed (we did not setup this server).
Btw, if we try and connect to the existing instance we get:
Code Snippet
TITLE: Connect to Server ------------------------------
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: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (Microsoft SQL Server, Error: 10060)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=10060&LinkId=20476
------------------------------ BUTTONS:
OK ------------------------------
Here is the error log for that instance:
Code Snippet
2008-02-15 06:43:16.92 spid4s Server name is 'SERVERNAMES15271584'. This is an informational message only. No user action is required. 2008-02-15 06:43:16.92 spid4s Starting up database 'msdb'. 2008-02-15 06:43:17.14 spid8s Clearing tempdb database. 2008-02-15 06:43:17.19 Server A self-generated certificate was successfully loaded for encryption. 2008-02-15 06:43:17.20 Server Server is listening on [ 'any' <ipv4> 1177]. 2008-02-15 06:43:17.20 Server Server is listening on [ 'any' <ipv4> 1433]. 2008-02-15 06:43:17.31 Server Server local connection provider is ready to accept connection on [ \.pipeSQLLocalS15271584 ]. 2008-02-15 06:43:17.31 Server Server named pipe provider is ready to accept connection on [ \.pipeMSSQL$S15271584sqlquery ]. 2008-02-15 06:43:17.31 Server Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required. 2008-02-15 06:43:17.33 Server The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies. 2008-02-15 06:43:17.33 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
We've also run a network sniff with wireshark and get see the request hitting SQL on the right port... but there is never a response back.
Any ideas? I'm open to anything short of slitting my wrists!!
I'm having a strange situation in my SQL SErver 2000 SP3a with 4 Processors, 4GB of RAM and high-end disk sub-system. I migrate a specific database from another instance with SQL SErver 2000 SP3a too to this new server with more hardware resource than another one. The application that access this DataBase stablish a connection with SQL SErver using TCP/IP, everything works fine. So, if I let the connection "sleeping", or better, if I let the connection idle for amount of time, I need to stablish the connection to ther SQL SErver again. I hadn't the same situation in the old instance as I having. I think that it's happening because the other instance was dedicated to this application and that new Instance don't. In this new Instance I have many other connections simultaneously, about 200 processes.
Anybody knows what's going on? Are there any settings to change this time-out configuration just for a specific connections?
Hi, I have Mirroring setup for 3 databases without a witness. The database mirroring monitor shows me that both Principal and Mirror are "Synchronized". SSMS also shows that the both instances are "Synchronized".
However, the following error message appears couple of times in the event viewer: The mirroring connection to "TCP://abc.xyz.com:5022" has timed out for database "DB" after 10 seconds without a response. Check the service and network connections.
Also came across this article. http://support.microsoft.com/kb/947462
My application having connection string which having Server Name --Erlier it is working fine. Now IP got chaged Server name is same but now Iam unable to connect server.
When I login using QA to my SQL Server database, it takes 15-20 secondsto establish a connection and open a query window. Drilling into adatabase via Enterprise Manager is similar. Once the connection isestablished, the server runs plenty fast however.Can someone tell me why it could take a long time for a connection tobe established?This behavior occurs when I am local on the box.Thanks,John
I have been requested to create an application for a client that will use a database of my choice. I have considered using sql compact 3.5 but i feel it might be best to go ahead and start with express until the client wants to upgrade to workgroup or higher. So the problem i have is that the connection always takes 12 to 25 seconds to connect on every first connection. I guess this is because it creates an instance of the server each time. So my question: is there a way to have it ready all the time besides leaving the application open? I have it attached through management studio express on my server computer. And i need to be able to support several users reading and modifying records.
When I enable MultipleActiveResultSets in the "context connection" (SqlConnection), I get an error:
System.InvalidOperationException: The only additional connection string keyword that may be used when requesting the context connection is the Type System Version keyword.
Can we have MARS in the "context connection"?
note: I'm doing this to support multiple open datareaders in a CLR stored procedure.
I am using MS JDBC driver 2005 1.2 and in-house written connection pooling that was working fine for a number of years. This combination worked OK with SQLserver 2000. But recently we switched to SQLServer 2005 (x64) on WIN Server 2003 Standard x64 eddition. Everything seems work OK during business hours, however, after business hours when there are lesser users and connection stays idle for sometime, I am getting the following error: com.microsoft.sqlserver.jdbc.SQLServerException: The connection is closed. at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.checkClosed(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.setAutoCommit(Unknown Source) at com.nms.serverframework.dbaccess.OnlineTransactionManager.freeConnection(OnlineTransactionManager.java:420) at com.nms.serverframework.dbaccess.OnlineTransactionManager.releaseConnection(OnlineTransactionManager.java:707) at com.nms.serverframework.dbaccess.OnlineTransactionManager.releaseConnection(OnlineTransactionManager.java:688) at com.nms.serverframework.dbaccess.OnlineTransactionManager.finalize(OnlineTransactionManager.java:399) at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method) at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:83) at java.lang.ref.Finalizer.access$100(Finalizer.java:14)
everytime i used to open the package has a sql server configuration file saved and also has loggin enabled, with password for sensitive data storage given, it shows some errors and all the time the errors are with the created connection.
yes, i have given the right password at the time of opening it.
Is there a way to dynamically create a connection manager @ run time? I would like to do this from a data set of connection strings so I can link them into a union all component.
I'm trying to use SSIS in MSSQL 2012 to extract data from MAS90 database.The connection string is tested to be working, because I can extract successfully using the same one in Excel.I follow the wizard of import data in management studio, but after selecting the tables and mapping all those things, when clicking finish, the management studio always freezes.
I have C# application which will create normally 200 pool connection with SQL server. Previously i was using the SQL Server 2000.I don't have any issue. Recently i have upgraded the Database to SQL Server 2005 with SP1. After that problem Started. I was getting the Timoout problem and due to this my application getting crahsed.
To give about the Detail about my SQL sever 2005 Database: i have six merge Subscribers and three Transactional Publishers. I don know that "is the Replication giving all the time Out issue for my C# application?".
so by default i beleive it is 30 seconds as the Time Out. I don know why within this period there is no response from SQL server 2005. My application Server and Database Server are in the Same network with 100Mbps.
What is the wrong here ? Is it SQL server 2005 with the Replication gives the problem to me ?
Can anyone help me. I assumed that SQL server 2005 will work without issues and we have implemented in prod. now in prod i am getting this Error.
I installed SQL server 2005 express edition on my windows server and I had no problem with connecting it remotely through Management Studio, then I removed it and installed a full edition SQL server 2005. That's when it's gone all wrong.
Now I can't remotely connect the server through Management Studio. The error I get is the same as some of the people in this forum has which is:
"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) (Microsoft SQL Server, Error: -1)"
The problem is that I have all protocols enabled and even when I disable firewall and unassign all the ip filters still no go.
I looked at te machine.config file at my server and the connection string bit goes like this:
I have a simple package, which reads a flat file source, does some transformation, and outputs to a flat file destination. The package runs as a SQL Agent job, so I have the flat file source and OLEDB connection ticked and configured on the data sources tab.
What I would like to do is get hold of the flat file source connection string property from inside the package at run time, and use it to set the flat file destination connection string using property expressions.
The easy option is to set the destination in the agent job, but I'd like to add a date/time stamp to the destination filename.
I am trying to import data from flat file to sql server 2005 DB table using SSIS. There are 4 different text files in the input folder. I am using for loop to iterate reading and importing 4 times. In order to do this I have set "Connection String" property of a connection manager to a package level variable using expression. There is a script which supplies the source file name and assigns to this variable.
The package works fine. The data gets imported successfully into the destination table. However, when I close the package, reopen it and then run, the Data Flow task fails with the error "Can not open the source file". If I enter a valid file name in the Flat File Source task and run the package it works again. As soon as I close the file/package, reopen and then run, the data flow task fails with the same error.
How do I make this working. I am planning to schedule a job which will execute the package programatically. In that case no user intevention is possible.
I would appreciate your help on this. I can provide further details if required.
If I have 6-8 queries running in parallel, Whether having a Single connection Manager (for the same source) for all the Extract performs faster or having Distinct Connection Manager for each of the extract performs faster ?
In VS2008 SSRS, when creating a dataset, only the name of the stored procedure was required. When populating the dataset, VS prompted for the parameters, whether or not there were any. In VS2010, the name of the stored procedure is not enough if there are parameters.When creating a dataset in Visual Studio 2010 for databases and stored procedures in SQL 2012, I must provide (what should be) run-time parameters to obtain a field list and then to preview the report.Â
So the embedded dataset looks like this (wherein the only parameter is a password): exec dbo.spu_procedure1 @PW='999'.This works well and as expected during report design and development. But 999 must be provided at run-time by the requester, and not in the dataset definition. If I remove the parameter in the dataset's exec string before deploying the report, the field list is cleared and the report is unusable. So I cannot overcome what seems a contradiction: necessary to obtain a field list, but "yet-to-be-provided" when the user selects the report.
By keeping @PW='999' in the dataset specification, the user cannot override the parameter and automatically has a password to view the report. Â
I am in between of creating a dynamic SSSIS package which will run for multiple zones having different source connection.My source is in Oracle.I am having 3 DFT with the 3 different source tables.I want to create a package with above DFT dynamically so that my single package can run for the entire zone with dynamically source connection change.I have created a Master table which stores the zone source connection string and zone name. I have 2 different connection.so if in future any new zones come so only newly zone details need to be add in master table without opening the package.
I€™m suffering a queer behaviour when I use BIDS. Concretely, when I open a dtsx from my project (it has 10 packages) many times Sequence Container and Data Flow tasks are invisible. I mean, its lines are not visible at all whereas its titles are. I mean, what you see is just a white box€¦
Then, I€™m gonna Data Flow layer and I have to do double-clik over the tasks and are visible but on Control Flow I don€™t see how to solve.
Curiously in our development and production server such behaviour doesn€™t happen (we are accessing by mean Terminal Server from our workstations)
How odd!. Everything is fine except this.
I want to remark you that such project has been copied from the server, this is, these packages are been built on the server
