|
Home > Archive > BizTalk Server General > January 2005 > Rogue Jupiter debug code
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Rogue Jupiter debug code
|
|
| Hugo Rodger-Brown 2005-01-28, 5:49 pm |
| Whilst monitoring debug info using dbgview.exe I get a lot of entries
similar to the following:
[3820]
d:\depot4000qfe\voyqfe\source\private\mo
zart\source\engine\msg\endpointmanag
er\epmreceivemanager\receiverrecord.cpp(151): Error - 0x80070057
[3136]
c:\depot4000\jupiter\source\private\moza
rt\source\engine\common\dbaccessor\t
ransactions.cpp(80): Error - 0x8000ffff
The paths don't exist, and the processes generating the messages are
btsntsvc.exe.
The reference to Jupiter suggest that this is something left over from early
days in the product cycle, and the connotations of "QFE" are a bit alarming.
Is this something that other people are seeing, am I running an older
version of btsntsvc.exe, and is it anything to worry about?
I'd be very grateful if someone from MSFT could help out here.
Hugo
| |
| Tomas Restrepo \(MVP\) 2005-01-28, 8:46 pm |
| Hugo,
> Whilst monitoring debug info using dbgview.exe I get a lot of entries
> similar to the following:
>
> [3820]
>
d:\depot4000qfe\voyqfe\source\private\mo
zart\source\engine\msg\endpointmanag[vbc
ol=seagreen]
> er\epmreceivemanager\receiverrecord.cpp(151): Error - 0x80070057
> [3136]
>[/vbcol]
c:\depot4000\jupiter\source\private\moza
rt\source\engine\common\dbaccessor\t[vbc
ol=seagreen]
> ransactions.cpp(80): Error - 0x8000ffff
>
> The paths don't exist, and the processes generating the messages are
> btsntsvc.exe.
>
> The reference to Jupiter suggest that this is something left over from[/vbcol]
early
> days in the product cycle, and the connotations of "QFE" are a bit
alarming.
> Is this something that other people are seeing, am I running an older
> version of btsntsvc.exe, and is it anything to worry about?
>
> I'd be very grateful if someone from MSFT could help out here.
I do not know about the QFE thingie, but yes, I've seen these messages a lot
(since I do use a lot DbgView), and they are *very* annoying.
--
Tomas Restrepo
tomasr@mvps.org
| |
| Asbjørn Rygg 2005-01-29, 2:46 am |
| Hugo Rodger-Brown wrote:
> Whilst monitoring debug info using dbgview.exe I get a lot of entries
> similar to the following:
>
> [3820]
> d:\depot4000qfe\voyqfe\source\private\mo
zart\source\engine\msg\endpointmanag
> er\epmreceivemanager\receiverrecord.cpp(151): Error - 0x80070057
> [3136]
> c:\depot4000\jupiter\source\private\moza
rt\source\engine\common\dbaccessor\t
> ransactions.cpp(80): Error - 0x8000ffff
>
> The paths don't exist, and the processes generating the messages are
> btsntsvc.exe.
>
> The reference to Jupiter suggest that this is something left over from early
> days in the product cycle, and the connotations of "QFE" are a bit alarming.
> Is this something that other people are seeing, am I running an older
> version of btsntsvc.exe, and is it anything to worry about?
>
> I'd be very grateful if someone from MSFT could help out here.
I`m also seeing these all the time when using dbgview.
The 0x80070057 error has been explained by Lee Graber (MSFT) in an
earlier post:
"Don't worry about the 80070057. I can double check, but I am pretty
sure we just throw that when a receive location is disabled. I was
actually noticing that the other day when debugging and probably for our
next release we will fix that and get it out of the trace output."
I`d still like to see the explanation on the 0x8000ffff message..
- Asbjørn
|
|
|
|
|