Install Problem: Shared Memory Provider: No Process Is On The Other End Of The Pipe.
Jul 5, 2006
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.
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
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'
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.
When 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.
Hello all, I have question regarding the error message that I'm getting above. I have a program written in .NET that is suppose to traverse through a database and retrieve various records and then write a summary record. The code worked without issue. The database the used to hold the data was a SQL 7.0. However, recently I moved the server over to SQL 2005. Since that time I have been getting the following error:
Description: [Microsoft][SQL Native Client]Named Pipes Provider: No process is on the other end of the pipe.
ramdomly throughout the execution of the program. It doesn't happen on record and is intermittent when it occurs.
Here is the code that is having issues any help would be appreciated.
Thanks Mike Gisonda
Dim mreleaseqty As Double Dim mmakeqty As Double Dim k As Integer Dim mbackorderqty As Double Dim mOnOrder As Double Dim mOnHand As Double Dim mMaximumqty As Double Dim mMinimumQty As Double Dim muomfactor As Double Dim mSafetyStockQty As Double Dim mQtyInTransit As Double Dim mQtyAllocatedWip As Double Dim mQtyAllocated As Double
Dim cnLean As New ADODB.Connection Dim cnSyspro As New ADODB.Connection Dim cnLean2 As New ADODB.Connection
Dim cmdPullItems As New ADODB.Command 'command to retrieve pull items Dim cmdWHTotals As New ADODB.Command 'command to get combined warehouse totals Dim cmdUpdatePull As New ADODB.Command Dim cmdBkOrd As New ADODB.Command Dim cmdInvMst As New ADODB.Command Dim cmdInitPull As New ADODB.Command 'command to clean our old pull data
Dim prmStockCode As New ADODB.Parameter 'parameter to supply stockcode.
Dim rsPullItems As New ADODB.Recordset 'recordset to hold pull items. Dim rsWHTotals As New ADODB.Recordset 'recordset to hold warehouse records Dim rsBkOrd As New ADODB.Recordset Dim rsInvMst As New ADODB.Recordset Dim rsSalesOrders As New ADODB.Recordset Dim rsWipMaster As New ADODB.Recordset
Dim mPullSQL As String Dim mWHSql As String Dim mBackOrderStr As String Dim mInvSQL As String Dim mStockCode As String Dim mSalesSQL As String Dim aBackOrderRec As Array Dim mReqDate Dim mShipDate As Date Dim mcol As Integer Dim mNewVal As Double Dim mWipSql As String Dim mAdjAmt As Double Dim mStockStatus As Integer Dim mBackOrder As Double Dim mBackLate1 As Double Dim mBackLate2 As Double Dim mBackLate3 As Double Dim mBackLate4 As Double Dim mWeeklyStDev As Double Dim mWeeklyUsage As Double
Dim mBackLog1 As Double Dim mBackLog2 As Double Dim mBackLog3 As Double Dim mBackLog4 As Double Dim mBackLog5 As Double Dim mBackLog6 As Double Dim mBackLog7 As Double Dim mBackLog8 As Double Dim mBackLog9 As Double Dim mBackLog10 As Double Dim mBackLog11 As Double Dim mBackLog12 As Double
Dim mLEAN_BACKORDER_BFLAG As Integer Dim mLEAN_LATE1_BFLAG As Integer Dim mLEAN_LATE2_BFLAG As Integer Dim mLEAN_LATE3_BFLAG As Integer Dim mLEAN_LATE4_BFLAG As Integer Dim mLEAN_BACKLOG1_BFLAG As Integer Dim mLEAN_BACKLOG2_BFLAG As Integer Dim mLEAN_BACKLOG3_BFLAG As Integer Dim mLEAN_BACKLOG4_BFLAG As Integer Dim mLEAN_BACKLOG5_BFLAG As Integer Dim mLEAN_BACKLOG6_BFLAG As Integer Dim mLEAN_BACKLOG7_BFLAG As Integer Dim mLEAN_BACKLOG8_BFLAG As Integer Dim mLEAN_BACKLOG9_BFLAG As Integer Dim mLEAN_BACKLOG10_BFLAG As Integer Dim mLEAN_BACKLOG11_BFLAG As Integer Dim mLEAN_BACKLOG12_BFLAG As Integer
Dim mBFlagValue As Integer Dim mFileNum As Integer Dim mTrnFileNum As Integer Dim mtest As String Dim mCountOfRecords As Long Dim mPullCount As String Dim rsPullcount As ADODB.Recordset Dim mCurRecordCount As Long
Dim mWipAllSQL As String Dim rsWipAll As New ADODB.Recordset
'On Error GoTo ehbtnUpdateLean_Click 'open connection to springdesign With cnLean .ConnectionString = "DSN=SPRINGDESIGN;UID=sa;PWD=" .Open() End With With cnLean2 .ConnectionString = "DSN=SPRINGDESIGN;UID=sa;PWD=" .Open() End With
'open connection to syspro With cnSyspro .ConnectionString = "DSN=COMPANYM;UID=sa;pwd=" .CommandTimeout = 300 .Open() End With btnUpdateLean.Enabled = False Me.Cursor = Cursors.WaitCursor
** Bunch of code to set up commands and select statements ** 'Initial command that will update the pull records as they are being processed. With cmdUpdatePull .let_ActiveConnection(cnLean) .CommandType = ADODB.CommandTypeEnum.adCmdStoredProc .CommandText = "sp_MX_Daily_UpdateMRPData" .CommandTimeout = 300 .Parameters.Refresh() End With
** More Code **
Try rsPullItems.CursorLocation = ADODB.CursorLocationEnum.adUseClient 'Get all the pull items. 'rsPullItems = cmdPullItems.Execute rsPullItems.Open(mPullSQL, cnLean2) rsPullItems.ActiveConnection = Nothing
'Initial flags used to determine if the individual sales order dates are 'before or after the request date. cmdUpdatePull.Parameters("@LEAN_BACKORDER_BFLAG").Value = 0 cmdUpdatePull.Parameters("@LEAN_LATE1_BFLAG").Value = 0 cmdUpdatePull.Parameters("@LEAN_LATE2_BFLAG").Value = 0 cmdUpdatePull.Parameters("@LEAN_LATE3_BFLAG").Value = 0 cmdUpdatePull.Parameters("@LEAN_LATE4_BFLAG").Value = 0
** ** If IsNothing(rsWHTotals) = False Then If rsWHTotals.EOF = False Then 'If there are values in the warehouse query. ** BUNCH MORE CODE ** cmdUpdatePull.Parameters("@stock_code").Value = mStockCode cmdUpdatePull.Parameters("@MINIMUM_QTY").Value = mMinimumQty cmdUpdatePull.Parameters("@MAXIMUM_QTY").Value = mMaximumqty cmdUpdatePull.Parameters("@SAFETYSTOCKQTY").Value = mSafetyStockQty
cmdUpdatePull.Parameters("@ON_HAND").Value = mOnHand cmdUpdatePull.Parameters("@ON_ORDER").Value = mOnOrder ** cmdUpdatePull.Parameters("@BACKORDER_QTY").Value = mbackorderqty mmakeqty = (mMaximumqty - mOnHand) If mmakeqty > 0 Then cmdUpdatePull.Parameters("@MAKE_QTY").Value = mmakeqty Else cmdUpdatePull.Parameters("@MAKE_QTY").Value = 0 End If
'Initiale Binary flags that represent if the ship date is 'before or after the request date. cmdUpdatePull.Parameters("@LEAN_BACKORDER_BFLAG").Value = 0 cmdUpdatePull.Parameters("@LEAN_LATE1_BFLAG").Value = 0 cmdUpdatePull.Parameters("@LEAN_LATE2_BFLAG").Value = 0 cmdUpdatePull.Parameters("@LEAN_LATE3_BFLAG").Value = 0 cmdUpdatePull.Parameters("@LEAN_LATE4_BFLAG").Value = 0
** more Code ** Try rsSalesOrders = New ADODB.Recordset rsSalesOrders.Open(mSalesSQL, cnSyspro) Catch ex As Exception mtest = "Exception Message: " & ex.Message & vbCrLf & "SQLStatement: " & mSalesSQL LogError(mStockCode, mtest) rsSalesOrders = Nothing End Try
If IsNothing(rsSalesOrders) = False Then Do While rsSalesOrders.EOF = False ** More Code ** Select Case mcol Case Is <= -5 cmdUpdatePull.Parameters("@LEAN_BACKORDER").Value = cmdUpdatePull.Parameters("@LEAN_BACKORDER").Value + mNewVal 'Check to see if the bit is marked. If not then mark it. If mBFlagValue <> (cmdUpdatePull.Parameters("@LEAN_BACKORDER_BFLAG").Value And mBFlagValue) Then cmdUpdatePull.Parameters("@LEAN_BACKORDER_BFLAG").Value = cmdUpdatePull.Parameters("@LEAN_BACKORDER_BFLAG").Value + mBFlagValue End If
mBackOrder = mBackOrder + mNewVal
Case Is = -4 cmdUpdatePull.Parameters("@LEAN_LATE4").Value = cmdUpdatePull.Parameters("@LEAN_LATE4").Value + mNewVal 'Check to see if the bit is marked. If not then mark it. If mBFlagValue <> (cmdUpdatePull.Parameters("@LEAN_LATE4_BFLAG").Value And mBFlagValue) Then cmdUpdatePull.Parameters("@LEAN_LATE4_BFLAG").Value = cmdUpdatePull.Parameters("@LEAN_LATE4_BFLAG").Value + mBFlagValue End If
mBackLate4 = mBackLate4 + mNewVal
Case Is = -3 cmdUpdatePull.Parameters("@LEAN_LATE3").Value = cmdUpdatePull.Parameters("@LEAN_LATE3").Value + mNewVal 'Check to see if the bit is marked. If not then mark it. If mBFlagValue <> (cmdUpdatePull.Parameters("@LEAN_LATE3_BFLAG").Value And mBFlagValue) Then cmdUpdatePull.Parameters("@LEAN_LATE3_BFLAG").Value = (cmdUpdatePull.Parameters("@LEAN_LATE3_BFLAG").Value + mBFlagValue) End If
mBackLate3 = mBackLate3 + mNewVal
Case Is = -2 cmdUpdatePull.Parameters("@LEAN_LATE2").Value = cmdUpdatePull.Parameters("@LEAN_LATE2").Value + mNewVal 'Check to see if the bit is marked. If not then mark it. If mBFlagValue <> (cmdUpdatePull.Parameters("@LEAN_LATE2_BFLAG").Value And mBFlagValue) Then cmdUpdatePull.Parameters("@LEAN_LATE2_BFLAG").Value = (cmdUpdatePull.Parameters("@LEAN_LATE2_BFLAG").Value + mBFlagValue) End If
mBackLate2 = mBackLate2 + mNewVal
Case -1 To 0 cmdUpdatePull.Parameters("@LEAN_LATE1").Value = cmdUpdatePull.Parameters("@LEAN_LATE1").Value + mNewVal 'Check to see if the bit is marked. If not then mark it. If mBFlagValue <> (cmdUpdatePull.Parameters("@LEAN_LATE1_BFLAG").Value And mBFlagValue) Then cmdUpdatePull.Parameters("@LEAN_LATE1_BFLAG").Value = (cmdUpdatePull.Parameters("@LEAN_LATE1_BFLAG").Value + mBFlagValue) End If
mBackLate1 = mBackLate1 + mNewVal
Case Is = 1 cmdUpdatePull.Parameters("@LEAN_BACKLOG1").Value = cmdUpdatePull.Parameters("@LEAN_BACKLOG1").Value + mNewVal 'Check to see if the bit is marked. If not then mark it. If mBFlagValue <> (cmdUpdatePull.Parameters("@LEAN_BACKLOG1_BFLAG").Value And mBFlagValue) Then cmdUpdatePull.Parameters("@LEAN_BACKLOG1_BFLAG").Value = (cmdUpdatePull.Parameters("@LEAN_BACKLOG1_BFLAG").Value + mBFlagValue) End If
mBackLog1 = mBackLog1 + mNewVal Case Is = 2 cmdUpdatePull.Parameters("@LEAN_BACKLOG2").Value = cmdUpdatePull.Parameters("@LEAN_BACKLOG2").Value + mNewVal 'Check to see if the bit is marked. If not then mark it. If mBFlagValue <> (cmdUpdatePull.Parameters("@LEAN_BACKLOG2_BFLAG").Value And mBFlagValue) Then cmdUpdatePull.Parameters("@LEAN_BACKLOG2_BFLAG").Value = (cmdUpdatePull.Parameters("@LEAN_BACKLOG2_BFLAG").Value + mBFlagValue) End If
mBackLog2 = mBackLog2 + mNewVal
Case Is = 3 cmdUpdatePull.Parameters("@LEAN_BACKLOG3").Value = cmdUpdatePull.Parameters("@LEAN_BACKLOG3").Value + mNewVal If mBFlagValue <> (cmdUpdatePull.Parameters("@LEAN_BACKLOG3_BFLAG").Value And mBFlagValue) Then cmdUpdatePull.Parameters("@LEAN_BACKLOG3_BFLAG").Value = (cmdUpdatePull.Parameters("@LEAN_BACKLOG3_BFLAG").Value + mBFlagValue) End If
mBackLog3 = mBackLog3 + mNewVal
Case Is = 4 cmdUpdatePull.Parameters("@LEAN_BACKLOG4").Value = cmdUpdatePull.Parameters("@LEAN_BACKLOG4").Value + mNewVal If mBFlagValue <> (cmdUpdatePull.Parameters("@LEAN_BACKLOG4_BFLAG").Value And mBFlagValue) Then cmdUpdatePull.Parameters("@LEAN_BACKLOG4_BFLAG").Value = (cmdUpdatePull.Parameters("@LEAN_BACKLOG4_BFLAG").Value + mBFlagValue) End If
mBackLog4 = mBackLog4 + mNewVal
Case Is = 5 cmdUpdatePull.Parameters("@LEAN_BACKLOG5").Value = cmdUpdatePull.Parameters("@LEAN_BACKLOG5").Value + mNewVal If mBFlagValue <> (cmdUpdatePull.Parameters("@LEAN_BACKLOG5_BFLAG").Value And mBFlagValue) Then cmdUpdatePull.Parameters("@LEAN_BACKLOG5_BFLAG").Value = (cmdUpdatePull.Parameters("@LEAN_BACKLOG5_BFLAG").Value + mBFlagValue) End If
mBackLog5 = mBackLog5 + mNewVal
Case Is = 6 cmdUpdatePull.Parameters("@LEAN_BACKLOG6").Value = cmdUpdatePull.Parameters("@LEAN_BACKLOG6").Value + mNewVal If mBFlagValue <> (cmdUpdatePull.Parameters("@LEAN_BACKLOG6_BFLAG").Value And mBFlagValue) Then cmdUpdatePull.Parameters("@LEAN_BACKLOG6_BFLAG").Value = (cmdUpdatePull.Parameters("@LEAN_BACKLOG6_BFLAG").Value + mBFlagValue) End If
mBackLog6 = mBackLog6 + mNewVal
Case Is = 7 cmdUpdatePull.Parameters("@LEAN_BACKLOG7").Value = cmdUpdatePull.Parameters("@LEAN_BACKLOG7").Value + mNewVal If mBFlagValue <> (cmdUpdatePull.Parameters("@LEAN_BACKLOG7_BFLAG").Value And mBFlagValue) Then cmdUpdatePull.Parameters("@LEAN_BACKLOG7_BFLAG").Value = (cmdUpdatePull.Parameters("@LEAN_BACKLOG7_BFLAG").Value + mBFlagValue) End If
mBackLog7 = mBackLog7 + mNewVal
Case Is = 8 cmdUpdatePull.Parameters("@LEAN_BACKLOG8").Value = cmdUpdatePull.Parameters("@LEAN_BACKLOG8").Value + mNewVal If mBFlagValue <> (cmdUpdatePull.Parameters("@LEAN_BACKLOG8_BFLAG").Value And mBFlagValue) Then cmdUpdatePull.Parameters("@LEAN_BACKLOG8_BFLAG").Value = (cmdUpdatePull.Parameters("@LEAN_BACKLOG8_BFLAG").Value + mBFlagValue) End If
mBackLog8 = mBackLog8 + mNewVal
Case Is = 9 cmdUpdatePull.Parameters("@LEAN_BACKLOG9").Value = cmdUpdatePull.Parameters("@LEAN_BACKLOG9").Value + mNewVal If mBFlagValue <> (cmdUpdatePull.Parameters("@LEAN_BACKLOG9_BFLAG").Value And mBFlagValue) Then cmdUpdatePull.Parameters("@LEAN_BACKLOG9_BFLAG").Value = (cmdUpdatePull.Parameters("@LEAN_BACKLOG9_BFLAG").Value + mBFlagValue) End If
mBackLog9 = mBackLog9 + mNewVal
Case Is = 10 cmdUpdatePull.Parameters("@LEAN_BACKLOG10").Value = cmdUpdatePull.Parameters("@LEAN_BACKLOG10").Value + mNewVal If mBFlagValue <> (cmdUpdatePull.Parameters("@LEAN_BACKLOG10_BFLAG").Value And mBFlagValue) Then cmdUpdatePull.Parameters("@LEAN_BACKLOG10_BFLAG").Value = (cmdUpdatePull.Parameters("@LEAN_BACKLOG10_BFLAG").Value + mBFlagValue) End If
mBackLog10 = mBackLog10 + mNewVal
Case Is = 11 cmdUpdatePull.Parameters("@LEAN_BACKLOG11").Value = cmdUpdatePull.Parameters("@LEAN_BACKLOG11").Value + mNewVal If mBFlagValue <> (cmdUpdatePull.Parameters("@LEAN_BACKLOG11_BFLAG").Value And mBFlagValue) Then cmdUpdatePull.Parameters("@LEAN_BACKLOG11_BFLAG").Value = (cmdUpdatePull.Parameters("@LEAN_BACKLOG11_BFLAG").Value + mBFlagValue) End If
mBackLog11 = mBackLog11 + mNewVal
Case Is = 12 cmdUpdatePull.Parameters("@LEAN_BACKLOG12").Value = cmdUpdatePull.Parameters("@LEAN_BACKLOG12").Value + mNewVal If mBFlagValue <> (cmdUpdatePull.Parameters("@LEAN_BACKLOG12_BFLAG").Value And mBFlagValue) Then cmdUpdatePull.Parameters("@LEAN_BACKLOG12_BFLAG").Value = (cmdUpdatePull.Parameters("@LEAN_BACKLOG12_BFLAG").Value + mBFlagValue) End If
mBackLog12 = mBackLog12 + mNewVal
End Select End If rsSalesOrders.MoveNext() Loop rsSalesOrders.Close() rsSalesOrders = Nothing End If
Else cmdUpdatePull.Parameters("@stock_code").Value = mStockCode End If rsWHTotals.Close() rsWHTotals = Nothing Else 'rswhtotal is nothing cmdUpdatePull.Parameters("@stock_code").Value = mStockCode End If 'rswhtotal is nothing
'Update the record in DesignLean Try ********* This is where it fails ********* cmdUpdatePull.Execute()
SqlConnection cmiDBCompConnection = new SqlConnection(myConnectString);
cmiDBCompConnection.Open();
when I attempt to run the apps, I get the
"System.Data.SqlClient.SqlException was unhandled Message="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.)".....
any idea what I am doing wrong, given that the connection string works using other means? I am using Windows authentication.
To add, the error in my log shows:
2007-03-17 21:10:55.82 Logon Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: <local machine>]
I had to un-install and re-install SQL Server 2005 for a different problem which has been resolved.
But now when I try to make a connection to the database I get the following error:
"...No process is on the other end of the pipe"
I have verified that the server allows named pipeing which seems to be the common answer I found after searching. I have also verified that the account I use is setup and has all the proper permissions.
Can someone help me in resolving this issue noting what I have verified above???
I'm currently having an issue with a linked server. Here's the surrounding information:
A) I have a clustered SQL Server 2005 Instance (A) and a SQL Server 2000 instance (B). B) There is a linked server on A to B. When I set it up, I did run the fix to ensure A could talk to B (There was an issue with communication between 2005 and 2000 servers). It has been there since I installed A, and has worked fine.. Until last week. C) This linked server uses static credentials to connect to B. D) Named Pipes are enabled on both servers to listen to both connections on both A and B in cliconfg. So A has a named pipe listening for B, and B has a named pipe listening for A. E) A has a view that looks at a table on B - It's a table view, very simple, just pulls in all the data from the table on B.
So, I go to do a select statement from the view, connected as a user other then 'sa'. I then get the error:
Named Pipes Provider: Could not open a connection to SQL Server Linked Server Error Source: ncli Client (Paraphrasing, didn't copy that down, but it was the ODBC connector)
Well, that's odd. It's been working fine for months now..
I then go and connect as sa on A to query B. It works! Mind you, absolutely NO QUERY from A to B will run again until I run SOME kind of query has been run as sa on A.
Mind you, this is not a credential issue. Every user who connects to the linked server to B uses a stored credential that is DBO to the database on B. The same User Name and Password exists on both A and B.
Also of note, I check the activity monitor. There's a process that is "dormant" every time I run a query against the view. The details of this connection are:
sp_reset_connection;1
My question is, why is it resetting the connection on B when being queried from A? Why is it "all of a sudden" a problem? Are there any changes that coudl ahve been made that would cause this?
Any help with this confusing issue would be appreciated.
I downloaded MS Pet Shop 4.0 recently for best-practice training purposes. The installation went smoothly with a SQL Server 2005 backend. At first I had a problem authenticating the mspetshop4 user in the database, but that was solved by fixing some settings with the password policy. Now the mspetshop4 user is authenticated properly, but I came across this error instead:Server Error in '/Web' Application. 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.) 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: 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.)
Source Error:
Line 216: Line 217: if (conn.State != ConnectionState.Open) Line 218: conn.Open(); Line 219: Line 220: cmd.Connection = conn;
Source File: C:Program FilesMicrosoft.NET Pet Shop 4.0DBUtilitySQLHelper.cs Line: 218
Stack Trace:
[SqlException (0x80131904): 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.)] System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +117 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +346 System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error) +619 System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj) +224 System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32 bytesExpected) +113 System.Data.SqlClient.TdsParserStateObject.ReadBuffer() +59 System.Data.SqlClient.TdsParserStateObject.ReadByte() +36 System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +181 System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK) +56 System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +1083 System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +272 System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +688 System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +82 System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +558 System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +126 System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +651 System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +160 System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +122 System.Data.SqlClient.SqlConnection.Open() +229 PetShop.DBUtility.SqlHelper.PrepareCommand(SqlCommand cmd, SqlConnection conn, SqlTransaction trans, CommandType cmdType, String cmdText, SqlParameter[] cmdParms) in C:Program FilesMicrosoft.NET Pet Shop 4.0DBUtilitySQLHelper.cs:218 PetShop.DBUtility.SqlHelper.ExecuteReader(String connectionString, CommandType cmdType, String cmdText, SqlParameter[] commandParameters) in C:Program FilesMicrosoft.NET Pet Shop 4.0DBUtilitySQLHelper.cs:127 PetShop.SQLServerDAL.Category.GetCategories() in C:Program FilesMicrosoft.NET Pet Shop 4.0SQLServerCategory.cs:27 PetShop.BLL.Category.GetCategories() in C:Program FilesMicrosoft.NET Pet Shop 4.0BLLCategory.cs:20 PetShop.Web.NavigationControl.BindCategories() in c:Program FilesMicrosoft.NET Pet Shop 4.0WebControlsNavigationControl.ascx.cs:53 PetShop.Web.NavigationControl.Page_Load(Object sender, EventArgs e) in c:Program FilesMicrosoft.NET Pet Shop 4.0WebControlsNavigationControl.ascx.cs:27 System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +31 System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +68 System.Web.UI.Control.OnLoad(EventArgs e) +88 System.Web.UI.Control.LoadRecursive() +74 System.Web.UI.Control.LoadRecursive() +158 System.Web.UI.BasePartialCachingControl.LoadRecursive() +61 System.Web.UI.Control.LoadRecursive() +158 System.Web.UI.Control.LoadRecursive() +158 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3035
Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42Now I'm clueless. What does No process at the other end of the pipe mean?
I have a Windows sever 2012 with sql server 2012 enterprise. Ram size is 22GB. Sometimes SQL sever takes 95% memory.My question, How to reduce memory size without killing any process because it's production server.So there are many background process is running. And,Is there any guides to learn why Memory is raise d so high and how to reduce it.
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.
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?
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 ?
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.
[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.
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.
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.
I am running a .Net Windows Service hourly which connects to Sybase Link Server thru SQL Server 2000. The service is a threaded application as it spawns 40 threads to connect to Sybase DB's using 'openquery' from SQL stored procs.
After it ran for hours (approx 30 Hrs), the when the service calls SP whcih has got openqeury to Sybase Linked Servers fails. It throws following exception,
"System.Data.SqlClient.SqlException: OLE DB provider 'Sybase.ASEOLEDBProvider' reported an error. The provider ran out of memory."
The sybase provider is told to use Out of SQL Server process memory. When the sybase provider runs out of memory, I checked the Available free memory in the machine. It is still 4GB out of 8GB.
Please let me know the reason for the Provider running out of memory often if anybody has faced this issue before.
The version of the Sybase provider in the machine is Sybase.ASEOLEDBProvider 5.0.
I have a problem with a PIPE "|" delimited flat file. I have a column "Description" in which we get a string in which we have PIPE "|" as data. How we can skip this and load it as a data into the column Description.
I frequently see the following message on SQL Server log
2008-06-09 07:46:18.17 spid3s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 1079156, committed (KB): 17156388, memory utilization: 6%.
What does it indicates and what appropriate action has to be taken to fix it.
The database runs on
SQL 2005 Dev 64-bit SP2 9.00.3042.00 Win 2003 standard x64 SP2 16GB RAM
I am using a tool to monitor SQL Server and Windows. It is warning me that:
Process 1004:services has a virtual address space of 1,846.20 MB. This is close to the Windows two gigabyte address space limit.
When locate the process 1004, it shows 15 threads that Elapsed time for all of them is 1d, 3hrs. The Thread state is Waiting and the Thread Wait Reason is "Waiting for an Execution Delay to be resolved".
I think that 1d, 3hrs is from the time I rebooted my server.
Out techs informed me that they are getting reports of a system slow down. When they look, they find sqlserver.exe has lots of memory allocated to it. They reboot the server and then it runs okay for a few weeks. They tell me this just started happening recently.
SQLServer itself has not been touched in months. They are, however, starting to use one of the databases heavier.
I found a setting where you can set max_server_memory. Any problems if I set this to a value?
Hi AllSome my SQL Server are experience high memory usage.1. How can I detect which process which process cause the big memoryusage and not released?2. Which sql server components in this memory, and what are their usagedistribution?Any help will be appreciated.ThanksWillie
I got a Small Business Server 2003 running. It has 2 sqlserverprocesses. One of them is growing by 200mb every day. Does anyone havea clue to this. It's serving as a printserver, fileserver and exchangeserver. There is no specific use of the sqlserver. The antivirus isMCaffee
I see the following message in SQL Server logs. What does this indicates. What should I do to avoid this.
2008-05-20 01:25:02.12 spid2s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 33920, committed (KB): 15142988, memory utilization: 0%.
The server configuration is
SQL 2005 Dev edition SP2 64bit Win 2003 R2 SP2 Standard X64 editioin RAM size is 16GB
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.
In my SQL Server Errorlog, I see the below error. The system has 8 GB of RAM with enough free RAM, something I can do to prevent this alert? (Note: I have no MIN/MAX memory set on this Instance)
A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 328 seconds. Working set (KB): 76896, committed (KB): 167628, memory utilization: 45%.
I have just installed MS SQL Server 2005 Express edition along with the SSMSE. I am using windows authentication. When I open SSMSE it connects me to a 'local instance' of the server. From there I right click on Database and select to add a new Database and I get the error above. I think I only need to allow local connections to the engine but I have tried allowing remote conections with all varations of named pipes and TCP/IP. I am running on Windows XP SP2 (home).
Hi, I'm running an application on a server which grabs data from a database table on another server using SqlConnection, SqlDataAdapter and DataSet. The application then updates every row in that DataSet's DataTable and the updates are saved back using DataAdapter. The code is pretty much straightforward code that you would find on MSDN documentation for using DataSets. The table contains a little over a million rows. When I run the application, I get an error saying the Server Application is not available. Upon looking into the application event log, I get this message. aspnet_wp.exe was recycled because memory consumption exceeded the 306 MB (60 percent of available RAM) How do I get round this? I thought DataSets were supposed to handle large datatables comfortably without having memory issues. -Thanks