April 12, 2024

QuickFix: "Value cannot be null. Parameter name: proxy" in DIXF

Problem: After creating a new data entity and refreshing the entity list, the new entity doesn’t appear in DIXF data entity list. Interestingly, no errors are encountered when compiling the project. However, the following error message was received when trying to add the data entity in list manually. 

Value cannot be null. Parameter name: proxy




Possible Reason: While building your project or solution exclusively, your code may not exhibit any issues. However, inspect the output window messages in Visual Studio to identify any error messages originating from objects not included in your code.

Proposed Solution: Attempt to build the entire model and rectify any errors. Upon successful build, perform a database synchronization and try again. You should then be able to view new entities after refreshing or manually add them to the list.

-Harry Follow us on Facebook to keep in rhythm with us. https:fb.com/theaxapta

April 02, 2024

Issue while installing ExFlow ISV

Error:

Request for the permission of type 'System.Security.Permissions.FileIOPermission, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.
   at System.Security.CodeAccessSecurityEngine.Check(Object demand, StackCrawlMark& stackMark, Boolean isPermSet)
   at System.Security.CodeAccessPermission.Demand()
   at System.Security.Permissions.FileIOPermission.QuickDemand(FileIOPermissionAccess access, AccessControlActions control, String[] fullPathList, Boolean checkForDuplicates, Boolean needFullPath)
   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, Boolean checkHost)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize)
   at System.Xml.XmlDownloadManager.GetStream(Uri uri, ICredentials credentials, IWebProxy proxy, RequestCachePolicy cachePolicy)
   at System.Xml.XmlUrlResolver.GetEntity(Uri absoluteUri, String role, Type ofObjectToReturn)
   at System.Xml.XmlSecureResolver.GetEntity(Uri absoluteUri, String role, Type ofObjectToReturn)
   at System.Xml.XmlTextReaderImpl.FinishInitUriString()
   at System.Xml.XmlReaderSettings.CreateReader(String inputUri, XmlParserContext inputContext)
   at Microsoft.Dynamics.AX.AXUpdateInstallerBase.ServiceModelData.InitFromFile(String filePath)
   at Microsoft.Dynamics.AX.AXUpdateInstallerBase.AXUpdateInstallerBase.CreateQuickInstallRunbookGeneratorParameter(String updatePackageFilePath, String serviceModelFile)
   at Microsoft.Dynamics.AX.AXUpdateInstallerBase.AXUpdateInstallerBase.Install(String updatePackageFilePath, Boolean versionCheck, String serviceModelFile, Boolean parallel, Boolean devInstall, Parameters parameters)
   at Microsoft.Dynamics.AX.AXUpdateInstaller.Program.InstallUpdate(String[] args)
   at Microsoft.Dynamics.AX.AXUpdateInstaller.Program.Main(String[] args)

ExFlow installation CMD screen


Solution:
It’s crucial to ensure that the Package zip file is unblocked before extracting it. If it’s blocked, the AXUpdateInstaller won’t be able to access the files even after they are extracted.

To verify this, one can right-click on any file in the extracted package folder, go to Properties, and look for the Unblock checkbox. If it’s unchecked, it means the file is still blocked.

This is a valuable tip for anyone working with zip files and encountering issues with the AXUpdateInstaller.


ExFlow package folder property


Just before extracting the zip file, right-click on it > Properties and tick Unblock. and try again. 


-Harry Follow us on Facebook to keep in rhythm with us. https:fb.com/theaxapta