You cannot format the msmqlog.bin file. You can open a case with Microsoft
support and send the file.
You didn't explain what's the problem that you troubleshoot. Maybe if you
provide some details about the crash that you mentioned we can help to
understand it.
Thanks, Doron
--
This posting is provided "AS IS" with no warranties, and confers no rights.
.
"campwes" <***@discussions.microsoft.com> wrote in message news:506e01c48094$8c7e9e80$***@phx.gbl...
Muhammed,
Thanks for the reply. I enabled MSMQ logging, per the msmqfaq.doc
(applying the registry entries, as required in the faq), and set up mqtrace.
Now I can get the msmqlog.bin in .txt format. Does mqtrace provide the
complete msmqlog.bin file? The .bin file is MUCH larger that the .txt file.
Here's what I got:
<mqtrace>
mqtrace 1.3 - Manage MSMQ Release Bits Tracing.
Starting msmq trace logging to 'C:\WINDOWS\debug\msmqlog.bin'...
Updating msmq trace logging to 'C:\WINDOWS\debug\msmqlog.bin'...
msmq trace noise level is ERROR...
Querying if msmq logger is currently running...
Name: msmq
Age Limit: 15
Buffer Size: 64
Buffers Written: 19
Clock Type: System
Events Lost: 0
Flush Timer: 0
Buffers Free: 7
Buffers Lost: 0
File Mode: Circular
File Name: C:\WINDOWS\debug\msmqlog.bin
Logger Id: 2
Logger Thread Id: 2644
Maximum Buffers: 26
Maximum File Size: 4
Minimum Buffers: 4
Number of buffers: 9
Real Time Buffers Lost: 0
Provider Flags Level
----------------------------------------------------------------
---------------
* "MSMQ: General" (error) 0x00
{45033C79-EA31-4776-9BCD-94DB89AF3149} 0x00000001
0x00
* "MSMQ: AC" (error) 0x00
{322E0B22-0527-456E-A5EF-E5B591046A63} 0x00000001
0x00
* "MSMQ: Networking" (error) 0x00
{6E2C0612-BCF3-4028-8FF2-C60C288F1AF3} 0x00000001
0x00
* "MSMQ: SRMP" (error) 0x00
{DA1AF236-FAD6-4DA6-BD94-46395D8A3CF5} 0x00000001
0x00
* "MSMQ: RPC" (error) 0x00
{F8354C74-DE9F-48A5-8139-4ED1E9F20A1B} 0x00000001
0x00
* "MSMQ: DS" (error) 0x00
{5DC62C8C-BDF2-45A1-A06F-0C38CD5AF627} 0x00000001
0x00
* "MSMQ: Security" (error) 0x00
{90E950BB-6ACE-4676-98E0-F6CDC1403670} 0x00000001
0x00
* "MSMQ: Routing" (error) 0x00
{8753D150-950B-4774-AC14-9C6CBFF56A50} 0x00000001
0x00
* "MSMQ: XACT_General" (error) 0x00
{8FDA2BBD-347E-493C-B7D1-6B6FED88CE04} 0x00000001
0x00
* "MSMQ: XACT_Send" (error) 0x00
{485C37B0-9A15-4A2E-82E0-8E8C3A7B8234} 0x00000001
0x00
* "MSMQ: XACT_Receive" (error) 0x00
{7C916009-CF80-408B-9D91-9C2960118BE9} 0x00000001
0x00
* "MSMQ: XACT_Log" (error) 0x00
{1AC9B316-5B4E-4BBD-A2C9-1E70967A6FE1} 0x00000001
0x00
* "MSMQ: Log" (error) 0x00
{A13EC7BB-D592-4B93-80DA-C783F9708BD4} 0x00000001
0x00
The command completed successfully.
msmq logger is currently running, changing existing trace settings...
The command completed successfully.
mqtrace 1.3 - Manage MSMQ Release Bits Tracing.
Formatting binary log file 'C:\WINDOWS\debug\msmqlog.bin' to 'C:
\WINDOWS\debug\msmqlog.txt'.
Setting log file to: C:\WINDOWS\debug\msmqlog.bin
Getting guids from C:\Program Files\Support Tools\default.tmf
Event traces dumped to C:\WINDOWS\debug\msmqlog.txt
Event Summary dumped to C:\WINDOWS\debug\msmqlog.txt.sum
Exit Status: 2
</mqtrace>
So, is it not possible to discern why MSMQ keeps crashing without calling MS
Support? Thanks again.
- campwes
-----Original Message-----
The logging Mechanism in MSMQ v3.0 is somewhat different, there is no way
view the log file as a text file (as is the case with MSMQ v2.0). By
default error logging is enabled, you can also modify the level of logging,
via the mqtrace utility. Data is written to %windir%\debug\msmqlog.bin,
you can send the resulting log file to Microsoft Product Support Services
who can parse the file into a readable format.
See 15.2 and 15.3 in the MSMQ FAQ for more information on logging in MSMQ
http://www.microsoft.com/windows2000/technologies/communications/
msmq/wp_msm
qfaq.asp
--
Sincerely,
Muhammed Ismail
Please do not send email directly to this alias. This alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
Content-Class: urn:content-classes:message
Subject: How do I enable msmq diagnostic logging?
Date: Wed, 11 Aug 2004 08:17:32 -0700
Lines: 20
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Newsreader: Microsoft CDO for Windows 2000
Thread-Index: AcR/tlMF/k6tWXlmQF6xpNrPRub62g==
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Newsgroups: microsoft.public.msmq.performance
Path: cpmsftngxa06.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.msmq.performance:2669
NNTP-Posting-Host: tk2msftngxa12.phx.gbl 10.40.1.164
X-Tomcat-NG: microsoft.public.msmq.performance
Hi. I'm trying to troubleshoot our MSMQ 3.0 implementation, but I cannot
1. Click Start, click Run, type regedit, and then click OK.
hklm\software\microsoft\msmq\parameters\debug
3. On the Edit menu, point to New, and then click DWORD Value.
4. Type LoggingTypes, and then press ENTER.
5. On the Edit menu, click Modify.
6. Type c00000000, and then click OK.
I followed the instructions on my Windows Server 2003 box, but I don't see
the msmq.log file at \windows\debug\msmq.log. Any suggestions are
appreciated. Thanks!
- campwes
.