I've extensively searched the forums for an answer to this. I've been periodically getting sandbox related errors thrown for a CRM Plug-in we use. It seems like the plug-in process retries multiple times and then does finish but it errors out 6,7,8 times before it finally successfully executes. Can anyone help me with this? We have Dynamics CRM 2013 On Premise.
Error is below:
Sync workflow failed with error message - Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: The plug-in execution failed because no Sandbox Hosts are currently available. Please check that you have a Sandbox server configured and that it is running.
System.ServiceModel.EndpointNotFoundException: Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #8594C280Detail:
<OrganizationServiceFault xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/xrm/2011/Contracts">
<ErrorCode>-2147204722</ErrorCode>
<ErrorDetails xmlns:d2p1="http://schemas.datacontract.org/2004/07/System.Collections.Generic" />
<Message>The plug-in execution failed because no Sandbox Hosts are currently available. Please check that you have a Sandbox server configured and that it is running.
System.ServiceModel.EndpointNotFoundException: Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #8594C280</Message>
<Timestamp>2017-09-06T18:13:03.6732168Z</Timestamp>
<InnerFault>
<ErrorCode>-2147220970</ErrorCode>
<ErrorDetails xmlns:d3p1="http://schemas.datacontract.org/2004/07/System.Collections.Generic" />
<Message>System.IO.PipeException: Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #30BA0652</Message>
<Timestamp>2017-09-06T18:13:03.6732168Z</Timestamp>
<InnerFault i:nil="true" />
<TraceText i:nil="true" />
</InnerFault>
<TraceText>
[Mkto_Pack_Plugins: Mkto_Pack_Plugins.ProcessAssign]
[f248c719-a487-e111-98ea-005056810010: Mkto_Pack_Plugins.ProcessAssign: Assign of lead]
</TraceText>
</OrganizationServiceFault>
at System.Activities.WorkflowApplication.Invoke(Activity activity, IDictionary`2 inputs, WorkflowInstanceExtensionManager extensions, TimeSpan timeout)
at System.Activities.WorkflowInvoker.Invoke(Activity workflow, IDictionary`2 inputs, TimeSpan timeout, WorkflowInstanceExtensionManager extensions)
at Microsoft.Crm.Workflow.SynchronousRuntime.SynchronousWorkflowActivityHost.ExecuteWorkflowUsingInvoker(Activity workflow, ICommonWorkflowContext context)
at Microsoft.Crm.Workflow.SynchronousRuntime.SynchronousWorkflowActivityHost.StartWorkflow(WorkflowActivationData activationData, ICommonWorkflowContext context)
, error code - -2147204722
Related
I want to update my app to support the new requirements of Android API 33 (push notification permission request) but I am not able to get the token, or even get the OnNewToken() to fire.
I do have <uses-permission android:name="android.permission.POST_NOTIFICATIONS"/> in my manifest, I am requesting the permission and allowing it, but every time I try to initialize firebase, this is the error I get in the console:
E/FirebaseInstanceId(25547): Topic sync or token retrieval failed on hard failure exceptions: AUTHENTICATION_FAILED. Won't retry the operation.
This is how I'm requesting the permissions:
if (isNotificationsAllowed == Android.Content.PM.Permission.Denied)
{
CrossCurrentActivity.Current.Activity.RequestPermissions(new [ {"android.permission.POST_NOTIFICATIONS"}, 0);
FirebaseApp.InitializeApp(CrossCurrentActivity.Current.AppContext);
return;
}
This is how I'm trying to get the token:
var token = await FirebaseMessaging.Instance.GetToken();
return token.ToString();
On API 32 and lower, since there's no need to request the permission, the OnNewToken() gets fired and has no issue generating the FCM token.
Also I have to specify that I am trying on an Android Emulator that has Google Play Services (Same emulator with api 30 works just fine).
These are the relevant packages with their versions:
<PackageReference Include="Xamarin.Firebase.Messaging" Version="120.3.0"/>
<PackageReference Include="Xamarin.Forms" Version="4.8.0.1451" />
<PackageReference Include="Xamarin.GooglePlayServices.Base" Version="118.1.1"/>
<PackageReference Include="Xamarin.Google.Dagger" Version="2.27.0"/>
If anyone has any idea, it would be greatly appreciated!
Thanks!
Android 13 introduces a new runtime notification permission and here is the documentation on this : Notification runtime permission.
Althogh the FCM SDK (version 23.0.6 or higher) includes the POST_NOTIFICATIONS permission defined in the manifest (no downside to add it in Manifest), you also have to request the runtime permission from the user. For more info, you could refer to the official Firebase documentation which gives an example how to request permission: Request runtime notification permission on Android 13+.
Hope it works for you.
Well, seems like the solution, for me, was a bit underwhelming. I simply deleted the Emulator with API level 33 and created a new one. Things went smoothly.
I am developing azure bot using python sdk v4. From yesterday, this bot is giving below error when i opened personal teams chat with bot on browser
2022-04-12T11:42:47.992Z ConversationsServiceHelper: getChatConversation(): 28:a2146824-9e29-4eff-b4c2-ba6f24c7e235 not found
2022-04-12T11:42:48.123Z meetingCoachService retrieve meetingObjectsConfig failed (threadId 28:a2146824-9e29-4eff-b4c2-ba6f24c7e235, messageId undefined). Error message: Failed to retrieve flag from thread properties. Conversation not found.
After deploying a Word Add-in via centralised deployment, it doesn't show up in Word. We used this procedure to deploy the add-in and it lists it there succesfully.
Because we were worried it may be due to something wonky with our own plugin, we then decided to try to deploy the 'Contoso Citations' plugin which is used in the same procedure and screenshots here.
After capturing traffic whenever we press 'Update' under the Add-in Admin Managed dialog, we noticed a connection to Exchange. We then captured the traffic using a proxy and some root certificates, and we found the following call:
POST https://outlook.office365.com/ews/exchange.asmx
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<s:Header>
<RequestServerVersion Version="V2016_10_10" xmlns="http://schemas.microsoft.com/exchange/services/2006/types"/>
<MailboxCulture xmlns="http://schemas.microsoft.com/exchange/services/2006/types">en-US</MailboxCulture>
</s:Header>
<s:Body>
<GetPrivateCatalogAddIns xmlns="http://schemas.microsoft.com/exchange/services/2006/messages"><Client Code="Win32_Word" Version="16.0.0.0"/></GetPrivateCatalogAddIns>
</s:Body>
</s:Envelope>
Which seems to retrieve the catalog from Exchange. This for some reason seems to return a 500 with the following response:
<?xml version="1.0" encoding="utf-8"?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<s:Header>
<Action s:mustUnderstand="1" xmlns="http://schemas.microsoft.com/ws/2005/05/addressing/none">*</Action>
</s:Header>
<s:Body>
<s:Fault>
<faultcode xmlns:a="http://schemas.microsoft.com/exchange/services/2006/types">a:ErrorInternalServerError</faultcode>
<faultstring xml:lang="en-US">An internal server error occurred. The operation failed.</faultstring>
<detail>
<e:ResponseCode xmlns:e="http://schemas.microsoft.com/exchange/services/2006/errors">ErrorInternalServerError</e:ResponseCode>
<e:Message xmlns:e="http://schemas.microsoft.com/exchange/services/2006/errors">An internal server error occurred. The operation failed.</e:Message>
</detail>
</s:Fault>
</s:Body>
</s:Envelope>
However, no error dialog or so is shown. It just shows 'No add-ins currently available'. We are running different versions of Office 365 ProPlus (build 1704, 1703 and some others), but all seem to result in a 500 result code. We also have enabled OAuth authentication on our Exchange Mailboxes. Removing all our plugins from the Office 365 admin centre still results in 500's.
Does anybody know why Exchange may be throwing 500's at us, how we can work around this and still deploy the Add-in using the Office 365 Admin Centre?
Unfortunately, both deploying using SharePoint or Shared Folders is not a possibility and our Add-in shouldn't be deployed using the store.
can you delete the Add-In and re-add it? We had an issue earlier this week which is now resolved
While trying to register a bot in Microsoft Bot Framework, I am getting the following error message :
The remote server returned an error: (409) Conflict.
The messaging endpoint is of the form :
https://your_bots_hostname/api/messages
The bot is hosted in azure.
I got the same Error during the registration of a bot in Microsoft Bot Framework. Mostly the above error occurs whenever we are trying to create a new bot, in that registration we are specified the Existing Microsoft Application Id in the Microsoft Application Id field of bot registration form.
So, try to create new Microsoft Application with new name (like that the name would never use before) for your new bot then your issue resolve.
-Hope it will be help to you.
-Kishore
I have build a C# application using Exchange Web Services to read Outlook Contact data from Office 365. Until April 2013, this was working just fine. However, Office 365 has been updated. Now, when I query contact data I receive an Exception "The remote server returned an error: (403) Forbidden."
I read some info about SharePoint Online App authentication, but can't find any details on MSDN. Is anyone familiar with this?