Run-Time Error '52'

[SAPSTAR]

Hi,

I just wanted to mention that the Run-Time error '52' is still there. I'm currently working on a MultiNode tool for AQE, and so I had to work on shared folders instead of "local" folders.(Source Path : U: ; Working Dir: V:)
The problem is : regularly DVDRB stop with Run-Time Error '52', I just restart it....and it goes on. I dont change anything I just restart it...Something else, the encode is started, it's just that DVDRB does this error and die?!

@jdobbs: If you needed more info let me know.

[EDIT] I forgot to mention I'm using the version 1.10.5

[jdobbs]

Can you give me a specific set of circumstances that will repeat it? Unfortunately that error is the result of operations by the O/S. DVD-RB is simply trying to perform I/O.

Are you saying the shared folder is on another computer? Is it possibly being accessed by other software that might be locking it? That might explain it. DVD-RB always assumes it has its files to itself.

It also seems that it only happens with AQE... at least that's the only reports I've gotten. Does AQE open any of the Rebuilder created files for access?

One likely area is ITEM.ECL file. DVD-RB creates it, passes it to the encoder, and then deletes it after the encode. Is it possible that you may be leaving it open and the O/S tells DVD-RB it can't continue?

[SAPSTAR]

Can you give me a specific set of circumstances that will repeat it? Unfortunately that error is the result of operations by the O/S. DVD-RB is simply trying to perform I/O.

Are you saying the shared folder is on another computer? Is it possibly being accessed by other software that might be locking it? That might explain it. DVD-RB always assumes it has its files to itself.

It also seems that it only happens with AQE... at least that's the only reports I've gotten. Does AQE open any of the Rebuilder created files for access?

One likely area is ITEM.ECL file. DVD-RB creates it, passes it to the encoder, and then deletes it after the encode. Is it possible that you may be leaving it open and the O/S tells DVD-RB it can't continue?
In my case, all the folders were shared "locally"...I'll check if the ECL is left open in AQE. I'm currently running exactly the same encode with no sharing...to see if it could be related.....I'll let you know the results.

[SAPSTAR]

@jdobbs : Ok here are my results :
- I checked in AQE, no file is left open.
- I ran the same encode, with the same tool (MP_AQE : Massively Parallel AQE), but with my physical C: drive as working dir => It worked flawlessly.

Here is what I did which made an error :
I shared C:\DVDTemp (my usual working dir). I connected it and called it V:
I shared my DVD source, and connected it as U:

Then in DVDRB, I chose V:\ as being my working dir and U:\ as being my source drive.
Then I started the encode, but regularly it dies with a runtime error 52....I just have to restart it to make it work.

It's like if it was a question of timing...maybe on a slower drive, it takes longer to properly close all file descriptors?!
[EDIT]BTW, DVDRB dies but the encode is started ?! So it dies after having started the encode...
[EDIT2] Something else, I "reopen" stderr as I use it for my logs ?! Could it be related?!

[jdobbs]

I was planning on releasing v1.10.6 tomorrow, but I'll do some testing with your settings before I do. If I can get it to repeat at least I should be able to find what I/O is causing the error.

I can't imagine why a shared drive would make a difference -- except the fact that is is traversing the network abstract layering.

[jdobbs]

@SAPSTAR

I created two network shared folders and mapped drives to them. I mapped them to my source and my working directories. I gave read/write network access to both directories. I have since run two complete DVDs using those directories and have yet to have experienced a "Runtime Error 52".

I'm using DVD-RB v1.10.5 and AQE v0.33.0.7. The discs were "SEABISCUIT, R1, NTSC" and "ROME S1 D4, R1, NTSC".

Not sure what else I can try. I'm out of ideas...

How about I make a special test version for you that identifies specifically if the problem happens to the ITEM.ECL.

[SAPSTAR]

Not sure what else I can try. I'm out of ideas...

How about I make a special test version for you that identifies specifically if the problem happens to the ITEM.ECL.
It sounds good for me...but dont lose too much time because of this....I never had this issue before myself, I just had it once I started playing with the share drives?!
Thank you for your dedication to the community!!!