I have an Outlook Web Addin, running in O365. This is currently hosted at my first server. (oldserver.domain.com)
I wanted to change the address the addin calls, so I changed all Urls in the Manifest file to (newserver.domain.com)and uploded it via the Microsoft 356 Admin Center. The new manifest was accepted, but the Addin is always calling the oldserver.domain.com. Since these updates sometime take a while to finish, I waited for the next morning.
I found this:
How often does the Outlook exchange server pull the web-addin manifest if they are "sideload" installed via URL
With this description it should already work. How can I get my addin to call the new url?
The changes may take an effect in up to 24 hours, not just next morning. You can find the following statement in the Deploy add-ins in the admin center article:
Outlook add-ins can take up to 24 hours to appear on app ribbons.
Sometimes it is necessary to enable and disable the add-in (multiple times) from the Office 365 admin center.
Related
A customer of ours is using a kind of sharepoint (not sharepoint) -a document repository- that, for what I saw, uses webdav.
There are two terminal servers, one of them is Windows 2008 R2 Datacenter v6.1 build 7601, Office 2016, and Internet Explorer 10.0.9200.17609IS. They couldn't access anything at all, they went as far clicking "edit" on the site and then Word they that he's sorry because he couldn't open the document.
I've fixed that, I added the site to the Trusted Sites list, and disabled SSL 3.0 and TLS 1.0. Local admins can open and update documents. Non admin users can open the document but not update it, and by can't I mean that Word opens the document in read-only mode and any attempt to switch to read-write will save the document in the local computer.
Now, the other server, Windows Server 2012 R2 version 6.3 build 9600, Internet Explorer 11.0.9600.19867, the former fix did the trick for both admins and non-admins.
Does anyone know where to look?
Thanks,
Max
I followed the documentation on https://support.office.com/en-ie/article/Deploy-Office-Add-ins-in-the-Office-365-Admin-Center-737e8c86-be63-44d7-bf02-492fa7cd9c3f to publish a created addin to our users. Unfortunately it is not showing up when users check out their Add Inns ( I see a caption Office 365 / Managed by admin but no selectable addin.
I tried:
Restarted MS Word
Logging in and out from MS Word does not help.
Removing the add in and adding again (through file or URL both not work)
Any ideas?
We seem to have the same issue; If you intercept the HTTPS traffic (by Fiddler for instance), do you see a 500 response to the 'POST /ews/exchange.asmx' with the body containing 'GetPrivateCatalogAddIns'?
So far, this seems to be an issue with Exchange internals. We've been trying to get into contact with Microsoft about the issue. Here you can find the StackOverflow issue we have filed, and Here you can find the question on the MS fora.
EDIT: It was confirmed that this was indeed an internal problem. We have removed our deployed plug-ins and added them again. The call now responds with a 200 and everything seems to be working again.
Unfortunately, we also found out that there is an issue with the Add-in registration interface in the Office 365 Admin Centre, as people who are not full administrator but User management administrator instead can no longer upload Add-ins due to an Exchange credential error. A Office 365 Administrator however can and this seems to be working with us.
Today I had a support engineer of Microsoft on the phone about my case and they resolved the issue. I can deploy add-ins again.
Recently we updated our systems to Office 2016. I have a scheduled task that reads information in an MS Access DB and then sends this information to a mail recipient via Outlook. All was fine until the upgrade.
The Scheduled task launches a .bat file which opens MS Access, calls a function, performs a task and then send the the information via email using outlook.
When I run the batch file manually by double clicking on it, it works as intended and sends the email. However, when I run through Task Scheduler it does not work. I know for certain that it opens the MS Access file and can read, but for some reason it fails to send the email. I have lowered all security setting to no avail.
The scheduled task runs with the highest privileges and all was fine before the upgrade.
Does anyone have any suggestions.
Outlook has security settings that will prevent an application from sending e-mail through it programmatically. It will use a popup dialog to ask for permission to send the e-mail. While I have successfully gotten rid of the popup and made Access send through Outlook while Outlook is open (both manually and as a scheduled task), it still fails when Outlook is not already open.
Your best bet, if you have the capability, is to leave Outlook open on the machine that runs the scheduled task. Otherwise you have to try to figure out what combination of policies and registry/outlook settings will make Outlook work the way you want it to.
Edit: My experience is with a windows domain/local exchange server environment.
We upgraded to Office 2016 a few weeks ago, and had been facing the same problem as you. Our batch file runs Access and triggers a macro that exports some data to a text file, and works fine when run manually. However, when run through Task Scheduler, everything seemed to run fine, but the text file was never updated. After trying for weeks with no success, I finally found the reason for the problem, and a solution.
In our case, the problem was that Access 2016 wants to be run as a foreground app. But when running as a Task Scheduler app (with the "run whether user is logged on or not" option checked), it views itself as a background app and therefore won't run. See Jim Dettman's answers here for a bit more on that: https://www.experts-exchange.com/questions/28988837/
Next, I found this post by Microsoft employee Blake Morrison where he discusses the changes in the latest version of Task Scheduler. One of his troubleshooting suggestions worked for us:
Try creating a new task, but select the Configure for: option to be
“Windows Server 2003, Windows XP, or Windows 2000” – this will create
an XP/2003 fashioned task
Unfortunately you probably have to do this as a new task - existing tasks don't seem to allow you to choose this option (it didn't show up in the dropdown menu for my existing task). So my settings for the new task are:
Running as an administrator account
"Run whether user is logged on or not" - checked
"Run with highest privileges" - checked
Configure For: Windows Server 2003, Windows XP, or Windows 2000
If I manually trigger the task, I see a command prompt open, then Access briefly opens and disappears (our macro has a Quit Access command at the end), and then the command prompt disappears. Output to our text file is written as expected. If I schedule it to run while I'm logged out of the machine, obviously I see nothing, but the text file is again written as expected, so I know it worked.
Our Global company is in the process of rolling out office 365 for the whole group. currently i am the only user in my location to start using office 365. I can create a new outlook 2013 profile for the office 365 account and it works well. Problem i'm having is after launching the new Office 365 profile outlook keeps prompting me for my local windows username and password. this only happens when i'm connecting to my local network. Our local exchange server is still in production and cant be removed at this stage as all my other 400+ users use it.
If i connect to my office 365 profile in outlook from another network this does not happen.
I created a new profile for outlook 2013 and this still occurs.
If i enter my credentials in outlook 2013 it downloads my local OAB instead of using the new Office 365 address book.
Current setup: Local Exchange 2007 server.
Office 2013 on windows 7 64bit
Microsoft employee here - sorry to hear about the difficulties you're having!
Can you answer these questions for me:
1. What specific Outlook 2013 version are you using? e.g. 15.0.4631.1000
2. Does the problem still occur if you set the ExcludeScpLookup Autodiscover reg value? Steps to do so can be found below:
a. Start regedit
b. Select reg key HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\AutoDiscover
c. Create a new DWORD value in this AutoDiscover reg key named "ExcludeScpLookup" (no quotes) with value 1
d. Restart Outlook and boot into your O365 profile
Note that #2 is not a permanent solution, just a troubleshooting step to determine where the issue might be occurring. Please delete that reg value after confirming whether or not the issue still occurs with it set.
Thanks!
I've deployed in Windows Azure a website made with Umbraco, using
Windows Azure Accelerator for Umbraco.
For development and test i used a test Hostname. Now it's time to switch to the official DNS hostname..
How can I change current hostname?
Actually i configured hostname at deployment time (the only way i know to do this) but i can't deploy again, since many files have been changed working on website on Azure.
EDIT
Let me explain: at the step prompt in the image (during web site deploying) I used as Domain Name "test.mywebsite.com", and configured real DNS.
Now the website is configured, so I'd like to make mywebsite.com point to that site;
But is'nt enough if i configure mywebsite DNS! Shall I deploy again? An will I lose any of the changes I made?
I'd like to make two comments on your question:
1) In order to host your Azure application under a custom host name, you will need to sign up with a DNS provider that supports C-NAME records (most do). I suggest someone like GoDaddy.com because by default C-NAME records can only resolve your "www.domainname.com" records and cannot do anything for queries where "www." is dropped from the URL. DNS providers like GoDaddy also have an option to redirect all traffic destined for "domainname.com" to a URL of your choice. This is a huge deal for Azure apps. Frankly speaking, it is somewhat disappointing that for all the PaaS and IaaS features of Azure, DNS was not included in the overall package.
2) I am a little worried when you say that you can no longer redeploy your app due to the changes made. Can you elaborate on that? Have you made changes to the application's code running on VM's in Azure without going through redeployment process? If so, this is a huge no-no. Your VM's running in Azure are not "permanent". Microsoft and your redeployment process can (and will) re-stage those VM's to the original package at any given time. Microsoft will re-image your VM's at least once a month during their monthly OS upgrades. But they can also do so when they need to move your VM to another rack, etc. Whatever changes that you make to your app must be either stored in source-control before deployment or in a permanent storage facility like SQL Azure, Azure Storage, etc.
HTH
Finally i think that the answers to my questions are:
-Shall I deploy again? Yes, i must deploy again
-Will I lose any of the changes I made? Many changes will be mantained since are stored into DB. But I have to do many activities to make new website work!
This answer confirms my theory:
In my case, I created and uploaded a site with a name, let's say
http://www.contoso.com and then paid a domain from a registrar let's say
http://www.example.com, when I mapped
http://MyAcceleratorsService.cloudapp.net/ to my new domain
( http://www.example.com ) and tried to open that domain I got the home page of
the Accelerator and not the uploaded site.
I had to upload the site again to Azure (using UploadUmbracoSite.cmd
from Accelerator application) and when uploading enter the same domain
name as the one I registered: http://www.example.com. Then, I was able to
browse my uploaded site as expected.
As for your question, will upload site again using
UploadUmbracoSite.cmd (is in the Setup folder) and will enter the new
domain name when requested.
Exactly what I was trying to avoid.. but the only solution, i suppose.
Well it was not easy to publish again, i got errors of many type (i suppose tied to some components that i've installed after deploy and that are not installed in new deployed website).. i'm going to solve them.
Edit
Completed my work:
- loads of different attempts, no-one worked
- CTP backup of DB
- deleted DB and website
- new full deploy of umbraco
- CTP restore of DB
finally:
-all work on content is OK
-all work on styles, pages, templates is lost
Changing hostname is hard; dont'use test hostname but definitive hostname from the beginning.
If anyone has suggest, i'll be pleased to test it, anyway
This is not really an answer to your question, but it might be a solution to your problem: Use a CNAME record to make the production DNS name point to your development name. E.g. www.productionname.com will the point to www.testname.com. I am not sure if everything will just work out of the box, but it seems to be worth a try.
This requires, that your hosting provider allows you to set up CNAME records.
http://en.wikipedia.org/wiki/CNAME_record