johoja - While the message may be triggered or "irritated" as a result of some interaction between X1 and Outlook it is an Outlook message/error. I'd like to direct your attention to a couple Microsoft Forum sites that may be of use to you.
http://answers.microsoft.com/en-us/offi ... ba49009ad8
http://answers.microsoft.com/en-us/offi ... 1a2d62e3b0
Additionally, In working on this issue with other forum members several other possible work-arounds have been known to help:
- Changing from non-cached to cached and back again
- Rebooting
In one case it only occurred when X1 was started first so, if you have X1 set to Load on Startup you could disable that setting which would allow you to reboot your machine, set up your work environment; including launching Outlook and when Outlook is up to date, launch X1 manually.
http://answers.microsoft.com/en-us/offi ... ba49009ad8
http://answers.microsoft.com/en-us/offi ... 1a2d62e3b0
Additionally, In working on this issue with other forum members several other possible work-arounds have been known to help:
- Changing from non-cached to cached and back again
- Rebooting
In one case it only occurred when X1 was started first so, if you have X1 set to Load on Startup you could disable that setting which would allow you to reboot your machine, set up your work environment; including launching Outlook and when Outlook is up to date, launch X1 manually.
