|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
SQL Profiler error message?was wondering if anyone could help shed some light on an error message that I've noticed popped up a couple of times in running SQL Profiler: SQL Server Profiler Failed to read trace data. [Microsoft][SQL Native Client]TCP Provider: The specified network name is no longer available. (State 08501)(Code 64) [Microsoft][SQL Native Client]Communication link failure (State 08501)(Code 64) Everything seems to be working properly still in that our SQL Server is up and running. Just wondering if this is something that I should be concerned or something else that I need to be aware of? Any info would be appreciative. J This would indicate some possible network connectivity issues.
Somewhere along the line the two computers can not talk to each other. It could be for a million reasons. Do you have intermittent outages? -- Show quote/* Warren Brunk - MCITP - SQL 2005, MCDBA www.techintsolutions.com Tech Blog - www.technologyis.com */ "J" <IDontLikeSpam@Nowhere.com> wrote in message news:eTPRYqt9GHA.536@TK2MSFTNGP04.phx.gbl... > Hello. Sorry if this isn't the appropriate place to ask this question but > I was wondering if anyone could help shed some light on an error message > that I've noticed popped up a couple of times in running SQL Profiler: > > > SQL Server Profiler > Failed to read trace data. > [Microsoft][SQL Native Client]TCP Provider: The specified network name is > no longer available. > (State 08501)(Code 64) > [Microsoft][SQL Native Client]Communication link failure (State > 08501)(Code 64) > > > Everything seems to be working properly still in that our SQL Server is up > and running. Just wondering if this is something that I should be > concerned or something else that I need to be aware of? > > Any info would be appreciative. > > J > I recently ran a test in that I had Profiler running from 2 separate
machines (A and B) and noticed that I got the same error message on the new machine (B) that I was having it run from and the old machine (A) that I was getting the error message didn't have an error and that it was still running just fine. So I think you are correct in that it maybe perhaps a network interruption coming from machine (A)...but I'm pretty sure both machines are on the same network so I would have assumed that I would've gotten the error message on both machines? Thanks for your reply Warren. I totally appreciate it. J Show quote "Warren Brunk" <wbr***@techintsolutions.com> wrote in message news:%23j8fyWv9GHA.3264@TK2MSFTNGP04.phx.gbl... > This would indicate some possible network connectivity issues. > > Somewhere along the line the two computers can not talk to each other. > > It could be for a million reasons. > > Do you have intermittent outages? > > > > -- > /* > Warren Brunk - MCITP - SQL 2005, MCDBA > www.techintsolutions.com > Tech Blog - www.technologyis.com > */ > > > "J" <IDontLikeSpam@Nowhere.com> wrote in message > news:eTPRYqt9GHA.536@TK2MSFTNGP04.phx.gbl... >> Hello. Sorry if this isn't the appropriate place to ask this question >> but I was wondering if anyone could help shed some light on an error >> message that I've noticed popped up a couple of times in running SQL >> Profiler: >> >> >> SQL Server Profiler >> Failed to read trace data. >> [Microsoft][SQL Native Client]TCP Provider: The specified network name is >> no longer available. >> (State 08501)(Code 64) >> [Microsoft][SQL Native Client]Communication link failure (State >> 08501)(Code 64) >> >> >> Everything seems to be working properly still in that our SQL Server is >> up and running. Just wondering if this is something that I should be >> concerned or something else that I need to be aware of? >> >> Any info would be appreciative. >> >> J >> > >  |
|||||||||||||||||||||||
Other interesting topics