Forum Discussion

Mendes_Bruno's avatar
Mendes_Bruno
Level 3
8 years ago

Phase 2 import failed - status 40

Hi all,  I'm triyng to import an backup data created on a different backup server than the one that i'm trying to import the data. But I geting this error: 1/26/2017 10:15:39 AM - Error bpbrm(pid=2...
7.5
Windows Server (2003/2008)
  • mph999's avatar
    mph999
    8 years ago

     

    Just a wild idea, but ….

    Where are you running this import from ???

    EG. RDP session to server from your laptop ...

    1/23/2017 4:24:30 PM - positioned DIF768; position time: 00:00:00

    1/23/2017 4:24:30 PM - begin reading

    1/23/2017 4:31:00 PM - Error bpbrm(pid=26856) could not write BPBRM_READ_FILENAME message to stderr: An existing connection was forcibly closed by the remote host.  (10054)

    1/23/2017 4:31:00 PM - Error bpbrm(pid=26856) could not write EXIT STATUS to OUTSOCK      

    1/23/2017 4:31:00 PM - Info tar32(pid=28944) done. status: 40: network connection broken       

    client process aborted(50)

     

    It's starts around 10.xx in the morning and runs happily all day ....  4.30pm could be 'going home time' - so you logoff, expecting the job to continue running ... where as Windows will have other ideas and will kill off any processes spawned during the RDP session (eg. the import) ....  

    ? 

mph999's avatar
mph999
Level 6

 

Just a wild idea, but ….

Where are you running this import from ???

EG. RDP session to server from your laptop ...

1/23/2017 4:24:30 PM - positioned DIF768; position time: 00:00:00

1/23/2017 4:24:30 PM - begin reading

1/23/2017 4:31:00 PM - Error bpbrm(pid=26856) could not write BPBRM_READ_FILENAME message to stderr: An existing connection was forcibly closed by the remote host.  (10054)

1/23/2017 4:31:00 PM - Error bpbrm(pid=26856) could not write EXIT STATUS to OUTSOCK      

1/23/2017 4:31:00 PM - Info tar32(pid=28944) done. status: 40: network connection broken       

client process aborted(50)

 

It's starts around 10.xx in the morning and runs happily all day ....  4.30pm could be 'going home time' - so you logoff, expecting the job to continue running ... where as Windows will have other ideas and will kill off any processes spawned during the RDP session (eg. the import) ....  

? 

Mendes_Bruno's avatar
Mendes_Bruno
Level 3
8 years ago

Hi mph999,

Yes I saw something regarding run import from RDP and now I'm performing a test using the console direct. Let's see if works beucause is taking long time due to the quantity of data to import.

But the error already happened when I was logged on server.

Anyway thanks for your coment!