Unhandled Error - cleaner is unable to access the file path about clrvpin

[stojy]

hi @SteloPin, sorry to hear you're having issues.

The problem you're seeing is happening when the file is being renamed. Looking online, the most common cause appears to be either..

• Folder + file name exceeds Windows 255 char limit.
• Folder has a trailing space.

Neither of these should be an issue though if you're running a 'modern' windows OS as the .Net version used by ClrVpin automatically works around both of these limitations. I've tested both those scenarios on my Windows 10 box and it works fine. Perhaps you're running an older Windows OS which doesn't support long folder names? Or perhaps it's something unrelated (e.g. network drive, mapped folder, etc)?

In any event, it should be an easy fix (or at least display a warning dialog instead of an unhandled error). Can you please attach your log file (typically located here.. c:\ProgramData\ClrVpin\logs\ClrVpin.log) so I can be sure of the root cause.

Also, if there's any special instructions/repro steps be sure to add them to the issue description.

[stojy]

hi @SteloPin, just checking in to see if you wanted me to pursue this posible bug? I'll need the log file and (ideally) some steps to repro.

If not, I'll close out the issue.

[SteloPin]

Hi stoj, I‘m sorry but I have very little time to do more debugging. I have linked folders in my PinballX-Folders. That is maybe the problem. Thank you for your effort to develop the whole thing! Have a nice day, Stefan stoj ***@***.***> schrieb am Mi. 26. Apr. 2023 um 15:55:

…

hi @SteloPin <https://github.com/SteloPin>, just checking in to see if you wanted me to pursue this posible bug? I'll need the log file and (ideally) some steps to repro. If not, I'll close out the issue. — Reply to this email directly, view it on GitHub <#60 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARVK67EMEA4PTRFLHXVCND3XDESN5ANCNFSM6AAAAAAWWXM22A> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[stojy]

No worries @SteloPin. I've tried a few more things to get a repro without any success..

• setup a linked folder
• setup a network folder
• access network folder via mapped drive

Which makes me think the issue you've got is caused by an older OS (or an unusual linked folder configuraiton) that doesn't support long folder names.

However, I did manage to create a related issue where it fails to handle a network folder that is readonly. So I've added some special handling for that which perhaps might fix your issue too.

Going forward..

• Please update to 7.2.0 (or later) which includes the above fix.
• I'll close this issue out.
• If it happens again then let ClrVpin v7.2.0 submit a new bug as this will include the extra information needed.. i.e. last few clrvpin log entries and some basic system info.

Thanks

[SteloPin]

Thank you for your effort to make ClrVpin more stable in unusual konfigurations! I will try it out. Thanks, Stefan stoj ***@***.***> schrieb am So. 30. Apr. 2023 um 12:54:

…

No worries @SteloPin <https://github.com/SteloPin>. I've tried a few more things to get a repro without any success.. - setup a linked folder - setup a network folder - access network folder via mapped drive Which makes me think the issue you've got is caused by an older OS (or an unusual linked folder configuraiton) that doesn't support long folder names. However, I did manage to create a related issue where it fails to handle a network folder that is readonly. So I've added some special handling for that which *perhaps* might fix your issue too. Going forward.. - Please update to 7.2.0 (or later) which includes the above fix. - I'll close this issue out. - If it happens again then let ClrVpin v7.2.0 submit a new bug as this will include the extra information needed.. i.e. last few clrvpin log entries and some basic system info. Thanks — Reply to this email directly, view it on GitHub <#60 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARVK67HY6DQKYXGPV6WYBXDXDZAFNANCNFSM6AAAAAAWWXM22A> . You are receiving this because you were mentioned.Message ID: ***@***.***>