The best interface to your Outlook calendar.

Receiving an error on initialization.

Tue, 07/08/2008 - 10:50

Hi,

I'm receiving an initialization error when the program loads as follows:

There was an error initializing the application: System.IO.FileLoadException: Could not load file or assembly 'Microsoft.Office.Interop.OutlookViewCtl, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

File name: 'Microsoft.Office.Interop.OutlookViewCtl, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'

Then the 'at's follow which I would gladly pass on if you really need them.

Thanks.

 

Forums: 
Bugs

crocos says:

Tue, 07/08/2008 - 12:32

sorry did not read this thread

running outlook 2003 and vista home

same problem

 

 

Miq69 (not verified) says:

Wed, 07/09/2008 - 05:28

I got exactly the same error. Pls help

arpita (not verified) says:

Thu, 07/10/2008 - 08:29

I have the same problem. Outlook 2003 + XP.

Mike, any ideas?

Outlooker (not verified) says:

Fri, 07/11/2008 - 00:38

I also got the same error. I am using Outlook 2003 on WinXP Professional and .NET at 3.5

One of the things I noticed with 1.4.4 was the following which seems to be leading to this error.

The versions of the PIA files in the install directory are as follows.

AxInterop.Microsoft.Office.Interop.OutlookViewCtl.dll - 12.0.0.0
Microsoft.Office.Interop.Outlook.dll - 11.0.5530.0
Microsoft.Office.Interop.OutlookViewCtl.dll - 11.0.5530.0
Outlook.dll - 11.0.5530.0

This seems to be causing a conflict and hence the error message. I do not know if we can get around this without Mike putting out a new version update with the proper version file to load.

I tried installing 1.4.0 which is present in the web-site (under Download > Changelog) and I was able to run it. I noticed that the DLL file versions were as follows.

AxInterop.Microsoft.Office.Interop.OutlookViewCtl.dll - 12.0.0.0
Microsoft.Office.Interop.Outlook.dll - 12.0.4518.1014
Microsoft.Office.Interop.OutlookViewCtl.dll - 12.0.4518.1014
Outlook.dll - 12.0.4518.1014

Well, 1.4.0 does not seem to have the features listed for it in the Changelog, though the log states that it has the ability to do multiple instances pinned to the desktop et al, whereas it does not. Please see my other comment below.

Another thing that I noticed was that eventhough I had downloaded and installed 1.4.0, the "About" information shows the version as 1.3.4 on the install. Probably a wrong version is kept for download on the web-site though the file is named as setupv140.exe.

Version 1.3.5 also seems to be having matching version files.

Hope Mike remedies this inconsistency.

Endruuu (not verified) says:

Tue, 07/15/2008 - 12:14

same for me... I just checked the following (very helpful) Microsoft page:

http://msdn.microsoft.com/en-us/library/aa159923(office.11).aspx#officeprimaryinteropassembliesfaq_after

After checking C:\Windows\assembly I noticed that all my Microsoft.Office.Interop. assemblies are version 11.0.0.0 and not 12.0.0.0 as expected.

What's the standard procedure of updating these assemblies? Sorry I'm no expert in the Microsoft world.

kr Andrew

mike says:

Thu, 07/17/2008 - 09:44

Hey guys,

Thanks for the very detailed reports.  I deliberately tried including the Oulook 2003 assemblies in the latest version (instead of 2007) to try and fix a problem that a handful of people are having, but it seems like it may have caused more issues. 

I think the solution might be that I have to downgrade to Office 2002 on my development box.  That way it will generate an older version of the Outlook View Control interop assembly.

Thanks,
Mike

WimH (not verified) says:

Thu, 07/31/2008 - 16:05

"that a handful of people" are growing rapidly!!!

SkykeN (not verified) says:

Wed, 09/10/2008 - 04:33

WimH is right, I have the same problem...

Could the problem be I have Office 2007 installed but don't use Outlook 2007 but still Outlook 2003 because I think it's quicker...

lg4me (not verified) says:

Wed, 11/05/2008 - 12:32

Same problem. Outlook 2003 + XP (SP3).

test (not verified) says:

Tue, 02/17/2009 - 03:01

Same problem. Outlook 2003 + XP  (SP2).

 

Release 1.4 didn't help me, it doesn't work at all

inserthere (not verified) says:

Thu, 02/19/2009 - 14:37

