intraVnews KnowledgeBase

File not found during uninstallation of intraVnews

peterbru@intravnews.com (Peter) — Tue, 02 Aug 2005 11:58:13 GMT

Problem:
When you uninstall certain builds of intraVnews, you receive an error:
Error 1001. Exception occurred while initializing the installation: System.IO.FileNotFoundException: File or assembly name fguninst3.dll, or one of its dependencies, was not found.

More Information:
This is a known problem when uninstalling intraVnews build 1.12.2026.789

Solution:
1. Download the missing file from http://www.intravnews.com/downloads/fguninst3.zip, unpack it and and place fguinst3.dll in c:\\program files\\intraVnews.
2. Uninstall intraVnews via Control Panel, Add/Remove Programs.

More Information:
We are researching the cause of this problem. This article will be updated when more information becomes available.

.Net Framework 2.0 Compatibility Information

peterbru@intravnews.com (Peter) — Fri, 20 Aug 2004 20:36:02 GMT

Problem:

intraVnews 1.01 may cause errors when the Microsoft .Net Framework 2.0 is installed.

More information:

An error like the following may occur when the Beta Microsoft .Net Framework 2.0 is installed:

System.InvalidOperationException: DragDrop registration failed. ---> System.Threading.ThreadStateException: The current thread must set to single thread apartment (STA) mode before OLE calls can be made. Ensure that your Main function has STAThreadAttribute marked on it. at System.Windows.Forms.Control.SetAcceptDrops(Boolean accept) --- End of inner exception stack trace --- at System.Windows.Forms.Control.SetAcceptDrops(Boolean accept) at System.Windows.Forms.Control.OnHandleCreated(EventArgs e) at System.Windows.Forms.ListView.OnHandleCreated(EventArgs e) at System.Windows.Forms.Control.WmCreate(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ListView.WndProc(Message& m) at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

This problem occurs because intraVnews automatically uses the .Net 2.0 Framework if it is present. The 2.0 Framework contains some breaking changes. intraVnews 1.01 was not tested with the 2.0 Framework since it was not available at the time of publication.

Workaround:

You can either edit your machine.config file, or put a manifest file or config file in the Outlook folder.

See http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgenref/html/gngrfAssemblyBinding.asp

1. Create a config file with notepad containing the following:

2. Save the file as "Outlook.exe.config" (When using Notepad, make sure to include the quotes or else your file will be named Outlook.exe.config.txt).
3. Start Outlook.

Status:

This problem is fixed in intraVnews 1.1.

intraVnews 1.01: Memory Leak with Outlook 2003

peterbru@intravnews.com (Peter) — Sat, 31 Jan 2004 01:11:34 GMT

Problem:

intraVnews 1.01 may leak memory in Outlook 2003. When intraVnews is running for a long period of time, the Task Manager will report a large and increasing amount of memory being used by OUTLOOK.EXE.

More information:

The intraVnews AutoCleanup task is constantly monitoring Outlook in the background, even though it should be idle. During monitoring, intraVnews repeatedly makes a call to Outlook 2003 for which Outlook allocates memory that intraVnews can no longer release. Over time, this process may eventually consume all available memory.

Workaround:

By starting AutoCleanup, intraVnews stops constant monitoring and will not repeatedly make the call that costs memory.
If you do not wish to run AutoCleanup, you may start and immediately stop AutoCleanup.
This procedure should be repeated every time right after Outlook is started.

Status:

This problem is fixed in intraVnews 1.1