I'm working on an addin for Excel, the manifest has permission for ReadWriteDocument.
I'm adding a handler to Office.EventType.DocumentSelectionChanged Event
First time, I insert the addin in Excel Online, it works perfectly.
Later if the access the Excel, it fails with:
OSF.DDA.Error
code: 7000
message: "You don't have sufficient permissions for this action."
name: "Permission Denied"
I was seeing this issue as well, and we dug into it and discovered it was in fact a bug in the sideloading feature. It is now fixed, so please try it again!
Cheers,
Harrison
Related
Here's an example of a connection configuration that has stopped working (it's for connecting to an Azure managed database):
{
"server": "sqldb.12345abcde.database.windows.net",
"database": "sqldb01",
"authenticationType": "AzureMFA",
"profileName": "sqldb01",
"azureAccountToken": "",
"expiresOn": 1648022420,
"email": "benmcf#work.com",
"accountId": "aaaaaaaa-0000-bbbb-1111-cccccc222222"
}
When I try to connect, VS Code displays a dialog saying mssql: Credential Error: Account credentials have expired. Please re-authenticate. and another saying mssql: undefined:
After clicking the refresh credentials button, the linked page fails to resolve in my browser, showing ERR_CONNECTION_REFUSED:
When I reinstall the plugin, remove my connection definitions from settings.json and attempt to create a new connection, the browser page resolves correctly and allows me to authenticate, but it has no effect in VS Code.
I'm able use the same connection details in Azure Data Studio to connect successfully.
I had the same/similar problem and found 2 possible issues in my case. I went into Windows Credential Manager and Removed the aad-iv and aad-key credentials, as well as all the others that did not say Modified: Today (presumably overkill).
When I then tried again in VSCode, I received an error but was able to proceed by it giving me a chance to enter credentials. In my case, it then failed to connect with an option to automatically add a firewall rule... and then everything worked.
I'm not sure if it wasn't smart enough to figure out how to refresh credentials OR if it was trying to but something with the firewall rule came into the picture and disrupted it.
After this, I noticed Windows Credential Manager had aad-iv and aad-key credentials added back. So... I would try removing just those 2 and see what happens.
I resolved this by deleting the contents of this folder (Mac): ~/Library/Application Support/vscode-mssql/AAD.
I believe the equivalent on Windows would be something like C:\Users\{username}\AppData\Roaming\vscode-mssql\Azure Accounts.
I did the same as benmcf. However, I also deleted the AAD folder:
C:\Users\{user}\AppData\Roaming\vscode-mssql\AAD
After it, I uninstalled the MSSQL extension and installed again. Then it worked.
I have started learning oracle APEX and installed oracle apex 20.2 on my desktop PC just now. I am facing a problem that on running a sample application after install it shows me 404 - Not Found error.
Can anybody help me on this issue?
I had a similar issue when I imported an application. Try this: in application properties untick "Friendly URLs" and run it again.
If you're still getting the issue show the end of your url (all parameters after the server).
I have solved this issue. Actually the issue was with the user rights. I created a new user other the APEX_PUBLIC_USER and then the APEX was not working well because my new user didn't have those rights which APEX_PUBLIC_USER has.
I solved it by configuring the APEX back to the APEX_PUBLIC_USER and it runs well.
I maintain a large WPF application which I inherited from another developer. I use ClickOnce to publish it. Suddenly, today I got an error message:
Error 2 Cannot publish because a project failed to build. 1 1
Error 3 An error occurred while signing: Failed to sign bin\Debug\app.publish\setup.exe. SignTool Error: No certificates were found that met all the given criteria.
I do have a file called SomeName.snk, which is referred in project settings, Signing tab. I have no idea what happened today that caused the problem.
I use VS 2012.
Go to main project properties > Signing > If the expiration date is over > click on Create Test Certificate, password is not mandatory, and you're done.
I'd check whether the certificate expired. Most (all?) certs have an expiration date.
I got this problem installing visual c++ on top of a VS2017 .net install. I solved it by unchecking Properties -> Security -> Enable ClickOnce security settings.
It then created an app.manifest file. After that the error went away. Interestingly enough, I checked it again to see what would happen and the problem did not come back.
Did you check for the certificate?
View or manage your certificates
You can use the MMC Snap In or Internet Explorer.
Go to main project properties > Signing > Select from Store...
Click certificate properties
And install certificate
Go to Main project (Startup Project) and right click > properties
Then go to Signing
Then unchecked "Sign the ClickOnce manifests"
It's work for me.
This happens mostly if your certificate for that particular project has expired or has some issues.
Right Click Project -> Properties -> Signing Tab -> More Details button -> Shows your certificate details. Check if your certificate has expired
Ways to Fix
1. Un-check the "Sign the ClickOnce manifests" and try
2. Extend the Certificate by creating a Test Certificate (If your certificate is expired)
Hit "Create Test Certificate..." button
Enter your credentials (Not mandatory)
Save
3. Re-validate your existing certificate (If your certificate is not expired)
Hit "Select from file" button and use your existing key file (eg. .pfx)
OR
Hit "Select from Store" button and select from the available options
Tip: If you still face issues building the project. Just restart your
Visual Studio.
Hope that helps.
I had this same issue and I was able to solve it by removing or changing the timestamp server URL. After removing that, the project was able to build successfully.
I just ran into the problem today. In my particular case, it was caused by this Microsoft Windows Update.
I uninstalled that update and publish began working as it always had. This is only a temporary work around and means you should probably regenerate your keys/certificates.
In my case, the cert was not expired and none of the other solutions worked (restarting VS, using a temp test cert, restarting computer, etc.)
The issue was resolved by deleting my output directory and rebuilding.
Simple Clean sorted it for me.
Build - Clean Solution
In my situation I had many projects in the solution, so I browsed to the non-startup project and:
Go to main project properties > Signing > uncheck the Sign the ClickOnce option
Using Visual Studio 2019
I am trying to deploy a cube for the first time on my PC. I have run SSMS as an Admin and made myself (Gary-pc\gary, using Windows authentication) an admin. Doing this got me past the error message user does not have permission to create a new object in 'GARY-PC', or the object does not exist.
When I deploy the cube now, I get the error: the syntax for the ImpersonationInfo object is incorrect. If the ImpersonateAccount value is used for ImpersonationInfo, then the Account property cannot be empty.
I have not (knowingly! LOL) set up anything related to impersonation.
I've resolved the problem with this:
Double click on data source
Select impersonation
Choose use credentials of user
As #user1335419 says.
I tried changing the impersonation to "Credentials of User" and although I was successful in deploying the cube, I could not process it. I ended up getting an error that said:
"The datasource contains an ImpersonationMode that is not supported
for processing operations"
So I changed the impersonation from "Credentials of User" to "Inherit" and was able to process. I don't know if the first deployment would have worked with "Inherit", but thought I would share my experience.
I have a web application that has been up and running for quite some time now using the Windows Live ID delegated authentication. It's been in production for a couple of months, and all of a sudden this morning, it failed with the following error:
There's a problem with the site you are trying to share your information with. Please try again later.
The url of the error page is
https://consent.live.com/pp700/Error.aspx?mkt=en-US&ErrorCode=1017
We require users consent to be able to see what e-mail address they used to log in. Has anybody run into this before? If so, what did you do to resolve it?
Thanks very much!
Still not sure what the error actually means, but the following forum posts give some more details. Basic problem: Microsoft changed the API and didn't tell anyone, Contact.View should be ContactsSync.FullSync when using the contacts API.
http://social.msdn.microsoft.com/Forums/en-IE/wliddev/thread/7f0bcc69-d256-4e2d-a596-25e6318d83b5
http://social.msdn.microsoft.com/Forums/en-IE/wliddev/thread/7ade3e5b-8329-4dde-b08b-a98515363383