I am trying to import the PRM portal solution into a RTM CRM 2011 on-premise installation -currently busy taking snapshots of my envronment so I can install update rollup 1.
I get the following error when the upload is completed:
ErrorCode: 0x80048425
ErrorText: The Form XML does not conform to the required schema.
A schema validation error has been detected at line 0, position 0.
Details: The 'ordinalvalue' attribute is not declared.
The account entity is customized and I have a couple of other managed solutions imported, an OData Query Designer as well as the Metadata Browser.
Any help or tips will be greatly appreciated.
Problem fixed by installing KB2461082 and updating CRM 2011 RC to CRM 2011 RTM
Related
I'm facing a very weard bug trying to export records from my Dyn365 Portal environment.
Anyone is getting the same error?
Error message:
RetrieveMultiple: GetEntityDataSearchParams |=> Failed to download a file entity [Annotation] with Id...
The specified blob does not exist...
Thank you all.
Ok, I found the issue.
Corrupt Note records was the culprit.
After remove all the records and create it again, i'm good to go...
im currently using MSCRM Toolkit for Dynamics 365 and wanted to export Audit reports.
When using the Audit Export Manager
On a CRM Online 2016 Update instance
While executing the "(Re) Load Source Structure" command
the following error message is received:
Error: Found a string attribute with unrecognized format.
How can i resolve the issue stated above so that i can load the entities, etc. to make audit export possible?
Here is the screenshot of the error, though we put the needed credentials still same error we still get.
Please help, we have presentation to come hope that professionals in Dynamics365 or those that have answers to my question can help
I came across this with MetadatDiagramConsole.exe as well when trying to pull from Dynamics365 online environment. I found changing RetrieveAsIfPublished to true worked.
Also the wonderful toolbox team has posted an updated version recently that worked for others trying the audit process you mention.
https://mscrmtoolkit.codeplex.com/releases/view/630624
I have upgraded MS CRM 2015 to 2016 and it is working fine. We are using XRMServiceToolkit(2.2) javascript library to fetch data from server.
The main problem is we are getting logical name in name attribute and logical name is blank, whereas earlier we use to get value of the field in name attribute and field name in logical name. Please refer the screenshot for better understanding.
Below is the screenshot from MS CRM 2016 :
Below is the screenshot from MS CRM 2015 :
I have searched online but couldn't find anything related to this. I tried making change in the library but it lands up into other errors. If I check the XML response from the server in 2015 :
<b:value i:type="a:EntityReference">
<a:Id>0698841a-e9cf-e511-9420-fcaa14b7a801</a:Id>
<a:LogicalName>ccs_category</a:LogicalName>
<a:Name>MORTGAGE</a:Name>
</b:value>
in 2016 :
<b:value i:type="a:EntityReference">
<a:Id>0698841a-e9cf-e511-9420-fcaa14b7a801</a:Id>
<a:KeyAttributes xmlns:c="http://schemas.microsoft.com/xrm/7.1/Contracts" />
<a:LogicalName>ccs_category</a:LogicalName>
<a:Name>ORGANIZATION</a:Name>
<a:RowVersion i:nil="true" />
</b:value>
I think this could be a reason for this problem but I don't know how to resolve it.
I hope you've solved this issue.
I will post the answer for everyone else who might be experiencing this issue.
As stated in the project description page, since Dynamics CRM 2015 Update 1, you should use the 2.2.1 version of the library.
This is the link to the download page: XrmServiceToolkit v2.2.1.
Also keep in mind this issue. I don't know if the publisher has already solved it.
Last but not least, you should keep in mind that from Dynamics CRM 2016, the OData endpoint has been deprecated (it still works but will stop working in future releases) and the supported way to query OData endpoint is through the Web API.
You can find a starting point to query CRM data here.
Cheers.
I am try to use the visual studio add-in "CRM 2011 Web Resource Linker/Publisher" from http://webresourcelinker.codeplex.com/.
When connecting to CRM 2013 Online, I get this error "Connection failed: There is an error in XML document(5, 5)"
I have checked Discovery Url, Username, Password, Unique Org Name.
Could you tell me what's wrong?
Thank you
I've found out how to resolve it, but still don't know the root cause. Here the steps:
Go to path: C:\Users\<current user>\LiveDeviceID
Delete the LiveDevice.xml
Try to connect from the application.
If this doesn’t solve the error, follow steps 1 and 2, reboot and try connecting from the application.
This should solve the problem.
Reference: http://skynetr.wordpress.com/2012/04/24/crm-2011-error-there-is-an-error-in-xml-document-5-5/
I have an organization that is deployed on an IFD CRM. My goal is to import that organization to new farm that has CRM 2011 with no IFD. Everything is ok while importing
but after import I cannot open that organization on new server. The error detail is:
Event code: 3007
Event message: A compilation error has occurred.
Event time: 27.12.2012 03:32:20
Event time (UTC): 27.12.2012 01:32:20
Event ID: 658277a3edea44089ca9af6e0c31f6c4
Event sequence: 236
Event occurrence: 5
Event detail code: 0
Exception message: c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\web.config(389):
error CS0234: The type or namespace name 'Linq' does not exist in the namespace 'System' (are you missing an assembly reference?)
After that error, I created new organizations and there is no problem with that new organization.
The CRM is with update rollup 8.
Turn on crm server side tracing. You'll get much better error information. Use the CRM diagnostic tool to turn on trace logging: http://crmdiagtool2011.codeplex.com.
I'm wondering if you have some plugin associated with the organization. So when you try to access it, the plugin fires and throws that exception.
You may have plugins in some of your solutions. It maybe configured to use the connections to your previous server. Hence, when you import it some error encountered. This is just a guess! If you provide more information on your error message, then could be analyze it better.