Everything was working fine until morning, but now I am not able to deploy my office app to Sharepoint server. It throws access denied error.
Please suggest the way out.
Sharepoint service was downgraded, maybe some maintenance going on. I was able to login after an hour or so.
Related
we are facing some major probelems with odoo v13 and importing mails from microsoft365/outlook. We setup our ticket system to import e-mails and create tickets from these e-mails which works fine until today. Now odoo can't login to the e-mail accounts anymore.
We changed passwords, tried other mail accounts and only with microsoft it's not working. Other accounts work well. It seems like something on microsoft side has changed.
Any solution?
Microsoft deactivated base authentication, so logging in by regular credentials (loginname, password) won't work anymore. Instead you should upgrade your Odoo 13 to get the new modules for outlook/o365: fetchmail_outlook and microsoft_outlook.
To get more information just look into this Issue. At the end of this issue a nice finnish guy shared a little documentation how to set up the oauth2 way.
As far as i know all verions from 13 have those modules.
I am trying to use FTP to upload specific files (not a full release) to an Azure Web App. Essentially I am using a PowerShell script to FTP files up to the web app in Azure. I can add new files, create files and folders but when I try to overwrite or delete a file, I get a 550 Access is denied.
I tried creating a a new deployment credential and was able to log in but the result was the same when trying to delete anything; 550 Access is Denied.
Is there any way to grant more permissions to this user or is this impossible? Thanks!
Check that you are not using the READ ONL FTP URL.
The publish profile gives two FTP url's the bottom on is ready only and will always give a 550 error.
550 Denied error, it indicates that you have no enough permission to do that.
You could download the Azure publish profile to get ftp user and password.
You also could follow this tutorial to get FTP information.
or
As zahid Faroq mentioned that you could use KUDU tool(https://{yoursite}.scm.azurewebsites.net) to do that easily. For more information about KUDU, please refer to this document
If you still can reproduce the issue, I recommand that you could create a support ticket to get help from Azure team.
You can't overwrite runnig app. Stop the app first, then upload, then start app again. You can stop/start the app from azure portal or using az cli
az webapp stop --name %AZURE_APP% --resource-group %AZURE_RESOURCE_GROUP%
and
az webapp start --name %AZURE_APP% --resource-group %AZURE_RESOURCE_GROUP%
p.s.: Funny thing is that you can delete running app. Then you still can't upload the running app even when it's already deleted.
I restarted the server, then I could delete/alter the app.
I can see the message using network capture tool Microsoft Message Analyzer. I can see the I receive Kerberos error "KDC_ERR_C_PRINCIPAL_UNKNOWN: Client not found in Kerberos database".
I can see all parts of the message, I have been searching online and tried a few things and did not work.
But in order to understand the problem, what does the "client" mean here?
- Is it the Server / Computer that is requesting
- Is it the Application that is requesting
The error is for KRB_TGS_REQ which means that its requesting for a token.
Would be great if anyone could help understand, which I believe can lead to a resolution.
Added more Details:
We have a SharePoint farm setup with SQL Reporting Services (SharePoint Integrated mode) and Excel Services. We have a datasource defined in Sharepoint which are used in SSRS Reports and Excel Reports. We use Windows Authentication from Sharepoint to SQL. When we test connection on Sharepoint datasource we get an error which says Cannot convert Windows token to Claims token. On opening the reports in SSRS we also receive error.
Strange part is that it works for some users which is why I'm not sure how to tackle this issue. If its SQL Server previlage issue, we have assigned sys admin role, this user also added as admin in SSRS. If AD or SPN issue it must not work for all users not for individual users.
I can see successful KRB_TGS_REQ for an admin user but fails for a normal user. No clue what to look for.
Kerberos Message :
KRB_TGS_ERROR, KDC_ERR_C_PRINCIPAL_UNKNOWN: Client not found in Kerberos database, Cname: nothing, Realm: SUB.DOMAIN.COM, Sname: SP_SVC_ACT
Does this mean that the delegation is not working?
My company is currently migrating our on prem Exchange users to the hosted Exchange Online platform. Migrating users is easy but we have hit a snag when on boarding new users. Our environment has multiple RDS servers. In the past we would setup a users mailbox on one server and when they would log in to another server the settings would follow them. That does not seem to be the case with Exchange Online. We are having to logon to each RDS server and manually set them up each time they logon to a new one(only for new users). If the user had an old on prem Exchange account that we migrated to the cloud then those settings get over-written and their Exchange Online account comes over no problem. Just trying to figure out a way that will setup the new user EOL accounts when they logon to the new servers. We are using Roaming profiles too if that helps. Maybe some sort of powershell script that I can modify with the new users names when I am setting them up?
Sounds like the AutoDiscovery isn´t working correctly. Please check with the Microsoft Remote Connection analyzer if you see any errors (e.g. as explained in KB 2404385). Here is by the way a good starting point how that should work.
I have setup SSO with Netsuite and Azure using the following instructions:
https://azure.microsoft.com/en-us/documentation/articles/active-directory-saas-netsuite-tutorial/.
The SSO works for users from Office 365 to NetSuite, however if a user clicks on a NetSuite link in an email they receive an invalid SAML protocol message from Azure during authentication.
For example:
Email Link is
"https:\system.netsuite.com/app/accounting/transactions/purchord.nl?id=167770&c={ACCOUNT_ID}"
Get redirected to (by NetSuite)
"https:\login.windows.net/9621cdc8-e1c4-4a3c-849e-35be6db5a45e/saml2"
which then redirects to :
"https:\login.microsoftonline.com/9621cdc8-e1c4-4a3c-849e-35be6db5a45e/saml2?RelayState=https%3A%2F%2Fsystem.netsuite.com%2Fapp%2Faccounting%2Ftransactions%2Fpurchord.nl%3Fid%3D167770%26c%3D{ACCOUNT_ID}"
which generates error:
Sign In
Sorry, but we’re having trouble signing you in.
We received a bad request.
Additional technical information:
Correlation ID: a8ceee9f-8507-4f55-aa56-e65266bf7d92
Timestamp: 2016-04-13 05:18:07Z
AADSTS75005: The request is not a valid Saml2 protocol message.
Does anyone have any ideas how to get further details on the error, or fix it?
I recently came across this issue and found a solution that works for me.
Try using the following format
https://account.activedirectory.windowsazure.com/applications/signin/{AZURE NETSUITE - APPLICATION_ID}?RelayState=https%3A%2F%2F{NetSuite_Account#}.app.netsuite.com%2Fapp%2Faccounting%2Ftransactions%2Fpurchord.nl%3Fid%3D{Purchae_Order_Record_ID}
I hope this helps.
Recently I faced this issue with Azure SSO, link does not work it fails # the SSO provider's(Azure) login URL. Issue is not with the Netsuite it is sending the request for authentication to Azure but Azure could not authenticate the user even though user is logged into the AD. You can resolve this issue by syncing Azure AD and source of authority. Also make sure your Azure SSo is setup correctly -by running zure Active Directory Module for Windows PowerShell as an admin.
Good luck