My initial thought would be that it was a temporary connectivity
issue between CF and SQL Server, especially if it worked the second
time. Are SQL Server and CF running on the same physical box? Keep
an eye on it and if starts happening with regularity you'll want to
dig into things a bit deeper. I wouldn't bother rebooting anything
if it was a one-time problem.
Matt
On Jun 10, 2005, at 11:23 AM, Brent Helms wrote:
I received a error that said a stored procedure could not be found,
from a client application. After checking the database, the SP was
there, so I ran it again and it worked.
Does this hint that the Database temporarily failed, or the database
server temporarily failed?
If you were going to be pro-active on something like this, would you
recommend a stop/start on SQL Server, or in the extreme case,
rebooting the box? Or is it probably nothing, so just keep chugging
along and do nothing?
Any info is appreciated.
Regards,
Brent Helms
----------------------------------------------------------
To post, send email to [email protected]
To unsubscribe:
http://www.dfwcfug.org/form_MemberUnsubscribe.cfm
To subscribe:
http://www.dfwcfug.org/form_MemberRegistration.cfm
--
Matthew Woodward
[EMAIL PROTECTED]
----------------------------------------------------------
To post, send email to [email protected]
To unsubscribe:
http://www.dfwcfug.org/form_MemberUnsubscribe.cfm
To subscribe:
http://www.dfwcfug.org/form_MemberRegistration.cfm