Same problem here.  Outlook 2003, Vista Buiness.  Wish I could use the app, it looks like exactly what I've been looking for.

sescora says:

Thu, 03/12/2009 - 22:14

 Same problem here - Office 2007 and XP (SP3)

mike says:

Sun, 03/22/2009 - 19:50

Hey guys,

if anyone is still following this thread and has this problem.  Can you tell me, does this only happen when your computer reboots and OooT is set to start with Windows?   If you get the error, then wait for your desktop to fully load and try loading OotD manually, do you still get the same error?

I'm thinking it might have something to do with Outlook not being able to load fast enough on windows startup because of all the other stuff that is being loaded.

Mike

WIN4US (not verified) says:

Thu, 04/02/2009 - 02:00

If happens both ways for me. The only way I got around it was to use Admin User, copy its Outlook.pst to the User having the problem. I also had to remove the Outlook Backup pst file. Before copying the new Outlook.pst, I export the calendar to be used later to load calendar.

 

After Outlook.pst copy, I ran Outlook again and started OOTDT and it worked. I then exited OOTDT and ran import in Outlook to reload Calendar appointments. Exited Outlook and when I start OOTDT again, I got error. You would think that standard Outlook 2007 calendar entries woruld be OK. I had no other entries in notes, events, contacts, tasks... just calendar.

mike says:

Thu, 04/02/2009 - 10:00

Thanks for the reply.  It sounds like this is a bug in the Outlook View Control that is triggered by certain data scenarios in the pst.   The problem is, I have very little control over what the Outlook View Control does and not being able to reproduce the problem is even more of a problem.   Would anyone with the problem be willing to send me their Outlost.pst file to test?

Mike

persiphone77 says:

Tue, 04/28/2009 - 01:57

I am having same problem, new laptop, just put outlook on computer (2003) and was extremely excited to get rid of my xemico active desktop for this, but it's not working at all.  Even uninstalled Xemico.  Immediately after download, after it ran setup it popped up with all these errors and even after restarting computer it still has all these errors, can't even close out the program unless I go into task manager and close it that way.  I love the idea of this and the screenshots look awesome, I hope I will be able to use it.  Please let me know what to do to fix this, the program looks so awesome and I love desktop calendars.

 

persiphone77@gmail.com

 

Thanks,

Persiphone

mike says:

Thu, 05/07/2009 - 14:51

Persiphone,  you can uninstall the program if you are getting errors.  

I do have some new information on this issue though.  A user was kind enough to send me their Outlook.PST file to test.   The good news is that I was able to reproduce the problem on my machine.  The bad news is that it completes crashes my development environment when it attempts to create the Outlook View Control instance.   This indicates to me that the problem is entirely Microsoft's and there's not a whole lot I can do about it.  

What's even more interesting is that this particular user says it works fine in OotD until he installs Office 2007 SP2 at which point the crash starts happening.  If he uninstalls SP2, it works fine.

It appears that the Outlook View Control is more of afterthought for Microsoft, as it's not as resilent to bad/corrupt data as Outlook itself is.

Mike

TheVirus says:

Wed, 06/24/2009 - 13:18

Hey Mike,

Any updates on the problem? Hope it will be fixed soon!

AndreB says:

Fri, 06/26/2009 - 02:09

Hi Mike,

If you run OooT right after you installed it, it works fine. Now reboot the machine and your'e stuck, no pgm. startup, only an error. Ignore the displayed error message and leave the system to start. Try again to start it. Again nothing.

I also did try to have it startup later by using "Startup Delayer" but the result stay the same.

Now the interesting part.

  1. Uninstall
  2. Reinstall
  3. Anwer Yes to have OooT run
  4. All's well UNTIL you reboot or restart. Then you can  be sure that you wil start at point 1 again.

My question is why is it running the first time.

 

mike says:

Mon, 07/06/2009 - 13:31

Hey Andre 

It sounds like your system is extremely busy on startup and is not able to initialize outlook fast enough for OotD to use.  Can you give me the specs on your system?   CPU Type and Speed, RAM, Hard Drive, etc.  If you know them.  

The workaround for now is not to have to start on startup, and just launch it after your system is fully booted.

Mike

brain.tom72 (not verified) says:

Fri, 09/11/2009 - 07:00

 

 “Sometimes I wake up and I think I should start wearing a beret, but I don't do it. One day I'm gonna, though. You bet your ass, I will have a beret on. That's ridiculous, but it's true. I always fight with wearing a beret.”

 

 well right now i am doing mcse and i suggest you the same may be your career lies in it.

