Volume Consistency Checker input string was not in a correct format

asked on August 4, 2016

Trying to run Volume Consistency Checker 8.0.0.3 on LF 9 repository and it is giving me an error = Input string was not in a correct format.

From the run log of the utility I see this:

DefaultSource   Information   0   ValidatePage(1, E:\GABC-VOLU\, ImageFiles, False)
DefaultSource   Information   0   Calculating storeidend based on the volume paths
DefaultSource   Information   0   Hex storeidend = SubscribrLogsSubscriberLogsGABCIIS0100
DefaultSource   Information   0   Attempted to get integer from the hex string: SubscribrLogsSubscriberLogsGABCIIS0100
DefaultSource   Information   0   System.FormatException: Input string was not in a correct format.
at VolCon8.Main.GetIntegerFromHexString(String str)
at VolCon8.Form1.ValidatePages(Int32 volid, String volpath, ValidateType type, Boolean IgnoreNonLF)
at VolCon8.Form1.ValidateVolume()

0 0

SELECTED ANSWER

replied on August 4, 2016

The utility assumes the subfolders are all strings of hex digits and doesn't expect that you'd have files that didn't initially come from a Laserfiche volume. Do you have a path in there for \SubscribrLogs\SubscriberLogs\GABC\IIS\01\00 or similar (maybe with different breakdown)?

0 0

View 1 previous reply

replied on August 5, 2016

The Image Path, Text Path and EDocument Path were loaded into the dialog box with E:\GABC-VOLU.

I changed them all to E:\GABC-VOLU\00 and it is chugging away now.

Thanks for the clue about the folder names.

I was one too high in the hierarchy and under that folder were the Audit folder, Logs, Search, etc. as well as the 00 folder.

0 0

replied on August 5, 2016

Addendum - I looked at the report and it was showing every image as missing so I checked the path and it had two slashes in the path so I re-ran with:

E:\GABC-VOLU\00

(no trailing slash)

0 0

replied on August 5, 2016

Still no joy. It runs but it reports all images and texts in error because the path is wrong.

That is to say, if the image is in E:\GABC-VOLU\00\0A\0A it will report it as missing because it is looking in E:\GABC-VOLU\00\00\0A\0A.

Our folder structure at the highest level is this:

Directory of E:\GABC-VOLU

07/13/2016 02:40 PM <DIR> 00
08/05/2016 11:39 AM <DIR> AUDIT
02/10/2012 05:39 PM <DIR> e00
10/22/2014 04:59 PM <DIR> LOGS
08/05/2016 11:29 AM <DIR> SEARCH
11/25/2013 05:02 PM <DIR> SEARCH8
08/02/2016 05:02 PM <DIR> TEMP
07/28/2016 04:13 PM <DIR> WF

The error I am getting, Attempted to get integer from the hex string: SubscribrLogsSubscriberLogsGABCIIS0100, looks to me like it has gone into the WF folder -

Directory of E:\GABC-VOLU\WF\SubscriberLogs\GABCIIS01

08/05/2016 10:36 AM <DIR> 73e31147-6085-41ee-a78c-2a97beb43645

0 0

replied on August 5, 2016

It looks like your volume was misconfigured and ended up in the repository root (ie, the repository root is set to E:\GABC-VOLU and the volume is also set to E:\GABC-VOLU). This is not a problem for the LF Server, but the utility does not expect that. It looks like the Workflow volume was also put into the repository location (the "WF" folder where the SubscriberLogs are residing).

Probably the easiest thing to do now would be to separate things out first, then re-run the Volume Consistency Checker.

1. Run through the WF Server configuration wizard and move the WF volume to a location outside of the E:\GABC-VOLU folder. This will move all the file in the "WF" folder out. (Caveat: this is a guess based on the screenshot, it's possible that your WF volume is already in a different location and this is just a manual copy of its files somebody made.)

2. Create a new volume into its own folder (something like E:\GABC-VOLU\MyNewVolume) and migrate all documents in the repository to it.

3. Run the consistency checker on the new volume.

If any of this sounds complicated, have your reseller open a case with Tech Support and they'll help you sort it out.

1 0

Question

Question

Volume Consistency Checker input string was not in a correct format

Answer

Replies

Sign in to reply to this post.