Office Exchange user service account with valid o365 E3 license getting disabled and we are getting following error after every 3-4 weeks:
Error Message: An internal server error occurred. The operation failed., Mailbox 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' doesn't have a valid license.
are we missing any configuration settings, etc.
this is happening with valid o365 E3 license, when we create a new account it works as expected but after every 3-4 weeks getting this issue.
Related
I setup my Jasper Report Server. As well as I already schedule my reports and every things was working fine with me. During the setup, I was using my personal Gmail accounts to share the emails witch associated with gmail.smtp.com
I changed the SMTP setup to my domain account (Corporate Microsoft Exchange Server) but emails stopped working. I believe there is issue with the SMTP configuration.
Whenever I change the setup to my personal email, everything working fine but when I swap it to my domain account, which is corporate Microsoft Exchange server, it is not working. My domain account Microsoft outlook base, I believe there should not be any issue. Using same credential, I can access from the web.
I check following provided URL from Jasper Community and it seems I am following the same.
URL: https://community.jaspersoft.com/wiki/configuring-report-scheduler
What could be the issue?
Here is the error details, which I got:
Subject: The job failed to execute. Review its parameters.
Date: Today
Component: Report Scheduler
Message:
Job: Immediate Execution2323 (ID: 3889) Report unit: /reports/Paid_Violation_of_last_week_ Quartz Job: ReportJobs.job_3889 Quartz Trigger: ReportJobs.trigger_3886_0 Error Message: There was an error on the server. Try again or contact site administrators. (Error UID: 4d89f7cc-28cc-4d1d-86cb-cd0c764e1348).
I would appreciate if someone will share his/her experience if he/she face the same before.
code:5001
message:"An internal error has occurred."
name:"Internal Error"
I get this error when I call getAccessTokenAsync in my outlook addin. In desktop version I get a another error with code:13003. With the AttachemntDemo sample I get the same errors.
You are most likely using an on-premises Exchange Server with a local Domain Account.
From the documentation:
13003
User Type not supported. The user isn't signed into Office with a valid Microsoft Account or Work or School account. This may happen if Office runs with an on-premises domain account, for example. Your code should ask the user to sign in to Office.
Also confirm that your server meets these requirements:
If the user is connected to Office 365 or Outlook.com, mail server requirements are all taken care of already. However, for users connected to on-premises installations of Exchange Server, the following requirements apply.+
The server must be Exchange 2013 or later.
Exchange Web Services (EWS) must be enabled and must be exposed to the internet. Many add-ins require EWS to function properly.
The server must have a valid authentication certificate in order for the server to issue valid identity tokens. New installations of Exchange server include a default authentication certificate. For more information, see Digital certificates and encryption in Exchange 2016 and Set-AuthConfig.
In order to access add-ins from the Office Store, the client access servers must be able to communicate with https://store.office.com.
:
Try to inspect the network traffic and see the actual request - there is more information about the error as this function is just a wrapper around the network request and does not give enough information.
I was receiving the same error and when checked the network request - discovered that I have to add one more application as a Pre-authorized application.
Today I recieved a notificiation e mail from Google:
"This is a notification that your Google Play Publisher account has been terminated.
REASON FOR TERMINATION: Prior violations of the Developer Program Policies and Developer Distribution Agreement by this or associated accounts as outlined in previous emails sent to the registered email address(es) of the Publisher account(s).
Google Play Publisher suspensions are associated with developers, and may span multiple account registrations and related Google services.
You can visit the Developer Policy Center to better understand how we enforce Developer Program Policies. If you’ve reviewed the policy and feel this termination may have been in error, please reach out to our policy support team.
Do not attempt to register a new developer account. We will not be restoring your account at this time.
The Google Play Team"
1- I did not recieved any mails before this. There is no previous e mails.
2- I sent a mail to support about this.
3- What should I do now?
I am trying to configure two accounts in Microsoft outlook 2007 connected to the same exchange server/same domain. First account is configured associated with the user but when I try to configure the second account it is giving an error :
unable to connect to IMAP server.
Can anyone assist me to how to configure the same or it is supported by Microsoft outlook 2007.
IMAP accounts are supported in Outlook 2007. The error message indicates a connection problem with the server, or incorrect configuration values. You must also ensure that IMAP connections are supported on your Exchange server.
I've set up a forward mailbox in Dynamics CRM 2013 using the new server profile features and I an alert when performing the test and enable action. The error I am receiving is "The location of the mailbox [name] could not be determined while receiving email.".
The server profile is connected to an Office 365 and appears to be working fine for a user mailbox.
Has anyone else come across this problem?
The problem turned out to be with Office 365's auto discover.
Setting the Email Server Profiles incoming and outgoing address to https://outlook.office365.com/EWS/Exchange.asmx manually solved the problem.
I don't know if this was a local or remote issue.