I get these in my output when I build, and my site takes forrrrrreeeevvvvvverrrrrrr to finished loading.... very bad...
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\ntdll.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\mscoree.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\kernel32.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\KernelBase.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\advapi32.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\msvcrt.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\sechost.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\rpcrt4.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\sspicli.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\cryptbase.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\shlwapi.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\gdi32.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\user32.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\lpk.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\usp10.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\imm32.dll', Cannot find or open the PDB file
if i let the project just sit there and run i get even more weird stuff....
The thread 'Win32 Thread' (0xae4) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0xc40) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x23c0) has exited with code 0 (0x0).
The thread '<No Name>' (0x1978) has exited with code 0 (0x0).
The thread '<No Name>' (0xad8) has exited with code 0 (0x0).
The thread '<No Name>' (0x20d0) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x1978) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x20d0) has exited with code 0 (0x0).
The thread '<No Name>' (0x348) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0xad8) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x348) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x334) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x1f6c) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x1884) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x1588) has exited with code 0 (0x0).
The thread '<No Name>' (0x9e0) has exited with code 0 (0x0).
The thread '<No Name>' (0xff4) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x9e0) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0xff4) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x1dfc) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x1890) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x81c) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x17fc) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x9e4) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x22b0) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x222c) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x1f8c) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x226c) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x1f3c) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x1098) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x1234) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x1cac) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x1900) has exited with code 0 (0x0).
We have a discussion about similar issue before, I think it’s a good reference for you below,
Please check whether it’s helpful to you.
“The message you seen indicates that Visual Studio is looking for symbol files of some dlls, they are system dlls, usually you can ignore 'PDB not found' messages, since they will not prevent you from debugging, but what do you mean by "I am unable to debug"?
To load symbol file for those dlls, you may open the Modules window (Debug -> Windows -> Modules), right click a module, and select Load Symbols From -> Microsoft Symbol Servers.”
hope it helps you,
Kind regards
Please mark the replies as answers if they help or unmark if not.
Feedback to us
Xequence
Contributor
4508 Points
1578 Posts
building website has lots of problems with syswow64
Jan 30, 2013 03:57 PM|LINK
I get these in my output when I build, and my site takes forrrrrreeeevvvvvverrrrrrr to finished loading.... very bad...
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\ntdll.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\mscoree.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\kernel32.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\KernelBase.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\advapi32.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\msvcrt.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\sechost.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\rpcrt4.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\sspicli.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\cryptbase.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\shlwapi.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\gdi32.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\user32.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\lpk.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\usp10.dll', Cannot find or open the PDB file
'WebDev.WebServer40.EXE': Loaded 'C:\Windows\SysWOW64\imm32.dll', Cannot find or open the PDB file
Credentials
Xequence
Contributor
4508 Points
1578 Posts
Re: building website has lots of problems with syswow64
Jan 30, 2013 04:09 PM|LINK
if i let the project just sit there and run i get even more weird stuff....
The thread 'Win32 Thread' (0xae4) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0xc40) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x23c0) has exited with code 0 (0x0).
The thread '<No Name>' (0x1978) has exited with code 0 (0x0).
The thread '<No Name>' (0xad8) has exited with code 0 (0x0).
The thread '<No Name>' (0x20d0) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x1978) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x20d0) has exited with code 0 (0x0).
The thread '<No Name>' (0x348) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0xad8) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x348) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x334) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x1f6c) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x1884) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x1588) has exited with code 0 (0x0).
The thread '<No Name>' (0x9e0) has exited with code 0 (0x0).
The thread '<No Name>' (0xff4) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x9e0) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0xff4) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x1dfc) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x1890) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x81c) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x17fc) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x9e4) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x22b0) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x222c) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x1f8c) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x226c) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x1f3c) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x1098) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x1234) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x1cac) has exited with code 0 (0x0).
The thread 'Win32 Thread' (0x1900) has exited with code 0 (0x0).
Credentials
Angie xu - M...
All-Star
20273 Points
1728 Posts
Microsoft
Re: building website has lots of problems with syswow64
Feb 05, 2013 12:45 AM|LINK
Hi Xequence
We have a discussion about similar issue before, I think it’s a good reference for you below,
Please check whether it’s helpful to you.
“The message you seen indicates that Visual Studio is looking for symbol files of some dlls, they are system dlls, usually you can ignore 'PDB not found' messages, since they will not prevent you from debugging, but what do you mean by "I am unable to debug"?
To load symbol file for those dlls, you may open the Modules window (Debug -> Windows -> Modules), right click a module, and select Load Symbols From -> Microsoft Symbol Servers.”
hope it helps you,
Kind regards
Feedback to us
Develop and promote your apps in Windows Store