Blog

Get up to date and stay in the know

I was recently attempting to add a Wait step to the beginning of a workflow.    When I tried to add the Wait step CRM would throw the error “Unexpected Error An error has occurred”. The expanded error when you Download log file is Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=7.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: Unable to find metadata information for attribute !Process_Custom_Attribute_URL_Detail: <OrganizationServiceFault xmlns:i=”http://www.w3.org/2001/XMLSchema-instance” xmlns=”http://schemas.microsoft.com/xrm/2011/Contracts”&gt; <ErrorCode>-2147220970</ErrorCode> <ErrorDetails xmlns:d2p1=”http://schemas.datacontract.org/2004/07/System.Collections.Generic” /> <Message>Unable to find metadata information for attribute !Process_Custom_Attribute_URL_</Message> <Timestamp>2015-02-23T15:38:17.4397312Z</Timestamp> <InnerFault...

Read More

We recently upgraded to CRM 2015 On Premise and decided to enable a default SLA.    As soon as we enabled the SLA, we couldn’t resolve any cases.  Every time we would get the error “This case has already been resolved. Close and reopen the case record to see the updates.” The log file would show: Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=7.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: This case has already been resolved. Close...

Read More

So today I had to look into why our newly activated SLA was causing our Case Resolutions to fail.   During this troubleshooting I came across some lessons learn that might be helpful to others. Lesson 1 When you activate a SLA it creates a workflow of the same name (in our case Atrio SLA) and a workflow per SLA Item.  However you cannot see the workflow using...

Read More

Error: Access Denied 404 Scenario: A user changes his or her name in AD then when the username is updated in CRM it does not allow them to login under the new username. Access Denied Error or 404 Cause: This issue occurs when a user signs in via ADFS, the sign-in information may be cached on the Active Directory Federation Services (AD FS) server, or the UPN may no...

Read More
})(jQuery)