CRM 2011 - Error while importing organization RRS feed

  • Question

  • Hi all,

    Client is currently in the process of refreshing their pre-prod environments with latest prod data. For this purpose, they exported the CRM organization database from production, imported the database into the pre-prod environment and then imported the organization.

    The organization import was successful, but the logs had the below error.

    Is this a problem ? Has anyone faced such an issue before ?

    CRM version is 2011 and UR 11

    11:52:20|  Error| Applying database updates to organization with name = {Organization Name} Id={Organization GUID} failed with Exception:

    System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IO.FileNotFoundException: Could not find file 'D:\Program Files\Microsoft CRM\Tools\[target_revision]'.

       at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

       at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath)

      at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)

       at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access)

       at Microsoft.Crm.Setup.MetadataPatchDiffSet.InflateFromFile(String filePathAndName, Guid organizationId, Int32 lcid, Boolean runInTestMode)

       at Microsoft.Crm.Setup.MetadataPatchService.ProcessMetadataDiffFile(String metadataPatchDiffFullPath, Int32 lcid, ExecutionContext context)

       at Microsoft.Crm.Setup.MetadataPatchService.ProcessMetadataDiffFile(String metadataPatchDiffFullPath)

       --- End of inner exception stack trace ---

       at System.RuntimeMethodHandle._InvokeMethodFast(IRuntimeMethodInfo method, Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeType typeOwner)

       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)

       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)

       at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)

       at Microsoft.Crm.Setup.Database.DllMethodAction.Execute()

       at Microsoft.Crm.Setup.Database.DatabaseInstaller.ExecuteReleases(ReleaseInfo releaseInfo, Boolean isInstall)

       at Microsoft.Crm.Setup.Database.DatabaseInstaller.Install(Int32 languageCode, String configurationFilePath, Boolean upgradeDatabase, Boolean isInstall)

       at Microsoft.Crm.Setup.Database.DatabaseInstaller.InstallUpdate(Int32 languageCode, String configurationFilePath, Boolean upgradeDatabase)

       at Microsoft.Crm.Setup.Common.Update.DBUpdateDatabaseInstaller.ApplyDBUpdatesInternal(Guid orgId, String releaseFilePath, Boolean throwOnError)

       at Microsoft.Crm.Tools.Admin.InstallDatabaseUpdatesAction.ApplyDBUpdatesInternal(Guid orgId, String orgUniqueName, String releaseFilePath, Boolean ignoreErrors)


    Tuesday, June 2, 2015 6:29 AM

All replies

  • The error relates to apply updates to the database after import. This shouldn't be a problem (and may be a benefit, as it will mean the organisation database will retain the same version as that in production).

    It's worth checking why an upgrade is attempted. The 2 possible reasons are:

    • The production environment is on a earlier update rollup version than pre-prod
    • The environments are the same version, but the source organisation database hadn't been updated to match the environment

    Neither of those are fundamental problems, but it may be worth updating the production environment / organisation database for consistency across environments, then re-exporting the database

    Microsoft CRM MVP - http://mscrmuk.blogspot.com/ http://www.excitation.co.uk

    Tuesday, June 2, 2015 8:07 AM