cancel
Showing results for 
Search instead for 
Did you mean: 

Error 25 SQL Error

inn_kam
Level 6
Partner Accredited

NB 7.5.0.4

WIN SERVER 2003 R2

SQL 2008 ON  operating system WIN 7 (sp1)

12/19/2013 12:10:42 AM - Info bpbrm(pid=7940) listening for client connection         
12/19/2013 12:10:48 AM - Info bpbrm(pid=7940) INF - Client read timeout = 1800      
12/19/2013 12:15:48 AM - Error bpbrm(pid=7940) listen for client protocol error - couldn't accept from data socket, An operation was attempted on something that is not a socket.  (10038)
1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Yes sql 2008 on win 7 sp1 , it is compaitable.

No. It is not. See Microsoft SQL Server - Supported Configurations in NetBackup 7 Application/Database Agent (CL):   http://http://www.symantec.com/docs/TECH126904  

bpclntcmd normally only tests name lookup, not connectivity - except for bpclntcmd -pn.
bpclntcmd -pn will test client -> master connectivity.
Please post output and master's bprd log.

See the rest of my post for troubleshooting - your client is unable to connect to bprd on the master. That is why the client cannot obtain license info.

View solution in original post

7 REPLIES 7

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

SQL 2008 ON  operating system WIN 7 (sp1)

Sure about the OS? I cannot imagine that this combination is supported...

Please post client's bpcd log.

Check that Windows Firewall is disabled on the client.

Test connectivity between client and master:

Ensure bprd log folder exists on the master. 
If you need to create it, restart NBU on master after creating the log.
Run 'bpclntcmd -pn' on the client.
Check bprd log on master server to if client's connection request was received.

Please post bprd log as well.

inn_kam
Level 6
Partner Accredited

Yes sql 2008 on win 7 sp1 , it is compaitable.

the connectivity is fine bpclntcmd working fine.

windows firewall off

connection is fine,

i think i see in db client log the error below

 

u can find this

21:01:26.350 [7280.5972] <16> bsa_checkFeatureId: Server exit status = 25: cannot connect on socket
21:01:26.350 [7280.5972] <16> VxBSAInit: ERR - The license for the requested feature is not available.
 
May be this is the problem
what this error means

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Yes sql 2008 on win 7 sp1 , it is compaitable.

No. It is not. See Microsoft SQL Server - Supported Configurations in NetBackup 7 Application/Database Agent (CL):   http://http://www.symantec.com/docs/TECH126904  

bpclntcmd normally only tests name lookup, not connectivity - except for bpclntcmd -pn.
bpclntcmd -pn will test client -> master connectivity.
Please post output and master's bprd log.

See the rest of my post for troubleshooting - your client is unable to connect to bprd on the master. That is why the client cannot obtain license info.

inn_kam
Level 6
Partner Accredited

Yes it is not supported

so if it is not compaitable . it will not work?

but when i ran manually it rans, but when it ran with other jobs it will fail.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

I cannot comment on whether SQL backups will work or not.

The point where this backup is failing is with initial comms between client and master server. It is not getting to the backup stage because comms is failing.

Please see my previous posts for steps to troubleshoot.

Once comms is working fine, you can perform backups and then restores to confirm that all is well.

Mark_Solutions
Level 6
Partner Accredited Certified

The log looks a little strange - it starts of not knowing the FQDN of the master but later says it is in the work queue of the short name of the master.

It is looking very  much like a DNS / resolution issue - as a test add the information to the hosts file on the Master:

ipaddress       CONTROLLER.YKK.COM.PK       CONTROLLER

Also set the NetBackup Legacy Network Service to run as the same account you are using for the NetBackup Client Service (both should be set as an account with dbadmin rights to all SQL databases)

If you have not set your accounts then that may be why a manual one works (using your credentials when it runs) but a scheduled one does not

inn_kam
Level 6
Partner Accredited

Thanks both above

i will upate tomorrow after trying all these steps.as its off time here