Our company has a shared network drive folder for everyone's Free/Busy .vfb files. I confirmed I have permissions to read/write to this folder.
I followed the directions to configure Outlook 2013 (32-bit version, running off Windows 7 x64) from Microsoft's Knowledge Base. I can see other people's Free/Busy information, but nobody can see mine. Outlook never publishes my .vfb file to the folder. Other employees with Outlook 2007 and 2010 don't have this issue.
Another person posted this problem that's very close to mine on another forum and I've tried the same troubleshooting steps. I'm experiencing the same "71 months" issue he's having as well. I've tried disabling the firewall and verified registry settings, but nothing is working. I even tried adding an older Outlook "UseLegacyFB" DWORD value but that didn't work either.
There's a bug in Outlook 2013. See this : http://social.technet.microsoft.com/Forums/fr-FR/d265a5c6-9f99-410a-8862-a374de1b4144/freebusy-not-publishing-with-outlook-2013-without-exchange
This issue has been submitted to the Outlook Team for a fix but we do not have an estimated
release date yet. Once I get more information I will post back and update. When using POP
accounts the *.vfb file does not get created properly.
Related
I have a Windows Form app that I developed with Microsoft Visual Studio 2015. I recently got a message that my license "has gone stale" and must be updated. When I click the link, I get an error message: "We could not download a license. Please check your network settings or proxy settings."
Going to my subscription online, I see "Visual Studio Dev Essentials"
I tried the solutions from https://cloudopszone.com/visual-studio-2015-error-message-we-could-not-download-a-license/ without success. My account is a "work" account and we do not use MFA at this time.
Visual Studio Community 2015 won't sign in. How do I fix this? suggests that uninstall/reinstall is needed, so perhaps that is my best next step.
I found the VS2015 installer here: https://my.visualstudio.com/Downloads?q=visual%20studio%202015&wt.mc_id=o~msft~vscom~older-downloads
Anyone know if it is possible to update a stale VS2015 license currently? It occurs to me that MS may have made that impossible somehow since it is an old version.
I installed VS2019 CE to use that, and it opens just fine but my app has issues with fonts (which is a separate issue), and forms look almost ok on screen but very bad when run.
This was caused because years ago, I used a "personal" microsoft account, which has the same user id as my "domain" account. The domain account is what I use for Office 365, Azure, and domain logins. Apparently VS 2015 was connected to the personal account. I knew of this personal account, but since I don't use it anymore, I incorrectly assumed it was kaput.
To fix, I opened VS2015, and when prompted to update license, I selected "Add an account..." and entered my userid and noted it was a personal account, and entered that password (different from domain p/w, and thankfully saved in chrome for better or worse). Then, when I clicked on "Check for an updated license", it found one right away and is now working.
I have a Client Project relationship in my web-app. I want to allow my web-app users to be able to file emails right from within Outlook. So in my Outlook Web Add-In, I want to create the client project folders on the fly, if they do not exist already, and move the selected email item in the respective project folder.
My code works fine in Outlook Windows. In Outlook Web, it executes without any errors, but the folders are not displayed. If I reload the web page, the folders are there and the email is in the right folder.
I have talked to Microsoft support and they are saying that OWA is working fine.
Can anybody help me spot any issues with my code?
CreateFolderPath EWS operation is not allowed in my add-in. So that does not seem to be an option.
The manifest file is available at https://newdev.timesolv.com/Integrations/addin/SimpleVersion.xml
This is a bug. It has been submitted to Microsoft and they have acknowledged it.
Update: On January 27th, 2020, the issue was closed by OfficeDev. I confirmed and it was working fine.
We've created an Outlook add-in which integrates our custom CRM with Outlook. A command button is added to messages in read and compose mode. A function file is called on the button click.
The add-in manifest passes validation and installs properly on all machines. However on Outlook 2016 desktop (only) we are seeing an error on some machines. The exact error message says: “We’re sorry, we couldn’t access [NCS Outlook Add-in]. Make sure you have a network connection. If the problem continues, please try again later.” ([NCS Outlook Add-In] is the name of our add-in.)
Note that this message appears IMMEDIATELY after clicking the add-in command button. It does not first say “[NCS Outlook Add-in] is working on your request” like it add-ins do when an error has occurred.
We have tried Outlook logging and haven't found anything useful in the logs. We've checked settings and disabled other add-ins. We have also tested across machines with user accounts. The same user will have the error on one machine and not the other. In short, it seems that the error is machine specific and not profile related.
Version of Office 365 installed: 1705 (Build 8201.2209).
We experienced this exact behavior in Outlook 2016, the solution was to enable protected mode for the restricted and internet zones.
The easiest way to change this is in IE.
In Internet Explorer, click the Tools button, and then click Internet Options.
Click the Security tab, and then select the Restricted Sites Zone.
Select the Enable Protected Mode check box, and then click OK.
Restart Internet Explorer.
Here is a little more information:
https://support.microsoft.com/en-us/help/2761180/apps-for-office-don-t-start-if-you-disable-protected-mode-for-the-rest
Try this:
1) Close Outlook
2) Rename the folder C:\Users\%USERNAME%\AppData\Local\Microsoft\Outlook
to C:\Users\%USERNAME%\AppData\Local\Microsoft\Outlook.OLD
(Where %USERNAME% is current User Name.)
3) Start Outlook, Setup User Profile
4) Add/Test Add-In.
If that works, then something broken on old Outlook profile. But if same problem: Exit Outlook, delete the Outlook folder and rename Outlook.OLD back to Outlook.
I ran into this exact same problem after uninstalling Visual Studio 2015 on my development machine. (I had been using Visual Studio 2017 for Outlook add-in development.)
The problem went away as soon as I reinstalled Visual Studio 2017. The Outlook 2016 installation had nothing to do with the problem, I never changed Outlook or its profile at all.
This would indicate that the problem is somehow related to the SDK tooling on the machine...perhaps something to do with the .Net framework?
If I ran into this problem on a customer machine I would try reinstalling or repairing the .Net framework, or perhaps reinstalling Outlook (assuming it contains some add-in tooling that is broken.)
Just passing this on in case it helps anyone else.
This is a very strange situation that I am in; scratching my head for answers.
I have developed an outlook addin that works perfectly on my dev machine and on about 90 % of the clients machines.
The load behavior of the addin is 3.
On 10% of the users, outlook starts up without loading the addin despite the load behaviour being 3. The user can manually make the addin active by going to the addin manager on outlook but after a restart this addin reverts back to being inactive bbut load behavior never changes from 3.
I used Install Shield LE to package this addin. I don't even know where to debug anymore, I tried changing different load behaviour values but still the same outcome. The addin just won't load on startup with this set of users.
The company uses ZenWorks to automatically install the addin on all the PCs from the MSI i generate using install shield.
One weird thing is, If i go to the installation directory of the addin and install the addin using the .vsto deployment file, it works and gets loaded on outlook (but thats makes it two addins installed).
I also checked the Resiliency section on the registry and the addin isn't there.
I have faced this issue. To solve this, you need to manually delete the registry entries from the following path.
Open registry editor and go to HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\Addins\<Your add-in> and change the LoadBehavior to 3.
If the above registry entry is not found, then look for HKEY_CURRENT_USER\Software\Wow6432Node\Microsoft\Office\Outlook\Addins\<Your add-in> and change the LoadBehavior to 3.
Go to HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\Resiliency – remove the REG_BINARY keys found in DisabledItems and CrashingAddinList
where 15.0 is for outlook 2013.
If you are using 2010 outlook, replace 15.0 by 14.0 and for Outlook 2016 replace 15.0 by 16.0
Hope this helps.
I know this has been asked before, but I've never found a solution to this. I created an Addin in Visual Studio for Outlook 2007. I created an Installer and copied the files and created the registry values. It installs perfectly on the developer computer and it uninstalls perfectly as well. But on the second computer, which is also Windows 7 32bit and Office 2007, the registry key LoadBehavior is always reset to 2 when Outlook opens. I edit it to say 3 and it just resets to 2 again. No error message or anything. This also happened on my computer at work.
Now, I did read something about this guy that tried installing Visual Studio on the computer and it would run just fine after. Made me think I need some other .NET library or something?
Why does this happen and has anyone ever found a solution?
In my case this turned out to be caused by an issue in a license protection wrapper from a third-party vendor. The issue has apparently been fixed in more recent versions of that product (contact me in private if you need more details).
Also, watch out for message boxes shown during Outlook startup. Outlook is really sensitive to those and AFAICT it has only gotten worse with Outlook 2010, especially under Windows 7.
Also, see this question of mine for links to a MS blog entry about this.