When I try to sideload my Outlook add-in, created based on the last Ignite session by Andrew Salamatov, I get following error when I add the add-in from a URL (https://bulkpermissiondemo.azurewebsites.net/manifest-bulkpermission.xml): "The app can't be installed. This app isn't supported by the version of Exchange Server that your account connects to."
any idea what I'm doing wrong?
Thanks :-)
We’ve tried installing the manifest provided in the link but were unable to reproduce the error listed in the original post on recent builds. Could you try installing the manifest again and see if the same error occurs? If so, would you be willing to provide the email address for the account you are trying to install the add-in to? Then we can take a look at the server logs to see what the issue might be.
Related
I am wrapping headless chrome using the excellent ChromeHtmlToPDF library. This we are using to dynamically render PDFs from a website. This works locally under IIS express, and also works on the server when recompiled as a console app, so the technology works. However running under IIS, chrome always exits immediately and a error of "one or more parameters are invalid", is returned.
You can fix this by passing Chrome a custom user profile directory:
chrome.exe --user-data-dir="C:\NewChromeProfile" ...
This directory will be created by the account under which Chrome is running, and therefore the account will have the permissions it needs.
After many many hours looking into this I finally solved it by running it under my own user, the restricted IIS user, then comparing the activity logs generated by the excellent microsoft process monitor.
I tracked it down to file permissions on one directory: C:\Windows\System32\config\systemprofile\AppData\Local\Google\Chrome\User Data
The app pool user needs write + modify permissions to this directory. It's up to you if you feel this is an acceptable security risk; however for us it is, for now.
This is where headless chrome stores it's crashpad directory. No amount of parameter fiddling seems to be able to dissuade it of this. That seems to be a bug.
Hope this helps someone else, I couldn't find anything on this anywhere.
We have two instances of SSRS 2016 installed, as one of them requires Windows authentication and the other requires custom authentication. The latter follows all the latest direction from the sample everyone references, except that it leverages a REST call to a separate authentication API we use for our applications rather than creating a user DB just for this use. We have given ourselves all permissions via the web portal, using the user account from this separate authentication API. Everything works fine until we finally try to execute a report and receive the error,
Could not load file or assembly 'Microsoft.ReportingServices.ProcessingObjectModel, Version=13.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. Access is denied.
We've found nothing referencing such an error and are stumped at this point. Any help would be greatly appreciated.
I had ran into this exactly same issue, and the cause was permissions setup for the execution account. I was providing him with admin permissions and full control setups on the folder, and file but the issue persisted. The solution was to remote desktop on the machine with the execution user account and acess the REport Server bin folder. With this the pop up to gain permanent admin permissions on it showed, and accepting this lifted the issue.
It took me days to nail this down, which seems like a bug. so I thought of posting this. I hope this helps.
I'm getting the following error when trying to upgrade an application I wrote:
Sorry an error occurred
The application cannot be installed due to a certificate problem. The
certificate does not match the installed application certificate, does
not support application upgrades, or is invalid. Please contact the
application author.
Here is a screenshot:
I'm the application author. I recently created a new project and copied the old project files to the new location.
Is this due to that or am I possibly using a different certificate somehow? In the drop down list I have multiple entries pointing to same cert. I will try going through them but I'm wondering too if it's possible if anyone else has run into this issue.
I was using the incorrect cert. When I created a new project, Flash Builder preloaded certs from somewhere. They looked correct, however, the cert I was using was not in that list. So I opened the previous project and found a cert from that the project was using. After recompiling and attempting to update, the install went correctly with no error.
Simple question... Using Visual Studio 2013 to build and deploy A Windows Store App for Windows 8.1 with Javascript. Unfortunately, even basic sample apps will not deploy. The error that pops up everytime when attempting to deploy is RDSAppXNotifyRecoveryTrigger.
I cannot seem to find any information on this error which makes it very frustrating. There is no problem when building the solution, however then we get the message...
The app needs to be deployed. When you click deploy we get this annoying ERROR: Error 1 Error : DEP0700 : Registration of the app failed. error 0x80070003: AppX Deployment operation failed. The specific error text for this failure is: RDSAppXNotifyRecoveryTrigger (0x80073cf9)
So it would help if I could find anything on MSDN about this error unfortunately someone asked this same question and then the entire post was deleted from the forums. Please help, I have tried to repair my Visual Studio installation, since even when you open a brand new Template App and press F5 you get this error, so I am thinking something is wrong or corrupt in my environment that is preventing any type of Windows Store App deployments, I cannot even run the apps. Thank you for any suggestions.
The specific Error 0x80073cf9 is related to apps not being able to be installed with Windows Store.
Some users have been successful with any of these 2 solutions:
1: The problem is that the folder AUInstallAgent is missing from the Windows folder.
Press Win+R, in Run type %windir% and press Enter. Create new folder named AUInstallAgent if that is missing in the Windows directory. Reboot computer
2: Start Command Prompt with 'Run as Administrator' option.
run this command:
powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRoot\WinStore\AppxManifest.xml
Hope this helps.
I have the same problem and this did not work for me. Still found lots of comments that this worked for others.
I know several similar questions to this have been posted, but I've walked through each of the provided solutions and nothing seems to resolve this issue...
I have SQL Express 2012 installed, and have created a simple report and want to deploy it to my local Report Manager website. Every time I try to deploy it from VS, I'm getting an error message that says "The specified Report Server URL "http:///Reports_SQLEXPRESS" could not be found. Verify the syntax of the URL and that the report server exists.
I'm able to browse this URL in my browser no problem; I've also confirmed through Reporting Services Configuration Manager that the URL and Virtual Directory are correct. As far as I can see this should be working...
Does anyone have any advice for next steps so i can deploy this report? I looked into it at the MSDN site and confirmed that the SQL Express w/ advanced tools should have this functionality... any help is appreciated!
"http://machine name/reportserver_sqlexpress"
is what my research has lead me to.
HTH