View Full Version : run-time error '52'
jollyrogr
6th March 2008, 20:24
Since installing 1.27.2 pro I've been unable to complete an encode. The latest instance everything seemed to be going fine, it was well into the encode step when I got a "Run-time error '52': Bad file name or number". When I click ok, the program closes.
rebuilder.log doesn't show anything.
setarip_old
6th March 2008, 22:35
What is the Title and Region number of the original DVD?
jollyrogr
6th March 2008, 22:48
I restarted, and this time it failed with "Run-time error '5': Invalid procedure call or argument"
The dvd is saw3, region 1.
setarip_old
6th March 2008, 23:21
Try re-ripping the DVD using either RipIt4Me, DVD95CopyPro, or DVDFabHDDecrypter...
jdobbs
6th March 2008, 23:58
When you see goofy errors like that it is almost always a bad rip. DVD-RB tries to adjust for bad rips... but there are just too many things that could go wrong to cover all of them.
jollyrogr
7th March 2008, 06:04
Ok, I'll give it a shot. Thanks
jollyrogr
7th March 2008, 20:05
Ok re-ripping hasn't worked. I even ran the rip through dvdshrink (which processed it just fine) and then ran dvdrb on shrink's output, and it still fails.
Next thing I'm gonna try is reverting back to an older version of dvdrb and see if that works.
setarip_old
7th March 2008, 20:17
Ok re-ripping hasn't worked. I even ran the rip through dvdshrink (which processed it just fine) and then ran dvdrb on shrink's outputWhat did you use to re-rip the DVD?
2) Did you try using that rip DIRECTLY in DVDRB, without first running it through DVD Shrink?
jdobbs
7th March 2008, 23:36
If it's the NTSC/R1 version send me your REBUILDER.INI file (with the settings used at the time of the attempt), and I'll try running that disc. Send to: dvd-rb@dvd-rb.com
jollyrogr
8th March 2008, 00:04
email sent
jollyrogr
8th March 2008, 06:42
Update: I have tried encoding a different movie, and am seeing the same errors. I uninstalled and reinstalled dvd-rb, still errors. I have noticed sometimes a message appears saying "Failed to find and run encoder. The path may be incorrect. Aborted."
This is odd since CCE is installed and the path is defined. The encoder will even sometimes run through a few vts segments before giving me that message.
I'm going to revert to 1.266 now and see what happens.
jollyrogr
8th March 2008, 09:49
Another update: I uninstalled 1.27.2 and went back to 1.26.6 and guess what, it works perfectly. Same source (rip), same settings, same encoder. It appears to me something broke in the new version.
jdobbs
8th March 2008, 10:38
But only for you? That seems a little unlikely. I'd say it is more likely that it was the reinstallation.
jollyrogr
8th March 2008, 10:44
1.27.2 wouldn't work even though I uninstalled and reinstalled multiple times.
jdobbs
8th March 2008, 10:50
We'll see what happens when I do SAW 3 later today. It could be a bug that only pops up when that title is run.
jollyrogr
8th March 2008, 11:00
If you aren't seeing problems with other titles, I'm not sure you'll see a problem with saw3. I tried Last of the Mohicans just for the heck of it and was getting the same type of failures.
What are some things I can do to try and isolate what's causing this? I'm gonna keep pluggin and trying things to see if I can get it to work or find out what's causing the failures.
jdobbs
8th March 2008, 20:27
Runtime Error 52 is a report indicating that a call to the O/S returned with "Bad filename" -- so that may be a place to start.
jollyrogr
15th March 2008, 11:18
I still am unable to get 1.27.2 to work at all. I was unsure if maybe there was a conflict with another process running on my machine, so I stopped all but the necessary processes, to no avail. I have tried other movies, still getting the run time 52.
It does not seem to be encoder related.
Running dvdrb in full backup mode, the runtime 52 error showed up during the prepare phase.
FYI, my machine is a dual athlon xp 1700+, 1gb ram, running windows 2003 server, service pack 2.
jdobbs
15th March 2008, 11:41
Sorry about that, I completely forgot about this one. I'll pick it up and run it today using your INI.
jollyrogr
15th March 2008, 12:44
jdobbs, it doesn't seem to matter which movie, I can't get 1.27.2 to run any movie without crashing. If you have any specific questions, don't hesitate to ask. I'm completely baffled why this would happen. All previous versions have worked great.
jdobbs
15th March 2008, 18:47
Give me a specific group of actions that you take and when (exactly) the error occurs.
jollyrogr
15th March 2008, 21:19
Here goes:
Normally I would use one-click mode, but since I've been experiencing these problems I've been using the 3 click method. It would always make it through the Prepare phase fine and then fail during the encode, so using 3 click would save me from having to run through the prepare every time.
To make sure the issue wasn't movie or rip related, I've tried other movies. Once while attempting a movie in full backup mode I experienced the run-time 52 (hereafter referred to as RT52) during the prepare phase. I retried the prepare and was able to make it through. Then it failed (RT52) during encode.
So then I'll retry the encode again, and then click 'No' on the resume so it starts from the beginning. Typically what happens is the encoder will run through a few segments, then some time during the encode of the 2nd, 3rd, 4th, or 5th segment (it appears to be random) rebuilder.exe will stop responding (according to task manager) and then when the encoder finishes it's segment the RT52 will pop up. Sometimes the RT52 pops up immediately, and sometimes there is a long period where rebuilder.exe is 'not responding' before the RT52 shows up, at which point rebuilder.exe is shown to be running fine. I think this may be a function of exactly what time rebuilder.exe stops responding, whether it's just after the encoder starts the segment, or towards the end of the encoder's 2nd pass. When rebuilder.exe is 'not responding' the cpu usage for rebuilder.exe is very high. It drops off when the RT52 message appears.
Bottom line: I have yet to be able to complete an encode with 1.27.2. If I go back to 1.26.6, it will work perfectly without error. To me, this narrows it down to something that changed in rebuilder between versions.
From your point of view I can see where this is extremely odd, if you aren't receiving complaints from others about the same issue. I wonder if it somehow isn't related to the fact that I'm running windows 2003 server? As I'm sure the majority of people out there are on XP or vista.
Thanks for listening.
jdobbs
16th March 2008, 01:14
What kind of drive are you using? The "bad filename or number" normally comes up when you have lost access to a file -- for example when it is dismounted during execution. Is this a USB-2 mounted drive? I have gotten a report of someone who got a "Runtime Error 52" -- but only on a USB mounted drive. I chalked it up to a flaky controller. The other possibility is privileges -- since you're using the server version. Does the REBUILDER.EXE file have administrative privileges when it runs (not sure how you set it in Server 2003).
The only reports I've gotten of "Runtime Error 5" is when attempting to run DVD-RB on a system that is configured for an Asian language. In that case the system has to be configured a specific way.
jollyrogr
16th March 2008, 01:47
I'm using a PATA Seagate 320 gig drive. Previous versions of rebuilder work using the same source files on the same drive.
I'm logged in as an administrator, so yes rebuilder.exe has admin privs.
EDIT: Ok you got me thinking...I have that same HD mounted from my linux machine also....I unmounted the drive and am trying again.
Hmm. Nope that wasn't it. She froze up during the encode of segment 3. :(
jdobbs
16th March 2008, 04:45
You aren't running VMWARE are you?
jollyrogr
17th March 2008, 07:08
You aren't running VMWARE are you?
Nope. 2 diff machines.
kreigle
28th April 2008, 16:25
Has this issue been resolved yet?
I am also having this problem in Windows 2003. I am currently running v1.26 fine, but I cannot run any of the 1.27.xx versions due to this 'error 52'.
1.27 will do the prepare phase, then when encoding it will only process 2 to 4 segments and then throw the error 52. When I close and restart DVDRB, I can restart the encode where it stopped and it will again process 2-4 segments and throw another error 52. I tried processing the disk this way, but after 3 days I started installing older packages until I found one that worked. I have since processed 4 DVDs with 1.26 with no further problems.
I posted on http://dvd-rb.dvd2go.org/modules.php?name=Forums detailing my problem before I found this thread. I can't get the exact post link right now because my work is blocking that forum, but the post date is about 1 week ago.
blutach
28th April 2008, 17:14
This is it - http://dvd-rb.dvd2go.org/modules.php?name=Forums&file=viewtopic&t=1439
Regards
vBulletin® v3.8.5, Copyright ©2000-2012, Jelsoft Enterprises Ltd.