Navigate
Wasp Helpdesk
  • Register

  • or
  • Login
    Need a password reminder?
or
Contact Us
  • Get in touch

    Send us an email

  • Start a chat session

  • Knowledgebase Read help articles
  • News News & updates
  • Contact Us We are here to help
  • Training View our options
  • Product Sunsets Non-Supported Products
Barcode System Consult
Barcode Printer Consult
Barcode Label Consult
  • Portal
  • Knowledgebase
  • Hardware
  • Mobile Computers
  • MobileAsset v7: Database transfer to mobile device fails at step 2 of 3; service log mentions FIPS
Subscribe Download PDF

MobileAsset v7: Database transfer to mobile device fails at step 2 of 3; service log mentions FIPS

Scott Leonard
2021-02-08
in Mobile Computers
MobileAsset v7: The mobile device can browse the service PC on port 10008 as expected, but when transferring database to device, the process gets to step 2 of 3, then fails.
 
The mobile device's MobileAsset.log file contains an error similar to:
 
2016-09-14 13:35:46.000 VERBOSE | IpSync Error(ErrorCode=0,ErrorCodeSpecified=False,ErrorDesc=Error downloading DevFile=\Program Files\MobileAsset\Database\MobileAssetDb_temp.sdf, SvcFile=C:\ProgramData\Wasp Barcode Technologies\MobileAssetWindowsService\7.0.0.0\App_Data\MobileAsset_86829e20 6aad483baa35a5c8a2dbfb86.sdf, SentByServiceMD5=C:\ProgramData\Wasp Barcode Technologies\MobileAssetWindowsService\7.0.0.0\App_Data\MobileAsset_86829e20 6aad483baa35a5c8a2dbfb86.sdf, RecvdOnDevMD5=,Source=,StackTrace=,LoggedInUser=1)
 
And on the PC running the Wasp MobileAsset Windows Service, the WaspMobileAssetServices.log file contains an error similar to the following (note the mention of FIPS):
 
2016-09-15 10:17:16.072          5 --------------- ERROR       | Error in RunCommand(): System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
                                    |    at System.Security.Cryptography.MD5CryptoServiceProvider..ctor()
                                    |    --- End of inner exception stack trace ---
                                    |    at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
                                    |    at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
                                    |    at System.Security.Cryptography.CryptoConfig.CreateFromName(String name, Object[] args)
                                    |    at System.Security.Cryptography.MD5.Create()
                                    |    at Wasp.WCFService.IPSync.WaspIPSyncService.GetMD5(String sFile)
                                    |    at Wasp.WCFService.IPSync.WaspIPSyncService.RunCommand(String sToken, IPSyncOperation op)

Cause

The service PC has FIPS enabled, which is incompatible with the MD5 used to validate the mobile database.

Resolution

FIPS will need to be disabled on the service PC in order for the mobile download to work.


HKLM\System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\Enabled. Change the value of this registry entry to 0 to disable it.

Rate the quality of this page

This page was helpful :) :( This page was not helpful

10 of 16 people found this page helpful


Quick Jump
  • Wasp Helpdesk
  • Knowledgebase
  • News
  • Contact Us
Top
Helpdesk software provided by Deskpro