Showing posts with label messages. Show all posts
Showing posts with label messages. Show all posts

Monday, February 27, 2012

Help - Corrupted SQL Server 2K Log. Is this serious

Hello,

I have a SS2K (SP3) that is appending very wierd looking error messages
to the SQL Server Log (Current). The messages are not formatted as
other log entries. The messages suggest some kinda dump information.
The messages have the following characteristics:

Date Information is invalid
Source information is invalid
Message information is strange

The following is a message that appear in my current SQL Server Log

DATE:78008454
SOURCE: Module(MSVCRT+
Message (_endthread+000000C1)

There are many messages like this in the log.

Is this serious?

Thanks - CoviCovi (covilc@.earthlink.net) writes:
> I have a SS2K (SP3) that is appending very wierd looking error messages
> to the SQL Server Log (Current). The messages are not formatted as
> other log entries. The messages suggest some kinda dump information.
> The messages have the following characteristics:
> Date Information is invalid
> Source information is invalid
> Message information is strange
> The following is a message that appear in my current SQL Server Log
>
> DATE:78008454
> SOURCE: Module(MSVCRT+
> Message (_endthread+000000C1)
> There are many messages like this in the log.
> Is this serious?

When a connection runs into an execution error, one that really should
not occur, for instance an access violation, SQL Server terminates the
connection and leaves a stack dump in the error log. Most such dumps
are due to bugs in SQL Server, and could come from specific queries.
Hardware errors could be involved too. In the latter case, there is
certainly cause for alarm. If you want to sleep better at night, you
could run a DBCC CHECKDB on the database related to the dumps.

But stackdumps can occur on healthy machines too.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Sunday, February 19, 2012

help

every time i log onto yahoo messenger i keep getting this
screen full of messages and it shuts down my computer,
please help. gunnerIt probably doesn't have anything to do with SQL Server
security...not that I can think of anyway. You may want to
check Yahoo messenger help site instead:
http://help.yahoo.com/help/mesg/index.html
-Sue
On Fri, 9 Apr 2004 15:37:43 -0700, "gunner1469@.yahoo.com"
<anonymous@.discussions.microsoft.com> wrote:

>every time i log onto yahoo messenger i keep getting this
>screen full of messages and it shuts down my computer,
>please help. gunner

HelloWorld_CLR not sending messages anymore...........

Hello,

Yesterday I made the HelloWorld_CLR sample work and figured today I would create a simple windows service to immulate its functionality. When this was not working I tried the sample again and it stopped working. I have tried several things and nothing has worked. Has anyone seen this before or have any ideas on how I can get it working again? I even tried removing SQL Server and its samples then reinstalling to give me a clean slate but that did not work. I did not make any changes to the software nor did I make any changes to the database however the sample did so I need to make sure I can fix this incase it happens in development not to mention I need to continue development.

The Client Queue is normally empty but sometimes has a request to two in it. The Server Queue has alot in it that are both Request and an unspecified type or has a URL for a type. I would paste it in but it takes too much space. Please let me know if you have any ideas because I am not sure what else to try.

Bellow is a sample of the output from running this sample.

Connecting to SQL Server instance
Connected to SQL Server instance

Transaction 1 begun
Dialog begun from service (HelloWorldClient) to service (HelloWorldService)
Message sent of type 'Request'
Transaction 1 committed

Transaction 2 begun
Waiting for Response....
No message received - Ending dialog with Error
Transaction 2 committed

Connection closed - exiting

Press Enter to Exit

Thanks,
Scott Allison...

Here is a good article from Remus on diagnosing Service Broker problems:

http://blogs.msdn.com/remusrusanu/archive/2005/12/20/506221.aspx

|||

Hello Rushi,

I checked out the link you sent in your reply. I am not if when he states profiler he means the SQL Server Profiler and I am not familiar with it. I will play with it some but if this will give me the needed information I was wondering if you could tell me more on how to setup the options correctly and how to use it to attach to the local machine.

Thanks,

Scott Allison...

|||

Before using the profiler, you should probably check what's in the transmission queue:

select * from sys.transmission_queue

Other places to look for errors is the Intiator and Target queues.

Rushi