Skip to main content
Solved

Deployment package : error writing files to storage (halfway)

  • August 27, 2024
  • 1 reply
  • 39 views

Forum|alt.badge.img

When making a deployment package, the process stops at writing files to storage.

For storage we are using a Azure blob container, since indicium is running on a app service in Azure

In the container the folders and files are created, but after some it stops with an error. And to make it a bit more strange, at 1 of 10 times it is working.

See the Indicium log for the error:

2024-08-26T07:18:46.6853191+00:00  [ERR] Process action "write_file" in process flow "system_flow_write_code_files_to_disk" in application 21 returned the following message: "The parameter 'Target file name' was provided with an invalid value 'Projectname\V0.991_ACC\Deploy\Install'. The target file name must have a file extension." (ec7db0a5)
2024-08-26T07:30:40.1251206+00:00  [ERR] The storage configuration "generated_scripts_location" took too long to respond and might be invalid. This can be because of permissions, connection issues or the path not existing. (1e7d4f16)
2024-08-26T07:30:40.1268799+00:00  [ERR] Process action "clean_folder" in process flow "system_flow_write_code_files_to_disk" in application 21 threw an exception. (dedd009e)
System.Exception: The file path '\generated-script\projectname2\RELEASE\Deploy\Install' is relative. The storage configuration 'generated_scripts_location' only allows absolute paths.
   at Indicium.FileStorage.Shared.UrlBasedFileStorageProvider`1.ValidateAndFinalizeURL(String input, Boolean allowPathsOutsideBase, Boolean useRelativePaths, Boolean preserveQuery) in C:\azp\agent\_work\1\s\src\FileStorage\Indicium.FileStorage.Shared\UrlBasedFileStorageProvider.cs:line 90
   at Indicium.FileStorage.Shared.UrlBasedFileStorageProvider`1.ValidateAndFinalizeURL(String input, Boolean allowPathsOutsideBase, Boolean useRelativePaths) in C:\azp\agent\_work\1\s\src\FileStorage\Indicium.FileStorage.Shared\UrlBasedFileStorageProvider.cs:line 61
   at Indicium.FileStorage.Azure.AzureFileStorageProvider.ValidateAndFinalizePath(String input, Boolean allowPathsOutsideBase, Boolean useRelativePaths) in C:\azp\agent\_work\1\s\src\FileStorage\Indicium.FileStorage.Azure\AzureFileStorageProvider.cs:line 109
   at Indicium.Shared.ProcessFlows.SystemActions.DeleteFolderFileStorageConnector.StartInternal(ReadOnlyDictionary`2 inputParameters) in C:\azp\agent\_work\1\s\src\Indicium.Shared\ProcessFlows\SystemActions\DeleteFolderFileStorageConnector.cs:line 100
   at Indicium.Shared.ProcessFlows.ActiveProcessAction.Start(ReadOnlyDictionary`2 variableState) in C:\azp\agent\_work\1\s\src\Indicium.Shared\ProcessFlows\ActiveProcessAction.cs:line 301
2024-08-26T07:31:03.4854244+00:00  [ERR] Process action "write_file" in process flow "system_flow_write_code_files_to_disk" in application 21 threw an exception. (dedd009e)

And the screenshot of the Azure container:
 

 

When execute the ‘synchronisation to iam’ with synchronize to storage. it works without any problems.

Has anybody encountered the same issue, or can anybody point me into the right direction?
 

Best answer by Bart Huizer

The error no longer appears, not sure why, but it seems to be solved.

View original
Did this topic help you find an answer to your question?
This topic has been closed for comments

1 reply

Forum|alt.badge.img
  • Author
  • Apprentice
  • 7 replies
  • Answer
  • September 9, 2024

The error no longer appears, not sure why, but it seems to be solved.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings