VB.net program crashed under Windows Server 2003

VB.net program crashed under Windows Server 2003

• Hockey Nut

  "Class not registered".
  
  Windflower, what this message almost always points to is an environmental problem. It means the registry doesn't know about a control or dll which generally means it hasn't been installed, which returns us to an environmental problesm.
  
  

• Silverdragontech

  If you are using a dll which needs to be registered on the client machine, you need to select the file in the installation project and set the property "Register" to "vsdraCOM". Try that and see if it works out for you.
  
  

• Peacho

  Thank you Guys,
  
  Here's a list of my references, I'm not too sure which ones need register.
  - AxInterop.ShockwaveFlashObjects
  - AxInterop.WMPLib
  - Interop.Microsoft.Office.Core
  - Interop.ShockwaveFlashObjects
  - Interop.WMPLib
  - Interop.Word
  - mscomctl
  - mscorlib
  - Microsoft.Vbe.Interop
  - Microsoft.VisualBasic
  - Microsoft.VisualBasic.Compatibility
  - stdole
  - System
  - System.Data
  - System.Design
  - System.Drawing
  - System.Web
  - System.Windows.Forms
  - System.Xml
  

• Dan_12345

  In your project have you made a reference to any COM dlls
  
  To check your references do the following:
  
  1. In Solution Explorer under your project node, double-click My Project
  2. In the window that opens, select the References tab
  3. Post eveything in the References list
  
  

  
  
  

• Conor Morrison - MSFT

  Im assuming this is a ComException so make sure the components you are using in your application are also installed and registered on the machine with Windows Server 2003.
  
  

• MRashed

  First of all in the References tab, click the Unused References button and click Remove on the dialog that displays.
  
  This will remove any references you are not using.
  
  Going by the list of references you are interoping with a lot of COM components; Shockwave, Windows Media Player and Microsoft Office/Word.
   
  Have you made sure that these components are installed on the Windows 2003 Server machine
  
  

• william.c.schneider

  Word is not installed on that machine. I guess that might be the cause. Thank you Guys very much.
  
  

  
  

• N2H

  Thank you Joe,
  
  I did make a setup package(.msi) and ran the setup on windows server 2003 machine. There's no problem with the setup, but the application still does not run. So could you tell me what else I should do to register the components.
  
• VB.net program crashed under Windows Server 2003