CNET TechTracker forum: "Error submitting scan results to server." on Windows 7 x64

I just noticed that when I go to my updates list at "http://www.cnet.com/techtracker/" and I set an application to be update using "Smart Install" my browser opens the "cbsitt" file using TechTracker. Then, the application update is automatically downloaded and installed. It seems to work for all the available applications (except for TechTracker; it continually tries to update itself).

I agree with "Out_There", the problem is on their web service. It looks to be failing updating your personal list of applications that need updating.

I will keep trying things in this new version...

I just solved this problem!!! I added http://www.cnet.com to my trusted sites in internet options and then downloaded and installed. Once I'd run it one time successfully, I removed the trusted site and it still works fine I'd tried SO many different things to get this software to work. I FINALLY cracked it! YAY!!!

I tried this in response to it not working anymore, and now I can't even get it to recognize my computer, because it has to complete the scan process and communicate with their web service, which always fails. I am surprised that this works "sometimes" for "some people".... I wonder what the issue is with the web service and what triggers the problem, and why they can't seem to figure it out or admit that there is a problem. I sure wish we could at least get a better answer than "let techtracker through your firewall" when it is really clear that this isn't the issue. I am using Win 7 Ultimate 32-bit.

didnt' work for me either

I am only having this issue on computers that are running Visual Studio 2010... Is that the case for others as well?

If we can get some more verification from others... I will start tracing the root cause (Since Cnet is obviously incapable, incompetent, or just apathetic.
I will also mention that on my machine that has a beta of Dev11 works as expected. I work for Microsoft so i'm hopeful that I can determine what in the VS 2010 (sp1 only?) install package breaks techtracker.
The more information/verification we get the better we'll be able to determine what is blocking the app from working.

The machine that TT still does not work on for me has VS2010 SP1 installed.

The other machine (which TT is now working on, after doing the steps I got from CNET Support that I posted earlier) does not have VS2010 installed on it.

I wish I could say that is the answer to the failure on my machine, but I don't have that software.

Funny thing is, when I built this machine one of the first software I installed was TechTracker, so it was pretty much a virgin machine.

I don't think uninstalling, by normal msiexec methods would remedy the problem. Based on what i found was that once VS10 was installed on a machine, that machine was no longer able to submit TT scan results to CNet. Uninstalling doesn't unbreak TT from my experience.
What I'm looking for is someone to disprove the hypothesis... e.g. someone who has VS2010 on a machine that TT is working perfectly.
If you don't have VS2010 installed and you are having the same problem what i'd like to know is what apps do you have installed... It will help us potentially find the common denominator... which could be a service pack, a runtime, any number of things.
Looks like we will figure it out ourselves though.

Here is a list of the files that ProcessExplorer reports TT loads when I run it and it errors. Anyone know why it would be loading VS7 Debug dlls or RealPlayer Chrome dlls?


C:\Program Files (x86)\Common Files\microsoft shared\VS7DEBUG\msdbg2.dll
C:\Program Files (x86)\Common Files\microsoft shared\VS7DEBUG\pdm.dll
C:\Program Files (x86)\Common Files\microsoft shared\Windows Live\WLIDNSP.DLL
C:\ProgramData\Microsoft\Windows\Caches\{6AF0698E-D558-4F6E-9B3C-3716689AF493}.2.ver0x000000000000001d.db
C:\ProgramData\Microsoft\Windows\Caches\{DDF571F2-BE98-426D-8288-1A9A39C3FDA2}.2.ver0x0000000000000002.db
C:\ProgramData\Microsoft\Windows\Caches\cversions.2.db
C:\ProgramData\Microsoft\Windows\Caches\cversions.2.db
C:\ProgramData\Microsoft\Windows\Caches\cversions.2.db
C:\ProgramData\Real\RealPlayer\BrowserRecordPlugin\Chrome\Hook\rpchrome14browserrecordhelper.dll
C:\Users\jonathan\AppData\Local\Microsoft\Windows\Caches\{AFBF9F1A-8EE8-4C77-AF34-C647E37CA0D9}.1.ver0x0000000000000014.db
C:\Users\jonathan\AppData\Local\Microsoft\Windows\History\History.IE5\index.dat
C:\Users\jonathan\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.IE5\index.dat
C:\Users\jonathan\AppData\Roaming\CBS Interactive\CNET TechTracker\TechTracker.exe
C:\Users\jonathan\AppData\Roaming\CBS Interactive\CNET TechTracker\zlib.dll
C:\Users\jonathan\AppData\Roaming\Microsoft\Windows\Cookies\index.dat
C:\Windows\Fonts\StaticCache.dat
C:\Windows\Globalization\Sorting\SortDefault.nls
C:\Windows\System32\apisetschema.dll
C:\Windows\System32\C_1250.NLS
C:\Windows\System32\C_1251.NLS
C:\Windows\System32\C_1253.NLS
C:\Windows\System32\C_1256.NLS
C:\Windows\System32\C_950.NLS
C:\Windows\System32\locale.nls
C:\Windows\System32\ntdll.dll
C:\Windows\System32\wow64.dll
C:\Windows\System32\wow64cpu.dll
C:\Windows\System32\wow64win.dll
C:\Windows\SysWOW64\advapi32.dll
C:\Windows\SysWOW64\apphelp.dll
C:\Windows\SysWOW64\bcrypt.dll
C:\Windows\SysWOW64\bcryptprimitives.dll
C:\Windows\SysWOW64\cabinet.dll
C:\Windows\SysWOW64\cfgmgr32.dll
C:\Windows\SysWOW64\clbcatq.dll
C:\Windows\SysWOW64\comdlg32.dll
C:\Windows\SysWOW64\credssp.dll
C:\Windows\SysWOW64\crypt32.dll
C:\Windows\SysWOW64\cryptbase.dll
C:\Windows\SysWOW64\cryptnet.dll
C:\Windows\SysWOW64\cryptsp.dll
C:\Windows\SysWOW64\d2d1.dll
C:\Windows\SysWOW64\d3d10_1.dll
C:\Windows\SysWOW64\d3d10_1core.dll
C:\Windows\SysWOW64\d3d10warp.dll
C:\Windows\SysWOW64\davclnt.dll
C:\Windows\SysWOW64\davhlpr.dll
C:\Windows\SysWOW64\devobj.dll
C:\Windows\SysWOW64\devrtl.dll
C:\Windows\SysWOW64\dnsapi.dll
C:\Windows\SysWOW64\drprov.dll
C:\Windows\SysWOW64\dwmapi.dll
C:\Windows\SysWOW64\DWrite.dll
C:\Windows\SysWOW64\dxgi.dll
C:\Windows\SysWOW64\en-US\crypt32.dll.mui
C:\Windows\SysWOW64\en-US\ieframe.dll.mui
C:\Windows\SysWOW64\en-US\KernelBase.dll.mui
C:\Windows\SysWOW64\en-US\mpr.dll.mui
C:\Windows\SysWOW64\en-US\msctf.dll.mui
C:\Windows\SysWOW64\en-US\mshtml.dll.mui
C:\Windows\SysWOW64\en-US\propsys.dll.mui
C:\Windows\SysWOW64\en-US\setupapi.dll.mui
C:\Windows\SysWOW64\en-US\shell32.dll.mui
C:\Windows\SysWOW64\en-US\urlmon.dll.mui
C:\Windows\SysWOW64\en-US\user32.dll.mui
C:\Windows\SysWOW64\FWPUCLNT.DLL
C:\Windows\SysWOW64\gdi32.dll
C:\Windows\SysWOW64\gpapi.dll
C:\Windows\SysWOW64\ieframe.dll
C:\Windows\SysWOW64\ieframe.dll
C:\Windows\SysWOW64\iertutil.dll
C:\Windows\SysWOW64\imm32.dll
C:\Windows\SysWOW64\IPHLPAPI.DLL
C:\Windows\SysWOW64\kernel32.dll
C:\Windows\SysWOW64\KernelBase.dll
C:\Windows\SysWOW64\linkinfo.dll
C:\Windows\SysWOW64\lpk.dll
C:\Windows\SysWOW64\mlang.dll
C:\Windows\SysWOW64\mpr.dll
C:\Windows\SysWOW64\msasn1.dll
C:\Windows\SysWOW64\msctf.dll
C:\Windows\SysWOW64\mshtml.dll
C:\Windows\SysWOW64\msi.dll
C:\Windows\SysWOW64\msimtf.dll
C:\Windows\SysWOW64\msls31.dll
C:\Windows\SysWOW64\msvcrt.dll
C:\Windows\SysWOW64\mswsock.dll
C:\Windows\SysWOW64\ncrypt.dll
C:\Windows\SysWOW64\nlaapi.dll
C:\Windows\SysWOW64\normaliz.dll
C:\Windows\SysWOW64\nsi.dll
C:\Windows\SysWOW64\ntdll.dll
C:\Windows\SysWOW64\ntlanman.dll
C:\Windows\SysWOW64\ntmarta.dll
C:\Windows\SysWOW64\ole32.dll
C:\Windows\SysWOW64\oleacc.dll
C:\Windows\SysWOW64\oleaccrc.dll
C:\Windows\SysWOW64\oleaut32.dll
C:\Windows\SysWOW64\oledlg.dll
C:\Windows\SysWOW64\profapi.dll
C:\Windows\SysWOW64\propsys.dll
C:\Windows\SysWOW64\psapi.dll
C:\Windows\SysWOW64\rasadhlp.dll
C:\Windows\SysWOW64\rasapi32.dll
C:\Windows\SysWOW64\rasman.dll
C:\Windows\SysWOW64\riched20.dll
C:\Windows\SysWOW64\rpcrt4.dll
C:\Windows\SysWOW64\RpcRtRemote.dll
C:\Windows\SysWOW64\rsaenh.dll
C:\Windows\SysWOW64\rtutils.dll
C:\Windows\SysWOW64\schannel.dll
C:\Windows\SysWOW64\SearchFolder.dll
C:\Windows\SysWOW64\sechost.dll
C:\Windows\SysWOW64\secur32.dll
C:\Windows\SysWOW64\SensApi.dll
C:\Windows\SysWOW64\setupapi.dll
C:\Windows\SysWOW64\shell32.dll
C:\Windows\SysWOW64\shlwapi.dll
C:\Windows\SysWOW64\sspicli.dll
C:\Windows\SysWOW64\stdole2.tlb
C:\Windows\SysWOW64\sxs.dll
C:\Windows\SysWOW64\urlmon.dll
C:\Windows\SysWOW64\user32.dll
C:\Windows\SysWOW64\userenv.dll
C:\Windows\SysWOW64\usp10.dll
C:\Windows\SysWOW64\uxtheme.dll
C:\Windows\SysWOW64\version.dll
C:\Windows\SysWOW64\WindowsCodecs.dll
C:\Windows\SysWOW64\wininet.dll
C:\Windows\SysWOW64\winmm.dll
C:\Windows\SysWOW64\winnsi.dll
C:\Windows\SysWOW64\winspool.drv
C:\Windows\SysWOW64\winsta.dll
C:\Windows\SysWOW64\wintrust.dll
C:\Windows\SysWOW64\Wldap32.dll
C:\Windows\SysWOW64\ws2_32.dll
C:\Windows\SysWOW64\wship6.dll
C:\Windows\SysWOW64\WSHTCPIP.DLL
C:\Windows\winsxs\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\msvcp90.dll
C:\Windows\winsxs\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\msvcr90.dll
C:\Windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\comctl32.dll
C:\Windows\winsxs\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17514_none_72d18a4386696c80\GdiPlus.dll

This is not an old discussion. They just haven't fixed it in a year's time.

when members post to older threads, especially such large ones as this, those who help in these forums see the date of the thread and often just 'walk on by'.

Your choice here, but the common advice, in all public forums and not just these, is to create your own discussion, post your problems and any relevant details and by all means, provide a link in your post to the 'other' discussion as a reference.

That way your chances of getting seen to enhance greatly.

Mark

Let's say all support tickets are to fix this. Message?

Yes. My machine that has the error has Visual Studio 2010. Also, my machine is running XP Pro/SP3 (32-bit) , so the error is not limited to just Windows 7 machines.

Sytyguy,

Just to clarify, does "no 2 VS2010" mean that you do NOT have VS2010 installed and TT is working fine?