Service | Customer Service, Contact Center, Fie...

Field Service Sample Data installation

(3) Share

Report

Posted on by CU09040926-0

I am trying to install Field Service Demo Data(2017) but Package deployer is throwing error. I tried to use latest package deployer with package and dll given in above sample data folder but no luck. Have anyone went through for this issue?

PackageDeployment   Verbose   16   9/04/2025 7:00:40 PM Message: solution does not exist on server - solutionName = FieldServiceDemoData - targetEnviromentSolutionVersion = 0.0.0.0 - incomingSolutionVersion = 6.1.0.4
PackageDeployment   Error   2   9/04/2025 7:00:40 PM Message: Failed to load solution Field Service Demo Data with version 6.1.0.4. Message: Cab file required for importing solution with name FieldServiceDemoData and publisher name microsoftdynamics.
PackageDeployment   Information   8   9/04/2025 7:00:40 PM Message: Completed Processing Of Solution: Field Service Demo Data(FieldServiceDemoData), Version: 6.1.0.4, PackageVersion: 8.1, Duration: 00:00:02.560, Result: Error
PackageDeployment   Information   8   9/04/2025 7:00:40 PM Message: SOLUTION_STATS=SOL:FieldServiceDemoData|Result:Error|Operation:Import|IsUpgrade:False|OldVersion:|NewVersion:6.1.0.4|ImportType:Sync|RT:00:00:02.560|ST:00:00:02.560|DPT:00:00:00.000|WT:00:00:00.000|WTMB:00:00:00.000
PackageDeployment   Verbose   16   9/04/2025 7:00:40 PM Message: package deployment failure exception type : System.ServiceModel.FaultException`1[Microsoft.Xrm.Sdk.OrganizationServiceFault]
PackageDeployment   Error   2   9/04/2025 7:00:40 PM Message: ErrorCode: -2146863614
ErrorName: NotProvided
Message: Cab file required for importing solution with name FieldServiceDemoData and publisher name microsoftdynamics.
Type: ClientError
StatusCode: 400
Source: PackageDeployer
Date: 04/09/2025
Time: 9:0:41 AM
ActivityId: 8e3bfd90-4242-49a9-b394-51d5a32fe4a0
HelpLink: http://go.microsoft.com/fwlink/?LinkID=398563&error=Microsoft.Crm.CrmException:80097602&client=platform
TraceText: <Redacted>
PackageDeployment   Information   8   9/04/2025 7:00:40 PM Message: RaiseFailEvent - update progress with fail event
PackageDeployment   Information   8   9/04/2025 7:00:40 PM Message: ************** BEGIN Queuing UpdateRibbonClientMetadata Job *****************
PackageDeployment   Verbose   16   9/04/2025 7:00:40 PM Message: Updating PackageHistory entity record in UpdatePackageHistoryStatus. RecordId: 0f6e270e-2115-f011-998a-6045bdc24ba4 packageId 0f6e270e-2115-f011-998a-6045bdc24ba4 currentProgress.ItemText Beginning queueing up UpdateRibbonClientMetadata job. _coreData.PackageHistoryId 0f6e270e-2115-f011-998a-6045bdc24ba4
PackageDeployment   Verbose   16   9/04/2025 7:00:40 PM Message: UpdatePackageHistoryStatus processing. RecordId: 0f6e270e-2115-f011-998a-6045bdc24ba4 packageId 0f6e270e-2115-f011-998a-6045bdc24ba4 packagehistory.PackageId 00000000-0000-0000-0000-000000000000 message Beginning queueing up UpdateRibbonClientMetadata job.
PackageDeployment   Information   8   9/04/2025 7:00:41 PM Message: Trying to queue up UpdateRibbonClientMetadata Job.
PackageDeployment   Verbose   16   9/04/2025 7:00:41 PM Message: Updating PackageHistory entity record in UpdatePackageHistoryStatus. RecordId: 0f6e270e-2115-f011-998a-6045bdc24ba4 packageId 0f6e270e-2115-f011-998a-6045bdc24ba4 currentProgress.ItemText Successfully queued up UpdateRibbonClientMetadata request. _coreData.PackageHistoryId 0f6e270e-2115-f011-998a-6045bdc24ba4
PackageDeployment   Verbose   16   9/04/2025 7:00:41 PM Message: UpdatePackageHistoryStatus processing. RecordId: 0f6e270e-2115-f011-998a-6045bdc24ba4 packageId 0f6e270e-2115-f011-998a-6045bdc24ba4 packagehistory.PackageId 00000000-0000-0000-0000-000000000000 message Successfully queued up UpdateRibbonClientMetadata request.
PackageDeployment   Information   8   9/04/2025 7:00:42 PM Message: Time taken for queuing the ribbon job: 00:00:00.892
PackageDeployment   Information   8   9/04/2025 7:00:42 PM Message: ************** UpdateRibbonClientMetadata Job QUEUED *****************
PackageDeployment   Verbose   16   9/04/2025 7:00:42 PM Message: Checking PackageHistory entity record in Completion. foundPackageHistoryRecId: 0f6e270e-2115-f011-998a-6045bdc24ba4 packageId 0f6e270e-2115-f011-998a-6045bdc24ba4 _coreData.PackageHistoryId 0f6e270e-2115-f011-998a-6045bdc24ba4
PackageDeployment   Verbose   16   9/04/2025 7:00:42 PM Message: Updating PackageHistory entity record in finalStatus. RecordId: 0f6e270e-2115-f011-998a-6045bdc24ba4 packageId 0f6e270e-2115-f011-998a-6045bdc24ba4 message Failed to load solution Field Service Demo Data, version: 6.1.0.4. See the log file.
PackageDeployment   Verbose   16   9/04/2025 7:00:42 PM Message: UpdatePackageHistoryStatus processing. RecordId: 0f6e270e-2115-f011-998a-6045bdc24ba4 packageId 0f6e270e-2115-f011-998a-6045bdc24ba4 packagehistory.PackageId 00000000-0000-0000-0000-000000000000 message Failed to load solution Field Service Demo Data, version: 6.1.0.4. See the log file.
PackageDeployment   Information   8   9/04/2025 7:00:42 PM Message: ****** PACKAGE DEPLOYMENT PROCESS COMPLETED. Result:FAILED Duration:00:00:05.929 ******
PackageDeployment   Information   8   9/04/2025 7:00:42 PM Message: Status: Failed to load solution Field Service Demo Data, version: 6.1.0.4. See the log file.

Categories:

Dynamics 365 Field Service

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

Daivat Vartak (v-9d... 7,835 Super User 2025 Season 2 on at

Like (2)

Report
Hello CU09040926-0,

Yes, this is a known issue that many users have encountered when trying to install older demo data packages, especially for versions around Dynamics CRM 2016/2017, into more recent Power Platform environments.

The error message "Cab file required for importing solution with name FieldServiceDemoData and publisher name microsoftdynamics" is the key here. It indicates that the Package Deployer is looking for a .cab file associated with the solution within the package, but it's likely not structured that way in the older demo data packages.

Here's a breakdown of the problem and the solutions that have worked for others:

Why This Error Occurs:

Older Solution Format: The older demo data packages were often structured with individual .zip solution files and custom code/data files within the package itself, rather than relying on a .cab file for the core solution import.

Package Deployer Updates: Newer versions of the Package Deployer might have stricter expectations or a different process for handling solution imports within packages, especially when dealing with older solution formats.

Missing Solution in Environment: The initial log line "solution does not exist on server - solutionName = FieldServiceDemoData" suggests the Package Deployer is trying to find an existing solution with that name before importing, which would be the case during an upgrade scenario, but not a fresh demo data install.

Solutions That Have Worked for Others:

Extract and Import Solutions Manually: This is the most consistently reported solution.

Locate the Solution Files: Within the extracted contents of the Field Service Demo Data package (the folder you downloaded), look for .zip files that represent the individual solutions that make up the demo data. These files will likely have names related to Field Service, like msdyn_FieldService, msdyn_FSMasterData, etc.

Import Solutions Individually:

Go to your Power Platform environment's Solutions area.

Click Import.

Browse to and select each of the .zip solution files you found in the demo data package.

Follow the import wizard for each solution.

Run the Package Deployer (Custom Code Step Only): After importing all the individual solution files, run the Package Deployer again, but unselect the option to import solutions. You should only select the option to run the custom code within the package. The custom code is often responsible for creating the demo data records after the base solutions are in place.

Use an Older Version of Package Deployer (Less Recommended):

Some users have reported success using an older version of the Package Deployer tool that might have been more compatible with the structure of the older demo data packages.

Caution: Using older tools can sometimes lead to compatibility issues with newer Power Platform environments. This should be a last resort if the manual import of solutions doesn't work. You can typically find older versions of the XrmToolBox which often includes the Package Deployer.

Modify the Package Definition (Advanced):

This involves manually editing the XML configuration files within the demo data package to potentially align with the Package Deployer's current expectations. This is more complex and requires a good understanding of the Package Deployer structure. Look for files like PackageDeployment.xml or similar configuration files. You might need to adjust how the solutions are referenced for import.

Steps to Try (Recommended Order):

Extract and Manually Import Solutions:

Extract the contents of the FieldServiceDemoData.exe or the downloaded package file.

Look for .zip files in the extracted folders.

Import each .zip solution file into your Power Platform environment.

Run the Package Deployer again, deselecting the solution import step and only running the custom code.

If Step 1 Fails: Consider trying an older version of the Package Deployer tool (via XrmToolBox) as a last resort.

Important Considerations:

Environment Version: Ensure the demo data you are trying to install is reasonably compatible with the version of your Power Platform environment. While the core schema might be similar, significant version differences could lead to other issues. The "2017" demo data is quite old, so compatibility issues are more likely with the latest Power Platform versions.

Dependencies: Some demo data packages might have dependencies on other solutions. Ensure all necessary base solutions are present in your environment before attempting to install the demo data.

Log File: Review the full log file for more detailed error messages or clues about the specific files or steps that are failing.

By manually importing the solution files and then running the custom code from the Package Deployer, you bypass the part that's expecting the .cab file and directly install the necessary components. This has been the most successful approach for many users facing this issue with older demo data packages.

If my answer was helpful, please click Like, and if it solved your problem, please mark it as verified to help other community members find more. If you have further questions, please feel free to contact me.

My response was crafted with AI assistance and tailored to provide detailed and actionable guidance for your Microsoft Dynamics 365 query.

Regards,

Daivat Vartak

Was this reply helpful? Yes No
CU09040926-0 9 on at

Like (0)

Report

Hi Daivat,

Appreciate for your kind answer. However, the same issue occurred

Was this reply helpful? Yes No
Suggested answer

abhisc 32 on at

Like (1)

Report
Hello,

I encountered the same issue recently and wanted to share what worked for me.

After some investigation, I found that the problem was caused by importing the following two solutions:

FieldServiceDemoData_managed

FieldServiceDemoAutoMove_6_1_0_4

Since my main goal was to import the available sample data, I decided to skip these two solutions.

I modified the ImportConfig.xml file by commenting out the steps that import them and removed the corresponding solution files from the folder.

However, even after doing that, the data still wasn’t being imported.

To work around this, I created a Test Solution (Empty) in a different environment, exported its managed version, added the solution .zip file to the FS_PkgFolder, and updated the ImportConfig.xml accordingly.

This time, the TestSolution was imported successfully, and the sample data import process started as expected.

Hope this helps someone facing a similar issue!

Was this reply helpful? Yes No