Question

Invalid volume path. [9044]

Laserfiche Version 10 Administration

Updated March 22, 2016

asked on March 22, 2016 • Show version history

Currently established volume path to volume fixed is E:\Laserfiche\GBHSLF\lf_Volumes. The volume name is Students.

Trying to add a District Volume with the same fixed path. Both have identical settings.

On OK getting this error Invalid volume path. [9044].

Actually tried copying the path from Students and that did not work either

All Laserfiche services are all set to Local System.

Details below:

Error Code: 9044
Error Message: Invalid volume path. [9044]

------------ Technical Details ------------

LFSO:
Call Stack: (Exception)
CLFVolume::Create
Additional Details:
HRESULT: 0xc0042354 (CLFVolume::Create, LFVolume.cpp:201)
(LFSO/10.0.0.865)
LFAdmin.dll (10.0.0.900):
Call Stack: (Current)
CCreateVolumeDialog::OnOK
Additional Details:
Exception: 0xc0042354 [9044] (Invalid volume path.) (CCreateVolumeDialog::OnOK at CreateVolumeDialog.cpp:546)
Call History:
CIndexNode::IndexNodeWndProc
CUserItem::UserItemWndProc
CIndexNode::IndexNodeWndProc
CComponent::Notify
CComponent::Notify
CComponent::Notify
CComponent::Notify
CCreateVolumeDialog::OnOK

0 0

Answer

APPROVED ANSWER

replied on March 22, 2016

Invalid Volume path error [9044] can have the following root causes:

- The account running the laserfiche server service has being set to use "Local System Account" which by default only has access to c local hard drive, ensure the account running the Laserfiche Server Service has the necessary access rights to access the volume path. In windows explorer check under folder's properties\security tab if the account in question has full control set (read/write and modify).

- the volume path does not contain a valid volume.id file. if for some reason the volume was moved from a different location and somehow the volume.id file is not present within the volume , then the volume path will be consider invalid. To create a new volume.id for the volume in question, refer to this link

- The volume path is recommended to use UNC notation can be found in this link

1 0

Replies

replied on March 22, 2016

A case has been opened with Support. We will update the thread with the results.

Thanks

0 0

replied on March 22, 2016

For posterity:

There was a combination of two issues. The first was that the server service account was LocalSystem and did not have rights to the non-local drive. The second was that originally, instead of the UNC name, the mapped drive letter path was given. Shule's post has more robust instruction and links.

0 0

You are not allowed to follow up in this post.

Question

Question

Invalid volume path. [9044]

Answer

Replies

Sign in to reply to this post.