[RESOLVED] XYcopy: Run-time error 5: invalid procedure call or argument

Things you’d like to miss in the future...
Forum rules
You might want to read this if you're looking for priority service

:info: Please Include The Following Information
1) Your XYplorer Version (e.g., v28.00.0801)
2) Your Windows Version (e.g., Win 11)
3) Your Screen Scaling Percentage (e.g., 125%).

:info: Use Your Profile Or Signature
We strongly recommend adding your Windows Version and Screen Scaling Percentage to the Location field in your Profile or to your Signature. That way, you only have to type them once, and we won't have to search for that vital information.

:info: How To Attach Images
When attaching an Image, please use the Attachment tab at the bottom of your post and click "Add files".
Post Reply
JLoftus
Posts: 600
Joined: 22 Jan 2014 14:58

[RESOLVED] XYcopy: Run-time error 5: invalid procedure call or argument

Post by JLoftus »

This just started happening today. I just updated to 22.60.0202 and it's still happening.

I searched the forum on this but did not find any references to this error with XYcopy:

Regardless of copy or move, and regardless of intra-volume or cross-volume, XYcopy is now throwing this error:

XYcopy: Run-time error 5: invalid procedure call or argument

If I disable XYcopy, the copy/move operations complete correctly.
Last edited by JLoftus on 30 Dec 2021 15:11, edited 1 time in total.

JLoftus
Posts: 600
Joined: 22 Jan 2014 14:58

Re: XYcopy: Run-time error 5: invalid procedure call or argument

Post by JLoftus »

I tested with Teracopy as the external handler and that's working fine (intra-volume, volume, copy, move). The runtime error 5 is only happening with XYcopy.

admin
Site Admin
Posts: 67235
Joined: 22 May 2004 16:48
Location: Win8.1, Win10, Win11, all @100%
Contact:

Re: XYcopy: Run-time error 5: invalid procedure call or argument

Post by admin »

XYcopy is handling the background operations. So you get no error if you untick Configuration | File Operations | File Operations | Background Processing | Enable background processing?

JLoftus
Posts: 600
Joined: 22 Jan 2014 14:58

Re: XYcopy: Run-time error 5: invalid procedure call or argument

Post by JLoftus »

Yes, thanks for the reply Don. If I untick background processing, I no longer get the runtime error 5.

I have always preferred to leave that option enabled, any idea why this would suddenly start happening?

Norn
Posts: 521
Joined: 24 Oct 2021 16:10

Re: XYcopy: Run-time error 5: invalid procedure call or argument

Post by Norn »

I only ticked these two.
To see the attached files, you need to log into the forum.
Windows 11 24H2 @100% 2560x1440

JLoftus
Posts: 600
Joined: 22 Jan 2014 14:58

Re: XYcopy: Run-time error 5: invalid procedure call or argument

Post by JLoftus »

I just tried with only those two options checked and [for me] a cross-volume move throws runtime error 5.

admin
Site Admin
Posts: 67235
Joined: 22 May 2004 16:48
Location: Win8.1, Win10, Win11, all @100%
Contact:

Re: XYcopy: Run-time error 5: invalid procedure call or argument

Post by admin »

Not here. Need more info:
- How many files?
- How do you move them?
- Show a screenshot of the error message.

JLoftus
Posts: 600
Joined: 22 Jan 2014 14:58

Re: XYcopy: Run-time error 5: invalid procedure call or argument

Post by JLoftus »

Doesn't matter whether it's copy or move, or whether to the same volume or a different one, I get the same runtime error 5 if background processing is checked.
If I uncheck background processing, then XYcopy works fine. If I use Teracopy, then the operation works fine as well.

It also doesn't matter whether the source or destination is local or a network location, same results.

EDIT: It also doesn't matter how many files are in the operation, 1 or a 100, and it doesn't matter whether I use the XY menu items to copy/move or whether I use CTRL+C/CTRL+V to copy, or CTRL+X/CTRL+V to move.

The first image shows a cross-volume copy failing, the second shows a cross volume move failing, and the third shows an intra-volume copy failing:
temp.png
To see the attached files, you need to log into the forum.

admin
Site Admin
Posts: 67235
Joined: 22 May 2004 16:48
Location: Win8.1, Win10, Win11, all @100%
Contact:

Re: XYcopy: Run-time error 5: invalid procedure call or argument

Post by admin »

And the copy or move does not happen?

JLoftus
Posts: 600
Joined: 22 Jan 2014 14:58

Re: XYcopy: Run-time error 5: invalid procedure call or argument

Post by JLoftus »

Correct, if I get the runtime error 5, the operation fails and no files are copied or moved.

admin
Site Admin
Posts: 67235
Joined: 22 May 2004 16:48
Location: Win8.1, Win10, Win11, all @100%
Contact:

Re: XYcopy: Run-time error 5: invalid procedure call or argument

Post by admin »

Can you reproduce it with a fresh; instance?

JLoftus
Posts: 600
Joined: 22 Jan 2014 14:58

Re: XYcopy: Run-time error 5: invalid procedure call or argument

Post by JLoftus »

Well, I didn't know about the FRESH; command, that's super handy.

Yes, I reproduced this with a FRESH; instance:
2021-12-29_11-58-25.jpg
To see the attached files, you need to log into the forum.

admin
Site Admin
Posts: 67235
Joined: 22 May 2004 16:48
Location: Win8.1, Win10, Win11, all @100%
Contact:

Re: XYcopy: Run-time error 5: invalid procedure call or argument

Post by admin »

Strange!

I see from your screenshots that you are using some 3rd party skin. Could that be the crucial factor?

JLoftus
Posts: 600
Joined: 22 Jan 2014 14:58

[RESOLVED] Re: XYcopy: Run-time error 5: invalid procedure call or argument

Post by JLoftus »

It's not a skin, it's Actual Window Manager, but, Don, you are a genius, that indeed is the problem! When I exit that program, XYcopy no longer throws the runtime error. I will report this bug to ActualTools.

Thank you!!

JLoftus
Posts: 600
Joined: 22 Jan 2014 14:58

Re: [RESOLVED] XYcopy: Run-time error 5: invalid procedure call or argument

Post by JLoftus »

The 22.60.0515 build fixes this issue with no changes to Actual Window Manager, so it looks like there may have been some conflict with XYcopy that has been resolved.

Post Reply