Showing results for 
Search instead for 
Did you mean: 

Error 43 backing up Exchange 2003

Level 3
This is a backup of exchange and I get an error "the client and server handshaking was not correct" Status Code 43...have any one of you ever seen this. I did an extensive search but I haven't come across this.

I get the following:
10/17/2006 9:29:24 PM - requesting resource SUG-1
10/17/2006 9:29:24 PM - requesting resource backup-03.NBU_CLIENT.MAXJOBS.exchange01
10/17/2006 9:29:24 PM - requesting resource backup-03.NBU_POLICY.MAXJOBS.WIN-Exchange
10/17/2006 9:29:25 PM - awaiting resource SUG-1 Reason: Storage unit concurrent jobs throttled., Media Server: backup-03, Robot Number: N/A, Robot Type: NONE, Media ID: N/A, Drive Name: N/A, Volume Pool: NetBackup, Storage Unit: BACKUP-to-DISK, Drive Scan Host: N/A
10/17/2006 9:29:26 PM - granted resource backup-03.NBU_CLIENT.MAXJOBS.exchange01
10/17/2006 9:29:26 PM - granted resource backup-03.NBU_POLICY.MAXJOBS.WIN-Exchange
10/17/2006 9:29:26 PM - granted resource BACKUP-to-DISK
10/17/2006 9:31:31 PM - started process bpdm (6884)
10/17/2006 9:31:32 PM - started process bpdm (7424)
10/17/2006 9:31:28 PM - started process bpbrm (8024)
10/17/2006 9:31:28 PM - connecting
10/17/2006 9:31:30 PM - connected; connect time: 00:00:02
10/17/2006 9:31:32 PM - begin writing
10/17/2006 9:33:07 PM - Error bpbrm(pid=8024) db_FLISTsend failed: unexpected message received (43)
10/17/2006 9:33:12 PM - end writing; write time: 00:01:40
unexpected message received(43)

Level 6
Partner Accredited Certified

Did it occur only once? Or everytime?
I guess some error happend on the connection between bpbrm and bpdbm.
First you should do is to enable debug logging.

Level 6

Networking error or hostnames dont jive, try that stuf below and post the logs.


Status Code: 43 Top

Message: unexpected message received

Explanation: The client and server handshaking was not correct.

Recommended Action:

1. Verify that the correct version of software is running on the client and the server.

2. Enable detailed activity logging:

o On the server, create a bpbrm activity log directory.

o On clients, create a bpcd activity log directory (created automatically on Macintosh clients).

o Increase the amount of debug information included in the logs as explained in the activity log topics in Chapter 3, "Using the Logs and Reports."

3. Retry the operation and examine the logs.

Note: If you are using bpstart_notify scripts on UNIX or Windows NT clients, verify that messages are not being written to stdout or stderr.

Status Code: 44

Level 3

I was able to figure out the solution. One of the messages that were posted on one of the public folders was corrupt. I deleted the corrupt message and my backups completed successfully.

Thank you all for your help.

Level 6
Thank you for following up your post.