Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

symproxy can't download from MS symbol server

178 views
Skip to first unread message

Chris

unread,
Jan 26, 2005, 2:41:04 PM1/26/05
to
I've installed windbg 6.4.7.2 and followed the instruction in symhttp.doc to
setup SymProxy on Win2003. The SymProxy app pool is running as Network
Service. There is a virtual directory "symbols" mapped to "D:\symbols". The
virtual directory allows anonymous access. I just want to it to cache all
the MS symbols so I can share them from many client machines. It just
doesn't want to download the symbols from MS public symbol server. I can
browse the virtual directory. What am I doing wrong? The event log just
have entries "http://msdl.microsoft.com/download/symbols/... not found". But
I can get them directly if I use IE so I know they exist.

Thanks.

Chris

unread,
Jan 27, 2005, 1:53:02 AM1/27/05
to
It seems I can't put any domain name for the server name. I tried using a
local machine without the domain name, then I see http connection going to
that machine. Of course, that machine doesn't have the symbols so it just
fails. However, when I add the domain name, then no connection is going to
the server at all.

Do I need to setup a internet proxy server to use SymProxy?

Holger Grund

unread,
Jan 28, 2005, 10:47:03 AM1/28/05
to
"Chris" <Ch...@discussions.microsoft.com> wrote

FWIW, I have the same problem. I can't make symproxy pick up
compressed symbols. It only looks for xxx.pdb (given it's a PDB sig)
and not for xxx.pd_. That said, the worker process receives both
requests from the client and discards the request for compressed
symbols.
Apparently, HTTP request for compressed symbols are discarded
and request for uncompressed symbols look for uncompressed
symbols only.

-hg


Pat Styles

unread,
Jan 31, 2005, 2:31:43 PM1/31/05
to
We have looked into this and we experience no problems downloading
compressed files with SymProxy. Do you have a minidump file that causes the
behavior you are experiencing to reproduce? If so, can you make it
available to me and I will see what is up.

You are correct in noting that the worker process (the service) discards the
request for the compressed file. That is because the service calls
symsrv.dll which will try for a compressed file, if a non-compressed one is
not found. This is how SymProxy communicates with SymSrv. SymSrv cannot
be called to find a compressed file. These requests are generated
internally..

.pat styles (microsoft) pa...@microsoft.com

"Holger Grund" <h...@remove.ix-n.net> wrote in message
news:O%23xKY$UBFHA...@TK2MSFTNGP10.phx.gbl...

Chris

unread,
Feb 1, 2005, 1:31:01 AM2/1/05
to
Further investigation shows that it keeps trying to find
symsrvbogusproxy.[mydomain.com] if I have domain name in the sym proxy
registry value. What does that mean?

Holger Grund

unread,
Feb 1, 2005, 5:54:53 AM2/1/05
to
"Chris" <Ch...@discussions.microsoft.com> wrote

> Further investigation shows that it keeps trying to find
> symsrvbogusproxy.[mydomain.com] if I have domain name in the sym proxy
> registry value. What does that mean?
>

FWIW, I have identified that same issue as the cause. Apparently,
WinHttpOpen is called with "symsrvbogusproxy" and "<local>"
effectively causing FQDNs to be accessed via the above proxy.

Things work fine if I create an netbios alias for msdl.micrsoft.com.

Not sure why this setting exists in the first place and if you
can change it.

-hg


Pat Styles

unread,
Feb 1, 2005, 12:18:35 PM2/1/05
to
There is a problem in WinHttp that causes it to be unable to resolve and
handle the credentialing for local intranet resources within a network of
Windows PCs. The only occurs if no proxy server is specified. Consequently,
symsrv tries to compensate for this by specifying a non-existent proxy
server which causes WinHttp to fall back to the correct code. Of course,
this presumes that if someone wants to get out of the intranet, then he or
she is going through a real proxy or firewall. However, the documentation
(SymHttp.doc) doesn't tell you how to do this.

The simplest way to set up the firewall/proxy settings for symsrv when
running under a service is to, set up Internet Explorer the way you need and
copy these settings to the WinHttp settings by running "symproxy.exe -u"
from a command prompt. There are other options for setting up WinHttp with
symproxy and you can see them by using the "-?" command line switch.

Sorry for this documentation omission. I guess I wrote it up a little to
fast at the end of the project.

.pat styles (pa...@microsoft.com)

"Holger Grund" <h...@remove.ix-n.net> wrote in message

news:%23VcjpuE...@TK2MSFTNGP10.phx.gbl...

Holger Grund

unread,
Feb 1, 2005, 1:16:27 PM2/1/05
to
"Pat Styles" <pa...@microsoft.com> wrote

> The simplest way to set up the firewall/proxy settings for symsrv when
> running under a service is to, set up Internet Explorer the way you need
> and
> copy these settings to the WinHttp settings by running "symproxy.exe -u"
> from a command prompt. There are other options for setting up WinHttp
> with
> symproxy and you can see them by using the "-?" command line switch.
>

Thanks for the explanations. But where is this symproxy.exe?

-hg


Pat Styles

unread,
Feb 1, 2005, 9:00:46 PM2/1/05
to
Sorry. That was a typo. The program is called "proxycfg.exe".

.pat styles

"Holger Grund" <h...@remove.ix-n.net> wrote in message

news:eriFflIC...@TK2MSFTNGP11.phx.gbl...

Pat Styles

unread,
Feb 1, 2005, 9:03:30 PM2/1/05
to
Oops! There was a typo. Here's a new post...

There is a problem in WinHttp that causes it to be unable to resolve and
handle the credentialing for local intranet resources within a network of
Windows PCs. The only occurs if no proxy server is specified. Consequently,
symsrv tries to compensate for this by specifying a non-existent proxy
server which causes WinHttp to fall back to the correct code. Of course,
this presumes that if someone wants to get out of the intranet, then he or
she is going through a real proxy or firewall. However, the documentation
(SymHttp.doc) doesn't tell you how to do this.

The simplest way to set up the firewall/proxy settings for symsrv when
running under a service is to, set up Internet Explorer the way you need and

copy these settings to the WinHttp settings by running "proxycfg.exe -u"


from a command prompt. There are other options for setting up WinHttp with

proxycfg. You can see them by using the "-?" command line switch.

Holger Grund

unread,
Feb 2, 2005, 2:22:30 PM2/2/05
to
"Pat Styles" <pa...@microsoft.com> wrote

> Sorry. That was a typo. The program is called "proxycfg.exe".
>
Thanks Pat, works like a charm now :-)

-hg


mikeb

unread,
Feb 25, 2005, 1:15:01 PM2/25/05
to

I have tried this with no success. I suppose from reading this that my
problem is that I have no actual proxy server for accessing the
internet. So my WinHttpSettings stays at "Direct access (no proxy
server)."

SymProxy requests directed at the local intranet zone work fine, going
to the Internet zone do not work (even if the site is in the Trusted
zone).

Do I have to set-up a proxy server just so WinHttp can access both the
local intranet and the outside Internet?

Pat Styles

unread,
Mar 2, 2005, 5:40:14 PM3/2/05
to
Yes you will. The next revision will handle this in some other way.

.pat

"mikeb" <mailbox...@mailnull.com> wrote in message
news:1109355301.5...@o13g2000cwo.googlegroups.com...

0 new messages