If you don’t have such error, i suggest help me find solution by simple task:
run process monitor, start new project from tuturial vehicle c++ and run new instance like in video, then stop process monitor tracking and save log, then give it to me, i will try compare my own and find the difference
reboot didn’t help, can you write log for me with process monitor? add process devenv.exe to filter and start logging right before compiling in vs, then turn off when ue appears and save log as PML, i will try compare and find the problem
hey man, I can’t recreate the problem. it seemed to happen when I’d done alot of builds in debugging, or development and then switched to debugging, and after my computer had been to sleep. It still happens from time to time. The other thing I’ve done is to rebuild, reboot.
don’t reproduce the problem, just write me a log of working fine compilation, just download microsoft’s process monitor http://download.sysinternals.com/files/ProcessMonitor.zip, start vs, run process monitor, add devenv.exe and start writing log, then compile, stop writing log and save as PML and upload to any file hosting (ofc i need link to that log file)
Run cmd.exe as administrator.
Type in and run the following two lines of commands:
netsh winsock reset catalog
netsh int ip reset reset.log hit
It may say that a reboot is required, but actually that is not necessary.
Try to debug your application again, the problem should be solved.
EDIT: Sorry for not providing an explanation for this before. The answer actually came from a Chines
e forum and the original author didn’t explain it much. But he did say that it’s because Visual Studio is a 32bit program which may have problem accessing network under 64bit Windows 7, and the aforementioned solution resets the network connection therefore solves the problem. Hope this helps.
