One of my production SQL Server 2000 systems is listening on TCP and Named Pipes, but not on Shared Memory.
This server has a lot of scheduled jobs that are internal to this box. I assume these jobs would benefit from using shared memory instead of TCP/IP, but I can't figure out why it doesn't use shared memory already and how to correct that.
Thanks in advance for all assistance.
A transport-level error has occurred when receiving results from the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.).Net SqlClient Data Provider at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32 bytesExpected)
at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
at System.Data.SqlClient.TdsParserStateObject.ReadByteArray(Byte[] buff, Int32 offset, Int32 len)
at System.Data.SqlClient.TdsParserStateObject.ReadUInt32()
at System.Data.SqlClient.TdsParser.ReadSqlValueInternal(SqlBuffer value, Byte tdsType, Int32 typeId, Int32 length, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.ReadSqlValue(SqlBuffer value, SqlMetaDataPriv md, Int32 length, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ReadColumnData()
at System.Data.SqlClient.SqlDataReader.ReadColumnHeader(Int32 i)
at System.Data.SqlClient.SqlDataReader.ReadColumn(Int32 i, Boolean setTimeout)
at System.Data.SqlClient.SqlDataReader.GetInt32(Int32 i)
Ive just started getting this on a stable application thats used a datareader on millions of records.
Not sure where to got from here and I can't find anyone else whos getting the failure during the processing.
I could disable shared memory protocol but that seems extreme. I'm on Sql Enterprise 9.00.2047. Maybe the process is hammering the server very hard? Personally I've rarely ever seen SQL be the cause of an error, only user config, bad disks or power issues.
I'm running the app again with SQL Profiler capturing "standard" events.
Just need it to blow up again.
I can run the app on another machine of course and I wouldn't get Shared Memory Provider being used. Maybe I ought to do that as well. At least if the error is not really in the Shared Memory I'd have another avenue to explore.
Anthony
I am new here and new to SQL Express. I've searched for my issue, but can 't quite find anything close to the problem or how to solve it, if it's even solvable. I am using SQL Express on a pc to connect to the back end of a database. The front end application (an access runtime) also runs on the same pc. This pc is on a domain. I think I've tried every combination of protocols, and although connectivity via ODBC is successful, the application can't connect - gives the "server doesn't exist or access denied". When I log on to this computer with the "machine" logon (not the domain), I have SQL Express configured to use shared memory, the application runs just fine. I need to use this database for testing in a non productivity environment, but I really hate to log off the domain to run it. Ideas?
Thanks,
pvdcats
Hi,
Our 32-bit applications connect to SQL Server 32-bit through OLEDB with Shared memory as preferred protocol. Our client applications and SQL Server generally reside on same machine.
We are evaluating possible impact when SQL Server 2008 64-bit is accessed with our 32-bit client applications running on 64bit WindowsServer 2008. Can shared memory protocol will be still used by underlying SQL server OLEDB dll considering the client application is 32-bit where as SQL Server is 64-bit ? Or it will switch to Named pipes or TCP/IP automatically ?
Thanks
prayags
Apparently this error was fixed in CU12 for SQL 2008, but it seems to have raised it's head again in SQL 2012.[SSIS.Pipeline] Warning: Warning: Could not open global shared memory to communicate with performance DLL; data flow performance counters are not available. To resolve, run this package as an administrator, or on the system's console.
I've got a client who is seeing it. but I've not seen a fix in CU1 or CU2 for 2012.
I'm getting this error on one of the test pc's when doing a adapter.fill for a datatable.
Any ideas on how to debug this?
Thanks,
Bernie
When I run this code...
DECLARE @bcpCommand varchar(2000)
SET @bcpCommand = 'bcp sp_text out test.txt -c -U -P'
EXEC master..xp_cmdshell @bcpCommand
I get this...
SQLState = 08001, NativeError = 14
Error = [Microsoft][ODBC SQL Server Driver][Shared Memory]Invalid connection.
SQLState = 01000, NativeError = 14
Warning = [Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen (Invalid Instance()).
NULL
What on earth does it mean?!
Thx,
Nick
Getting the following warning in SSIS - SQL 2012:
[SSIS.Pipeline] Warning: Could not open global shared memory to communicate with performance DLL; data flow performance counters are not available. To resolve, run this package as an administrator, or on the system's console.
Microsoft had a fix for SQL Server 2008.
How to get around this in SQL 2012?
I'm busy rewriting DTS packages as SSIS packages. As and when I finish a package I run it in debug mode via Microsoft Visual Studio and then examine the Exection Results to see the messages generated.
Now it may or may not matter how I run the package but the following warning has been generated :-
[SSIS.Pipeline] Warning: Warning: Could not open global shared memory to communicate with performance DLL; data flow performance counters are not available. To resolve, run this package as an administrator, or on the system's console.
When I try to install MsSQL Server 2005 Develop Edition do I get the error:
[Microsoft][SQL Native Client]Shared Memory Provider: No process is on the other end of the pipe.
I have trying to look at other posts on this forum and elsewhere, but cant find any solution that works for me - mainly cuz all solutions is after the installing.
Before trying to install MsSQL Server 2005 Dev did I install VS.Net 2005 Pro. First did the Native Client make troubles, but got it to work with reinstalling it, but now does the SQL setup stop on every try with the error above.
I have tried looking if the MSSQLServer is running when it tries to connect during install, and everything says it is running (Services, Net start, Taskman.).
I dont run any special setup on my system - it is a normal Windows XP Pro SP2 with all updates. I just need the SQL server installed so I can develop locally without access to out main SQL server.
I have been using MsSQL 2000 before and never had any problems, but the 2005 keep on bugging me.
The only solution I havent tried is to reinstall Windows itself, but I will pref. not to do so.
And to be honest, then have I no idea what a "pipe" is - I am used to develop webapplications and not so much on server maintaince/troubleshooting.
Need some more information? Then just ask.
I am getting the following warning for my SSIS08 package: Could not open global shared memory to communicate with performance DLL; data flow performance counters are not available. To resolve, run this package as an administrator, or on the system's console. I did check Warning in SSIS 2008 , but didn't find any solution. The package processes data and executes fine , but why do I see this warning? When I run this package on my machine, I see no such warning, it's only when I deploy it to our DEV SSIS server, I get this warning.
View 7 Replies View RelatedWhen running the etl I'm getting the error: <SSIS Task>: Shared Memory Provider: Timeout error [258] ; followed by the message "Communication link failure".
What is special about this message that it happens on a SQL Execute task (random task) and the Timeout is after 2 minutes.
When executing the packages separatly it is working fine. The SQL Tasks that are failing are also quit heavy, but reasonable and takes between >2min and 10 - 15 min. Statements are stored procedures that puts an index on 3 mil. records or update statements,...
I had a look to all my (SSIS-etl) timeouts and they have the default value 0, the "remote query timeout" of the server is set to 10 minutes. According to me, these are the only one that exists?
There are 2instances on the server each instance has 24GB allocated, the server has 64 in total. Also when the etl runs (that results in an error) no other etl is running on the 2 instances. I'm working with the oledb sql server native client11.0 provider : SQLNCLI11.1.
I am receiving the following error when starting a program called ShelbySystems that is supposed to connect to a local database. I don't think this is a security issue but I don't know much about SQL server either so...
DIAG [08001] [Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied. (17)
DIAG [01000] [Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen (Connect()). (2)
System Info:
Windows 10 Home - upgrade from 8 64 bit
SQL server 2012 Express
SQL Backwards compatibility 2005 64 bit
ShelbySystems software v5.4
I am including the trace log in case it is useful.
DBInstall 130c-728ENTER SQLAllocHandle
SQLSMALLINT 1 <SQL_HANDLE_ENV>
SQLHANDLE 0x00000000
SQLHANDLE * 0x02EC58F4
[code]....
sql server 2000 is running on windows server 2003 ... 4gb of memory on server .... 2003 was allocated 2.3gb nd sql server was allocated (and using all of it) 1.6gb for total of approx 4gb based on idera monitor software ... all memory allocated betweeen the OS and sql server .... then 4 more gb of memory added for total now of 8g ... now idera monitor shows 1.7gb for OS and 1.0 gb for sql server ..... 'system' info shows 8gb memory with PAE ... so I assume that the full 8gb can now be addressed .... why are less resources being used now with more total memory .... especially sql server ..... i thought about specifying a minimum memmry for sql server but i amnot convinced that would even work since it seems that this 1gb limit is artificial .... it it used 1.6 gb before why would it not use at least that much now ??
thank you
I am getting the following error when i try to connect to the my web site using froma different server. A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) i am using sql express and i attach the database through the connection string in the web config. Any ideas
View 1 Replies View RelatedHi Folks,
I'm not a SQL Server expert, but need to understand something. I'm currently have SQL Server 2000 SP4 installed locally on my machine for application development.
Using sp_lock, I noticed that there are lots of shared database locks. After some study, i produced this interesting script:
use Master
go
sp_lock
go
use Experience
go
sp_lock
go
which results in:
spid dbid ObjId IndId Type Resource Mode Status
------ ------ ----------- ------ ---- ---------------- -------- ------
52 1 85575343 0 TAB IS GRANT
spid dbid ObjId IndId Type Resource Mode Status
------ ------ ----------- ------ ---- ---------------- -------- ------
52 13 0 0 DB S GRANT
52 1 85575343 0 TAB IS GRANT
My question is about the extra lock added by the "Use Experience statement". It lasts as long as the Experience DB connection is open
Question 1:
The way I read this is: the "use Experience" statement creates a shared database lock.
Am I reading this right?
Question 2:
I started looking into this because my application produces lots of locks that seem to live for 15-20 minutes. I have not noticed other adverse side effects of these locks. I have confirmed that nothing I have control over creates transactions, so I do not see why locks would be maintained.
Should I be concerned about these locks? Is this expected behavior?
Thanks Much in advance.
- D
i'm going nuts with SQL server notification thing. I have gone throigh this artical which tells how to set user http://www.codeproject.com/KB/database/SqlDependencyPermissions.aspx. This article show how to create new user and setup for sql server notification.But In my case user was alredy existing in database. which is very common senario in most cases. So i did following( check the SQL script below) but then i get this error
"A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)"
this my sql script
use [master]Go
-- Ensuring that Service Broker is enabled ALTER DATABASE [DatabaseName] SET ENABLE_BROKERGO
-- Switching to our databaseuse [DatabaseName]GO
CREATE SCHEMA schemaname AUTHORIZATION usernameGO
ALTER USER username WITH DEFAULT_SCHEMA = schemaname GO
/* * Creating two new roles. We're not going to set the necessary permissions * on the user-accounts, but we're going to set them on these two new roles. * At the end of this script, we're simply going to make our two users * members of these roles. */EXEC sp_addrole 'sql_dependency_subscriber' EXEC sp_addrole 'sql_dependency_starter'
-- Permissions needed for [sql_dependency_starter]GRANT CREATE PROCEDURE to [sql_dependency_starter] GRANT CREATE QUEUE to [sql_dependency_starter]GRANT CREATE SERVICE to [sql_dependency_starter]GRANT REFERENCES on CONTRACT::[http://schemas.microsoft.com/SQL/Notifications/PostQueryNotification] to [sql_dependency_starter] GRANT VIEW DEFINITION TO [sql_dependency_starter]
-- Permissions needed for [sql_dependency_subscriber] GRANT SELECT to [sql_dependency_subscriber] GRANT SUBSCRIBE QUERY NOTIFICATIONS TO [sql_dependency_subscriber] GRANT RECEIVE ON QueryNotificationErrorsQueue TO [sql_dependency_subscriber] GRANT REFERENCES on CONTRACT::[http://schemas.microsoft.com/SQL/Notifications/PostQueryNotification] to [sql_dependency_subscriber]
-- Making sure that my users are member of the correct role.EXEC sp_addrolemember 'sql_dependency_starter', 'username'EXEC sp_addrolemember 'sql_dependency_subscriber', 'username'
How let SQL 7 listening on 0.0.0.0:1433? We are using Windows Server 2003 Standard and SQL 7 Standard.
Thanks.
Is there any windows API available to find the IP address on which the process is listening.
Want to find the IP address on which SQL Server is listening.
Hello,
I have an installation of SQL Server Express 2005 installed on a Windows 2003 server. Through the forums on the board I have been able to turn on and make sure that port 1433 and port 1434 are turned on and listening. However, both ports show that they are listening on IP address 0.0.0.0. and I need for port 1433 to either listen on the server's main IP address or at the very least on 127.0.0.1. I have set them to enabled in the Configuration manager but they still don't appear to be listening on either of those IP addresses. Could some one tell me if there's another configuration change I might need to make?
Thank you in advance.
Hi all,
I'm working on a school project on web and mobile applications, and had decided to use MS SQL Server for my backend database.
However, after I've installed MS SQL Server 2000, I ran a port scan and I couldn't find the server running on any ports (MySQL is running on my port 3306, but I guess it doesn't matter) Can something drop some hints on how to debug the problem?
I'm running on Athlon XP 2000+ w/ Windows XP Professional SP2
Thanks a lot!
Hi, folks!
My server machine have 2 ip address (Private and real), but my sql server is just listening on the first one and the default 127.0.0.1
What Can I do to resolve that?
Please, Any idea would be really apreciate a lot!
TIA.
Armando
Cti, Miami
Hi all,
I have SQL Server in NT 4.0 which has two IP addresses. How to force the SQL Server to listen to specific IP address ? We can make client to listen to specific port & IP and let me know the way to configure SQL Server to listen only to specific port that will make to ensure that SQL Server can be communicated throught that specific port.
Your answer would be highly appreciated.
regards,
Nana
I am running SQL Server 2000 on windows XP pro. I have configured (enabled) TCP/IP protocol and left the default port 1433, but SQL server still does does not listen for client connections.
Can anyone tell me what might stop SQL server from listening???
With the server running, here is what I see (nothing on 1433...):
Proto Local Address Foreign Address State
TCP 0.0.0.0:25 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1030 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1031 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1098 0.0.0.0:0 LISTENING
TCP 0.0.0.0:6401 0.0.0.0:0 LISTENING
TCP 0.0.0.0:10002 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1034 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1037 0.0.0.0:0 LISTENING
TCP 192.168.0.104:139 0.0.0.0:0 LISTENING
TCP 192.168.0.104:1138 38.119.97.5:119 ESTABLISHED
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:1027 *:*
UDP 0.0.0.0:3456 *:*
UDP 0.0.0.0:4500 *:*
UDP 127.0.0.1:123 *:*
UDP 127.0.0.1:1900 *:*
UDP 192.168.0.104:123 *:*
UDP 192.168.0.104:137 *:*
UDP 192.168.0.104:138 *:*
UDP 192.168.0.104:1900 *:*
and here is the server log:
2005-10-25 23:23:24.31 server Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Personal Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
2005-10-25 23:23:24.31 server Copyright (C) 1988-2000 Microsoft Corporation.
2005-10-25 23:23:24.31 server All rights reserved.
2005-10-25 23:23:24.31 server Server Process ID is 3792.
2005-10-25 23:23:24.31 server Logging SQL Server messages in file 'c:MS SQL ServerMSSQLlogERRORLOG'.
2005-10-25 23:23:24.34 server SQL Server is starting at priority class 'normal'(2 CPUs detected).
2005-10-25 23:23:24.71 server SQL Server configured for thread mode processing.
2005-10-25 23:23:24.71 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2005-10-25 23:23:24.74 spid3 Starting up database 'master'.
2005-10-25 23:23:24.92 server Using 'SSNETLIB.DLL' version '8.0.194'.
2005-10-25 23:23:24.92 spid5 Starting up database 'model'.
2005-10-25 23:23:24.96 spid3 Server name is 'GS-DELL'.
2005-10-25 23:23:24.96 spid3 Skipping startup of clean database id 4
2005-10-25 23:23:24.96 spid3 Skipping startup of clean database id 5
2005-10-25 23:23:24.96 spid3 Skipping startup of clean database id 6
2005-10-25 23:23:24.96 spid3 Skipping startup of clean database id 7
2005-10-25 23:23:25.10 spid5 Clearing tempdb database.
2005-10-25 23:23:25.28 server SQL server listening on Shared Memory, Named Pipes, Rpc.
2005-10-25 23:23:25.28 server SQL Server is ready for client connections
2005-10-25 23:23:25.59 spid5 Starting up database 'tempdb'.
2005-10-25 23:23:25.71 spid3 Recovery complete.
2005-10-25 23:23:40.37 spid51 Using 'xpstar.dll' version '2000.80.194' to execute extended stored procedure 'xp_MSADEnabled'.
2005-10-25 23:23:40.71 spid51 Error: 15457, Severity: 0, State: 1
2005-10-25 23:23:40.71 spid51 Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install..
2005-10-25 23:23:40.89 spid51 Using 'xplog70.dll' version '2000.80.194' to execute extended stored procedure 'xp_msver'.
2005-10-25 23:23:40.93 spid51 Starting up database 'msdb'.
2005-10-25 23:24:54.20 spid51 Starting up database 'gpldb'.
2005-10-25 23:24:54.26 spid51 Analysis of database 'gpldb' (7) is 100% complete (approximately 0 more seconds)
2005-10-25 23:24:54.46 spid51 Starting up database 'Northwind'.
2005-10-25 23:24:54.60 spid51 Starting up database 'pubs'.
Does anyone know how or where to adjust Ram Memory usage for SQL 2000.
I've just added Changed the 512 MB Ram that came with the Server and Exchanged it with 4 GIG Ram . Is it a good Idea to allow only 2GiG for SQL . I 've heard that SQL will take/use all Ram that you install if you let. If this is true
Can anyone advise on how/where to make adjustments. Thank You...
I am looking for recommandations regarding the memory distribution for SQL 2000 server. In the memory tab of the server properties you can define use a fixed memory size or dynamically configure SQL server or even reserve physical memory for SQL server.
Are there any hints available or must it be handled according trial and error?
Thanks for any info
mipo
Running sqlserver 2000 on a w2k server with 1gb of memory. After a reboot the memory usage is around 500m but quickly climbs. At 1 point it was up to 1.5gb so it must have been swapping. Are there any good docs about this or any recommendations on how to limit sqlserver from using all the memory. It is the only application on the server so it isn't affecting anything else so maybe it isn't a problem. I just wanted to get people's inpit on this.
View 2 Replies View RelatedWe have a SQL server that has a failover cluster on our network. We are looking to updrade the memory by adding a couple gigs of ram.
We don't need to upgrade the failover cluster to have the exact amount of memory as the primary do we?
DotNetJunkie
I would like to ask regarding the memory allocation fo SQL Server 2000. For example if my Data Server have 8GB physical memory installed how much memory can SQL Server 2000 utilize? Based on my research and understing SQL 2000 Server can only utilize 3GB memory? But using the AWE you can set the memory to a maximum server memory?
View 8 Replies View RelatedI recently changed the max. memory option in SQL from 24 GB to 30GB but the perfmon counters still only show 24 GB. Any ideas on why it is not recognizing the change? The server has Win 2003 EE and 32 GB of RAM.
View 5 Replies View RelatedI have SQL Server 2000 STD installed on a Windows Server 2003 STD machine. It's essentially the only app on this box. I have 4GB of RAM installed. SQL is configured to dynamically allocate memory. I run a batch file daily to restart the SQL services as SQL does not seem to release memory once it's got it. I don't think this is a problem because, like I said, it's basically the only app. But I want to make sure my OS memory settings and SQL's memory settings are optimized. Will adding the /3gb switch to the boot.ini file make a difference? Also, can someone educate me a little on PAE and AWE?
Thanks
Hi. I'm a SQL Server novice, so apologies if any of this sounds simple.I am running Windows XP SP2, and have just installed SQLServer 2000. Ineed another application to connect to SQLServer, and am specifying itto do so via localhost:1433, but keep getting an error whenever I trydoing so saying it cannot connect to the database. A colleague of minehas the exact same set up on his machine, and he can connect to SQLServer fine. Running 'netstat -a' at the command line on his machinereveals that the system is listening to port 1433/ms-sql-s. Runningnetstat on my machine shows that the system is not listening to1433/ms-sql-ms. I have checked in Network Config in SQLServerEnterprise Manager, and TCP/IP is set to be using 1433.To confirm this, my application can connect over the network to mycolleague's SQL Server. but he cannot connect over the network to mine.So I'm pretty sure the issue is related to this 1433/ms-sql-s problem.Does anyone know how to resolve this? Many thanks.
View 1 Replies View Relatedi setup a 2 node sql cluster but 1433 is not listening. I check sql configuration manager and entered 1433 for all ip addresses restarted services but still not 1433
View 14 Replies View Related