Would need to upgrade the MS Outlook from 2000 to 2010, because the exchange server was upgraded to 2010. I suddenly found that I cannot connect to the exchange server with MS Outlook 2000. I got the admin and he said 2000 are not supported anymore.
We got a program written in VB 6.0 to automate massive(100+) emails sending. The program cooperates with Outlook client and send emails out through the exchange server.
Now I cannot even access the exchange mailbox, so a upgrade is necessary. But I wonder the VB code still valid? Are there compatible?
I have no idea of the detail of the code because it is left by one of our colleagues who had already left the company. There are some .bas .frm .frx .ocx and it cooperates with .mdb file.
According to this Stackoverflow question you will need to change your Outlook object reference to Outlook.Application.14 from Outlook.Application. and of course there may be some other differences in the object models.
Related
This is in an Enterprise setup (had a lot of GPO set) running Exchange 2013 Server, with Outlook 2013 client.
I installed the add-in using OWA
Manage Add-ins > Add from file
The add-in appeared in and worked fine
When I open outlook 2013, I do not see the add-in appear, tried a lot of steps to debug.
As per this doc https://learn.microsoft.com/en-us/outlook/add-ins/troubleshoot-outlook-add-in-activation
Version no was ?Session.ExchangeMailboxServerVersion
15.0.1320.4000
Is the add-in disabled?
Enabled
Is the add-in manifest installed properly, and does Outlook have a cached copy?
%LocalAppData%\Microsoft\Office\15.0\WEF \<insert your guid>\<insert base 64 hash>\Manifests\<ManifestID>_<ManifestVersion>
The new added add-in files would get removed everytime the data is pulled from exchange servers. Only 3 default add-in files were available.
Checked Windows Logs in Eventviewer
The Exchange web service request GetAppManifests succeeded.
Got this message with event id 63
We also checked Fiddler and could see the call going to get the manifests but that would give the manifest of only 3 add-ins that come installed by default on Exchange Setup.
For the same account, the add-in works fine in a Virtual Environment, VDI setup. But doesn't appear on the desktop environment, if that helps.
To rule out the possibility of a wrong manifest file, we tried using the Outlook Command Demo Add-in. This also worked on Virtual Environment, VDI setup. But doesn't appear on the desktop environment.
Are there any other steps that can help us debug this? Any directory where logs are available for add-ins?
We have hit a roadblock due to this with no idea how to debug/get it working.
We developed an add-in for Outlook which is published in the store already. It has paid and trial versions. License checking in the add-in works fine if the add-in is used from a browser, Outlook for Mac. But if it is Outlook for Windows or outlook.live.com (versions where "add-in commands" feature is enabled and add-in is opened in a side bar) then no license information is passed.
Example:
This correct URL is navigated from Outlook Web and Outlook Mac:
https://serverurl?et=%3cr+v%3d%221%22%3e%3ct..............
This is how the URL looks like for Outlook for Windows:
https://serverurl?_host_Info=Outlook|Win32|16.01|en-US
So, since Outlook for Windows does not supply license information we have to refuse add-in access for our clients on Outlook for Windows.
I found related questions for Excel and Word, but none of them was answered yet. The problem is that it is Outlook that needs to send the data, so we can do nothing in our code to troubleshoot.
Guys, any ideas where the problem is or what to check in the manifest?
Here is the link to the add-in listing in the Office store (TextMiner) if it may help to answer.
I am having a horrible time getting started at creating an add-in for Outlook. I want to use the new html/javascript/manifest approach. I have been able to create a manifest and application which works great with outlook.live.com. Where I am completely getting stuck is with desktop Outlook. How do I install/debug my add-in with desktop Outlook?
I cannot find anything in the UI which will let me add this style of add-in. Additionally the Microsoft documentation did not make things any clearer. Their docs seem to hint using this type of add-in is only possible if you are connecting to an Exchange server.
Any help would be greatly appreciated.
Yes the add-in will load on Outlook desktop only if your mailbox is Exchange. I am not sure the add-ins work with a personal Microsoft account (e.g hotmail.com, outlook.com) and Office desktop. Keep in mind that the support of mail add-ins for personal account is relatively new (officially announced in march 2016).
To develop your add-in I suggest you to use a organizational account (i.e. Office365 account). Support for organizational account has been released in 2013 and is a much more mature solution for you to get started. You can have a free dev account at dev.office.com.
Edit: October 2016 personal account are supported now by "Personal mailbox accounts" aka outlook.com accounts
Let us keep in mind that a mail add-in is not installed on a mail client (desktop, OWA) but on the mail account. When you "install" an add-in you only set a xml file on your mailbox that basically says "there is a web add-in out there called X and that is served at this url...". Then, if you install add-in X on your mailbox smaclell#mytestcompany.onmicrosoft.com, this add-in will load the add-in web iframes whether you are consulting your mailbox with Outlook Web Access (OWA) or Outlook Desktop.
To install the add-in for one user mailaccount, you have to use the Outlook Web Access. See this blog post. Note also that you can install the add-in for the whole organisation (Admin > Exchange Admin > Add-ins). Finally, Visual Studio is also able to push the manifest to your office 365 mailbox. To have this you need Office Development Tools.
For debugging in Outlook Desktop, I know two approaches.
Use the Office Developement Tools with visual studio
and select your sample add-in project as 'Starting project' and in properties select 'Office Desktop'.
Plain web development.
Personally, I do not use really much the Office Development Tools. I install manually my add-in with "https://localhost:XXXX" for url and I start the web project on IIS express to do the debugging. For stepping into the source code, I use the debugger of my browser (Chrome, Edge, IE etc.) when browsing in OWA. When I need to step into source code specifically on Desktop (For windows or for Mac) I use Vorlon.js see also this blog post.
My advice is also to test/debug frequently with IE 11 (still available in Win10!) and OWA. Indeed, the browser used internally by Office Desktop for the add-ins is IE.
Hi we recently installed an SBS 2011 server for one of our clients and we had some problems using software that creates messages using mapi on exchange 2010. After investigation we found out that the root cause of this problem is that STORE_HTML_OK is not set in the PR_STORE_SUPPORT_MASK.
The weird thing is we (the firm, one of my collegues) did the installation of the sbs 2011 server with exchange 2010 for the client where STORE_HTML_OK is not set, during my investigation of the problem we installed another sbs 2011 server for testing purposes and there STORE_HTML_OK is set whereas it wasn't in the previous installation.
I would like to know what could cause the STORE_HTML flag not to be set in PR_STORE_SUPPORT_MASK on exchange 2010, i also would like to know if we can still change this somehow by changing settings in exchange management console or shell ?
We would like our futurue sbs 2011 servers always to have the STORE_HTML to be set in the PR_STORE_SUPPORT_MASK and like to know what could have caused it not to be set.
Thanks in advance
Willems Davy
EDIT:
Our new sbs 2011 installation has the same problem, i was always testing the code from a client pc where outlook was installed and when outlook is install the mapi version of outlook is used so when running the code from a client with outlook 2007 or even outlook 2003 installed the issue is not there, When installing the mapi runtime (messaging api and datacolaboration objects ...) on SBS2011 the problem is the same (i tested 3 sbs 2011 installations now). The weird thing however is i use the same setup for installing the mapi runtime on a SBS 2008 server and there we don't see this problem, could this be a problem with the mapi runtime being somehow incompatible with sbs2011 / exchange 2010 ?
EDIT2:
we were wrong in our assumption that the STORE_HTML_OK flag was the cause of the program failing, after some more testing it seems this flags is only set when using the mapi dll from outlook, it's never set in our test when looking with MFC_MAPI at the PR_STORE_SUPPORT_MASK on the server when using the mapi runtime not even on SBS 2008.
However the problem with the software is related to the PR_BODY_HTML flag, on exchange 2007 (SBS 2008) servers using the mapi runtime we can change this property on exchange 2010 servers (SBS 2011) we can not and get an error when opening the PR_BODY_HTML propert using openproperty that says "the client operation has failed" this seems to be our main problem and the problem of the software we have.
so it's not related to the PR_STORE_SUPPORT_MASK, maybe i should ask a new question about it, since the problem is not the same as we initally thought?
I don't think this is a server setting. That bit is exposed by the store provider, which runs locally.
What version of MAPI did you install on the machine where your code runs? Is it an older version of Outlook?
Outlook Anywhere is not enabled on the Exchange server used at the company I work for.
People using Outlook on the Mac are able to get their mail remotely using EWS but i can't find any information on doing this in Outlook running on Windows 7.
The Exchange Server is 2010, does anyone know if I can use EWS to send/receive mail from Outlook in Windows 7?
Thanks.
The version of Windows is irrelevant. All Windows versions of Outlook connect to Exchange via MAPI (unless of course you're using Outlook Anywhere, POP, or IMAP).
Earlier versions of Mac Outlook (certain versions of Entourage) used WebDAV via the Exchange virtual directory. Later versions of Entourage/Outlook 2011 starting using EWS.
Outlook for Windows isn't capable of this (as far as I know) but why would you want it to? MAPI works well and accessing mail via EWS is more taxing on your Exchange server.