You are viewing limited content. For full access, please sign in.

Question

Question

Creating volume in Azure Storage File Share

Installation and Upgrades Laserfiche
Updated January 13, 2022
asked on January 11, 2022

Hi everyone,

 

Has anyone experience in creating volume in Azure Storage File Share?

The file share is mapped on a drive on a local server. 

I've tried using the drive and UNC when creating the volume but I got 

Error Message: Invalid volume path. [9044]

 

Wondering whether it is possible?

 

Thanks in advance.

0 0

Replies

replied on January 12, 2022

Hi Mohd,

Laserfiche repositories support hosting volumes on Azure Files. 

I would first check if the Azure Files share/mapped drive is visible and accessible to the service account running Laserfiche Server (by default Local System). If it's only mapped for the logged in user, Laserfiche Server may be unable to see or access the share.

Hope that helps.

-Sam

0 0
View 2 previous replies
replied on January 12, 2022

Hi Sam,

 

Appreciate your response.

I can access the Azure File and can also create, modify, delete inside the shared folder. 

I also tried change LF server service account to local admin (the one I use to access the Azure File)  however still getting the same error.

 

Is there any white paper or documentation on this for me to refer?

 

 

0 0
replied on January 12, 2022

Could you please check the Laserfiche Server event log, find the matching event message, and post the entire stack trace here?

0 0
replied on January 12, 2022 • Show version history

Here's the error I'm getting in the Event Viewer everytime I tried to create the volume.

 

A volume file I/O error occurred. Repository="Training"; File type=D; Volume ID=30; Store ID=0x0; File name="\\test.file.core.windows.net\lffilesharetest\Azuretest"; Operation=mkdir; Error=The specified path is invalid.

0 0
replied on January 13, 2022

As a workaround, can you map the Azure path to a drive letter? It would have to be done in the profile of the service account.

0 0
replied on January 13, 2022

Hi Pieter, 

Yes, already tried to map to a drive.

 

Just found workaround to this, hope it could help others as well.

The issue was with the UNC is that it is an alias and it doesn't want to work for some reason.

 

Did the nslookup on the UNC (test.file.core.windows.net) will reveal the "Global DNS" which then replace the initial UNC (the front  part).

Able to create volume now however not too sure if this is ideal.

 

Thanks.

 

2 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...