Home > Cannot Create > Cannot Create Data Socket Error 0 0

Cannot Create Data Socket Error 0 0

Error bpbrm(pid=5736) cannot create data socket, The operation completed successfully. (0) The job then terminates with a status 21. Thank you both for the log commands, helped point me in the right direction, and find a work around until I get a solution in place. bptestbpcd -client and I get the correct output Any ideas? C:\>bperror -S 21 -r socket open failed A socket was not opened. Source

DNS for resolution of hostnames. I have tried running this bpgetconfig -g myclient and I get the correct output. Details Last Modified: Last Year Last Modified By: kmarsh Type: ERRMSG Rated 3 stars based on 32 votes. Restart the computer.

bpbrm process uses vnetd to initiate bpcd which forks new process (bpbkar) The bpbrm also provides the port number on which the bpbkar can respond to. Handy NetBackup Links 0 Kudos Reply Sorry what I meant was I had Eamonn Level 3 ‎06-01-2011 08:47 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Also have a look at the client's bpbkar log around the same time period. Options Print Article Export As PDF Find Similar CuteFTPSocket error = #0 Customer Support Software By InstantKB 2016-3 Final Execution: 0.000. 6 queries.

Please create bpcd log directory on client, then post output of the following commands: On client: bpclntcmd -self bpclntcmd -hn bpclntcmd -ip On media server: bpclntcmd -hn (use No Yes Did this article save you the trouble of contacting technical support? Any hints would be most helpfull. 0 Kudos Reply With Status 21 you need logs Marianne Moderator Partner Trusted Advisor Accredited Certified ‎10-12-2010 11:56 AM Options Mark as New Bookmark Subscribe For more information about editing the Windows Registry, refer to Knowledge Base article Q10411 - HOWTO: Windows Registry Settings.

So going by that article I'll needto identify the non-NetBackup process that is randomly connecting, as leaving the setting as Daemon port only is not a desired setup for us. Labels: 7.1.x and Earlier Backing Up Backup and Recovery Configuring Error messages Monitoring NetBackup Troubleshooting 1 Kudo Reply 1 Solution Accepted Solutions Accepted Solution! On the client side I have enabled logging of level 3. https://vox.veritas.com/t5/NetBackup/Problems-with-backup-cannot-connect-on-socket-25/td-p/397975 It is a good practice to back up (export a copy of) the registry before you make any changes to it.

To resolve this issue, you will need to edit the Windows Registry. I have also tried this. There isn't a seperate backup network. I do not recommend starting with level 5 logging (only when requested by Tech Support) - something between 1 and 3 should give good enough indication.

In the morning the backups will start fine. http://cannot.create.data.socket.error.0.0.winadvice.org/ Do the following, as appropriate: * Check the NetBackup Problems report for clues on where and why the failure occurred. Have tried the following: Rerun the jobs during the day (normally run at night) - Still fails Created a brand new policy (not copying the old one) - Also fails Telnet BPBRM_VERBOSE = 6 0 Kudos Reply Level 6?

I will post logs below. this contact form On a scale of 1-5, please rate the helpfulness of this article 1 2 3 4 5 Not Helpful Very Helpful Optionally provide private feedback to help us improve this article... If you cannot determine the cause from the Problems report, create debug log directories for the processes that returned this status code. I will post when I get the error again.

Special thanks to egaille from the CuteFTP user forum who shared this information from http://freeforum.avg.com/read.php?12,183533,backpage=3,sv.1! Article has been viewed 44K times. Go to Solution. have a peek here Socket error = #0 Last Year GlobalSCAPE 5 CuteFTP for Windows THE INFORMATION IN THIS ARTICLE APPLIES TO: CuteFTP® (all versions) SYMPTOM When trying to transfer files, an error appears: ERROR:>

Thank you for your feedback! Go to Solution Problems with backup, cannot connect on socket(25) Eamonn Level 3 ‎05-31-2011 02:28 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a As soon as I switch Daemon connection port back to default we go back to the job failing.


Logging levels can be changed through host properties of the GUI or you can put entires in the bp.conf file. Solved! Looking further however I can't find anything connecting on the ports being requested in the vnetd log, so again I'm left with a puzzle of why this is failing on the Thank You!

Go Social Bookmarks Delicious Digg Redit StumbleUpon Furl Yahoo Handy NetBackup Links 0 Kudos Reply My hint for you would be to Daryl_Kinnaird Level 4 ‎10-12-2010 11:57 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print No Yes Veritas.com Support Veritas Open Exchange Login or Join Communities Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Veritas.com Support Communities Check This Out SFTP connection fails when password not specified in CuteFTP Site Properties or Quick Connect bar Submit a Ticket to Support Can GlobalSCAPE products be exported from the United States? (ECCN and