Member Avatar for nam.sri

I am using dot net 2003 but now want to move on dot net 2005
when I start installing through CD I got a error
"Suite Integration Toolkit Executable has encountered a problem and needs to close. We are sorry for the inconvenience."
can any one resolve my problem. Is it necessary to remove 2003 first? I am installing on windows XP Pro .
Pls help me.

  • 4 Contributors
  • 5 Replies
  • 111 Views
  • 5 Days Discussion Span
  • Latest Post Latest Post by jamello

Dani AI

Generated

A concise troubleshooting note for the "Suite Integration Toolkit Executable has encountered a problem and needs to close" error reported by . Earlier suggestions from , and covered removing older VS and checking media; the checklist below fills gaps those replies did not address and focuses on diagnostics that pinpoint why SIT.exe (the setup integration component) is crashing.

Start with installer diagnostics (log collection and event data). Reproduce the failure, then inspect the temporary folder (%temp%) for recent setup logs (look for files like SIT*.log, dd_*.log or any vs*setup*.log). The last 30–50 lines often show the failing action or a faulting module name. Also review the Windows Event Viewer (Application log) for .NET runtime or application error entries that name the faulting module and exception code. Microsoft guidance on Visual Studio setup logging is useful: Troubleshoot Visual Studio installation (logs and diagnostics).

Repair and capture failing behavior. Run the Microsoft .NET Framework Repair Tool to fix corrupted framework components: . Use Sysinternals Process Monitor to capture file and registry activity while SIT.exe crashes; that often reveals a missing or locked DLL or an access-denied condition: Process Monitor (Procmon).

Other useful steps not yet mentioned in the thread: run a Windows Installer repair/update, temporarily disable antivirus/shell-extension hooks during setup, extract CD contents to a local folder and run setup from disk, and avoid tools that alter the registry without a backup. Key diagnostic data for follow-up are OS build/service-pack, the top lines of the most recent SIT log, and any "faulting module" entries from Event Viewer; those point directly to .NET, CRT, or I/O issues and enable targeted fixes.

Recommended Answers

All 5 Replies

Member Avatar for srinivasparcha

HI,
I think u need to uninstall dotnet 2003 and then install Dotnet 2005.

Member Avatar for reach_yousuf

Hi

Its a prerequisite to un-install VS2003

Member Avatar for jamello

Hello there!

>Its a prerequisite to un-install VS2003

I currently have both vs 1.1 (2003) and vs 2.0 (2005) on my machine without much ado.
I do not think that is the problem because I didn't not run into any problem during my installation.

I advise that you check the integrity of your installation CDs.
peace

Member Avatar for nam.sri

thanks for the reply, I have check with 2 -3 CD's but getting the same error.

Member Avatar for jamello

>nam.sri thanks for the reply, I have check with 2 -3 CD's but getting the same error.

Though this is a long shot, It is possible to have repeated errors of a number of set of cd's if you got your set of cds from the same source.

I use XP sp2. I suggest you get the latest service pack from microsoft site.
please get back to me.
peace

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.