c30sm9 (not verified) says:

Fri, 09/18/2009 - 11:05

Ok, I'm posting because I have Outlook 2000 and when I tried run the program this is what I got:

 

Any hints?

 

 

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Runtime.InteropServices.COMException (0x80040154): Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG))
   at System.Windows.Forms.UnsafeNativeMethods.CoCreateInstance(Guid& clsid, Object punkOuter, Int32 context, Guid& iid)
   at System.Windows.Forms.AxHost.CreateWithoutLicense(Guid clsid)
   at System.Windows.Forms.AxHost.CreateWithLicense(String license, Guid clsid)
   at System.Windows.Forms.AxHost.CreateInstanceCore(Guid clsid)
   at System.Windows.Forms.AxHost.CreateInstance()
   at System.Windows.Forms.AxHost.GetOcxCreate()
   at System.Windows.Forms.AxHost.TransitionUpTo(Int32 state)
   at System.Windows.Forms.AxHost.CreateHandle()
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ContainerControl.WndProc(Message& m)
   at System.Windows.Forms.Form.WmShowWindow(Message& m)
   at System.Windows.Forms.Form.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
OutlookDesktop
    Assembly Version: 1.5.2.0
    Win32 Version: 1.5.2.0
    CodeBase: file:///C:/Outlook%20on%20the%20Desktop/OutlookDesktop.exe
----------------------------------------
log4net
    Assembly Version: 1.2.10.0
    Win32 Version: 1.2.10.0
    CodeBase: file:///C:/Outlook%20on%20the%20Desktop/log4net.DLL
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Microsoft.Office.Interop.Outlook
    Assembly Version: 10.0.4504.0
    Win32 Version: 10.0.4504
    CodeBase: file:///C:/Outlook%20on%20the%20Desktop/Microsoft.Office.Interop.Outlook.DLL
----------------------------------------
AxInterop.Microsoft.Office.Interop.OutlookViewCtl
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Outlook%20on%20the%20Desktop/AxInterop.Microsoft.Office.Interop.OutlookViewCtl.DLL
----------------------------------------
OutlookView
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Outlook%20on%20the%20Desktop/OutlookView.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.


 

anj (not verified) says:

Sun, 01/17/2010 - 17:29 


Hi there, :)

I just got a new laptop, and I'm getting the following
error message, which is different than the one above:

There was an error initializing the application:
System.Reflection.TargetInvocationException: Unable
to get the window handle for the 'AxOVVCtl' control.
Windowless ActiveX controls are not supported. ---> 
System.AccessViolationException:  Attempted to read or
write protected memory.  This is often an indication 
that other memory is corrupt.

at
System.Windows.Forms.UnsafeNativeMethods.IOleObject.DoVerb...

...and there are a lot more 'at's under that.



I'd love to be able to run it...any ideas?  I'm not
knowledgeable when it comes to computer error issues,
so if there is a solution, I may need a step-by-step
walkthrough.



Thank you so much! :D

Anj

 

mike says:

Thu, 02/25/2010 - 14:31

Hi all,

I've finally seen this issue on my own machine.  It most definitely has to do with a messed up Office Installation, specifically dlls that are not registered properly and/or a corrupt PST file.   I was able to fix it by doing the following:

1. Run ScanPST.exe located in C:\Program Files\Microsoft Office\Office[Version Number] and choose your Outlook.PST file and scan it.

2. Go into Outlook and go to the Help menu and choose "Office Diagnostics" in Outlook 2007 and in previous versions, I believe the option was called "Detect and Repair."  

Hope that helps!
Mike

reynolea (not verified) says:

Mon, 08/16/2010 - 12:20

Mike - how do you do all this troubleshooting in Office 2010?  I'm having the same COM registering problems as other users.

reynolea (not verified) says:

Mon, 08/16/2010 - 12:21

I'm getting the same error as you c30sm9.  Any suggestions or learned fixes?

VictorSvetlov says:

Tue, 08/31/2010 - 11:49

Error lunching OOD on Windows 7 Home Premium 64 bit Russian with Office 2010 Pro 64 bit Russian.

Screen here (this message is visible in administratime mode only):

http://s53.radikal.ru/i139/1008/a2/85ef1f98564e.jpg

Thanks a lot for your work. Will wait as long as needed.

If you like this program, consider helping out: