This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hello everyone,
we are trying to use a DSK C6713 together with CCS v3.3. However CCS v3.3 makes serious troubles.
CCS v3.3 (with or without the Service Release 12 Update) does not start. It shows the splash screen but as soon as the GUI should show it simply terminates. No error message, no hints, it just exits.
The system is running an up to date Windows XP SP3 (32bit). Several tries to fix CCS 3.3 by reinstalling didn't fix the issue. Note that the installation runs through without any complications or messages. Also CCS 3.3 is started by a user with admin rights.
The latest drivers for the DSK C6713 are installed (from http://support.spectrumdigital.com/ccs33/).
Any experiences with this behaviour? What could be wrong?
Best Regards,
Sebastian
Hello Sebastian,
It could be that there is some running process that is preventing CCS from starting up. In the past I've seen various anti-virus software (like kaspersky) interfere. I've also seen a machine that had some advertisement software installed (unknown to the user) that interfered. You can try starting up in Windows "safe mode" and see if CCS can launch ok. That would at least prove that it is related to some conflicting process.
ki
Well, it doesn't start in safe mode either. However I get the message:
Error initializing emulator
I/O Port = 540
Board Name: C6713 DSK
Cpu Name: CPU_1
Abort: Close Code Composer Studio.
Retry: Try to initialize the emulator again.
Ignore: Ignore the initialization error and start
potentially without target debugging access.
Diagnostic: Run diagnostic utility.
But that's probably due to missing USB-drivers in safe mode. I clicked on ignore, which should bring up the GUI, but as I said nothing happens again.
Regards,
Sebastian
Could you try configuring CCS for a different target and see if it will start? If not, you can try running this tool called Dependency Walker and see if any errors are detected. Open the main CCS exe (C:\CCStudio_v3.3\cc\bin\cc_app.exe) with it.
Different target doesn't solve the issue. CCS still disappears after the splash screen, respective the 'Can't connect to target'-message. Dependency Walker shows one warning due to the missing MSJAVA.DLL. But according to this (http://www.dependencywalker.com/faq.html), the warning can be ignored.
EDIT:
I overlooked a second warning (thought it belongs to the MSJAVA-warning). It belongs to MPR.DLL and states: Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module. But also according to above FAQ, this warning can be ignored.
/EDIT:
Any further suggestions?
Regards,
Sebastian
Sebastian,
Not sure if it helps, but are you able to open CCS from within CCSetup? Although I have a completely different system (Win7/64bit), I am having this exact same issue where CCS shows the screen but silently disappears, unless I run it straight from CCSetup.
I haven't found the exact cause for that, but I didn't pay much attention to it because my OS is completely unsupported by CCSv3.3...
Hope this helps,
Rafael
I found one previous instance where a similar thing occured on a machine that had Windows Firewall installed and they thought they may have inadvertantly "blocked" a program during the initial setup. The symptom was that CCS would not get past the splash screen. They discovered the issue by disconnecting their network connection, which then caused CCS to activate properly. Not sure if this could be the case here, but thought I'd mention it in case it helps.
I can test your suggestions not until Tuesday next week. But I'll report back...
Regards,
Sebastian
Nope, it doesn't start, when being started directly out of CCSetup and it also doesn't start when deactivating firewall and AntiVir and unplugging the network cable.
Does CCS write a log file during startup or? Or is there a command line option to make CCS giving additional info on what's happening exactly, kind of a debug mode?
Regards,
Sebastian
You can try to use VC++ to startup cc_app.exe process and catch all exception, except C++ exception. When an exception occure, look at the callstack and see which component generates the exception. If you don't have VC++, you can download windbg from Microsoft. With knowning which component generates the exception, it might be possible to identifiy the root cause.
Regards,
Patrick
I used windbg and received the following report. I pressed F5 (= Debug->Go) until nothing changed anymore. What can you see, I marked the errors/exceptions red?
CommandLine: C:\CCStudio_v3.3\cc\bin\cc_app.exe
Symbol search path is: srv*
Executable search path is:
ModLoad: 00400000 00c74000 cc_app.exe
ModLoad: 7c900000 7c9b2000 ntdll.dll
ModLoad: 7c800000 7c8f6000 C:\WINDOWS\system32\kernel32.dll
ModLoad: 10100000 1025b000 C:\CCStudio_v3.3\cc\bin\CWDLL32.dll
ModLoad: 7e410000 7e4a1000 C:\WINDOWS\system32\USER32.dll
ModLoad: 77f10000 77f59000 C:\WINDOWS\system32\GDI32.dll
ModLoad: 77dd0000 77e6b000 C:\WINDOWS\system32\ADVAPI32.dll
ModLoad: 77e70000 77f03000 C:\WINDOWS\system32\RPCRT4.dll
ModLoad: 77fe0000 77ff1000 C:\WINDOWS\system32\Secur32.dll
ModLoad: 7c9c0000 7d1d7000 C:\WINDOWS\system32\SHELL32.dll
ModLoad: 77c10000 77c68000 C:\WINDOWS\system32\msvcrt.dll
ModLoad: 77f60000 77fd6000 C:\WINDOWS\system32\SHLWAPI.dll
ModLoad: 71b20000 71b32000 C:\WINDOWS\system32\MPR.dll
ModLoad: 774e0000 7761e000 C:\WINDOWS\system32\ole32.dll
ModLoad: 10500000 10575000 C:\CCStudio_v3.3\cc\bin\CWCTLS32.dll
ModLoad: 10700000 107b4000 C:\CCStudio_v3.3\cc\bin\CWSTART.dll
ModLoad: 763b0000 763f9000 C:\WINDOWS\system32\comdlg32.dll
ModLoad: 5d090000 5d12a000 C:\WINDOWS\system32\COMCTL32.dll
ModLoad: 12000000 1226e000 C:\WINDOWS\system32\xerces-c_2_5_0.dll
ModLoad: 10000000 10042000 C:\CCStudio_v3.3\cc\bin\log4cplus.dll
ModLoad: 71ab0000 71ac7000 C:\WINDOWS\system32\WS2_32.dll
ModLoad: 71aa0000 71aa8000 C:\WINDOWS\system32\WS2HELP.dll
ModLoad: 76080000 760e5000 C:\WINDOWS\system32\MSVCP60.dll
ModLoad: 77c00000 77c08000 C:\WINDOWS\system32\VERSION.dll
ModLoad: 00330000 0033f000 C:\CCStudio_v3.3\cc\bin\TISCC.dll
ModLoad: 73dd0000 73ec1000 C:\WINDOWS\system32\MFC42.DLL
ModLoad: 65400000 6544d000 C:\CCStudio_v3.3\cc\bin\tiofr11.dll
ModLoad: 77120000 771ab000 C:\WINDOWS\system32\OLEAUT32.dll
ModLoad: 00340000 00351000 C:\WINDOWS\system32\MSVCIRT.dll
ModLoad: 00c80000 00e00000 C:\WINDOWS\system32\xerces-c_1_7_0.dll
ModLoad: 7df70000 7df92000 C:\WINDOWS\system32\oledlg.dll
(d2c.bc0): Break instruction exception - code 80000003 (first chance)
eax=00241eb4 ebx=7ffd4000 ecx=00000007 edx=00000080 esi=00241f48 edi=00241eb4
eip=7c90120e esp=0012fb20 ebp=0012fc94 iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202
ntdll!DbgBreakPoint:
7c90120e cc int 3
0:000> g
ModLoad: 773d0000 774d3000 C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.6028_x-ww_61e65202\comctl32.dll
ModLoad: 74720000 7476c000 C:\WINDOWS\system32\MSCTF.dll
ModLoad: 03000000 03113000 C:\CCStudio_v3.3\cc\bin\DBGHELP.DLL
ModLoad: 01650000 0170b000 C:\CCStudio_v3.3\cc\bin\CollectorServer.dll
ModLoad: 01710000 01733000 C:\CCStudio_v3.3\cc\bin\DotNETRuntimeLoader.dll
ModLoad: 79000000 7904a000 C:\WINDOWS\system32\mscoree.dll
ModLoad: 74c80000 74cac000 C:\WINDOWS\system32\OLEACC.dll
ModLoad: 73000000 73026000 C:\WINDOWS\system32\WINSPOOL.DRV
ModLoad: 603b0000 60416000 C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
ModLoad: 7e720000 7e7d0000 C:\WINDOWS\system32\SXS.DLL
ModLoad: 017c0000 017e3000 C:\CCStudio_v3.3\cc\bin\comp_mgr.dll
ModLoad: 017f0000 0181e000 C:\CCStudio_v3.3\cc\bin\CcsCoreComponentEngine.dll
ModLoad: 76fd0000 7704f000 C:\WINDOWS\system32\CLBCATQ.DLL
ModLoad: 77050000 77115000 C:\WINDOWS\system32\COMRes.dll
ModLoad: 74980000 74aa3000 C:\WINDOWS\system32\msxml3.dll
ModLoad: 77690000 776b1000 C:\WINDOWS\system32\NTMARTA.DLL
ModLoad: 71bf0000 71c03000 C:\WINDOWS\system32\SAMLIB.dll
ModLoad: 76f60000 76f8c000 C:\WINDOWS\system32\WLDAP32.dll
ModLoad: 77920000 77a13000 C:\WINDOWS\system32\SETUPAPI.dll
ModLoad: 01e90000 01ee6000 C:\CCSTUD~1.3\plugins\FLASH2~3\FLASH2~1.OCX
ModLoad: 01f30000 01f68000 C:\CCStudio_v3.3\cc\bin\ctools.dll
ModLoad: 017c0000 017cb000 C:\CCStudio_v3.3\cc\bin\cToolsIF.dll
ModLoad: 7c140000 7c23d000 C:\CCStudio_v3.3\cc\bin\MFC70.DLL
ModLoad: 7c000000 7c054000 C:\CCStudio_v3.3\cc\bin\MSVCR70.dll
ModLoad: 7c080000 7c0f7000 C:\CCStudio_v3.3\cc\bin\MSVCP70.dll
ModLoad: 01f70000 01fa1000 C:\CCStudio_v3.3\cc\bin\IceCD.dll
ModLoad: 01fb0000 01fd1000 C:\CCStudio_v3.3\cc\bin\icestorm21.dll
ModLoad: 01810000 0182f000 C:\CCStudio_v3.3\cc\bin\iceutil21.dll
ModLoad: 01fe0000 020bc000 C:\CCStudio_v3.3\cc\bin\ice21.dll
ModLoad: 020c0000 020dc000 C:\CCStudio_v3.3\cc\bin\LIBBZ2.dll
ModLoad: 71a50000 71a8f000 C:\WINDOWS\System32\mswsock.dll
ModLoad: 76f20000 76f47000 C:\WINDOWS\system32\DNSAPI.dll
ModLoad: 76fb0000 76fb8000 C:\WINDOWS\System32\winrnr.dll
ModLoad: 76fc0000 76fc6000 C:\WINDOWS\system32\rasadhlp.dll
ModLoad: 662b0000 66308000 C:\WINDOWS\system32\hnetcfg.dll
ModLoad: 71a90000 71a98000 C:\WINDOWS\System32\wshtcpip.dll
ModLoad: 02540000 02566000 C:\CCStudio_v3.3\cc\bin\IceTargetAdapter.dll
ModLoad: 02570000 02835000 C:\WINDOWS\system32\xpsp2res.dll
ModLoad: 3fde0000 40221000 C:\WINDOWS\system32\msi.dll
ModLoad: 02b40000 02b7f000 C:\CCStudio_v3.3\drivers\tisimC6xxx.dvr
ModLoad: 02b80000 02d43000 C:\WINDOWS\system32\Xalan-C_1_8.dll
ModLoad: 02d50000 02d59000 C:\WINDOWS\system32\XalanMessages_1_8.dll
ModLoad: 02f60000 02fee000 C:\CCStudio_v3.3\cc\bin\tpic6x.dll
ModLoad: 02f60000 02f66000 C:\CCStudio_v3.3\cc\bin\CCReg.dll
(d2c.bc0): C++ EH exception - code e06d7363 (first chance)
ModLoad: 13f00000 13f60000 C:\CCStudio_v3.3\cc\bin\cwsense.dll
ModLoad: 03120000 031b2000 C:\CCStudio_v3.3\cc\bin\CW_c4dll.dll
ModLoad: 10900000 10911000 C:\CCStudio_v3.3\cc\bin\CUA.dll
ModLoad: 02fc0000 02fcb000 C:\CCStudio_v3.3\cc\bin\ccsshortcuts.dll
ModLoad: 10d00000 10ddb000 C:\CCStudio_v3.3\cc\bin\cwdialog.dll
ModLoad: 11900000 1191f000 C:\CCStudio_v3.3\cc\bin\cwfopen.dll
ModLoad: 034c0000 03553000 C:\CCStudio_v3.3\cc\bin\rtdx.dll
ModLoad: 03970000 03b5e000 C:\CCStudio_v3.3\drivers\spkc6x1x.dll
ModLoad: 03b60000 03bc5000 C:\CCStudio_v3.3\drivers\SimBridge_c6x.dll
ModLoad: 08690000 0871e000 C:\CCStudio_v3.3\cc\bin\tpic6x.dll
ModLoad: 08720000 0873c000 C:\CCStudio_v3.3\cc\bin\ct6xapi.dll
(d2c.bc0): C++ EH exception - code e06d7363 (first chance)
(d2c.bc0): C++ EH exception - code e06d7363 (first chance)
(d2c.bc0): C++ EH exception - code e06d7363 (first chance)
(d2c.bc0): C++ EH exception - code e06d7363 (first chance)
(d2c.bc0): C++ EH exception - code e06d7363 (first chance)
(d2c.bc0): C++ EH exception - code e06d7363 (first chance)
(d2c.bc0): C++ EH exception - code e06d7363 (first chance)
(d2c.bc0): C++ EH exception - code e06d7363 (first chance)
(d2c.bc0): C++ EH exception - code e06d7363 (first chance)
(d2c.bc0): C++ EH exception - code e06d7363 (first chance)
(d2c.bc0): C++ EH exception - code e06d7363 (first chance)
(d2c.bc0): C++ EH exception - code e06d7363 (first chance)
ModLoad: 08720000 0873e000 C:\CCStudio_v3.3\cc\bin\CcsMemoryServerLoader.dll
(d2c.bc0): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=00000000 ebx=00000000 ecx=0012fb10 edx=00146898 esi=014e0009 edi=062bbcc4
eip=00534cb7 esp=0012f6fc ebp=0012fb1c iopl=0 nv up ei pl nz ac po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010212
*** WARNING: Unable to verify checksum for cc_app.exe
*** ERROR: Symbol file could not be found. Defaulted to export symbols for cc_app.exe -
cc_app!CComSupport::FireEvent+0x21f87:
00534cb7 8b08 mov ecx,dword ptr [eax] ds:0023:00000000=????????
0:000> g
ModLoad: 08750000 088ac000 C:\CCSTUD~1.3\cc\bin\projsvr.dll
ModLoad: 088e0000 0890b000 C:\CCStudio_v3.3\cc\bin\ProfileServer.dll
ModLoad: 08910000 0894c000 C:\CCStudio_v3.3\cc\bin\datasetserver.dll
ModLoad: 08950000 089aa000 C:\CCStudio_v3.3\cc\bin\C4dll.dll
ModLoad: 76b20000 76b31000 C:\WINDOWS\system32\ATL.DLL
ModLoad: 08bc0000 08bcc000 C:\CCStudio_v3.3\cc\bin\BkptCollector.dll
ModLoad: 08bd0000 08c92000 C:\CCSTUD~1.3\plugins\generic\watch.ocx
ModLoad: 08bd0000 08c92000 C:\CCSTUD~1.3\plugins\generic\watch.ocx
ModLoad: 08bd0000 08bd8000 C:\CCSTUD~1.3\plugins\bios\RTAToolbar.dll
ModLoad: 08bd0000 08bd8000 C:\CCSTUD~1.3\plugins\bios\RTAToolbar.dll
ModLoad: 08bd0000 08bd8000 C:\CCSTUD~1.3\plugins\bios\RTAToolbar.dll
ModLoad: 08bd0000 08bd8000 C:\CCSTUD~1.3\plugins\bios\RTAToolbar.dll
ModLoad: 08bd0000 08bd8000 C:\CCSTUD~1.3\plugins\bios\RTAToolbar.dll
ModLoad: 08bd0000 08bd8000 C:\CCSTUD~1.3\plugins\bios\RTAToolbar.dll
ModLoad: 08bd0000 08bd8000 C:\CCSTUD~1.3\plugins\bios\rtatoolbar.dll
ModLoad: 08bd0000 08c0e000 C:\CCSTUD~1.3\plugins\Joule\BREAKP~1\BREAKP~1.OCX
ModLoad: 08c10000 08cc9000 C:\CCSTUD~1.3\cc\bin\ADPlugin.ocx
ModLoad: 08cd0000 08d07000 C:\CCSTUD~1.3\plugins\GELOpen\GELOpen.ocx
ModLoad: 08d10000 08d3e000 C:\CCSTUD~1.3\plugins\Joule\PROPER~1\Property.ocx
ModLoad: 5edd0000 5ede7000 C:\WINDOWS\system32\OLEPRO32.DLL
(d2c.bc0): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=00000000 ebx=001a6bec ecx=063c2600 edx=7ffb001c esi=063c2600 edi=063c27cc
eip=08d13c0c esp=0012cad4 ebp=001a70bc iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010246
*** WARNING: Unable to verify checksum for C:\CCSTUD~1.3\plugins\Joule\PROPER~1\Property.ocx
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\CCSTUD~1.3\plugins\Joule\PROPER~1\Property.ocx -
Property!DllGetClassObject+0x25ac:
08d13c0c 8b08 mov ecx,dword ptr [eax] ds:0023:00000000=????????
0:000> g
(d2c.bc0): C++ EH exception - code e06d7363 (first chance)
ModLoad: 08d40000 08e02000 C:\CCSTUD~1.3\plugins\generic\watch.ocx
ModLoad: 08e10000 08e3d000 C:\CCSTUD~1.3\plugins\generic\SUMMAR~1.OCX
ModLoad: 08e40000 08ee3000 C:\CCSTUD~1.3\plugins\generic\SYMBOL~1.OCX
ModLoad: 08ef0000 08f1f000 C:\CCSTUD~1.3\plugins\tconfaxd\tconfaxd.ocx
ModLoad: 08f20000 08f55000 C:\CCSTUD~1.3\BIOS_5~1\packages\ti\bios\bti\bin\TCONFC~1.OCX
ModLoad: 08f60000 08f93000 C:\CCSTUD~1.3\cc\bin\TRACEE~1.OCX
ModLoad: 08fa0000 0900f000 C:\CCSTUD~1.3\plugins\CACHET~1\CACHET~1.OCX
ModLoad: 09010000 090ab000 C:\CCSTUD~1.3\plugins\CACHET~1\tcl83.dll
ModLoad: 090b0000 09196000 C:\CCSTUD~1.3\plugins\CACHET~1\tk83.dll
ModLoad: 091a0000 091d4000 C:\CCSTUD~1.3\plugins\generic\conflict.ocx
ModLoad: 091e0000 09233000 C:\CCSTUD~1.3\plugins\CONSUL~1\CONSUL~1.OCX
ModLoad: 09240000 09287000 C:\CCSTUD~1.3\plugins\CONSUL~1\ConsultantTranslator.dll
ModLoad: 09290000 092b1000 C:\CCSTUD~1.3\plugins\generic\ACTMgr.ocx
ModLoad: 092c0000 09308000 C:\CCSTUD~1.3\plugins\generic\coverage.ocx
ModLoad: 1da10000 1da53000 C:\CCStudio_v3.3\plugins\rtdx\rtdxconfig.ocx
ModLoad: 09310000 09327000 C:\CCStudio_v3.3\cc\bin\DataFileServer.dll
(d2c.bc0): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=0003055a ebx=00000000 ecx=0012d278 edx=7c90e514 esi=0012d79c edi=ffff0000
eip=000306a6 esp=0012d27c ebp=0012d718 iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010202
000306a6 ?? ???
0:000> g
(d2c.bc0): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=00000000 ebx=00000000 ecx=033e9e08 edx=7c9032bc esi=00000000 edi=00000000
eip=033e9e08 esp=0012ceac ebp=0012cecc iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010246
033e9e08 a6 cmps byte ptr [esi],byte ptr es:[edi] ds:0023:00000000=?? es:0023:00000000=??
0:000> g
(d2c.bc0): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=00000000 ebx=00000000 ecx=033e9e08 edx=7c9032bc esi=00000000 edi=00000000
eip=033e9e08 esp=0012cadc ebp=0012cafc iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010246
033e9e08 a6 cmps byte ptr [esi],byte ptr es:[edi] ds:0023:00000000=?? es:0023:00000000=??
0:000> g
(d2c.bc0): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=00000000 ebx=00000000 ecx=033e9e08 edx=7c9032bc esi=00000000 edi=00000000
eip=033e9e08 esp=0012c70c ebp=0012c72c iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010246
033e9e08 a6 cmps byte ptr [esi],byte ptr es:[edi] ds:0023:00000000=?? es:0023:00000000=??
Sebastian,
How did you re-install CCS? If there is previous installed version, you might run into a situation where binary incompatible due to uninstall doesn't clean up all files and registry. If you have a previous install, the best thing to do for install a fresh copy of CCS is to clean your system. These steps assumes that you only have one CCS install on your PC.
1) open regedit and revmoe these keys
- HKEY_LOCAL_MACHINE\SOFTWARE\Texas Instruments\*3.3* stuff
- HKEY_LOCAL_MACHINE\SOFTWARE\GODSP\*
- HKEY_CURRENT_USER\Software\Texas Instruments\*
2) delete this file
C:\Program Files\Common Files\Texas Instruments\ccs_Compdb.ini
3) delete previous CCS install directory
Reinstall CCS 3.3 latest. I believe there is an install executable with SR12 included.
Regarding your questions:
- C:\CCSTUD~1.3 is possibly the short path name of C:\CCStudio_v3.3
- Couple of exceptions can be related to binary incompatible (I am taking a guess here)
Before you try to re-install, here are few things that you can try to fix your current install.
- Look under C:\CCStudio_v3.3\plugins\Joule and search for all dlls, make sure other folders within C:\CCStudio_v3.3 have the same dlls as this folder.
- Than run "regsvr32 <ocx file>" for all ocx files within the Joule folder.
I hope this help.
Patrick
I have exactly the same problem. I just reinstall Windows XP SP3 and CCS 3.3. silently close after displaying the splash screen. I installed CCS 3.3. on several computers running XP or XP virtual machines before without any problems. So I reinstalled CCS 3.3. several times on this particular PC using different administrator users. I try the fix that patch proposed in its last reply without success so far.
I don't know what to do next :(
I compare windbg outputs of my new computer with another running CCS 3.3 normally. I found that CCS 3.3 depends on .NET Framework 1.1 so I installed it on my new computer, and it worked!
Conclusion: To fix the problem, install .NET Framework 1.1!
Hi Hugh
I can confirm your finding, as I had the same problems and installing .NET 1.1 solved them. Thank you very much
To be somewhat more precise here is my situation:
Some time ago I installed CCS3.3 on a HP Compaq nc6320 running XP. After installation CCS did not start. I don't remember anymore how I got it to start, but once I've gotten it to start there were no difficulties using it (but I remember it was not installing .NET 1.1, though maybe some other SW might installed it).
As the machine was in common use by all the staff and some students (I work at university) it got bloated so we restored it (last week) using clean image. CCS was not yet included in this image, so I had to install CCS again. And I came across the same problem of CCS not starting, again. As I have image of bloated system (with CCS working) I compared two systems using DependencyWalker, but I found no mentionable differences (I should check differences more thoroughly).
What is even more odd is that I installed clean windows XP with SP3, leaving the machine disconnected, and even before I installed any driver or any other piece of SW I installed CCS and it worked. Without .NET 1.1.
From all this I deduce that one of the drivers or other SW installed on a machine corrupts something (maybe corrupt is a bit to strong word), which can be solved by installing .NET 1.1
Best regards,
Mitja Nemec
Installing .net framework 1.1 also solved the issue on my computer. CCS is now starting up. Thank you very much.
Regards,
Sebastian
hi, I'd like know how you resolved that, I have the same bullshit problem and I getting crazy with that, I've reinstalled the CCS, updates, even the OS, and nothing, what the hell is wrong?
I'm very sorry, but I don't remember anything valuable and can't find something in my documents.