You can review the setup log for any errors (file called sqlsp.log in the
windows directory). It is perfectly safe to run SP4 again to try and make it
stick (assuming you have the system database backups just in case you need
to regress)
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
"Leon Parker" <u23479@.uwe> wrote in message news:625d255c1f101@.uwe...
>I upgraded from SQL 2000 Service Pack 3 to SQL 2000 Service Pack 4. The
> install says it completed but after I rebooted and did a select @.@.version
> it
> still shows SP3. I only have a default instance so I know that it
> installed
> on the right instance. Could anyone help me out with this?I tried it several times but got the same result.
I've attached a copy of my sqlsp.log file. I looked at the sqlsp.log file
and it only listed one non-fatal error...I can't see this being the problem
considering it was nonfatal.
Jasper Smith wrote:[vbcol=seagreen]
>You can review the setup log for any errors (file called sqlsp.log in the
>windows directory). It is perfectly safe to run SP4 again to try and make i
t
>stick (assuming you have the system database backups just in case you need
>to regress)
>|||I upgraded from SQL 2000 Service Pack 3 to SQL 2000 Service Pack 4. The
install says it completed but after I rebooted and did a select @.@.version it
still shows SP3. I only have a default instance so I know that it installed
on the right instance. Could anyone help me out with this?|||You can review the setup log for any errors (file called sqlsp.log in the
windows directory). It is perfectly safe to run SP4 again to try and make it
stick (assuming you have the system database backups just in case you need
to regress)
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
"Leon Parker" <u23479@.uwe> wrote in message news:625d255c1f101@.uwe...
>I upgraded from SQL 2000 Service Pack 3 to SQL 2000 Service Pack 4. The
> install says it completed but after I rebooted and did a select @.@.version
> it
> still shows SP3. I only have a default instance so I know that it
> installed
> on the right instance. Could anyone help me out with this?|||I tried it several times but got the same result.
I've attached a copy of my sqlsp.log file. I looked at the sqlsp.log file
and it only listed one non-fatal error...I can't see this being the problem
considering it was nonfatal.
Jasper Smith wrote:[vbcol=seagreen]
>You can review the setup log for any errors (file called sqlsp.log in the
>windows directory). It is perfectly safe to run SP4 again to try and make i
t
>stick (assuming you have the system database backups just in case you need
>to regress)
>|||What does the following query return?
SELECT SERVERPROPERTY('ProductLevel')
Hope this helps.
Dan Guzman
SQL Server MVP
"Leon Parker" <u23479@.uwe> wrote in message news:625d255c1f101@.uwe...
>I upgraded from SQL 2000 Service Pack 3 to SQL 2000 Service Pack 4. The
> install says it completed but after I rebooted and did a select @.@.version
> it
> still shows SP3. I only have a default instance so I know that it
> installed
> on the right instance. Could anyone help me out with this?|||What does the following query return?
SELECT SERVERPROPERTY('ProductLevel')
Hope this helps.
Dan Guzman
SQL Server MVP
"Leon Parker" <u23479@.uwe> wrote in message news:625d255c1f101@.uwe...
>I upgraded from SQL 2000 Service Pack 3 to SQL 2000 Service Pack 4. The
> install says it completed but after I rebooted and did a select @.@.version
> it
> still shows SP3. I only have a default instance so I know that it
> installed
> on the right instance. Could anyone help me out with this?|||SP3....
Dan Guzman wrote:[vbcol=seagreen]
>What does the following query return?
> SELECT SERVERPROPERTY('ProductLevel')
>
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200606/1|||SP3....
Dan Guzman wrote:[vbcol=seagreen]
>What does the following query return?
> SELECT SERVERPROPERTY('ProductLevel')
>
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200606/1
Showing posts with label errors. Show all posts
Showing posts with label errors. Show all posts
Wednesday, March 28, 2012
Problem With SQL Server
Hello,
Do any body knows about following errors
2006-05-09 11:51:51.77 spid99 Error: 4014, Severity: 20, State: 2.
2006-05-09 11:51:51.77 spid99 A fatal error occurred while reading the
input stream from the network. The session will be terminated.
2006-05-09 11:51:52.44 Server Error: 4014, Severity: 20, State: 2.
2006-05-09 11:51:52.44 Server A fatal error occurred while reading the
input stream from the network. The session will be terminated.
I am getting this error frequently, especially under mediam load. Pls help"input stream from the network" suggests you have networking issue. start
with network monitor to see if there is any problem.
http://support.microsoft.com/kb/812953/
-oj
"kailux4" <kailux4@.discussions.microsoft.com> wrote in message
news:CFDE6666-841F-4FFE-AC07-E4D60AB6D464@.microsoft.com...
> Hello,
> Do any body knows about following errors
> 2006-05-09 11:51:51.77 spid99 Error: 4014, Severity: 20, State: 2.
> 2006-05-09 11:51:51.77 spid99 A fatal error occurred while reading
> the
> input stream from the network. The session will be terminated.
> 2006-05-09 11:51:52.44 Server Error: 4014, Severity: 20, State: 2.
> 2006-05-09 11:51:52.44 Server A fatal error occurred while reading
> the
> input stream from the network. The session will be terminated.
> I am getting this error frequently, especially under mediam load. Pls help
>
Do any body knows about following errors
2006-05-09 11:51:51.77 spid99 Error: 4014, Severity: 20, State: 2.
2006-05-09 11:51:51.77 spid99 A fatal error occurred while reading the
input stream from the network. The session will be terminated.
2006-05-09 11:51:52.44 Server Error: 4014, Severity: 20, State: 2.
2006-05-09 11:51:52.44 Server A fatal error occurred while reading the
input stream from the network. The session will be terminated.
I am getting this error frequently, especially under mediam load. Pls help"input stream from the network" suggests you have networking issue. start
with network monitor to see if there is any problem.
http://support.microsoft.com/kb/812953/
-oj
"kailux4" <kailux4@.discussions.microsoft.com> wrote in message
news:CFDE6666-841F-4FFE-AC07-E4D60AB6D464@.microsoft.com...
> Hello,
> Do any body knows about following errors
> 2006-05-09 11:51:51.77 spid99 Error: 4014, Severity: 20, State: 2.
> 2006-05-09 11:51:51.77 spid99 A fatal error occurred while reading
> the
> input stream from the network. The session will be terminated.
> 2006-05-09 11:51:52.44 Server Error: 4014, Severity: 20, State: 2.
> 2006-05-09 11:51:52.44 Server A fatal error occurred while reading
> the
> input stream from the network. The session will be terminated.
> I am getting this error frequently, especially under mediam load. Pls help
>
Monday, March 12, 2012
Problem with Returning a recordset from a stored procedure in ADO/VBScript
I'm having trouble getting a recordset out of stored procedure in ADO. The SP executes without errors, but the recordset object I return into is always closed.
Here is my code:
<%
.....
Set cmm = Server.CreateObject("ADODB.Command")
Set cmm.ActiveConnection = Connect
cmm.CommandType = adCmdStoredProc
cmm.CommandText = "dbo.client_updates_proc"
cmm.Parameters.Refresh
cmm.Parameters(1) = client_id
Set logRS = cmm.Execute()
if not logRS.EOF then
.....
%>
My SP has one parameter, which I set above, and it ends with a select statement. When I run the SP in Query Analyzer, it outputs the table of results as is should, but I always get an error on 'if logRS.EOF then', saying that the object is closed.A good place to start looking is the ADO Connection Error collection. Check to see if Connect.Errors.Count > 0. If so, you will probably find your problem there.
Also, you can try adding SET NOCOUNT ON at the beginning of your SP, and SET NOCOUNT OFF at the end, before you return your recordset. Sometimes the command object stops asking for data when it gets the "X records affected" messages.
Finally, if that doesn't work, try being more explicit with your parameter naming. A good (and more readable) approach would be to use the CreateParameter function.
CreateParameter([Name As String], [Type As DataTypeEnum = adEmpty], [Direction As ParameterDirectionEnum = adParamInput], [Size As ADO_LONGPTR], [Value]) As Parameter
Assume your parameter is an INT named @.my_param
cmm.Parameters.Append cmm.CreateParameter("@.my_param",3,1, 4,client_id)
[Note: the values of DataTypeEnum and ParameterDriectionEnum can be found at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdaenumnz_2.asp ]
Hope this helps...|||Ahh. Thank you so much. It was the NOCOUNT property.
Here is my code:
<%
.....
Set cmm = Server.CreateObject("ADODB.Command")
Set cmm.ActiveConnection = Connect
cmm.CommandType = adCmdStoredProc
cmm.CommandText = "dbo.client_updates_proc"
cmm.Parameters.Refresh
cmm.Parameters(1) = client_id
Set logRS = cmm.Execute()
if not logRS.EOF then
.....
%>
My SP has one parameter, which I set above, and it ends with a select statement. When I run the SP in Query Analyzer, it outputs the table of results as is should, but I always get an error on 'if logRS.EOF then', saying that the object is closed.A good place to start looking is the ADO Connection Error collection. Check to see if Connect.Errors.Count > 0. If so, you will probably find your problem there.
Also, you can try adding SET NOCOUNT ON at the beginning of your SP, and SET NOCOUNT OFF at the end, before you return your recordset. Sometimes the command object stops asking for data when it gets the "X records affected" messages.
Finally, if that doesn't work, try being more explicit with your parameter naming. A good (and more readable) approach would be to use the CreateParameter function.
CreateParameter([Name As String], [Type As DataTypeEnum = adEmpty], [Direction As ParameterDirectionEnum = adParamInput], [Size As ADO_LONGPTR], [Value]) As Parameter
Assume your parameter is an INT named @.my_param
cmm.Parameters.Append cmm.CreateParameter("@.my_param",3,1, 4,client_id)
[Note: the values of DataTypeEnum and ParameterDriectionEnum can be found at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdaenumnz_2.asp ]
Hope this helps...|||Ahh. Thank you so much. It was the NOCOUNT property.
Subscribe to:
Posts (Atom)